CDCAS3.

User Manual
V2.0.5

北京永新視博數字電視技術有限公司
Beijing Novel-Super Digital TV Technology Co., LTD
Statement
All Rights Reserved. Beijing Novel-Super Digital TV Technology Co., Ltd reserves all rights.
Without the written permission of the Company, any unit or individual shall not make unauthorized excerpts, copy the
contents of this document in part or in full, or disseminate in any form.

Trademark Statement
And other Novel SuperTV trademarks all belong to Beijing Novel-Super Digital TV Technology Co., Ltd.
All other trademarks or registered trademarks referred in this document belong to their respective owners.

ATTN
Due to product version upgrades or other reasons, this document will be updated from time to time. Unless otherwise
agreed, this document is still used as a guide. All statements, information and advice in this document do not constitute
any expressed or implied guarantee or constitute a contract invitation or invitation. The text is still used for reference,
and NovelSuperTV enjoys the ultimate right to interpret the text.
 Table of Contents

1 Introduction................................................................................................................ 1

1.1 Document Purpose .................................................................................................................. 1

1.2 Terminology Explanation ....................................................................................................... 1
2 Overview ..................................................................................................................... 2
2.1 CDCAS Introduction .............................................................................................................. 2
2.2 Operating Environment ......................................................................................................... 2
2.2.1 Database Server ...................................................................................................................... 2
2.2.2 Application Server .................................................................................................................. 2
3 System Operating Monitor .................................................................................... 3
3.1 Functions of Head-End Modules ........................................................................................... 4
3.2 Stop, Start, restart and Delete Module .................................................................................. 5
3.3 Console Menu .......................................................................................................................... 6
4 Head-End Configuration ....................................................................................... 10
4.1 Activating Console ................................................................................................................ 10
4.2 Login Console ........................................................................................................................ 11
4.3 System Configuration ........................................................................................................... 12
4.4 Option Configuration ........................................................................................................... 13
4.4.1 Theme Setting ....................................................................................................................... 13
4.4.2 Icons Configuration .............................................................................................................. 14
4.4.3 Module Display Setting ........................................................................................................ 15
4.5 Area Configuration ............................................................................................................... 16
4.6 Add Module Group ............................................................................................................... 17
4.7 Log Level Setting................................................................................................................... 20
4.8 Encryptor Configuration...................................................................................................... 20
4.9 EMMG Configuration .......................................................................................................... 21
4.10 EMML Configuration ......................................................................................................... 22
4.11 EMMS Configuration ......................................................................................................... 26
4.12 ECMG Configuration ......................................................................................................... 29
4.13 RouterAdapter Configuration ........................................................................................... 32
4.14 Web Configuration.............................................................................................................. 34
4.15 SNMPAgent Configuration (Optional) ............................................................................. 35
4.16 Module State after Configuration...................................................................................... 37
4.17 Delete Module Group.......................................................................................................... 37
4.18 Rename Module Group ...................................................................................................... 38
4.19 Enable Operator customization ......................................................................................... 38
4.20 Enable Emergency Mode ................................................................................................... 38
4.21 Enable Group Authorization（Optional） ...................................................................... 39
4.22 User Accounts ...................................................................................................................... 41

III
 4.23 User Roles ............................................................................................................................ 42
4.24 Parameters Setting .............................................................................................................. 45
4.25 User Info .............................................................................................................................. 46
4.26 User Logs ............................................................................................................................. 47
4.27 Audit (Optional) .................................................................................................................. 51
5 Query and Maintenance ....................................................................................... 52
5.1 SMS Command Query ......................................................................................................... 52
5.2 Module Status ........................................................................................................................ 53
5.2.1 Performance Status............................................................................................................... 53
5.2.2 Working Status...................................................................................................................... 53
5.2.3 Log Display............................................................................................................................ 55
5.3 Exporting Logs ...................................................................................................................... 58
5.4 Exporting SMS Commands ................................................................................................. 59
5.5 Exporting Configuration ...................................................................................................... 60
5.6 Calculator .............................................................................................................................. 61
6 Introduction to Web ............................................................................................... 62
6.1 Uploading Card-issuing File ................................................................................................ 62
6.2 Uploading Patch File............................................................................................................. 64
7 Configuration Examples ....................................................................................... 66
7.1 Load Balance ......................................................................................................................... 66
7.2 Active-Standby Mode ............................................................................................................ 66
7.3 Dynamic IP Mode.................................................................................................................. 67
8 Appendix ................................................................................................................... 69
8.1 Template ................................................................................................................................. 69
8.1.1 Instant Container Template ................................................................................................. 69
8.1.2 Fixed Container Templates .................................................................................................. 70
8.1.3 FilterMode ............................................................................................................................. 71
8.1.4 Functions ............................................................................................................................... 72
8.2 Operator Authority Management........................................................................................ 72

II
 1 Introduction

1.1 Document Purpose

This document provides information for users and system administrators. It describes the usage of CDCAS3.0 in details,
and provides a reference and guide for users and system administrators.

1.2 Terminology Explanation

Abbreviation Explanation
BOSS Business & Operation Support System

CAS Conditional Access System

CDCAS NSTV Conditional Access System

MUX Multiplexer

SCS Simulcrypt Synchronizer

Table 1.2-1 CDCAS3.0 user manual terminology explanation

I
 2 Overview

2.1 CDCAS Introduction

CDCAS3.0 is a conditional access system provided by Novel-SuperTV, which offers a platform for cable
operators to guarantee the security of programs and enable the flexibility of subscriber management. It is the
key to personalized service. The basic function is to authorize users’ entitlement, control, and management in
the television system, thus realizing the payment service of the broadcasting system.

The CDCAS3.0 can achieve unified management, entitlement, and controlling the television business. From a
technical point of view, the system integrates a variety of advanced technologies including scheduling system
management, network technology and digital encoding, scrambling technology, encryption and decryption
technology, multiplexer technology, modulation and demodulation technology, set-top box technology, and
smart card technology. It is related to user management, program management, database management, charge
management, and other database application technologies.
The CDCAS3.0 head-end system includes ECMG, EMMG, EMML, EMMS, Web, Task, RouterAdapter, Agent,
BoradCast, Logger, Encryptor, DB and Console.

2.2 Operating Environment

2.2.1 Database Server
OS: Windows 2008 R2 (64bit) standard edition/ Windows 2012 (64bit) standard edition.
DB: Oracle 11g R2 (64bit) database server/MariaDB 10.0.17(64bit).

2.2.2 Application Server

OS: Windows 2008 R2 (64bit) standard edition/ Windows 2012 (64bit) standard edition.
DB: Oracle 11g R2 (64bit) database server/MariaDB 10.0.17(64bit).

2
 3 System Operating Monitor
Console is an interface between the CDCAS3.0 system and user. It’s used to configure and monitor each module of the
system, check logs, and SMS commands as shown below:

Fig. 3-1 Console Main Window

