Sie sind auf Seite 1von 46

Securing Content, Enhancing Entertainment

VCAS for DVB v2.0


Subscriber Management System Interface (SMSI)
Description

FASTFIND LOCATOR

Contents

Preface

Customer Care

ENG-59 / Revision 1
Notice: No part of this publication may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose
without the express written permission of Verimatrix, Inc.

Verimatrix, Inc. reserves the right to make changes to this document at any time without notice and assumes
no responsibility for its use. Verimatrix, Inc. products and services can only be ordered under the terms and
conditions of Verimatrix, Inc.'s applicable agreements. All of the features described in this document may not
be currently available. Refer to the most recent product announcement or contact Verimatrix, Inc. for
information on feature and product availability.

This document contains the most current information available at the time of publication. When new and/or
revised information becomes available, this entire document is updated and distributed to all registered users.

Verimatrix and the Verimatrix logo are registered trademarks and service marks of Verimatrix, Inc.

All other trademarks, service marks, company names or logos are properties of their respective owners. Mention
of third-party products is for informational purposes only and constitutes neither an endorsement nor a
recommendation. Verimatrix, Inc. assumes no responsibility with regard to the performance or use of these
products.

© 2009 Verimatrix, Inc. All rights reserved. 


Portions © 2004-2009 comvenient GmbH & Co. KG. All rights reserved. 
Specifications and product availability are subject to change without notice.

Verimatrix, Inc.
6825 Flanders Drive
San Diego, CA 92121
Telephone: +1.858.677.7800
Fax: +1.858.677.7804
Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1
Connection between SMS and BCSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

2 SMS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1


Online Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1
IMPENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1
IMPDEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1
IMSENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
IMSDEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
IMDALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
IMCALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
IMPINR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
IMPINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3
IMKSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3
IMREGI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3
IMPURS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3
IPEDEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
PESTOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Offline commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
CYPENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
CYPDEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
CYSENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
CYSDEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
CYKSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
Additional Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
REGIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
SHTDWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
HOLDTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
PROTRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
On-Screen-Message Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
INDOSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
ALLOSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
IPFOSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
APFOSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
DELOSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7
INDTXD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7
ALLTXD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7
IPFTXD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7
APFTXD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7
DELTXD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7
DIAGOSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

Subscriber Management System Interface (SMSI) Description iii


ENG-59 / Revision 1
Chat Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
CHTROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
CHTTXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
CHTLIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
CHTDEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
CHTDLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Pairing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
ADDPBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
PAIRSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
UNPAIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
GTPAIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Master Slave Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
JOINMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
UNJOIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
General syntax of the commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Message Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
SMS Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Command Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Syntax of the Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Values for the Parameters of the Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Dialog Text Meta Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Syntax of the return message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Error_code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Error_message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

3 Examples for SMS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1


Online commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
IMPENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
IMPDEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
IMSENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
IMSDEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
IMDALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
IMCALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
IMPINR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
IMPINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
IMKSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Offline commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
CYPENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
CYPDEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
CYSENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
CYSDEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
CYKSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Additional Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
REGIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
SHTDWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
HOLDTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
PROTRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
OSM Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

iv Subscriber Management System Interface (SMSI) Description


ENG-59 / Revision 1
INDOSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7
APFOSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7
DELOSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7
ALLTXD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7
DELTXD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7
Chat Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8
CHTROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8
CHTTXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8
CHTLIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8
CHTDEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8
CHTDLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8
Paring Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9
ADDPBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9
PAIRSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9
UNPAIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9
GTPAIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9
Master Slave Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10
JOINMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10
UNJOIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10
Examples of return messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10
Examples of error messages: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11

4 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

Subscriber Management System Interface (SMSI) Description v


ENG-59 / Revision 1
vi Subscriber Management System Interface (SMSI) Description
ENG-59 / Revision 1
Preface

This document describes the interface between the Verimatrix Broadcast Content Security
Manager (BCSM), which is the core component of the Verimatrix Video Content Authority
(VCAS™) for DVB, and a 3rd-party Subscriber Management System (SMS). Not included into
this documentation is the semantics of the VCAS for DVB specific parameters e.g. products

Document Revision Level


This section provides a history of the revision changes to this document.

Revision Date Description

1.0 January 2009 This document version applies to VCAS for DVB v2.0.x.

Audience
This guide is intended for software developers in order to integrate third-party subscriber
management systems with VCAS for DVB.

Style and Notation Conventions


This section informs the user about the style and notation conventions used throughout this
guide.

Notes, Cautions, and Warnings


The following conventions are used in this document to alert users to information that
requires special attention. Carefully read and follow the instructions included in this
document.

Note Provides important supplemental or amplified information.

Caution Warns users of adverse conditions and/or consequences (loss of data, etc.)

WARNING Warns users of severe conditions and/or consequences (destructive operations,


etc.)

Subscriber Management System Interface vii


ENG-59 / Revision 1
Typographical Conventions
The following typographical styles are used in this guide to represent specific types of
information.

Bold Used for names of buttons, dialog boxes, icons, menus, profiles when placed in body text,
and property pages (or sheets). Also used for commands, options, parameters in body
text, and user input in body text.

C od e Used in code examples for computer output, file names, path names, and the contents of
online files or directories.

Italic Used for book titles, chapter titles, file path names, notes in body text requiring special
attention, section titles, emphasized terms, and variables.

Related Documentation
The entire VCAS documentation suite can be accessed from the Verimatrix Customer Care
Portal at http://verimatrix.com/customercare.
Please read the VCAS for DVB Release Notes before installing or using this product. The
Release Notes contain information about what is new in this release, corrections made since
the last release, and late-breaking information.

Contacting Customer Care


Verimatrix is committed to providing 24x365 support for our customers worldwide. If you
require assistance with the installation or operation of your product contact Customer Care.
The contact information is shown below.

E-mail customercare@verimatrix.com
Telephone (North America) +1.800.574.3856
Telephone (International) +1.858.764.5300
Internet www.verimatrix.com
Customer Care Portal www.verimatrix.com/customercare/

Before contacting Customer Care, have the following information available:


 Verimatrix product you are using
 Software version running on the system
 Description of the issue
 Server logs as described in the VCAS for DVB Broadcast Content Security Manager
(BCSM) User Guide

viii Subscriber Management System Interface


ENG-59 / Revision 1
Chapter 1

Introduction

This document describes the protocol which is used for the interface between a Subscriber
Management System (SMS) and the Verimatrix Broadcast Content Security Manager
(BCSM).

Overview
A SMS sends commands to the BCSM to generate entitlements for products which are stored
on a sector of a ViewRight STB for DVB. The responses to these messages (return messages)
are sent back from the BCSM to the SMS. Within these responses are an acknowledgement
for the received message and an error code.
If a command is not rejected (because of an error), the BCSM produces an Entitlement
Management Message (EMM). This message is sent to a sector of a ViewRight STB using the
MPEG protocol.
The ViewRight STB is a multi-sector STB. This means there are several sectors within which
are cryptographical separated. One sector is under control of one BCSM. Therefore each
message triggered by a SMS and generated by a BCSM is directed to one sector.
In case of the BCSM is a standalone system, there is a direct connection between one or
more SMS and the BCSM shown in the Figure below.

Figure 1-1. Connection SMS-VCAS

