User's Manual

EMS User Manual-v2.0.0
Introduction
Kailash EMS is used to manage a network of Broadcast Radio Heads (hereafter referred to as BRH). The
management comprises of following:
- Fault Monitoring
- Configuration
- Accounting
- Provisioning
- Security
This confirms with the traditional FCAPS model for management of telecom networks. Details of
workflow and how the above model is available to the user is described in the following sections.
For any queries related to this document or operation of EMS, please contact the EMS Support using the
Email address provided in the “About” Section of the web page. The EMS Support Contact Email address
is support-ems@saankhyalabs.com .
Model Description
The following subsections detail the FCAPS aspect in an order which is relevant from the workflow point
of view
Security
EMS Security mainly comprises of two parts -
1. Secure communication between BRH Devices and EMS . This is achieved using TLS based security
for communication between a BRH device and EMS and a client authentication using client side
certificates.
2. Security of EMS is provided through role based access control and audit logging of user initiated
actions. For EMS, role based access control determines which actions can be performed by a
user belonging to a given role. An overview of different roles is provided below and Appendix A
details the complete capability matrix for individual roles.
There are three main roles in EMS
a. Owner - Owner is an owner of all the devices and is like Super Administrator having all
the required privileges to perform actions.
b. Administrator (admin) - This role is a high privilege role in EMS and is capable of
performing major provisioning and other actions that require elevated privileges (eg.
Uploading a firmware version to be upgraded across devices.)
c. Operator (operator) - This role is having lowest privilege levels and is mainly concerned
with day to day operation of devices. This role is allowed to take only a minimum set of
actions against devices in BRH EMS like acknowledging alarm notifications etc.
The above is better understood from the following hierarchy. Any operation that modifies or
tries to view data at level higher in hierarchy is not allowed
Copyright Saankhya Labs Private Ltd, Bangalore 3