◆ Module view located on the left side of the console is a tree view. Each node is a module group containing its
modules.
◆ The topology chart is on the right side. It shows the running status of the modules. (Green: running; Grey:
stopped; Red: alert)
◆ In the chart, the black lines represent the inner connections among modules, and the blue lines represent the
connections between the modules and the outside environment.
◆ A module information window is located on the bottom right of the window. It shows the details of the module
upon mouse-over in the topology chart.

3
CDCAS3.0 User Manual V2.0.1 3 System Operating Monitor

3.1 Functions of Head-End Modules

Modules Functions

Responsible for broadcasting the configuration

BroadCast
information of all the modules

DB Database

Responsible for encrypt EMM packets and ECM

Encryptor
packets.

Responsible for sending EMM packets. Upon

receiving EMM packets from EMML, EMMS
EMMS
will send them to MUX according to the
specified sending strategies.

Responsible for extracting EMM packets from

EMML DB, and sending them to EMMS in accordance
with the specified sending strategies.

The transportation module which responsible for

Web uploading scheduler files, card-issuing files and
patch files.

RouterAdapter Responsible for handling SMS commands.

Responsible for broadcasting local host IP (138

Agent
segment) and task management.

ECMG Entitlement Control Message Generator.

EMMG Entitlement Management Message Generator.

Responsible for renew host key and group

Task
entitlement scheduling.

4
 CDCAS3.0 User Manual V2.0.0 3 System Operating Monitor

Logger Responsible for writing logs into database.

3.2 Stop, Start, restart and Delete Module

Select the module under the module group on the left side of the console, right-click to select Start Module,
Stop Module, Restart Module or Delete Module as shown in Fig. 3-2.

Fig. 3-2 Delete Module

While an Encryptor is in use, DB, Agent, BroadCast, Logger and Task cannot be deleted
After starting, stopping, restarting or deleting the module, the module icons in the topology chart will be
displayed in different colors as shown in Fig. 3-3.

5
CDCAS3.0 User Manual V2.0.1 3 System Operating Monitor

Fig. 3-3 Console Main Window

◆ While starting, the module icon in the module view will show as: starting → started

◆ After starting, the module icon in the topology chart will show as: (Started)

◆ While stopping, the module icon in the module view will show as: stopping → stopped

◆ After stopping, the module icon in the topology chart will show as: (Stopped)

◆ While restarting (during restarting procedure), the module icon in the topology chart will show as:

→ → →

◆ If the module is stopped and then restarted, the module icon in the topology chart will show as: →

◆ When errors occur, the icon’s color in the module view will show as:

◆ When alerts occur, the module icon turns red in the topology chart, shows as:

3.3 Console Menu

1) The drop-down menu under System is shown in Fig. 3-4:

6
CDCAS3.0 User Manual V2.0.0 3 System Operating Monitor

Fig. 3-4 System Menu

a) Login - Refer to “4.2Login Console”.

b) Logout - Logout the user account.

c) Options - Refer to “4.4Option Configuration”.

d) Exit - Close the Console.

2) The drop-down menu under Windows is shown in Fig. 3-5:

Fig. 3-5 Windows Menu

a) New Window - Create a new window.

b) Cascade, Tile Horizontally and Tile Vertically are three ways to display windows.

c) Close All - Close all of the windows.

d) Window - The current windows in use.

3) The drop-down menu under Tools is shown in Fig. 3-6 (Refer to “5Query and Maintenance”)

7
CDCAS3.0 User Manual V2.0.1 3 System Operating Monitor

Fig. 3-6 Tool Menu

4) The drop-down menu under Advanced is shown in Fig. 3-7(refer to 4.3,4.5,4.19 , 4.20,4.27):

Fig. 3-7 Advanced Menu

5) User Management Menu is shown as Fig. 3-8 (For more information , refer to 4.22 ~ 4.26)

Fig. 3-8 User Management Menu

6) The Help menu is shown in Fig. 3-9:

8
CDCAS3.0 User Manual V2.0.0 3 System Operating Monitor

Fig. 3-9 Help Menu

a) Click on Language to switch between English, Chinese (Simplified) and Chinese (Traditional).
b) Click on Serial Number, the serial number window will be shown as in Fig. 3-10, you can enter a serial
number here or update the existing serial number with a new one.

Fig. 3-10 Serial Number

c) Click on About Console, a pop-up window will be shown as in Fig. 3-11:

Fig. 3-11 About CDCAS Console window

9
CDCAS3.0 User Manual V2.0.1 3 System Operating Monitor

4 Head-End Configuration
Use the CDCAS3.0 installation tool to complete CDCAS installation, and configure the system through the Console.
1、Configuration order:
The serial number is configured before other modules, and then configured ECMG, EMMG modules.
2、Log level configuration:
The system provides six kinds of log levels: Trace, Debug, Info, Warn, Error and Fatal (from lowest to
highest level), the system will display the log with a level higher than or equal to the selected one, Trace is
the lowest level, while Fatal is the highest, default level is Info.
-------------------------------------------------------------------------------------------------------------------------
Note:
For using the database installation tool to complete CDCAS3.0 database installation, please see CDCAS3.0
Installation Manual for more details. CDCAS3.0 only supports version 5.3 of the scheduler files.
-------------------------------------------------------------------------------------------------------------------------

4.1 Activating Console

After installing CAS programs, the initial activate console window will require to input serial number,

as shown in Fig. 4-1.

10
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

Fig. 4-1 Console Activation Window

After entering a correct serial number, the initial window is as shown in Fig. 4-2:

Fig. 4-2 Console Activation Window

4.2 Login Console

After activating the Console, select System→Login. In the pop-up login window, user needs to enter

11
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

correct user name and password, then clicks “login”. Only after passing the verification, user could
operate and edit the Console.

Fig. 4-3 Login Window

When login failed, the pop-up window will show the prompt message

Fig. 4-4 Login failed

The Console will display the corresponding interface according to logged-on user permission when
login succeed.
About user information please refer to “8.2Operator Authority Management”.

4.3 System Configuration

System configuration is used to view operator ID, and configuration operator name.

Select Advanced→System Configuration, as shown in Fig. 4-5:

Fig. 4-5 System Configuration Window

12
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

Pop up system configuration dialog as shown in Fig. 4-6:

Fig. 4-6 System Configuration Dialog

※ Operator ID: Display operator ID contained by current serial number, for viewing only.

※ Operator Name: Enter operator name according to the actual requirements.

※ Open Group Entitle: Check” Open Group Entitle” to enable group authorization, there will be a

prompt show that this operation is irreversible. In the Dispatch period option, user could define the

dispatch period of group authorization.

※ Local Log Path: the location to save local logs (valid for current machine only).

※ CASID Configuration: Configure the SuperCASID.

4.4 Option Configuration

4.4.1 Theme Setting
Select System→Options in the Console menu bar, as shown in Fig. 4-7:

13
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

Fig. 4-7 Option Menu

Pop up the Option dialog as shown in Fig. 4-8:

Fig. 4-8 Option Dialog