Subscriber Management System Interface (SMSI) Description 1-1


ENG-59 / Revision 1
The connection between SMS and BCSM should be protected against manipulation. Therefore
crypto router are installed between SMS and BCSM in case the two systems are not within
the same location. For the SMS and the BCSM this security layer is transparent.
For redundancy reasons there could be a second BCSM (1:1 redundancy).
In this case all SMS commands have to be distributed to both BCSM. In addition it is
important to ensure that the order of the commands is kept for both BCSM. Otherwise it is
possible the two BCSM have different data within their databases. In this situation the 1:1
redundancy of the two BCSM is lost.

Connection between SMS and BCSM


TCP/IP is used for the connection between SMS and BCSM.
The connection between SMS and BCSM is a synchronous interface. This means, after
sending a command to the BCSM the SMS waits for an answer. Afterwards the SMS sends the
next command.
The SMS connects to a dedicated port at the BCSM. If the connection breaks down, the SMS
has to reconnect.
At first the SMS has to send a registration command. Within this message it send the SMS
operator ID to the BCSM. The BCSM checks if the IP address and the SMS operator ID of the
SMS is configured within the system. The BCSM sends an acknowledgement for this
registration. In case the IP address or the SMS operator ID is not valid the BCSM sends a 'not
OK' within the acknowledgment and closes the socket.
If the SMS wants to disconnect it is recommended to sent an appropriate command (the
command is described in SHTDWN on page 3-5).
At the BCSM a time-out is implemented. If the BCSM gets no SMS command within a given
time frame it will close the socket. The connection is kept by sending a message within the
time frame. If no message needs to be sent, the HOLDTL message is used (this command is
described in HOLDTL on page 3-6).

1-2 Subscriber Management System Interface (SMSI) Description


ENG-59 / Revision 1
The handling of the connection between SMS and BCSM is shown in the figure below:

Figure 1-2. SMS-VCAS Messages

Subscriber Management System Interface (SMSI) Description 1-3


ENG-59 / Revision 1
1-4 Subscriber Management System Interface (SMSI) Description
ENG-59 / Revision 1
Chapter 2

SMS Commands

SMS commands are commands which are sent from a SMS to a BCSM.
There are two major types of commands: online and offline commands. These types are only
different in the handling within the BCSM.
Online commands trigger the production of one EMM, which is directly addressed to a sector
of a ViewRight STB client and played out only one time. In case of the command is not a PIN
related (IMPINR and IMPINS) command or a command which triggers an update of a key
(IMKSET) an online command triggers also an update of a cyclic EMM.
Offline commands only trigger an update of a cyclic EMM.
The BCSM sent a return message as an answer to a SMS command. Within this return
message could be an error message if an error occurred.
On-Screen-Message commands are either online (cycle_duration = ONCE) or offline
otherwise.
Examples of all commands and of error messages are shown in 3.
the following section are included:
 online commands
 off line commands

Online Commands
The name of an online command starts with "IM" (for "immediate") and is followed by four
letters or numbers which describe the meaning of the command.

IMPENT
Immediate Product Entitlement (for set of products)
The resulting EMM gives the entitlement for one product or a set of products to a ViewRight
STB client.
The name(s) of the product(s) is (are) sent from the SMS to the BCSM within this SMS
command.

IMPDEL
Immediate Product Deletion (for set of products)

Subscriber Management System Interface 2-1


ENG-59 / Revision 1
The resulting EMM deletes one product or a set of products from a ViewRight STB client.
The name(s) of the product(s) is (are) sent from the SMS to the BCSM within this SMS
command.

IMSENT
Immediate Product Entitlement (for a set of ViewRight STB clients)
The resulting EMM gives the entitlement for one product to one ViewRight STB client or to a
set of ViewRight STB clients.
The serial number(s) of the ViewRight STB client(s) is (are) sent from the SMS to the BCSM
within this SMS command.

IMSDEL
Immediate Product Deletion (for a list of ViewRight STB clients)
The resulting EMM deletes the entitlement for one product one ViewRight STB client or from a
set of ViewRight STB clients.
The serial number(s) of the ViewRight STB client(s) are sent from the SMS to the BCSM
within this SMS command.

IMDALL
Immediate Deletion of all entitled products
The resulting EMMs delete all entitlemented products from a sector of a ViewRight STB client.

IMCALL
Immediate clearing of all products, master/slave relations and pairing information.
The resulting EMMs delete all products from a sector of a ViewRight STB client. Additionally,
master/slave joining information and pairing information is removed.

IMPINR
Immediate reset of all PIN values
The resulting EMM writes the default values for the four PINs on the ViewRight STB client.
The default values are stored in the database of the BCSM.

2-2 Subscriber Management System Interface


ENG-59 / Revision 1
IMPINS
Immediate reset of a PIN
This SMS command transmits the values for a set of PINs and the indices of these PINs. The
resulting EMM writes the values for these PINs with the given indices on the ViewRight STB
client.
Actually the following PIN indices are supported:

Table 2-1. Supported PIN Indices

Pin Index Former impact

0 -

1 Parental Control / IOPS

2 Homeshopping

3 Set Top Box lock

IMKSET
Immediate G-Key Set
The resulting EMM writes an actual group key on the sector of the ViewRight STB client.

IMREGI
Immediate Region Download for one ViewRight STB client
The resulting EMM loads the region described as the parameter to the ViewRight STB client
on the first sector of the sms-operator. The region coding which must be used in ECMs is
translated in the CAS using the region-table in the database. If a ViewRight STB client has
assigned a region, this region is downloaded together with the keys when an IMKSET or
CYKSET is executed.
The serial number of the ViewRight STB client and the region-name are sent from the SMS to
the BCSM within this SMS command.

IMPURS
Immediate Purse Download for one ViewRight STB client
The resulting EMM loads the purse of the ViewRight STB client on the first sector of the sms-
operator to the given value. If the purse-value is smaller than the purse value stored on the
ViewRight STB client already, no action will happen on the ViewRight STB client. The purse
value on the ViewRight STB client is an only increasing value, which is compared to the used-
token-counter which is always incremented, when tokens are used. The difference between
the purse value and the used-token-counter can be read from the ViewRight STB client. The
absolute values are not available. The SMS is responsible for tracking the absolute value of
the purse.

Subscriber Management System Interface 2-3


ENG-59 / Revision 1
The serial number of the ViewRight STB client and the purse value are sent from the SMS to
the BCSM within this SMS command.

IPEDEL
Immediate PreEntitlement Deletion
The resulting EMM immediately deactivates an existing preentitlement by erasing the
specified products from the ViewRight STB client.

PESTOP
PreEntitlement Stop
The resulting EMM immediately ends preentitlement for all products by erasing all products
and the keys.

Offline commands
The name of an offline command starts with "CY" (for "cyclic") and is followed by four letters
or numbers which describe the meaning of the command.

CYPENT
Cyclic Product Entitlement (for a set of products)
The resulting EMM gives the entitlement for one product or a set of products to a ViewRight
STB client.
The name(s) of the product(s) is (are) sent from the SMS to the BCSM within this SMS
command.

CYPDEL
Cyclic Product Deletion (for a set of products)
The resulting EMM deletes one product or a set of products from a ViewRight STB client.
The name(s) of the product(s) is (are) sent from the SMS to the BCSM within this SMS
command.