In the option dialog, click on Themes, and then select Blue, Silver, or Green. After clicking on the OK
button, the Console will display according to the selected theme.

4.4.2 Icons Configuration

In the option dialog, select the Icon menu to set icon size, as shown in Fig. 4-9:

14
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

Fig. 4-9 Option Dialog

4.4.3 Module Display Setting

In system module area of the option dialog, you can choose whether to display system module, as

shown in Fig. 4-10:

Fig. 4-10 Option Dialog

15
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

This setting decides whether to display Agent, BroadCast, Logger, Task module.

4.5 Area Configuration

Configure areas of sending EMM packets. Only after configuring the areas, it is allowed to select areas
from the area list when configuring containers through EMML, and when configuring scramblers
through EMMS.

Select Advanced→Area configuration, as shown in Fig. 4-11:

Fig. 4-11 Area Configuration

Area Configuration dialog is as shown in Fig. 4-12:

Fig. 4-12 Area Configuration Dialog

Enter area name in the Area text box, and click on the Add button to add it into the area list, as shown

in Fig. 4-13:

16
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

Fig. 4-13 Area Configuration Dialog

After adding, the area name will be shown in the area list, as shown in Fig. 4-14:

Fig. 4-14 Area Configuration Dialog

Select one area from the area list, and click on the Delete button to delete it.

Click on the Exit button to exit the dialog.

4.6 Add Module Group

After enabling management successfully, adding the module groups is the first step of the CDCAS3.0

configuration. Right-click on the CDCAS3.0 root node to select New Group, as shown in Fig. 4-15:

17
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

Fig. 4-15 Console Main Window

Select the group type to add from the Module Group Type drop-down menu, as shown in Fig.

4-16:

Fig. 4-16 New Module Group Dialog

The Module Group Name is optional, as shown in Fig. 4-17:

Fig. 4-17 New Module Group Dialog

The module group name will be the same as Module Group Type if Module Group Name is blank.

Click on the OK button to add the module group on the left side, as shown in Fig. 4-18:

18
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

Fig. 4-18 Agent Configuration Window

The following module groups should be configured: EMMG, ECMG, EMML, EMMS, RouterAdapter,
Web and Encryptor. Add the module groups listed in Module Group Type.

-----------------------------------------------------------------------------------------------------------------------------

Notes:

1、For Encryptor, EMML, only one module group is allowed in the system.

2、For RouterAdapter, EMMS, ECMG, EMMG, and Web, multiple module groups are allowed in the

system. The group name should be unique.

3、DB, Broadcast, Agent, Task and Logger, cannot be configured manually, as the system will add

them automatically.

4、 All of the configurations have default parameters, which are recommended.

-----------------------------------------------------------------------------------------------------------------------------

Button functions of configurations as below:

Add - click on the Add button to add the edited information to the list.

Modify - select the item from the list, then click on the Modify button to update it in the list.

Delete - select the item from the list, then click on the Delete button to delete it from the list.

Edit - click on the Edit button to configure the parameters.

Save - click on the Save button to save the current information.

Resume - click on the Resume button to return system to the previous state of saving.

19
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

4.7 Log Level Setting

In order to analyze problems timely and effectively when a failure occurs, system modules will record

their own operating logs in real-time, the logs will stored in a database for later inquiry.

The system provides six kinds of log levels from lowest to highest levels as follows:

Trace: The details information about programs running.

Debug: Record program running state information about data stream transferring, distribution, etc.

Info: Record run-time event information, such as module starting, module stopping, etc.

Warn: Warning messages, the program in potentially dangerous.

Error: An error occurred when the program is running, it may cause the program not to run properly.

Fatal: A fatal error will cause the interrupt routine, once this error occurs, the program does not working

properly.

The default log level for each module is Info, the log level for each service can be configured according

to the operational requirements.

4.8 Encryptor Configuration

After adding Encryptor group, Encryptor modules need to be added.

Right-click on Encryptor group, then select New Module from the drop-down menu, as shown in Fig.

4-19:

Fig. 4-19 New Encryptor Module

（1） In the pop-up dialog, enter Server ID the same as the last segment of the encryptor IP. For
example: if the encryptor IP is 138.138.138.80, enter “80” in the text box, as shown in Fig. 4-20:

20
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

Fig. 4-20 New Module Dialog

After Server ID is configured and ensuring that the Encryptor running under normal status, the

module under Encryptor can be started. The icon is as shown in operating status:

Note: The last segment of IP address must be entered in the server ID dialog during creation of new

module.

4.9 EMMG Configuration

After adding EMMG group, EMMG modules need to be added.

Right-click on EMMG group, then select New Module from the drop-down menu, as shown in Fig.

4-21:

Fig. 4-21 New EMMG Module

In the pop-up dialog, enter Server ID the same as the last segment of the server IP.

For example: if the IP is 138.138.138.12, enter “12” in the text box, as shown in Fig. 4-22:

21
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

Fig. 4-22 New Module Dialog

Configure the EMMG parameters, as shown in Fig. 4-23:

Fig. 4-23 EMMG Configuration Window

Click on the Edit button to configure the following information:

Log Level - according to user’s needs, configure EMMG log Level. (Refer to “4.7 Log Level Setting”)

Encryptor ID - the last segment of the encryptor IP, for example: if the encryptor IP is 138.138.138.16,

check “Encryptor16” checkbox. (The premise is that encryptor group and “16” module have been

created).

4.10 EMML Configuration

Containers are divided into the following types:

◆ Instant Container: The EMM data can be sent out only once at the highest priority. EMML is

responsible for creating or destroying the instant containers.

◆ Fixed Container: The EMM data can be sent out in compliance with the sending strategy.

According to the time strategy, the data packets can be changed dynamically. EMML is responsible for

creating and destroying the fixed containers.

◆ Temporary Container: The EMM data can be sent out in compliance with the specified sending

22
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

duration or sending times. The temporary containers are destroyed automatically after sending the data

packets based on the sending strategy.

-----------------------------------------------------------------------------------------------------------------------------

Note:

EMML must configure Instant Container, currently all of containers are transmitted by region, and

there is no default configuration.

-----------------------------------------------------------------------------------------------------------------------------

After adding EMML group, the following dialog will appear if “maximum number of fixed container”

is 0, when adding EMML modules.

Fig. 4-24 Add EMML module Dialog

Click on the Edit button on the right side of parameters edit page, “Number of fixed container” will be

automatically configured as default number 8, click “Save”.

Right-click on EMML group, select New Module from the drop-down menu, as shown in Fig. 4-25:

Fig. 4-25 New EMML Module

（1） In the pop-up dialog, enter Server ID the same as the last segment of the server IP.

For example: if the IP is 138.138.138.12, enter “12” in the text box, as shown in Fig. 4-26:

Fig. 4-26 New Module Dialog

23
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

Configure EMML parameters. Click on the Edit button to configure the following information, as

shown in Fig. 4-27:

Fig. 4-27 EMML Configuration Window

Configure EMML Log Level according to user’s needs. (Refer to “4.7 Log Level Setting”). Operations

users can do are as follows:

Add Container: After configuring a new container, click on the Add button to add it to the list.

Modify Container: Select one container from the list, modify its parameters, and click on the Modify

button to update the edited information in the list.

Delete Container: Select one container from the list, and click on the Delete button to delete it from the

list. (Stop sending data packets before deleting a container).

24
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

Parameter Container Type Description

Container ID is the unique identifier of

one data container, users configure EMM

Instant Container sending strategy according to specific

application environment, this strategy is
Container ID Fixed Container
defined as EMM container in system.
Temporary Container (Container ID range: Instant Container is
1-32; Fixed Container is 1-8; Temporary
Container is 1-64)

Instant Container Select one area from the drop-down menu

(prerequisite: all the areas have been
Area Fixed Container
configured in the “Advanced” menu.
Temporary Container Refer to “4.5 Area Configuration”).

Fixed Container
The start time and end time for sending
Hour Range
Temporary Container data packets

The interval of sending data packets in

Sending Fixed Container
one container using milliseconds as a
Interval Temporary Container
unit. This range is 0-60000.

Fixed Container
The percentage of this container sending
Bandwidth
Temporary Container packet occupied bandwidth in this region.

Sending Times Temporary Container The times of sending data packets.

Temporary Container The duration of sending data packets.

Sending

25
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

Duration

Instant Container
Determine whether the EMM packets
Expression Fixed Container
should be sent in the container.
Temporary Container

Instant Container

Fixed Container The comment to describe the sending

Comment
strategy (optional).
Temporary Container

Fig. 4.10-1 Container Parameter And Meaning

EMML container expression editor description:

Click “editor” and in the pop-up dialog, user can add and configure expression according to different

requirements.

Fig. 4-28 Container Expression Editor Dialog

For Template selection in EMML configuration, refer to “8.1 Template”.

4.11 EMMS Configuration

After adding EMMS module group, add EMMS modules.

26
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

Right-click on the EMMS group, and select New Module from the drop-down menu, as shown in Fig.

4-29:

Fig. 4-29 New EMMS Module

（1） In the pop-up dialog, enter Server ID the same as the last segment of the server IP.

For example: if the IP is 138.138.138.12, enter “12” in the text box, as shown in Fig. 4-30:

Fig. 4-30 New Module Dialog

Configure EMMS parameters. Click on the Edit button to configure the following information, as

shown in Fig. 4-31:

Fig. 4-31 EMMS Configuration Window

27
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

Users configure EMMS log Level according to their needs. (Refer to “4.7 Log Level Setting”)

The EMMS arguments and their definitions are indicated in the following table:
Fig. 4-32 EMMS Arguments Definitions

Parameter Description
After configuring the areas in the Advanced menu, select one area from
Area
the drop-down list.
Bandwidth Band width, unit: Kbps(10-2000)
The interval of sending EMM packets for one card,
IntervalOfSameCard
unit: millisecond (50 - 5000), the suggested value is 1000ms.
EMMS IP address which connect with the MUX (must not be same
Floating IP
with floating IP of other modules )
Sub Mask EMMS Sub Mask which connect with MUX
NIC_Name Network Adapter which connect with the MUX network
SuperCASID SuperCASID used by EMMS
Communication TCP, TCP+UDP, Multicast (the same as the port configuration of the
Mode scrambler)
IP address The scrambler IP address
Data ID Parameter communicates with scrambler.
Channel ID Channel ID (TCP mode only), default is 1
Stream ID Stream ID (TCP mode only), default is 1
Reconnection
Reconnection Interval, default is 10,unit: seconds (1 - 120)
Interval
TCP Port The scrambler TCP Port
UDP Port The scrambler UDP Port
This parameter defines the format of the EMM carried on this interface:
-Section: the EMMs carried on the interface are in MPEG-2 section
format; default to Section.
Section_TSpkt_Flag
-TS: the EMMs carried on the interface are in MPEG-2 transport
stream packet format, all TS packets shall be 188 byte long, any other
payload length would be considered as an error.
EMM PID Valid only when Communication Mode is Multicast

28
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

4.12 ECMG Configuration

After adding ECMG module group, add ECMG modules.

Right-click on the ECMG module group, and select New Module from the drop-down menu, as shown

in Fig. 4-33:

Fig. 4-33New ECMG Module

（1） In the pop-up dialog, enter server ID the same as the last segment of the server IP.

For example, if the IP is 138.138.138.12, enter “12” in the text box, as shown in Fig. 4-34:

Fig. 4-34 New Module Dialog

Click on the Advanced button in ECMG configuration window, as shown in Fig. 4-35:

Fig. 4-35 ECMG Configuration Window

29
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

Enter the Advanced configuration window, as shown in Fig. 4-36 below:

Fig. 4-36 ECMG Configuration Window

Configure the ECMG parameters. Click on the Edit button to configure the following information.

According to user’s requirements, configure EMMS Log Level. (Refer to “4.7Log Level Setting”).

a) The EMMS parameters and their definitions are shown in the following table:

Fig. 4-37 ECMG Parameters Definitions

Parameter Description
This integer represents the period in milliseconds for the repetition of
ECM_Rep_Period data (e.g. ECMs).
Default is 100ms.
Maximum number of simultaneous opened streams supported by an
ECMG on a channel. This parameter is communicated from the ECMG
Max_Streams
to the SCS during the channel set-up.
Maximum count of streams supported is 512 by default.
This parameter is communicated by the ECMG to the SCS during
channel set-up. The time needed by an ECMG to compute an ECM
Max_Comp_Time
when all the streams in a channel are being used.
Unit is ms.
SCS_Server_Port SCS server monitoring port
The minimum CP period of scrambler.
Min_CP_Period
Unit is 100ms

30
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

This parameter defines the format of the ECM carried on this interface:
-Section: the ECMs carried on the interface are in MPEG-2 section
format; default to Section.
Section_TSpkt_Flag -TS: the ECMs carried on the interface are in MPEG-2 transport stream
packet format, all TS packets shall be 188 byte long, any other payload
length would be considered as an error; it is the head-end's
responsibility to fill the PID field in the TS packet header;
SendTestStream Indicates whether to send the test stream.
The delay start time corresponds to the first encryption cycle when the
AC_Delay_Start AC value changes.
ms is the unit, default is 2000
The delay stop time corresponds to the last encryption cycle of the last
AC_Delay_Stop AC before the AC value changing.
ms is the unit, default is 0
This signed integer represents the amount of time between the start of a
Crypto Period, and the start of the broadcasting of the ECM attached to
this period. If it is positive, it means that the ECM shall be delayed with
Delay_Start
respect to the start of the Crypto Period. If negative, it means that the
ECM shall be broadcasted ahead of this time.
ms is the unit, 0 by default
Specifies the interval of CP period start time and the corresponding
start time of ECM packets broadcasting. If it is a positive number, ECM
Delay_Stop packets broadcast after CP period starting, otherwise, ECM packets
broadcast before CP period starting
ms is the unit, 0 by default
From not scrambling to scrambling, the delay start time of the first CP
Trans_ Delay_Start
Period, ms is the unit, 0 by default
From scrambling to not scrambling, the delay stop time of the last
Trans_ Delay_Stop
CPPeriod, ms is the unit, 0 by default
ECMG IP address which connect with the MUX (must not be same
Floating IP
with floating IP of other modules )
Sub Mask ECMG Sub Mask which connect with the MUX
NIC_Name Network Adapter which connect with the MUX network
SCSIP Address The scrambler IP address
The forth segment of 138 network IP of encryptor, for example, if the
Encryptor Config
IP of encryptor is 138.138.138.12, check “Encryptor16” checkbox.