CYSENT
Cyclic Product Entitlement (for a set of ViewRight STB clients)
The resulting EMM gives the entitlement for one product to one ViewRight STB client or to a
set of ViewRight STB clients.
The serial number(s) of the ViewRight STB client(s) is (are) sent from the SMS to the BCSM
within this SMS command.

2-4 Subscriber Management System Interface


ENG-59 / Revision 1
CYSDEL
Cyclic Product Deletion (from a set of ViewRight STB clients)
The resulting EMM deletes the entitlement for one product one ViewRight STB client or from
a set of ViewRight STB clients.
The serial number(s) of the ViewRight STB client(s) is (are) sent from the SMS to the BCSM
within this SMS command.

CYKSET
Cyclic G-Key Set
The resulting EMM writes an actual group key on the sector of the ViewRight STB client.

Additional Commands

REGIST
Registration command
This command is used for the SMS to register at the BCSM. In case of a failure of the
registration the BCSM closes the socket after sending a return message.

SHTDWN
Shutdown
This command is sent from the SMS if it wants to disconnect. The BCSM sends a response to
this command and closes the socket.

HOLDTL
Hold the line
This command has to be sent regularly if no other command is sent to keep the TCP/IP
connection established.
The frequency of this command must be minor than the time-out value which is configured
at the BCSM.

PROTRI
Trigger for generation of EMMs
This command sets or updates product times in the database of the BCSM. These product
times are the start time of the product trailer, start time of the product and the end time of
the product. Receiving these parameters the BCSM sets the according values in the database
table IndividualTimedProduct where the value for product is the same as in the EMM Trigger.

Subscriber Management System Interface 2-5


ENG-59 / Revision 1
If there is no product with the name in the database table, an error message is created. If
there are values for start_trailer, start_product and end_product in the according record,
these values will be updated.
According to these times the EMM play-out is started or ended by the BCSM.
An EMM Trigger command is sent once. Only in case of a change of one of the times the
command regarding one product is sent once more. In this command all three times have to
be transmitted not only the part which shall be changed.
Re-use of a product
In some cases a product is re-used after the end time of the product (e.g. a special event is
repeated few days after the first broadcast and subscriber have access to this repetition as
well). This product has to be configured for all the time within the BCSM. The EMMTrigger is
sent twice.

On-Screen-Message Commands
This chapter describes a set of commands to the BCSM which trigger the playout of an OSM
or text download EMM. The general notion of OnScreenMessages (OSM) comprises two
different message types: OSMs that instruct the STB to actually display a certain message
and text downloads (TXDs) that add a text fragment to the STB's internal store for later use
(see \Txx meta characters in Dialog Text Meta Characters on page 2-18).
Several formatting options, the position on the screen and the display time can be defined in
a simple language referred to as osm descriptor. OSMs may refer to previously downloaded
(via text download) or box-specific text fragments and can be delivered in up to sixteen
separate parts.
OnScreenMessages are embedded into special EMMs and addressed either to all or to single
individual ViewRight STB clients.

INDOSM
Individual addressed OSM

ALLOSM
universal addressed OSM

IPFOSM
individual addressed OSM with product filter

APFOSM
universal addressed OSM with product filter

2-6 Subscriber Management System Interface


ENG-59 / Revision 1
DELOSM
OSM deletion

INDTXD
individual addressed text download

ALLTXD
universal addressed text download

IPFTXD
individual addressed text download with product filter

APFTXD
universal addressed text download with product filter

DELTXD
Text Download deletion

DIAGOSM
diagnostic OSM

Chat Commands
This chapter describes a set of commands to the BCSM which trigger the playout of EMMs
used to build up a chat forum. A chat forum is build sending different lines of the displayed
screen in single text messages and a layout definition comprising all messages to be
displayed.
The Chat messages containing the individual line information is sent out as an encrypted
EMM using a product filter to enable and disable the customers for this service. The layout
definition is sent out as a non encrypted EMM containing only the references for the lines.
Up to 16 chat forums can be supported by the one system. The receiving and the selection of
the broadcasted chat entries must be done outside of the BCSM.
Note that all chat commands are accepted only by a dedicated chat processor with a
dedicated port. In addition to the chat commands, described below, the common commands
in Additional Commands on page 2-5 (e.g. REGIST, HOLDTL, etc.) are also applicable for
chat.

Subscriber Management System Interface 2-7


ENG-59 / Revision 1
CHTROM
Universal addressed Chat message including the chat room title (no encryption).

CHTTXT
Universal addressed Chat message including the chat text with optional chat line references
(see section 2.8.5). Chat texts may be defined with a product filter. Application of a product
filter implies encryption of the EMM.

CHTLIN
universal addressed Chat message including the text of a specific chat line (referenced in
chat text). Chat lines may be defined with a product filter. Application of a product filter
implies encryption of the EMM.

CHTDEL
Chat deletion, stops the playout of all CHTTXT and CHTLIN messages for a chatroom. In
addition the chat room title is reset such that the chat room is no more visible in a chat room
list.

CHTDLI
Chat line deletion, stops the playout of a CHTLIN message.

Pairing Commands
This chapter describes a set of commands to the BCSM which trigger the playout of EMMs
used to build up the pairing between a set top box and the ViewRight STB client. The
maximal number of ViewRight STB client that can be paired to one set top box as well as the
maximal number of set top boxes that can be paired to one ViewRight STB client can be
configured in the BCSM.

ADDPBX
Adds the given set top box id to the list of known set top boxes. Only set top box ids, that are
known to the system can be used for the following pairing commands.

PAIRSC
Individually addressed EMM pairing the addressed ViewRight STB client to a given set top
box.

2-8 Subscriber Management System Interface


ENG-59 / Revision 1
UNPAIR
Individually addressed EMM unpairing the addressed ViewRight STB client from any or the
given set top box. Also used for unpairing a set top box from any ViewRight STB client.

GTPAIR
Utility command for querying the pairing status of the given ViewRight STB client. Does not
produce any EMM.

Master Slave Commands


This chapter describes a set of commands to the BCSM which trigger the playout of EMMs
used to build up the master slave binding between different ViewRight STB clients.

JOINMS
Joins the given first ViewRight STB client as the master to all other given slave ViewRight
STB clients. All other existing master/slave relations of the given STBs and their previous
masters and slaves are implicitly removed.

UNJOIN
Removes the joining information for all given ViewRight STB clients

Syntax

Rules
 For each parameter of the commands only ASCII-strings (7 bit characters) are
supported.
 The end of each command is indicated with '\n' or '\r'. Within the examples of this
document '\n' is used.
 The different parts of one command are separated with a comma.
 No blanks are supported.
 Parameters for lists (within the commands IMPENT, IMPDEL, IMSENT, IMSDEL, CYPENT,
CYPDEL, CYSENT and CYSDEL) are enclosed in parentheses '(...)'.
 Only upper case letters are supported (for the command names).

General syntax of the commands


The general syntax of the commands sent by a SMS looks like this:

Subscriber Management System Interface 2-9


ENG-59 / Revision 1
< me s sa ge _ nu mb er > ,< co mm a nd _n a me >, <p a ra me te r s>
The return messages are described in Syntax of the return message on page 2-18.