31
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

(Precondition is that the encryptor group and “12” module have been
created.)
CASID SuperCASID used by ECMG

4.13 RouterAdapter Configuration

After adding RouterAdapter module group, add RouterAdapter modules.

Right-click on the RouterAdapter module group, then select New Module from the drop-down menu,

as shown in Fig. 4-38:

Fig. 4-38 New RouterAdapter Module

（1） In the pop-up dialog, enter server ID the same as the last segment of the serve IP.

For example: if the IP is 138.138.138.12, “12”in the text box, as shown in Fig. 4-39:

Fig. 4-39 New Module Dialog

Configure RouterAdapter parameters, Click the “Edit” button to enter the edit mode, as shown in Fig.

4-40:

32
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

Fig. 4-40 RouterAdapter Configuration Window

According to user’s needs, configure RouterAdapter log Level. (Refer to “4.7 Log Level Setting”)
The parameters and their definitions are shown in the following table:
Fig. 4-41 RouterAdapter Parameters Definitions

Parameters Definitions

Security Level No Controls: No limits for SMS ID, IP. Key is not allowed
Controls
Low: Security control for SMS ID, IP. Key is not allowed

Middle: Security control for SMS ID, IP, Key combination.

High: Security control for SMS ID, IP, Key and Product combination;

Disable PreAuthorized entitlement will give entitlement 180 days in advance.

PreAuthorized
Disable or enable PreAuthorized entitlement by check the checkbox.

RouterAdapter IP address which connect with the MUX (must not be same
Floating IP
with floating IP of other modules )
Sub Mask RouterAdapter Sub Mask which connect with the MUX
NIC_Name Network Adapter which connect with the MUX network

33
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

The ID identifies the SMS

SMS ID

IP address Trusted SMS IP address

Key Key interface with SMS

SN/ Product SN or Product which allows to be operated.

4.14 Web Configuration

After adding Web module group, add Web module.

Right-click on the Web module group, then select New Module from the drop-down menu, as shown

Fig. 4-42 below:

Fig. 4-42 New Web Module

（1） In the pop-up dialog, enter server ID the same as the last segment of the serve IP.

For example: if the IP is 138.138.138.12, enter “12”in the text box, as shown in Fig. 4-43:

Fig. 4-43 New Module Dialog

Configure the Web parameters, Click the “Edit” button to enter the edit mode, as shown below:

34
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

Fig. 4-44 Web Configuration Window

According to user’s requirements, configure Web Log Level. (Refer to “4.7Log Level Setting”)

The parameters and their definitions are shown in the following table
Fig. 4-45 Web parameters Definitions

Parameters Definitions

Web Trusted IP If application side wants to upload file or signature file via web,
user need to add the machine IP into “Web Trusted IP”

The SMS IP address need to be added to the “SMS Trusted IP” if

SMS Trusted IP
SMS has communicated interface with Web.

4.15 SNMPAgent Configuration (Optional)

Right-click on the SNMPAgent module group, then select New Module from the drop-down menu, as

shown Fig. 4-46 below:

35
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

Fig. 4-46 New Web Module

（1） In the pop-up dialog, enter server ID the same as the last segment of the serve IP.

For example: if the IP is 138.138.138.102, enter “102”in the text box, as shown in Fig. 4-47:

Fig. 4-47 New Module Dialog

Configure the SNMPAgent parameters, Click the “Edit” button to enter the edit mode, as shown below:

Fig. 4-48 Web Configuration Window

According to user’s requirements, configure SNMPAgent Log Level. (Refer to “4.7Log Level Setting”)

The default polling interval is 5 seconds.

Read Community and Set Community for SNMP is “supertv” by default.

36
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

4.16 Module State after Configuration

After completing configuration of all the modules, click on the CDCAS3.0 root node, the modules

running normally will turn green in the topology chart, as shown in Fig. 4-49:

Fig. 4-49 Console Main Window

4.17 Delete Module Group

Select the module group to delete, and right-click to choose Delete Group from the drop-down menu,

as shown in Fig. 4-5050:

Fig. 4-50 Delete Module Group

（1） While Encryptor group is in use, DB, Agent, Task, Logger and Broadcast groups are not
allowed to be deleted. If you try to delete a running encryptor, the system will give a warning
message.

37
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

4.18 Rename Module Group

Select the module group needs to be renamed and right-click to select Rename from the drop-down

menu and enter the new name as shown in Fig. 4-51:

Fig. 4-511 Rename Module Group

4.19 Enable Operator customization

Click ‘Enable Operator Customization’ from the drop-down ‘Advanced’ menu, as shown in Fig. 4-52:

Fig. 4-522 Enable Operator Customization

After enabling operator customization, “Enable Operator Customization” will change to “Disable

Operator Customization” from the drop-down ‘Advanced’ menu, and click “Disable Operator

Customization” to turn off this function, as shown in Fig. 4-53:

Fig. 4-533 Disable Operator Customization

4.20 Enable Emergency Mode

Emergency Mode allows users to watch programs for free. Only when Flag911 attribute of one service

38
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

in the scheduler file is set to “1”, Emergency mode can take effect for this service.

Select Advanced→Enable Emergency Mode, as shown in Fig. 4-54:

Fig. 4-544 Enable Emergency Mode

The pop-up Enable Emergency Mode dialog appears, as shown in Fig. 4-55:

Fig. 4-555 Enable Emergency Mode Dialog

Enter the sentence shown in the dialog above to enable “Emergency Mode”.

4.21 Enable Group Authorization（Optional）

The group authorization function is designed for improving the efficient of sending authorization
information. The authorization information of all users in the same group can be send once with group
authorization enabled. This function is not a self-starting function.

Start this function and follow the steps below:

（1） Click ‘System Configuration under ‘Advanced’ menu.

39
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

（2） Select ‘Open Group Entitle ’, and set ‘Dispatch period’

----------------------------------------------------------------------------------------------------------------------------

Note

The group authorization function is irreversible.

Once group authorization is enabled, you can change the group authorization period, ranged from 30
days to 180 days, but you’re not allowed to cancel group authorization function.

40
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

----------------------------------------------------------------------------------------------------------------------------

4.22 User Accounts

Only system administrator and administrator can operate user accounts.

（1）Select UserManagement→User Accounts, as shown in Fig. 4-56.

Fig. 4-566 User Accounts

（2）Click User Accounts, as shown in Fig. 4-57.

41
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

Fig. 4-577 User Accounts Configuration

a） Unlock-Click this button, unlock the selected user.

b） Forbid -Click this button, forbid or permit the selected user.

c） Reset password-Click on this button to reset the password of the selected user, the reset password is
“TVcas+3Fp4”.

d） Delete-Click this button, delete the selected user.

e） New-Click this button, add a new user: edit username, role, expiration time, remark.

f） Modify-Click this button, reedit the selected user.

g） Save-Save the edited user.

h） Undo- Cancel the operation of the edited user.

4.23 User Roles

Only system administrator can operate user roles.

（1） Select UserManagement→User Roles, as shown in Fig. 4-58.

42
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

Fig. 4-588 Manage Roles

（2） Click User Roles, the pop-up dialog box is as shown in Fig. 4-59

43
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

Fig. 4-599 User Roles Configuration

a） Delete- When select user and click this button, information of the selected user will be deleted.

b） New-Click this button, add a new role.

c） Modify-Click this button, reedit the selected role.

d） Save-Save the edited role.

e） Undo- Cancel the operation of the edited role.

44
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

4.24 Parameters Setting

Parameter setting is the configuration of user’s locked parameters by system administrator or
administrator.

（1） Select UserManagement→Param Setting, as shown in Fig. 4-

Fig. 4-60 Param Setting

（2） Click Param Setting, the pop-up dialog box is as shown in Fig. 4-60

Fig. 4-601 Param Setting

a） Auto-lock times-Configure times of user auto-lock: It means when user login and input wrong
password that exceed the value in the blank, the user will be locked. The range of value is [1-10].

b） Auto-unlock duration -Configure the duration of auto-unlock: It means that if the user has been
locked, when the setting time is up, user will be unlocked automatically, and user can login again.
The range of value is [1-60].

45
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

4.25 User Info

（1）Select UserManagement→User Info, as shown in Fig. 4-61

Fig. 4-612 User Info

（2）Click User Info, the pop-up dialog box is as shown in Fig. 4-62

Fig. 4-623 User Info Configuration

（3） Click Change password, the pop-up dialog box is used for changing user password, as shown in
Fig. 4-63

46
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

Fig. 4-634 Modify password dialog-box

4.26 User Logs

User can query the operation history in User logs.

（1）Select UserManagement→UserLogs, as shown in Fig. 4-64

Fig. 4-645 User logs

（2）Click User Logs, Click User logs, the pop-up dialog box is as shown in Fig. 4-65

47
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

Fig. 4-656 User logs Configuration

When logged on user only has the permission to query user logs, the interface “Export Log settings” is
invisible.

a） User name- According to user information, operator can fuzzy query the user operation log.
If you do not input the user name, the default setting is to query all users’ operation logs.

b） Start time~End time- Set start time and end time, to query operation logs in this period.

c） Event type-User can choose different type of event to query operation logs, Click the drop
down button, the pop-up information is as shown in Fig. 4-66

48
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

Fig. 4-66 Event type

d） esource- User can choose different resource to query correlative information, Click
Resource, the pop-up dialog box as shown in Fig. 4-67

Fig. 4-67 Resource

e） Query-Click the button to inquire log records of configuration.

f） Export path-Choose a path and assign a file name to export.

49
CDCAS3.0 User Manual V2.0.0 4 Head-End Configuration

g） Delete after export-If checked, to export records with deleting, or export records without
deleting

h） Export- Click this button to export the queried logs.

Fig. 4-68 Export user log

50
CDCAS3.0 User Manual V2.0.1 4 Head-End Configuration

4.27 Audit (Optional)

Audit function is to save history records of entitlement and scheduler for query or audit in the further.
When the user clicks Advanced  Audit, a confirmation box will be displayed as shown below. The OK
button is not allowed to be clicked within 5 seconds. Click “OK” to enable audit function 5 seconds later.

Fig. 4-69 Confirmation box to enable audit

A checkmark will be displayed in front of Advanced Audit if audit function is enabled,.

Fig. 4-70 Audit function is already enabled

The user can disable audit function by click Advanced Audit once more. A confirmation box will be
displayed as shown below. The OK button is not allowed to be clicked within 5 seconds. Click “OK” to
disable audit function 5 seconds later.

Fig. 4-71 Confirmation box to disable audit

51
 5 Query and Maintenance

5.1 SMS Command Query

SMS commands are the commands which operator sends to CDCAS system through SMS. CDCAS will deal
with SMS commands and record the final result.
Select SMS command from the toolbar, a SMS command window shows up. The left side of the window
shows command classification and query condition, while the right side shows SMS command list and its
details, as shown in Fig. 5-1:

Fig. 5-1 SMS Command Window

The list shows the latest 100 SMS commands, including Time, IP, Command Result, Data and Record ID.
When selecting “Waiting Process” from command classification, query condition turns into gray and disabled.
Query records that meet the condition will be listed on the right side.
When selecting “Processed” and “Failed”, the query condition will be enabled. Specify the query period and
Card ID, then click on the Query button, Query records that meets the condition will be listed on the right
side.
CDCAS 3.0 User Manual V2.0.1 6 Introduction to Web

5.2 Module Status

5.2.1 Performance Status
Select module to view on the left side of the console, and click on Performance to display the performance
indexes of the module on the right side, as shown in Fig. 5-2:

Fig. 5-2 Performance Window

Check the server’s CPU and memory usage through the performance window of the module.
Kernel CPU Usage, CPU Usage and Memory Usage are displayed on the top side.
Performance and Parameters are displayed on the bottom side:
※ Time since the machine started
※ Last time the module change its status
※ Memory usage (KB)
※ Total memory usage (KB)
※ Module file version

5.2.2 Working Status

Select module to view on the left side, and click on Status to display the working status of the module.
◆ EMMS working status is shown in Fig. 5-3

53
CDCAS 3.0 User Manual V2.0.1 6 Introduction to Web

Fig. 5-3 EMMS Working Status Window

EMMS working status includes multiplexer list, container list and actual broadcast bandwidth.
Multiplexer list includes IP of MUX, communication mode, TCP port, UDP port, DATA ID, channel ID,
stream ID, MUX status.
MUX Status is the connection status of current module and MUX, specific connection status as follows:
Fig. 5-4 MUX status list
Status List
Disconnect
Connect
ChannelSetting
ChannelSetted
ChannelError
StreamSetting
StreamSetted
StreamError
BandwidthRequest
ReadyToSend
Container list is sending container’s information includes container ID, card’s number, EMM packets’ number,
send times, current sent package number, sent time, actual sending period. Actual Bandwidth is current actual
bandwidth of broadcast.
◆ EMML working status is shown in Fig. 5-5:

54
CDCAS 3.0 User Manual V2.0.1 6 Introduction to Web

Fig. 5-5 EMMS Working Status Window