Message Number
The message number within the SMS command will be copied in the answer of the BCSM as
it is and will be printed out in a log file. Therefore each message sent from a SMS can be
identified by its message number and the dedicated answer from the BCSM can be assigned
to. It is recommended to use unique message numbers.
The return message to a SMS commands gets the same message number. Thus it is possible
to link command and reply.
Message numbers are restricted to unsigned numbers (max. 9 digits).
The message number must not have leading '0's.

SMS Operator
The SMS operator is used to identify a SMS or a part of one SMS.
The SMS gateway (in case of redundancy at the BCSM) checks whether the SMS operator
mentioned in the command is allowed to send commands to this port.
The BCSM checks whether this SMS Operator is allowed to write an entitlement for the
product mentioned in the message on the sector for which the product is configured (in the
BCSM).

Command Name
The command name indicates which command should be used. It is written in upper case
letters.

Parameters
Belonging to the command name there are different parameters transmitted in the message.
The impact of the different parameters is shown in Table 2-3 on page 2-13.

Syntax of the Commands

Table 2-2. Syntax of the Commands

Command Syntax

< IM P EN T> <message_number>', IMPENT,'<serial_nr>','<product_list>'\n

< IM P DE L> <message_number>', IMPDEL,'<serial_nr>','<product_list>'\n

< IM S EN T> <message_number>', IMSENT,'<product>','<serial_nr_list>'\n

< IM S DE L> <message_number>', IMSDEL,'<product>','<serial_nr_list>'\n

2-10 Subscriber Management System Interface


ENG-59 / Revision 1
Table 2-2. Syntax of the Commands (Continued)

Command Syntax

<I M DA LL > <message_number>', IMDALL,'<serial_nr>'\n

<I M CA LL > <message_number>', IMCALL,'<serial_nr>'\n

<I M PI NR > <message_number>', IMPINR,'<serial_nr>'\n

<I M PI NS > <message_number>', IMPINS,'<serial_nr>','<PIN_list>'\n

<I M KS ET > <message_number>', IMKSET,'<serial_nr>'\n

<I M RE GI > <message_number>', IMREGI,'<serial_nr>','<Region-Name>'\n

<I M PU RS > <message_number>', IMPURS,'<serial_nr>'',''<number>\n

<I P ED EL > <message_number>','IPEDEL','<serial_nr>','< product_list>'\n

<P E ST OP > <message_number>','PESTOP','<serial_nr>'\n

<C Y PE NT > <message_number>', CYPENT,'<serial_nr>','<product_list>'\n

<C Y PD EL > <message_number>', CYPDEL,'<serial_nr>','<product_list>'\n

<C Y SE NT > <message_number>', CYSENT,'<product>','<serial_nr_list>'\n

<C Y SD EL > <message_number>', , CYSDEL,'<product>','<serial_nr_list>'\n

<C Y KS ET > <message_number>', CYKSET,'<serial_nr>'\n

<R E GI ST > <message_number>',REGIST,'<SMS_operator>'\n

<S H TD WN > <message_number>', SHTDWN\n

<H O LD TL > <message_number>', HOLDTL\n

<P R OT RI > <message_number>',PROTRI,'<triggered_product_list>'\n

<I N DO SM > <message_number>',INDOSM,'<serial_nr>','<sector_nr>','<cycle_duration


>','<msg_id>',' [<osm_descriptor>',']<dialog_text>'\n

<A L LO SM > <message_number>',ALLOSM,'<serial_nr>','<sector_nr>','<cycle_duration


>','<msg_id>',' [<osm_descriptor>',']<dialog_text>'\n

<I P FO SM > <message_number>',IPFOSM,'<serial_nr>','<sector_nr>','<cycle_duration


>','<pos_neg>','<product_list>','
<msg_id>','[<osm_descriptor>',']<dialog_text>'\n

<A P FO SM > <message_number>',APFOSM,'<serial_nr>','<sector_nr>','<cycle_duration


>','<pos_neg>','<product_list>','
<msg_id>','[<osm_descriptor>',']<dialog_text>'\n

<D E LO SM > <message_number>',DELOSM,'<serial_nr>','<sector_nr>','<msg_id>'\n

<I N DT XD > <message_number>',INDTXD,'<serial_nr>','<sector_nr>','<cycle_duration


>','<txt_index>','<dialog_text>'\n

<A L LT XD > <message_number>',ALLTXD,'<serial_nr>','<sector_nr>','<cycle_duration


>','<txt_index>','<dialog_text>'\n

Subscriber Management System Interface 2-11


ENG-59 / Revision 1
Table 2-2. Syntax of the Commands (Continued)

Command Syntax

< IP F TX D> <message_number>',IPFTXD,'<serial_nr>','<sector_nr>','<cycle_duration>


','<pos_neg>','<product_list>',' <txt_index>','<dialog_text>'\n

< AP F TX D> <message_number>',APFTXD,'<serial_nr>','<sector_nr>','<cycle_duration


>','<pos_neg>','<product_list>',' <txt_index>','<dialog_text>'\n

< DE L TX D> <message_number>',DELTXD,'<serial_nr>','<sector_nr>','<txt_index>'\n

< DI A GO SM > <message_number>',DIAGOSM,'<serial_nr>','<sector_nr>','<cycle_duratio


n>','<product_list>','<msg_id>','
[<osm_descriptor>',']<dialog_text>','[<osm_descriptor>',']<dialog_text>'\n

< CH T RO M> <message_number>',CHTROM,'<serial_nr>','<chat_id>',' <dialog_text>' \n

< CH T TX T> <message_number>',CHTTXT,'<serial_nr>', '[<product_list>',']<chat_id>','


<dialog_text>' \n

< CH T LI N> <message_number>',CHTLIN,'<serial_nr>','[<product_list>',']<chat_id>','<t


xt_index>',' <dialog_text>' \n

< CH T DE L> <message_number>',CHTDEL,'<serial_nr>','<chat_id>' \n

< CH T DL I> <message_number>',CHTDLI,'<serial_nr>', '<chat_id>','<txt_index>' \n

< AD D PB X> <message_number>',ADDPBX,'<byte8_box_id>

< PA I RS C> <message_number>',PAIRSC,'<byte8_box_id>

< UN P AI R> <message_number>',UNPAIR,’

< GT P AI R> <message_number>',GTPAIR,'[<serial_nr>]','[<byte8_box_id>]

< JO I NM S> <message_number>',JOINMS,'<serial_nr>','<serial_nr_list>

< UN J OI N> <message_number>',UNJOIN,'<serial_nr_list>

2-12 Subscriber Management System Interface


ENG-59 / Revision 1
Values for the Parameters of the Commands
Table 2-3. Values for Parameters

Parameter# Value Comment

<me ssa ge_ numb er> max. 9 digits Identifier for this message (unsigned
number).
<se ria l_n r_li st> 'list of serial_numbers, List of serial numbers of ViewRight
= each with 10 digits STB clients. The BCSM makes the
'(' <se ria l_nr >{' ,'< se mapping from this numbers to the
(max. 1000 serial_nr)
ria l_n r>} 999' ) sectors of the ViewRight STB clients,
where the entitlement or the group
keys are stored.
The serial numbers are separated with
commas ','. The parentheses '(' and ')'
indicate the start and the end of the list
and therefore are mandatory.

Within the braces '{' and '}' are further