EMML working status includes container list and EMMSIP list:
Container list is sending container’s information includes container ID, data load percentage, loading start
time, loading end time, send percentage, send start time, send end time.
EMMS IP list includes EMMS IP address, EMMS group number, EMMS connection time. EMMS IP is got
from EMML: if EMML and EMMS work in different servers, then EMMS IP is current EMMS server ‘s IP.
If EMML and EMMS work in the same server, then EMMS IP is native loopback IP（127.0.0.1）.
◆ ECMG working status, contains the scrambled program list, as shown in Fig. 5-6:

Fig. 5-6 ECMG Working Status

Abnormal scrambled programs, whose cws keep invariant more than a specific number (can be set, the
default value is 2) of cw duration, can be checked in “Abnormal stream details”.

5.2.3 Log Display

There are two ways to query logs：

55
CDCAS 3.0 User Manual V2.0.1 6 Introduction to Web

（1）Single Module Log Query

Select the module to view on the left side of Console, the query window will appear on the right side. The
upper half of the window contains query conditions and operation buttons, while the lower half is divided into
log lists and details, as shown in Fig. 5-7:

Fig. 5-7 Log Window

After specifying the query period and log level, click on the Query button to display the logs meeting the
query conditions.
Enter key word to query the logs meeting the conditions in the log list. (Log level on this page is only used
for querying)
（2）Multi-modules Log Query
Select Log Query from the toolbar, the left half of the window contains module selection, query conditions,
keyword search and operating button, while the right half contains log list and details, as shown in Fig. 5-8:

56
CDCAS 3.0 User Manual V2.0.1 6 Introduction to Web

Fig. 5-8 Log window

SELECT ALL is used to select all modules or clear all of the selected modules.
Select the module, specify query period and log level, and click on the Query button to display the log
records meet the query conditions. Only the first 1000 records are displayed, as shown in Fig. 5-9:

Fig. 5-9 Log window

Log window can view all modules logs, you can filter logs according to module type, date, log level. Key
words can also be used to filter logs. Meanwhile, you can modified the combination query condition
repeatedly, log list on the right side will update when refreshing the condition. Click the list header to sort the
results in the list. Log list contains log level, date, server IP, module type, log content and serial NO. in
module.
Enter one keyword, and click on the Search button to start searching. If the log contains the keyword is found
(highlighted), it stops searching. Click on the Search button again to search for the next one, as shown in Fig.
5-10:

57
CDCAS 3.0 User Manual V2.0.1 6 Introduction to Web

Fig. 5-10 log window

The function of the Reset button: Cancel all of the selected modules.
Set the start time as 00:00:00 on that day, and the end time as 00:00:00 on the next day.
Set the log level to “Trace” (the lowest level).

5.3 Exporting Logs

Export Log is used to export log records from DB into one file.
Select Tools→Export Log, as shown in Fig. 5-11:

Fig. 5-11 Log Export

Pop-up Export Log dialog as shown in Fig. 5-12:

58
CDCAS 3.0 User Manual V2.0.1 6 Introduction to Web

Fig. 5-12 Export Log Dialog

◆ Type Configuration
Select ALL or one module from the drop-down menu.
Users can configure the log level according to their actual needs.
◆ Time Range
If Total Time Range is selected, all of the logs will be exported, otherwise only the logs within the specific
period are exported.
◆ DB configuration
If Export and Delete from DB is not selected, the logs meeting the conditions will be exported and not
deleted from DB, otherwise the logs are exported and deleted from DB.
◆ Display Log Information
If Display Log Information is selected, the logs will display in Log list when logs export successful,
otherwise the logs are not display in Log list.
◆ Export Path
Exported log folder can be found in export path.
◆ Click on the Export Records to export the logs meeting the condition into the file.
Attention: all the name of log file, SMS file and configuration parameter file are composed of the export time.
(year/ month/ day/ hour/ minute/ second, e.g. 20080506101047.txt).

5.4 Exporting SMS Commands

Export SMS command is used to export SMS commands from DB into one file.
Select Tools→Export SMS Command, as shown in Fig. 5-13:

59
CDCAS 3.0 User Manual V2.0.1 6 Introduction to Web

Fig. 5-13 Export SMS Command

Configure the items on the pop-up Export SMS Command dialog, as shown in Fig. 5-14:

Fig. 5-14 Command Export Dialog

◆ CardID Range
If all ID is selected, all of the log records will be exported. Otherwise, only the records within the specific ID
are exported.
◆ Time Range
If Total Time Range is selected, all of the commands will be exported, otherwise only the commands within
the specific period are exported.
◆ DB Configuration
If Export and Delete from DB is selected, the commands meeting the conditions will be exported and
deleted from DB, otherwise the commands will be exported but not deleted from DB.
◆ Export Path
Exported SMS folder can be found in export path.
Click on Export Records to export SMS records meet the condition into file.

5.5 Exporting Configuration

Export Configuration is used to export configuration information from modules of the Console into one file,
thus users can check the configuration information easily.
Select “Exporting Configuration” under drop-down “Tools” menu, as shown in Fig. 5-15:

60
CDCAS 3.0 User Manual V2.0.1 6 Introduction to Web

Fig. 5-15 Config Export

The pop-up Export Configuration dialog, as shown in Fig. 5-16.

Fig. 5-16 Export Configuration

Click on the Export Records button, it will export the configurations into one file without deleting records in
DB. Exported configuration files can be found in the export path.

5.6 Calculator
Select Tools→Calculator, as shown in Fig. 5-17:

Fig. 5-17 Calculator

The pop-up Calculator window, as shown in Fig. 5-18:

Fig. 5-18 Calculator Window

61
 Web provides the function of uploading files.
6 Introduction to Web
a) In IE browser, enter Web server IP and Port (8384), such as: http://138.138.138.61:8384 (assuming Web
server IP is 138.138.138.61)

b) Upload a total of three types of documents: scheduler file, card-issuing file and patch file. Digital
signature is mandatory before uploading.

Fig. 6-1 Web Window

6.1 Uploading Card-issuing File

a) Click on the Browse… button to select the signature card-issuing file, and then click on the Submit
button to upload, as shown in Fig. 6-2:
CDCAS 3.0 User Manual V2.0.1 6 Introduction to Web

Fig. 6-2 Upload Card-issuing File

b) Web will prompt a success message, as shown in Fig. 6-3:

Fig. 6-3 Web Success Window

-----------------------------------------------------------------------------------------------------------------------------
Note:
Web does not verify the contents of card-issuing file, so it’s better to check emmg log to make sure that the
file is imported into DB successfully.
-----------------------------------------------------------------------------------------------------------------------------

63
CDCAS 3.0 User Manual V2.0.1 6 Introduction to Web

6.2 Uploading Patch File

a) Click on the Browse… button to select the signature patch file, and then click on the Submit button to
upload, as shown in Fig. 6-4

Fig. 6-4 Upload patch file

b) Web will prompt a success message, as shown in Fig. 6-5:

Fig. 6-5 Web Success Window