serial numbers of other ViewRight STB
clients (optional).
<se ria l_n r> 10 digits Serial number of a ViewRight STB
client (without the 'Luhn' control digit).
The BCSM makes the mapping from
this number to the sector of the
ViewRight STB client, where the
entitlement or the group keys are
stored.
<se cto r_n r> 0 .. 255 Sector number of a ViewRight STB
client
<pr odu ct_ list > 'list of products, each List of names of products.
= with 10 chars The products are separated with
'(' <pr odu ct>{ ',' <pr od
(max. 32 products) commas ','. The parentheses '(' and ')'
uct >}3 1')
indicate the start and the end of the list
and therefore are mandatory.
Within the braces '{' and '}' are further
products (optional).
<pr odu ct> max. 10 chars Name of a product.
<PI N_l ist > 'list of PINs with their List of indices and PINs.
= ' ('< PIN _no> '=' <PI N> indices The indices and their belonging PINs
{', '<P IN_ no>' ='< PIN >}
(max. 4 PINs) are separated with commas ','. The
3')
parentheses '(' and ')' indicate the start
and the end of the list and therefore
are mandatory.
Within the braces '{' and '}' are further
indices and PINs (optional).

Subscriber Management System Interface 2-13


ENG-59 / Revision 1
Table 2-3. Values for Parameters

Parameter# Value Comment

< PIN _no> 1 digit Identifier of the used PIN index


(Table 2-1 on page 2-3).
< PIN > 4 digits Pin code.
< SMS _ope rat or> 6 digits Identification of a SMS.
< tri gger ed_ pro duct _li 'list of List of products which are triggered.
s t> triggered_products The triggered_products are separated
=
(max. 31 products) with commas ','. The parentheses '('
' ('< trig ger ed_ prod uct
> {', ' and ')' indicate the start and the end of
< tri gger ed_ pro duct >}3 the list and are therefore mandatory.
1 ') Within the braces '{' and '}' are further
triggered_products (optional).
< tri gger ed_ pro duct > 'Each triggered_product comprise the
= parameter <product>, <start_trailer>,
< pro duct >'[ '<s tart _tr <start_product> and <end_product>.
a ile r>', '
These parameters are all mandatory.
< sta rt_p rod uct >','
< end _pro duc t>' ]

< sta rt_t rai ler > [YYYYMMDDHHMISS] UTC DateTime of the beginning of the
period to be generated: 14 digits ASCII
decimal characters.
< sta rt_p rod uct > [YYYYMMDDHHMISS] UTC DateTime of the beginning of the
period to be generated: 14 digits ASCII
decimal characters.
The value of <start_product> has to be
equal or greater than the value for
<start_trailer>.
< end _pro duc t> [YYYYMMDDHHMISS] UTC DateTime of the beginning of the
period to be generated: 14 digits ASCII
decimal characters.
The value of <end_product> has to be
greater than the value for
<start_product>.
Y YYY 4 digits 4 digits ASCII year number (e.q. 2002)
MM 2 digits (1-12) 2 digits ASCII month number (e.q. 08)
DD 2 digits (1-31) 2 digits ASCII day number (e.q. 15)
HH 2 digits (0-23) 2 digits 24 hours format ASCII hour
number (e.q. 18)
MI 2 digits (0-59) 2 digits ASCII minutes number
SS 2 digits (0-59) 2 digits ASCII seconds number

2-14 Subscriber Management System Interface


ENG-59 / Revision 1
Table 2-3. Values for Parameters

Parameter# Value Comment

<cy cle _du rati on> 'ONCE' 'Defines the cycle duration of the
| <minutes_dur> resulting EMM in minutes. ONCE
means immediate playout. FOREVER
| 'FOREVER implies no endtime for cycle.
Note: The cycle frequency depends on
the configuration of the BCSM for this
EMM type.
<mi nut es_ dur> 1 .. 65536
<po s_n eg> 'POS' | 'NEG 'Positive or negative mode. POS
means at least one of the products in
the product list applies. NEG means
none of the products in the product list
applies.
<ms g_i d> 0 .. 268435455 Identifies the OSM message
<ch at_ id> 0 .. 15 Identifies the chat channel
<tx t_i nde x> 0 .. 15 Identifies the text download
<di alo g_t ext> = 'Max. 160 characters Text to be displayed/downloaded.
'<c har act ers or Allowed characters are 0x20..0x7E
met ach ara cter s> and 0xA0..9xFE.The possible meta
character are described in section
2.8.5
<os m_d esc ript or> =
'(' <di spl ay_m ode >', '
<di spl ay_ dura tio n>' ,'
<x_ ori gin >','
<x_ pos iti on>' ,'
<x_ anc hor >','
<y_ ori gin >','
<y_ pos iti on>' ,'
<y_ anc hor >','
<te xt_ ali gn>' ,'
<bg _co lor >','
<bg _co lor >','
<al pha >
')’

Subscriber Management System Interface 2-15


ENG-59 / Revision 1
Table 2-3. Values for Parameters

Parameter# Value Comment

< dis play _mo de> 'FX_NEXTSTB' 'display mode. FX indicates, that the
| 'RM_NEXTSTB' OSM cannot be removed by the user,
while RM means the user can remove
| 'FX_NEXTCA' the OSM using the Remote Control.
| 'RM_NEXTCA' NEXTSTB means, the OSM is
| 'FX_STILLCA' displayed together with the next
| 'RM_STILLCA' message shown on the screen.

| 'FX_IMMED' NEXTCA means the OSM is displayed


together with the next message
| 'RM_IMMED triggered from the CA-subsystem
shown on the screen.
STILLCA means the OSM is displayed
together with the next message
triggered from the CA-subsystem
shown on the screen and as long as
this message is displayed.
IMMED means the OSM is displayed
without any further condition
immediately.
< dis play _du rat ion> 0 .. 65535 Display duration in seconds; 0 means
no duration, forever
< x_o rigi n> 'ORIGL' | 'ORIGR 'X-Origin left or right
< x_p osit ion > 0 .. 4095 X-Coordinate with respect to the X-
Origin. If X-Origin is right, the real
position is calculated to 4095-
x_position
< x_a ncho r> 'CENTER' 'X-Anchor. For details ref to Error!
| 'AUTOLR Reference source not found.

< y_o rigi n> 'ORIGTOP' | 'ORIGDWN 'Y-Origin left or right


< y_p osit ion > 0 .. 1023 Y-Coordinate with respect to the Y-
Origin. If Y-Origin is down, the real
position is calculated to 1023-
x_position
< y_a ncho r> 'CENTER' 'Y-Anchor. For details ref to Error!
| 'AUTOTD Reference source not found.

< tex t_al ign > 'LEFT' 'Text alignment


| 'RIGHT'
| 'CENTER'
| 'JUST

2-16 Subscriber Management System Interface


ENG-59 / Revision 1
Table 2-3. Values for Parameters

Parameter# Value Comment