----------------------------------------------------------------------------------------------------------------------------------------

64
CDCAS 3.0 User Manual V2.0.1 6 Introduction to Web

Note:
Before uploading the files（scheduler file, card-issuing file and patch file）, Web will validate the digital
signature. If the signature is invalid, Web will prompt a failure message, as shown in Fig. 6-6:
----------------------------------------------------------------------------------------------------------------------------------------

Fig. 6-6 Digital signature error

65
CDCAS 3.0 User Manual V2.0.1 6 Introduction to Web

7 Configuration Examples

7.1 Load Balance

EMMG, Web and Encryptor support load balance to improve the system’s performance. If multiple modules
are configured for the same module group and started simultaneously, the load of each module is roughly the
same.
For example, configure two EMMG modules and start them simultaneously on two servers, as shown below:

Fig. 7-1 EMMG in load balance

7.2 Active-Standby Mode

EMML, ECMG, EMMS, RouterAdapter, Agent, BroadCast, Looger and Task support active-standby
mode. If multiple modules are configured for the same module group and started simultaneously, only one
module will be in active, and the others will be in standby. If the active module stops running, the system will
automatically turn one standby module into active.
For example, configure two modules and start them simultaneously on two servers, as shown below:

66
CDCAS3.0 User Manual V2.0.1 8 Appendix

Fig. 7-2 Active-Standby Mode

7.3 Dynamic IP Mode

Dynamic ip, bond nic and subnet mask must be configured for ECMG and EMMS when enabling ECMG
and EMMS’s active-standby mode as mentioned above, which are different from other modules’
active-standby mode.
The next example shows how to configure dynamic ip, bond nic and subnet mask for ECMG while it is
similar for EMML.
The ECMG configuration interface is shown as Fig. 7-3. Click the “Advance” button and all ECMG
configuration parameters will show up. Enter the dynamic ip, subnet mask and bond nic name. After that,
change the ecmg ip of scrambler to the dynamic ip.

Fig. 7-3 ECMG Configuration Interface

-------------------------------------------------------------------------------------------------------------------------------------
Note:
The bond nic name is case sensitive.

--------------------------------------------------------------------------------------------------------------------------------------

Add two ECMG modules and start them (Fig. 7-4). One ECMG module is in active and the other one is in
standby, as shown in Fig. 7-5.

67
CDCAS3.0 User Manual V2.0.1 8 Appendix

Fig. 7-4 Add ECMG Modules

Fig. 7-5 Active-Standby ECMG

68
 8 Appendix

8.1 Template
If you don’t want to add containers manually, just use the templates in which the common sending strategies
have been defined. After selecting, the template is also allowed to modify.
Click on the “Edit” button in the lower left corner, the “Templates” button will be enabled when editing
Instant Container or Fixed Container.

Fig. 8-1 Container Config Window

8.1.1 Instant Container Template

Click on the “Templates” button and detailed instruction will show up when editing “Instant Container”.
“Expression” and “Comment” will be filled automatically with the content of template as shown in Fig. 8-2.

69
CDCAS3.0 User Manual V2.0.1 8 Appendix

Fig. 8-2 Template of “Instant Container”

Click the “Add” button after inputting container ID and area. Remember to click the “Save” button to save all
configurations at last.

Expression - select EMM.RecordID from EMM

Description- send all local EMM package immediately

8.1.2 Fixed Container Templates

There are several templates for option after clicking on the “Templates” button, when editing “Fixed Container” as
shown in Fig. 8-3.

Fig. 8-3 Templates of “Fixed Container”

The configuration window is as shown in Fig. 8-4 after selecting the template.

70
CDCAS3.0 User Manual V2.0.1 8 Appendix

Fig. 8-4 Add templates

Expression instruction：

 Container ID 1:

Expression - select EMM.RecordID from EMM where (Functions in (8,128,256, 1024,2048))

Description- send the operation info, entitlement, detitlement, slot-setting and character-setting packets.

 Container ID 2:

Expression - select EMM.RecordID from EMM where FilterMode = 8

Description - send the application data packets.

 Container ID 3:

Expression - select EMM.RecordID from EMM where Functions in (8,128,1024, 2048)

Description - send the opration info, entitlement, slot-setting and character-setting packets.

 Container ID 4:

Expression - Select EMM.RecordID from EMM where Functions in (256)

Description - send the detitlement packets.

8.1.3 FilterMode

FilterMode Code Description

0x07(7) Application data packet - addressing application data packet

71
CDCAS3.0 User Manual V2.0.1 8 Appendix

0x08(8) Application data packet - card application data packet

0x0F(15) patch packets
0x70(112) card packet - card common entitlement packet
0x71(113) patch key
0x72(114) card packet - card instruction packet

8.1.4 Functions

Function Code Description

0x00000001(1) Card Version Sync

0x00000002(2) Safe Chip Key

0x00000004(4) New Operator

0x00000008(8) Operator information, including operator private data, lock/unlock

state, family card flag and feeding interval
0x00000010(10) Family Card Key

0x00000020(32) Patch Key

0x00000040(64) Public Key

0x00000080(128) Entitlement
0x00000100(256) Detitlement
0x00000400(1024) Slot-setting

0x00000800(2048) Character-setting

0x00002000(8192) Reset PIN

0x00004000(16384) Reset SC-STB Pairing

0x00010000(65536) Group Entitlement

0x00080000(524288) OSD
0x00100000(1048576) Mail

0x00200000(2097152) Lock Channel

0x00400000(4194304) Notify STB to freeze, upgrade, restart, tune

0x08000000(134217728) Unlock Channel

8.2 Operator Authority Management

The aim of operator authority management is to improve the security of CDCAS system and realize the login
security control of the CDCAS operator.
Operator authority management support both NSTV operator management mode and LDAP operator management
mode.
(1) NSTV Operator Management Mode
NSTV operator management can be divided into several roles with different function authorities, at the same

72
CDCAS3.0 User Manual V2.0.1 8 Appendix

time, it can create multiple users and assign each user with related authority. When user login the system, the
system will automatically record various operations of the user.
There are 4 default roles of NSTV operator management: SystemManager, Manager, Operator and Visitor.
The authority of each role is shown as below:
Role Authority User
SystemManager Having all the authorities, It is created at the time when
including: CDCAS is created, the sole one

 Manage all users and roles

 Business checking
 Business operation

Manager  Manage all users and roles It is created by SystemManager

except SystemManager and
Manager
 Business checking
 Business operation

Operator  Business checking It is created by SystemManager or

 Business operation Manager

Visitor  Business checking It is created by SystemManager or

Manager
The default created user name of system administrator of NSTV operator management is CASSystem, the
password is CAS_sys+3Fp4, and both of them are case sensitive. It is a compulsive requirement to change
password at the first time to login CDCAS as the default user CASSystem.
(2) LDAP Operator Management Mode (Optional)

LDAP is a kind of Lightweight Directory Access Protocol. Based on this protocol, LDAP operator
management can achieve the function of Users Enter and Validate.

73