<bg _co lor > 'NOBG ' 'Background color. The colors are
| 'BGCOL1' depending on the look and feel of the
set top box and might be defined by
| 'BGCOL2' the operator together with the set top
| 'BGCOL3' box manufacturer. The color-system
| 'BGCOL4' should be hoosen in a way, that all
combinations of foreground color and
| 'BGCOL5' background color are readable on the
| 'BGCOL6' screen.
| 'BGCOL7'
| 'BGCOL8'
| 'BGCOL9'
| 'BGCOL10'
| 'BGCOL11'
| 'BGCOL12'
| 'BGCOL13'
| 'BGCOL14'
| 'BGCOL15
<al pha > 'OPAQ' 'Transparency. OPAQ means no-
| 'TRANSP1' transparency, TRANSP15 is most
transparency. The transparency
| 'TRANSP2' should hold for foreground and
| 'TRANSP3' background in the same way.
| 'TRANSP4'
| 'TRANSP5'
| 'TRANSP6'
| 'TRANSP7'
| 'TRANSP8'
| 'TRANSP9'
| 'TRANSP10'
| 'TRANSP11'
| 'TRANSP12'
| 'TRANSP13'
| 'TRANSP14'
| 'TRANSP15
<re gio n_n ame> = 'Max. 10 characters Region name as it is defined in the
'<c har act ers> region-table in the CAS database

byt e8_ box _id 2-16 hex-digits


Hex -di git [ 0 -9 A- Fa - f]

Subscriber Management System Interface 2-17


ENG-59 / Revision 1
Dialog Text Meta Characters
Table 2-4. Meta Characters

Meta character Description

\n newline character

\ f0 0 . .. \f 15 font shape selection

\ c0 0 . .. \c 15 font color selection

\ s0 0 . .. \s 15 font size selection

\ bf switch to boldface

\ it switch to italics

\ ul switch to underline

\ up typeset exponents

\ dn typeset indices

\ pl switch to plain text

\ SC include SmartCard number

\ CA M include CAM number

\ ST B include STB number

\ CI D include CA-ID number

\ VE R include Version number

\ T0 0 . .. \T 15 include download text with index 0 .. 15 (see TXD


commands)

\\ Backslash '\

\ 'Single quote

\ 0x H H hex byte HH

Syntax of the return message


There are four cases of return messages:
 acknowledgment of a registration command
 acknowledgment of a correct SMS command
 return message as answer to a shutdown command
 error message for an incorrect SMS command.
'Correct' means, no syntactical errors have occurred and the values of the parameters are
valid or existing in the database.
The general syntax of an acknowledge of registration command looks like this:
< me s sa ge _ nu mb er > ', 0, re g is tr a ti on _O K \n '

2-18 Subscriber Management System Interface


ENG-59 / Revision 1
The general syntax of a return message as answer to a shutdown command looks like this:
<m e ss ag e_ n um be r >' ,0 ,s h ut do wn \ n'
The general syntax of an acknowledge of a correct SMS command looks like this:
<m e ss ag e_ n um be r >' ,0 [, ' <o pt io n al t e xt >] '\ n '
The general syntax of an error message looks like this:
<m e ss ag e_ n um be r >' ,' <e r ro r_ co d e> ', ' <e rr or _ me ss ag e >' \n '
There is no return message for a HOLDTL command.

Error_code
The error_code indicates the type of error which has occurred:

Table 2-5. Description of the error_codes

Command Syntax

0 No error

10 0 0 Syntactical error

11 0 0 Missing parameter

12 0 0 Unknown command

20 0 0 SMS operator is not allowed to send this command

21 0 0 SMS operator is not allowed to make an entitlement for this product

30 0 0 Wrong parameter (e.g. ViewRight STB client not found)

40 0 0 Error of the BCSM

90 0 0 Failure of the registration

Error_message
The error_message is a detailed (textual) description of the error which occurred.
In case of an error within a list of products or a list of ViewRight STB clients, the
error_message indicates the incorrect item.

Subscriber Management System Interface 2-19


ENG-59 / Revision 1
2-20 Subscriber Management System Interface
ENG-59 / Revision 1
Chapter 3

Examples for SMS Commands

This chapter shows one or more examples for all SMS commands and shows examples of
error messages.
The syntax of each command is shown below the examples.

Online commands

IMPENT
Immediate Product Entitlement (for a list of products)
Syntax:
<m e ss ag e_ n r> ', I MP EN T, ' <s er ia l _n r> ' ,' <p ro d uc t_ li s t> '\ n '
Example for an entitlement of a ViewRight STB sector for one product:
1, I MP EN T, 1 23 45 6 78 90 ,( P RO D0 1) \ n
Example for an entitlement of a ViewRight STB sector for tree products:
2, I MP EN T, 1 23 45 6 78 90 ,( P RO D0 1, P RO D0 2 ,P RO D0 3 )\ n

IMPDEL
Immediate Product Deletion (for a list of products)
Syntax:
<m e ss ag e_ n r> ', I MP DE L, ' <s er ia l _n r> ' ,' <p ro d uc t_ li s t> '\ n '
Example for a deletion of one product from a ViewRight STB sector:
3, I MP DE L, 1 23 45 6 78 90 ,( P RO D0 1) \ n
Example for a deletion of tree products from a ViewRight STB sector:
4, I MP DE L, 1 23 45 6 78 90 ,( P RO D0 1, P RO D0 2 ,P RO D0 3 )\ n

Subscriber Management System Interface 3-1


ENG-59 / Revision 1
IMSENT
Immediate Product Entitlement (for a list of ViewRight STBs)
Syntax:
< me s sa ge _ nr >' ,I M SE NT ,' < pr od u ct >' ,' < se ri al _ nr _l i st >' \n '
Example for an entitlement of a product for a sector of one ViewRight STB:
5 ,I M SE NT , PR OD 01 , (1 23 45 6 78 90 ) \n
Example for an entitlement of a product for a sector of two ViewRight STBs:
6 ,I M SE NT , PR OD 01 , (1 23 45 6 78 90 , 12 34 56 7 89 1) \n

IMSDEL
Immediate Product Deletion (for a list of STBs)
Syntax:
< me s sa ge _ nr >' ,I M SD EL ,' < pr od u ct >' ,' < se ri al _ nr _l i st >' \n '
Example for an deletion of a product for a sector of one ViewRight STB:
7 ,I M SD EL , PR OD 01 , (1 23 45 6 78 90 ) \n
Example for an deletion of a product for a sector of two ViewRight STBs:
8 ,I M SD EL , PR OD 01 , (1 23 45 6 78 90 , 12 34 56 7 89 1) \n

IMDALL
Immediate Deletion of all entitled products
Syntax:
< me s sa ge _ nr >' ,I M DA LL ,' < se ri a l_ nr >' \ n'
9 ,I M DA LL , 12 34 56 7 89 0\ n

IMCALL
Immediate Clearing of all products, master/slave relations and pairing information.
Syntax:
< me s sa ge _ nr >' ,I M CA LL ,' < se ri a l_ nr >' \ n'
9 ,I M CA LL , 12 34 56 7 89 0\ n

3-2 Subscriber Management System Interface


ENG-59 / Revision 1
IMPINR
Immediate reset of all PIN values
Syntax:
<m e ss ag e_ n r> ', I MP IN R, ' <s er ia l _n r> ' \n '
10 , IM PI NR , 12 34 5 67 89 0\ n

IMPINS
Immediate reset of a PIN
Syntax:
<m e ss ag e_ n r> ', I MP IN S, ' <s er ia l _n r> ' ,' <P IN _ li st >' \ n'
Example of the reset of the PIN with index 1 ("Parental Control/IPPV"):
11 , IM PI NS , 12 34 5 67 89 0, ( 1= 43 21 ) \n
Example of the reset of the PINs with index 1 and 3:
11 , IM PI NS , 12 34 5 67 89 0, ( 1= 43 21 , 3= 12 3 4) \n

IMKSET
Immediate G-Key Set
Syntax:
<m e ss ag e_ n r> ', I MK SE T, ' <s er ia l _n r> ' \n '
12 , IM KS ET , 12 34 5 67 89 0\ n

Subscriber Management System Interface 3-3


ENG-59 / Revision 1
Offline commands

CYPENT
Cyclic Product Entitlement (for a list of products)
Syntax:
< me s sa ge _ nr >' ,C Y PE NT ,' < se ri a l_ nr >' , '< pr od u ct _l i st >' \n '
Example for an entitlement of a ViewRight STB sector for one product:
1 3, C YP EN T ,1 23 45 6 78 90 ,( P RO D0 1 )\ n
Example for an entitlement of a ViewRight STB sector for tree products:
1 4, C YP EN T ,1 23 45 6 78 90 ,( P RO D0 1 ,P RO D0 2 ,P RO D0 3 )\ n

CYPDEL
Cyclic Product Deletion (for a list of products)
Syntax:
< me s sa ge _ nr >' ,C Y PD EL ,' < se ri a l_ nr >' , '< pr od u ct _l i st >' \n '
Example for a deletion of one product from a ViewRight STB sector:
1 5, C YP DE L ,1 23 45 6 78 90 ,( P RO D0 1 )\ n
Example for a deletion of tree products from a ViewRight STB sector:
1 6, C YP DE L ,1 23 45 6 78 90 ,( P RO D0 1 ,P RO D0 2 ,P RO D0 3 )\ n

CYSENT
Cyclic Product Entitlement (for a list of ViewRight STBs)
Syntax:
< me s sa ge _ nr >' ,C Y SE NT ,' < pr od u ct >' ,' < se ri al _ nr _l i st >' \n '
Example for an entitlement of a product for a sector of one ViewRight STB:
1 7, C YS EN T ,P RO D0 1 ,( 12 34 5 67 89 0 )\ n
Example for an entitlement of a product for a sector of two ViewRight STBs:
1 8, C YS EN T ,P RO D0 1 ,( 12 34 5 67 89 0 ,1 23 45 6 78 91 )\ n

3-4 Subscriber Management System Interface


ENG-59 / Revision 1
CYSDEL
Cyclic Product Deletion (from a list of sectors)
Syntax:
<m e ss ag e_ n r> ', C YS DE L, ' <p ro du c t> ', ' <s er ia l _n r_ li s t> '\ n '
Example for an deletion of a product for a sector of one ViewRight STB:
19 , CY SD EL , PR OD 0 1, (1 23 4 56 78 90 ) \n
Example for an deletion of a product for a sector of two ViewRight STBs:
20 , CY SD EL , PR OD 0 1, (1 23 4 56 78 90 , 12 34 5 67 89 1) \ n

CYKSET
Cyclic G-Key Set
Syntax:
<m e ss ag e_ n r> 'C Y KS ET ,' < se ri al _ nr >' \ n'
21 , CY KS ET , 12 34 5 67 89 0\ n

Additional Commands

REGIST
Registration command
Syntax:
<m e ss ag e_ n r> ', R EG IS T, ' <S MS _o p er at o r> '\ n'
Example for the registration of SMS_operator number 12:
22 , RE GI ST , 00 00 1 2\ n

SHTDWN
Shutdown
Syntax:
<m e ss ag e_ n um be r >' ,S HT D WN \n '
23 , SH TD WN \ n

Subscriber Management System Interface 3-5


ENG-59 / Revision 1
HOLDTL
Hold the line
Syntax:
< me s sa ge _ nu mb er > ', HO LD T L\ n'
2 4, H OL DT L \n

PROTRI
Trigger for generation of EMMs
Syntax:
< me s sa ge _ nu mb er > ', PR OT R I, '< t ri gg er e d_ pr od u ct _l i st >' \n '
Example for a trigger for one product:
2 5, P RO TR I ,( PP V0 0 7[ 20 03 0 50 62 1 10 00 ,2 0 03 05 06 2 11 50 0 ,2 00 30 5 06 23 15 0 0] )
Example for a trigger of three products:
2 6, P RO TR I ,( PP V0 0 7[ 20 03 0 50 62 1 10 00 ,2 0 03 05 06 2 11 50 0 ,2 00 30 5 06 23 15 0 0] ,
P PV 0 08 [2 0 03 05 06 2 21 00 0, 2 00 30 5 06 22 15 0 0, 20 03 0 50 70 0 15 00 ], P PV 00 8
[ 20 0 30 50 6 23 10 00 , 20 03 05 0 62 31 5 00 ,2 00 3 05 07 01 1 50 0] )

3-6 Subscriber Management System Interface


ENG-59 / Revision 1
OSM Commands

INDOSM
Individual addressed OSM
Example with a default OSM descriptor:
28 , IN DO SM , 12 34 5 67 89 0, 3 ,O NC E, 1 0, 's e ct or 3 , m sg i d 1 0' \ n
Example with a full OSM descriptor:
29 , IN DO SM , 12 34 5 67 89 0, 3 ,6 0, (F X _I MM E D, 60 0, O RI GL ,2 0 00 ,C E NT ER ,O R IG TO P, 1 00
0, C EN TE R, LE FT , NO BG ,O P AQ ), 10 , 's ec t or 3 , 6 0 mi nu t es , m sg i d 1 0' \n

APFOSM
universal addressed OSM with positive product filter
Example with a default OSM descriptor:
30 , AP FO SM , 12 34 5 67 89 0, 3 ,F OR EV E R, 10 , 's ec to r 3 , ms g i d 1 0' \n
Example with a full OSM descriptor with negative product filter:
31 , AP FO SM , 12 34 5 67 89 0, 3 ,O NC E, N EG ,( P PC 00 0, P PC 00 1) ,
(F X _N EX TC A ,0 ,O R IG L, 40 9 5, AU TO , OR IG D WN ,0 ,A U TO TD ,R I GH T, B GC OL 1, T RA NS P1 5 ),
10 , 's ec to r 3 , m sg i d 1 0' \n

DELOSM
OSM deletion
Example for deletion of message 10:
32 , DE LO SM , 12 34 5 67 89 0, 3 ,1 0\ n

ALLTXD
universal addressed text download
Example with a text download for index 5:
40 , AL LT XD , 12 34 5 67 89 0, 3 ,6 0, 5, ' Te xt d ow nl oa d '\ n

DELTXD
Text Download deletion
Example with a text download deletion for index 5:
41 , DE LT XD , 12 34 5 67 89 0, 3 ,5 \n

Subscriber Management System Interface 3-7


ENG-59 / Revision 1
Chat Commands

CHTROM
Define a text message to display the name of the chat-room for chat nr 1:
5 3, C HT RO M ,1 23 45 6 78 90 ,1 , 'S po r ts d is c us si on ' \n

CHTTXT
Define a text message to display the corresponding chat-lines for chat nr 1 displaying textline
1 and textline 2:
5 3, C HT TX T ,1 23 45 6 78 90 ,1 , 'T es t -C ha t\ n \T 01 \n \ T0 2\ n '\ n

CHTLIN
Defines the textline 1 for chat 1 using product PROD01:
5 4, C HT LI N ,1 23 45 6 78 90 ,( P RO D0 1 ), 1, 1, ' Th is i s t he te xt f r om a c h at
m em b er '\ n

CHTDEL
Delete text message for chat nr 1:
5 3, C HT DE L ,1 23 45 6 78 90 ,1 \n

CHTDLI
Delete textline 1 for chat 1:
5 4, C HT LI N ,1 23 45 6 78 90 ,1 , 1 \n

3-8 Subscriber Management System Interface


ENG-59 / Revision 1
Paring Commands

ADDPBX
Add the set top box with id 0x1234567890ABCDEF to the list of set top boxes:
55 , AD DP BX , 12 34 5 67 89 0A B CD EF \n

PAIRSC
Pairs the set top box with the id 0x1234567890ABCDEF to the ViewRight STB with id
0123456789:
56 , PA IR SC , 01 23 4 56 78 9, 1 23 45 67 8 90 AB C DE F\ n

UNPAIR
Unpairs the set top box with the id 0x1234567890ABCDEF from the ViewRight STB with id
0123456789:
57,UNPAIR,0123456789,1234567890ABCDEF\n
Unpairs the set top box with the id 0x1234567890ABCDEF from all paired ViewRight STBs:
57,UNPAIR,,1234567890ABCDEF\n
Unpairs the smartcard with id 0123456789 from all paired set top boxes:
57,UNPAIR,0123456789,\n

GTPAIR
Retrieves the pairing status between set top box id 0x1234567890ABCDEF and ViewRight
STB id 0123456789:
57 , GT PA IR , 01 23 4 56 78 9, 1 23 45 67 8 90 AB C DE F\ n
Possible answers:
57 , 0, pa ir e d\ n
57 , 0, no t p ai re d \n
Retrieves the pairing status of ViewRight STB id 0123456789:
57 , GT PA IR , 01 23 4 56 78 9, \ n
Possible answers:
57 , 0, bo x 1 23 45 6 78 90 AB C DE F: \n
57 , 0, bo x 1 23 45 6 78 90 AB C DE F: 1 2 34 56 7 89 0\ n
57 , 0, bo x 1 23 45 6 78 90 AB C DE F: 1 2 34 56 7 89 0, 12 3 45 67 00 0 \n

Subscriber Management System Interface 3-9


ENG-59 / Revision 1
Retrieves the pairing status of set top box id 0x1234567890ABCDEF:
5 7, G TP AI R ,, 12 34 5 67 89 0A B CD EF \ n
Possible answers:
5 7, 0 ,s ma r tc ar d 1 23 45 67 8 90 :\ n
5 7, 0 ,s ma r tc ar d 1 23 45 67 8 90 : 1 23 45 67 8 90 AB CD E F\ n
5 7, 0 ,s ma r tc ar d 1 23 45 67 8 90 : 1 23 45 67 8 90 AB CD E F, 12 3 45 67 89 0 AB CF FF \ n
Note that the error code of a GTPAIR command is always 0 and does not reflect the pairing
state.

Master Slave Commands

JOINMS
Define ViewRight STB with id 0123456789 to be master and ViewRight STB with id
0123456788 to be slave:
5 8, J OI NM S ,0 12 34 5 67 89 ,( 0 12 34 5 67 88 )\ n

UNJOIN
Unjoin ViewRight STB with id 0123456788 to no longer be slave:
5 9, U NJ OI N ,( 01 23 4 56 78 8) \ n

Examples of return messages

Example of an acknowledge of a correct SMS command:


Syntax:
< me s sa ge _ nu mb er > ', 0> \n '
Return message to the SMS command with message number '1':
1 ,0 \ n

Example of a return message as answer to a registration command:


Syntax:
< me s sa ge _ nu mb er > ', 0, re g is tr a ti on _O K \n '
2 2, 0 ,r eg i st ra ti o n_ OK \n

3-10 Subscriber Management System Interface


ENG-59 / Revision 1
Example of a return message as answer to a shutdown command:
Syntax:
<m e ss ag e_ n um be r >' ,0 ,s h ut do wn \ n'
23 , 0, sh ut d ow n\ n

Examples of error messages:


Syntax of the return message:
<m e ss ag e_ n um be r >' ,' <e r ro r_ co d e> ', ' <e rr or _ me ss ag e >' \n '
After receiving one product within a list of products which can not be handled the parsing of
the command will be aborted. The products from the start of the list to the defective product
are processed correct. All following products are not processed at all. The resulting error
message shows (only) the defective product, even if more than this product are defective.
SMS command:
2, I MP EN T, 0 ,( pr o du ct 1, p ro du ct 2 ,p ro d uc t3 )\ n
Return message:
2, 1 00 0, SE R IA L N UM BE R: to ke n t oo s h or t\ n
SMS command:
2, I MP EN T, ( pr od u ct 1, pr o du ct 2, p ro du c t3 )\ n
Return message:
2, 1 10 0, mi s si ng se ri al nu mb er \ n
SMS command:
2, A BC DE F, 1 23 45 6 78 90 ,( p ro du ct 1 ,p ro d uc t2 ,p r od uc t3 ) \n
Return message:
2, 1 20 0, un k no wn co mm an d \n
SMS command:
2, I MP EN T, 0 00 00 0 00 00 ,( p ro du ct 1 ,p ro d uc t2 ,p r od uc t3 ) \n
Return message:
2, 2 00 0, sm a rt ca r d 00 00 0 00 00 0 d oe s n ot e xi s t\ n
SMS command:
2, G TP AI R, 0 00 00 0 00 00 ,1 2 34 56 78 9 0A BC D EF \n
Return message:
2, 3 00 0, bo x i d 1 23 45 67 8 90 AB CD E F do e s no t e xi st \n
SMS command:
2, R EG IS T, 0 00 00 4 \n
Return message:

Subscriber Management System Interface 3-11


ENG-59 / Revision 1
2 ,9 0 00 ,r e gi st ra t io n_ no t _O K: _ wr on g_ S MS _o pe r at or : 4 \n
Here are missing the error_messages for example if only a part of a product_list is missing.
These messages will be included in this document after the implementation within the BCSM.

3-12 Subscriber Management System Interface


ENG-59 / Revision 1
Chapter 4

Abbreviations

Table 5:

ASCII A(merican) S(tandard) C(ode for) I(nformation) I(nterchange)

BCSM B(roadcast) C(ontent) S(ecurity) M(anager)

EMM E(ntitlement) M(anagement) M(essage)

ID ID(entifier)

ISDN I(ntegrated) S(ervices) D(igital) N(etwork)

MPEG M(oving) P(ictures) E(xperts) G(roup)

OSM O(n) S(creen) M(essage)

PIN P(ersonal) I(dentification) N(umber)

SMS S(ubscriber) M(anagement) S(ystem)

TCP/IP T(ransport) C(ontrol) P(rotocol) / I(nternet) P(rotocol)

VCAS for DVB V(ideo) C(ertificate) A(uthority) S(erver) for D(igital) V(ideo)
B(roadcasting)

ViewRight STB for ViewRight S(et) T(op) B(ox) for D(igital) V(ideo) B(roadcasting)
DVB

Subscriber Management System Interface 4-1


ENG-59 / Revision 1
4-2 Subscriber Management System Interface
ENG-59 / Revision 1

Das könnte Ihnen auch gefallen