IPTV COE

Customer Experience Management System

Design Specifications
Version 1.0

Feb 15, 2011

Author(s)
TATA Consultancy Services Ltd

This document of is prepared Customer Experience Management and is for restricted circulation.
No part of this publication may be reproduced, stored in a retrieval system without permission of
TCS

Revision History
Revision Effective Comments/Revision Created By Reviewed By
Date Details
1
2
3
4
Contents
1 INTRODUCTION 6
1.1 Definitions, Acronyms and Abbreviations......................................................................7
1.2 References.................................................................................................................... 7
1.3 Intended Audience......................................................................................................... 7
1.4 System Requirements................................................................................................... 7
1.4.1 Hardware Requirements:..........................................................................................7
1.4.2 Software Requirements:............................................................................................7
1.5 Project Responsibilities.................................................................................................. 8
2 DESIGN OVERVIEW 9
2.1 Technical Architecture................................................................................................... 9
3 SCREEN DETAILS 11
3.1 Home Page.................................................................................................................. 11
3.1.1 Screen Description.................................................................................................. 11
3.1.2 Work Flow............................................................................................................... 11
3.1.3 Screen Layout......................................................................................................... 12
3.1.4 Tables accessed..................................................................................................... 12
3.1.5 Screen Functionality................................................................................................ 13
3.1.6 Screen GUI Field description..................................................................................13
3.2 Manage Projects -> Create Project..............................................................................14
3.2.1 Screen Description.................................................................................................. 14
3.2.2 Work Flow............................................................................................................... 15
3.2.3 Screen Layout......................................................................................................... 15
3.2.4 Tables accessed..................................................................................................... 16
3.2.5 Screen Functionality................................................................................................ 17
3.2.6 Screen GUI Field description..................................................................................18
3.3 Manage Projects -> Edit Project..................................................................................19
3.3.1 Screen Description.................................................................................................. 19
3.3.2 Work Flow............................................................................................................... 20
3.3.3 Screen Layout......................................................................................................... 21
3.3.4 Tables accessed..................................................................................................... 21
3.3.5 Screen Functionality................................................................................................ 22
3.3.6 Screen GUI Field description..................................................................................22
3.4 Manage Projects -> Allocate Resource.......................................................................23
3.4.1 Screen Description.................................................................................................. 23
3.4.2 Work Flow............................................................................................................... 24
3.4.3 Screen Layout......................................................................................................... 24
3.4.4 Tables accessed..................................................................................................... 25
3.4.5 Screen Functionality................................................................................................ 26
3.4.6 Screen GUI Field description..................................................................................26
3.5 Manage Projects -> Cancel Project.............................................................................27
3.5.1 Screen Description.................................................................................................. 27
3.5.2 Work Flow............................................................................................................... 27
3.5.3 Screen Layout......................................................................................................... 28
3.5.4 Tables accessed..................................................................................................... 28
3.5.5 Screen Functionality................................................................................................ 29
3.5.6 Screen GUI Field description..................................................................................29
3.6 Resource Management-> Add New Resource............................................................30
3.6.1 Screen Description.................................................................................................. 30
3.6.2 Work Flow............................................................................................................... 30
3.6.3 Screen Layout......................................................................................................... 30
3.6.4 Tables accessed..................................................................................................... 31
3.6.5 Screen Functionality................................................................................................ 31
 3.6.6 Screen GUI Field description..................................................................................32
3.7 Resource Management -> Modify Resource...............................................................32
3.7.1 Screen Description.................................................................................................. 32
3.7.2 Work Flow............................................................................................................... 33
3.7.3 Screen Layout......................................................................................................... 34
3.7.4 Tables accessed..................................................................................................... 34
3.7.5 Screen Functionality................................................................................................ 34
3.7.6 Screen GUI Field description..................................................................................35
3.8 Resource Management -> Delete Resource................................................................36
3.8.1 Screen Description.................................................................................................. 36
3.8.2 Work Flow............................................................................................................... 36
3.8.3 Screen Layout......................................................................................................... 37
3.8.4 Tables accessed..................................................................................................... 37
3.8.5 Screen Functionality................................................................................................ 37
3.8.6 Screen GUI Field description..................................................................................38
3.9 Reports -> Individual Workload Report........................................................................38
3.9.1 Screen Description.................................................................................................. 38
3.9.2 Work Flow............................................................................................................... 39
3.9.3 Tables accessed..................................................................................................... 39
3.9.4 Screen Functionality................................................................................................ 40
3.9.5 Screen GUI Field description..................................................................................40
3.10 Reports -> Project Resource Report............................................................................41
3.10.1 Screen Description............................................................................................. 41
3.10.2 Work Flow........................................................................................................... 41
3.10.3 Screen Layout..................................................................................................... 42
3.10.4 Tables accessed................................................................................................. 42
3.10.5 Screen Functionality........................................................................................... 43
3.10.6 Screen GUI Field description..............................................................................43
3.11 Reports -> Mega Program Workload Report...............................................................44
3.11.1 Screen Description............................................................................................. 44
3.11.2 Work Flow........................................................................................................... 44
3.11.3 Screen Layout..................................................................................................... 45
3.11.4 Tables accessed................................................................................................. 45
3.11.5 Screen Functionality........................................................................................... 46
3.11.6 Screen GUI Field description..............................................................................46
3.12 Reports -> Department Workload Report....................................................................47
3.12.1 Screen Description............................................................................................. 47
3.12.2 Work Flow........................................................................................................... 47
3.12.3 Screen Layout..................................................................................................... 48
3.12.4 Tables accessed................................................................................................. 48
3.12.5 Screen Functionality........................................................................................... 49
3.12.6 Screen GUI Field description..............................................................................49
3.13 Reports -> RAMP Report............................................................................................. 50
3.13.1 Screen Description............................................................................................. 50
3.13.2 Work Flow........................................................................................................... 50
3.13.3 Screen Layout..................................................................................................... 51
3.13.4 Screen Functionality........................................................................................... 52
3.13.5 Screen GUI Field description..............................................................................52
3.14 My Links -> My Allocations..........................................................................................53
3.14.1 Screen Description............................................................................................. 53
3.14.2 Work Flow........................................................................................................... 53
3.14.3 Screen Layout..................................................................................................... 54
3.14.4 Tables accessed................................................................................................. 54
3.14.5 Screen Functionality........................................................................................... 55
3.14.6 Screen GUI Field description..............................................................................55
3.15 My Links ->My Workload Report..................................................................................56
 3.15.1 Screen Description............................................................................................. 56
3.15.2 Work Flow........................................................................................................... 56
3.15.3 Screen Layout..................................................................................................... 56
3.15.4 Tables accessed................................................................................................. 57
3.15.5 Screen Functionality........................................................................................... 58
3.15.6 Screen GUI Field description..............................................................................58
4 DATABASE DESIGN 59
4.1 RMS_RES_DTLS........................................................................................................ 59
4.2 RMS_PROJ_DTLS...................................................................................................... 60
4.3 RMS_PROJ_PHASE_DTLS........................................................................................ 61
4.4 RMS_RES_ALLOC_DTLS.......................................................................................... 62
4.5 RMS_ERROR_DTLS................................................................................................... 63
4.6 RMS_PHASE_MONTH_DTLS....................................................................................63
4.7 RMS_USR_ACCESS_DTLS.......................................................................................64
4.8 Entity relationship Diagram.......................................................................................... 65
5 TRACEABILITY MATRIX 66
1 Introduction
Customer Experience Management System is a value added service to the IPTV customers by
the service providers. Customer Experience Management System allows the customer to log the
complaint against the current problem by selecting the problem details, channel details and
timings. Customer is given the privilege of raising a complaint against today’s and yesterday’s
problem. Every complaint logged is given an ID for tracking purpose. Customer Experience
Management System avoids making calls to service provider every time there’s some problem.
Customer can log a complaint easily by selecting from the list of problems. Customer Experience
Management System is designed and developed in ASP.Net using Mediaroom controls.

Implemented Functionality:

i. Customer is given the choice of raising a complaint for the problem that occurred
yesterday or today.
ii. Problem areas are listed for the customer to select.
iii. Based on the problem area selected, Problem descriptions are listed for the customer to
select.
iv. List of Channels along with search option to search channel is provided.
v. Once the channel is selected, the channel along with program timings is listed for the
customer to select.
vi. Once the timing is selected, the STB, Network trace is taken and a list of options to try is
displayed.
vii. If the Problem still exists, then the customer can log complaint and is provided with
complaint Id.

This document describes the high level design for Customer Experience Management System.

1.1 Intended Audience

 TCS Customer Experience Management project team

1.2 System Requirements

Following are minimum recommended system configurations required.

1.2.1 Hardware Requirements:

 Windows Server 2003 Service Pack 2
 Intel Xeon(TM) CPU 3.60 GHz
 4.00 GB RAM
 40GB Hard disk
 Tatung STB dev 2000
 CISCO 2820 / 3860 Router supporting Multicast
 PCI NIC – 2 No’s

1.2.2 Software Requirements:

 Microsoft visual studio 2005
 SQL server 2005, SP2
 Microsoft presentation framework, Part of ADK (Application Dev. Kit 2.1 )
 Media Room (IPTV) APIs.
 Open NMS ( Can be customized to any NMS product)
Mediaroom Products :

 Media Room Personal server 1.1 sp 3.2

 STB Client Version 1.6.24576.31.
2 Design Overview
The Resource Management System design will be based on the following criteria:

 Resource Management System is accessed with the same URL for all Project Managers
and Resources.
 Windows Authentication method is used to authenticate users.
 Incorporates “plug and play” framework where possible for added business logic and
future enhancements.
 Use of prototypes and business partner involvement during the development process
 Simplifies the deployment process.

2.1 Technical Architecture

Following is the description of various layers shown in the application architecture.

Client Layer
This represents the client browser (Internet Explorer 6.0 and above). Any request from the user
will be sent to the application server using presentation layer.

Presentation Layer (V - View and C –Controller in MVC architecture)

The primary task of the Presentation layer is to perform processing in order to present and
capture information from and to the client. This consists of the ASP.net. The client requests are
passed to Internet Information Server which process the request by invoking the Business logic
and forwards the response to the ASP.net within the web container for processing and HTML
page generation. The application is published on Internet Information Service for easy access to
users on network.

This pattern achieves a clean separation of functionality of each component based on

architecture needs.
Application Layer (Model in MVC architecture)
The request would then be forwarded to Business components comprised of C#. Business
components C# interacts with the database. ASP.net processes these data objects for page
generation.

Data Layer
The data layer comprises of the database for the application. The application database is SQL
server 2005.
3 Screen Details
3.1 Welcome Page
3.1.1 Screen Description

Screen  This is the first screen that welcomes the user to the Customer
Description Experience Management System.
 This screen is designed as an overlay on the TV, so as to give the
customer uninterrupted view of the program.
 The overlay contains two buttons Today and Yesterday providing the
customer, facility to complain on issues recorded on yesterday or today.
 When any button on the page is clicked, the control is navigated to the
next page to capture the complaint details.

3.1.2 Work Flow

Invoke From
Navigation Action Parameters Comments (Enabled
/Disabled / Default Populates)
None By clicking on the None The Welcome page is displayed
shortcut button of the with welcome note and various
TV remote. > User buttons for customer to choose
Assessment a day to complaint. Captures
the whether the problem is
today’s or yesterday’s and
forwards the details.

Invokes
Screen Action Parameters Comments
Problem Area Click on any button Captures the Forwards the Problem recorded
Page. navigates to Problem STB device ID, day to the Problem Area page.
area page. Problem
recorded day.

3.1.3 Screen Layout

 3.1.4 Screen Functionality

 This is the first page that welcomes the customer to Customer Experience Management
System.
 This page contains two buttons Today and Yesterday.
 When the Customer Clicks on the button, to raise a complaint against issues in the IPTV
programs, the STB device Id is captured.
 Whether the problem is of Yesterday’s or Today’s is captured when the customer clicks
on either of the buttons.
 Device Id is accessed using the TVSystemDataSource and setSystemDataBinder()
methods

3.1.5 Screen GUI Field description

Screen Field Field Description Field Type Scree Mapping DB Column DB DB field
Name n Name field size
Field type
Size
Welcome To display the TVLabel NA NA NA NA
welcome note
Today To navigate to TVButton NA NA NA NA
Problemareas page
Yesterday To navigate to past TVButton NA NA NA NA
Problemareas page
3.2 Problem Areas
3.2.1 Screen Description

Screen
Description  Allows the customer to choose the Problem from the list of problems
displayed.

Screen  All the Problems should be displayed in the list.

Validation

3.2.2 Work Flow

Invoke From
Navigation Action Parameters Comments (Enabled
/Disabled / Default
Populates)
Welcome Page On click of ‘Today’ or NA The page with entire list of
‘Yesterday’Assessmen problem areas is displayed
t

Invokes
Screen / Report Action Parameters Comments
Select Problem Click on the selected Problem Area Will allow the customer to
Problem area select the problem type based
on the Problem area selected.

3.2.3 Screen Layout

 3.2.4 Tables accessed

Table Select Insert Update Delete Comments

TDCPa  Stores the Problem areas.

3.2.5 Screen Functionality

 This page enables the customer to select the Problem area like Live TV, VOD, and EPG.
 The page is pre-populated with the problem areas from database using sqldatasource.
 Based on the Problem area selected and clicked, the customer is navigated to Select
Problem type page.
 Problem Area Id is accessed and passed as a query string to the page Problem Type.
 Href property of TVButton controls in ItemDataBound event of TVListview control helps
navigate to the page Problem Type on the click of selected Problem area.

3.2.6 Screen GUI Field description

Screen Field Field Description Field Type Scree Mapping DB Mapping DB DB DB field
Name n Column Name Table Name field size
Field type
Size
Problem Area Problem Area TVLabel NA NA NA NA NA
List List of Problem TVListView NA Pa TDCPa VAR 30
areas displayed with CHA
TVButtons R
3.3 Select Problem Type
3.3.1 Screen Description
Screen  Based on the selected problem area, the Problem types are pre-
Description populated.
 Allows the customer to select the exact problem type from the list.

Screen Level  Only Problem Types under the selected Problem Area are to
Validations be displayed in the list.

3.3.2 Work Flow

Invoke From
Navigation Action Parameters Comments (Enabled
/Disabled / Default Populates)
Problem Area On Click of the Problem Area Select Problem Type page will
selected Problem Id be populated with only the
Area problem types based on the
selected Problem area.

Invokes
Screen / Report Action Parameters Comments
Select Channel On Click of the
Problem Type
selected Problem
Type
3.3.3 Screen Layout

3.3.4 Tables accessed

Table Select Insert Update Delete Comments
TDCPa  Stores the Problem
areas
TDCPaDesc  Stores the Problem
Types

3.3.5 Screen Functionality

 The Problem area Id passed as a query string from the page Problem Area is accessed
and stored as a session variable for future access.
 The page is pre-populated with problem Types based on the selected problem area Id
from database using sqldatasource.
 This page helps the customer to choose the Problem Type from the list displayed.
 The Problem Type selected which is ‘padesc’ is stored as a session variable and also
passed as a query string to the page LastchannelViewed.
 Href property of TVButton controls in ItemDataBound event of TVListview control helps
navigate to the page LastchannelViewed on the click of selected Problem Type.
 3.3.6 Screen GUI Field description

Screen Field Field Description Field Type Screen Mapping DB Mapping DB DB field DB field
Name Field Column Name Table Name type size
Size
Select Select Problem TVLabel NA NA NA NA NA
Problem
List List of Problem TVListView NA Pa TDCPadesc VARCHA 50
Types with R
TVButtons

3.4 Select Channel

3.4.1 Screen Description
Screen  Allows customers to select the channel in which the problem
Description occurred.
 Provides search for the channel facility to the customer.

Screen Level  Search Text should accept only characters.

Validations  On search button click the channels starting with the typed
character should fill the list view.

3.4.2 Work Flow

Invoke From
Navigation Action Parameters Comments (Enabled
/Disabled / Default
Populates)
Problem Type On Click of Problem Problem Enables the customer to select
Type Type/Description the Problem Type.

Invokes
Screen / Report Action Parameters Comments
Program On Click on the Enables the customer to select
Channel name
Schedule Channel name the channel and schedule

3.4.3 Screen Layout

 3.4.4 Tables accessed
Table Select Insert Update Delete Comments
EPGChinfo  Stores the EPG information of
yesterday and today

3.4.5 Screen Functionality

 This page helps the customer to select the channel in which the problem aroused.
 The Problem Type which is sent as a query string by the Problem Type page is accessed
here.
 The list of the channel names are pre-populated in the list view by the help of
sqldatasource.
 Customer can also search for the channel name by typing the characters in the textbox
and clicking on the search button.
 Selected channel Id is passed as a query string to the channel schedule Page.

3.4.6 Screen GUI Field description

Screen Field Field Description Field Type Field Mapping DB Mapping DB DB field DB field
Name Size Column Name Table Name type size
Select Select Channel TVLabel NA NA NA NA NA
Channel
Channel Channel TVText NA Chname EPGChinfo NA NA
Search Search Channel TVButton NA NA EPGChinfo NA NA
List List of channel TVListView NA Chname EPGChinfo VARCHA 100
Names with R
TVButtons
3.5 Channel Schedule
3.5.1 Screen Description
Screen  Allows the customer to select the channel EPG Timings, when the
Description problem aroused.

3.5.2 Work Flow

Invoke From
Navigation Action Parameters Comments (Enabled
/Disabled / Default Populates)
Select channel On Click of Channel Chname Enables user to select the
name channel

Invokes
Screen / Report Action Parameters Comments
Problem solution On Click of Channel chname,schedule Provides customer the
schedule possible solutions or Log a
complaint
3.5.3 Screen Layout

3.5.4 Tables accessed

Table Select Insert Update Delete Comments
EpgProdetails  Stores the details of EPG
Programs
EPGSchedules  Stores the details of EPG
Schedules.

3.5.5 Screen Functionality

 This page allows the customer to select the channel schedule in which the problem
aroused.
 The channel Id which is passed as a query string is accessed here.
 Based on the Channel Id the channel Program details and Schedule Details are
accessed and displayed in the list.
 Once the Customer selects the channel schedule, the web service
‘DiagnosticsNotificationsWSSoap’ is instantiated and its web method called
‘SendDiagnosticRequestToDevice’ is invoked using the parameters DeviceId and the url
of the web service ‘ClientDiagEventSinkAgentWS’.
 The Write() web method of the web service ‘ClientDiagEventSinkAgentWS’ writes an xml
file with the diagnostic data of the STB.
  The diagnostics collected are categorized as STB parameters, Memory parameters,
Network parameters, Log file in xml format
 When the Channel Schedule is selected, the control is navigated to the Problem solution
page.

3.5.6 Screen GUI Field description

Screen Field Field Description Field Type Field Mapping DB Mapping DB Table DB field DB
Name Size Column Name Name type field
size
Channel Channel TVLabel NA NA NA NA NA
Schedule Schedule

List List of channels TVListview, NA Chname, EpgProdetails, Varchar 100

along with the TVButton and EpgProdetails, EPGSchedules
schedule TVLabel Scheduletime
within

3.6 Problem solution

3.6.1 Screen Description
Screen  Gives the customer possible solutions, if the problem still exists
Description then he can log a complaint.

3.6.2 Work Flow

Invoke From
Navigation Action Parameters Comments (Enabled
/Disabled / Default
Populates)
Channel On Click of Channel By using the all the details
Schedule Schedule chname,schedule collected the user can log a
complaint.

Invokes
Screen / Report Action Parameters Comments
None

3.6.3 Screen Layout

3.6.4 Tables accessed
Table Select Insert Update Delete Comments
STB_param(Database tdc)   Stores all the details of
STB.
Network_Param(Database tdc)   Stores all the details of
Network
Mem_Param(Database tdc)   Stores all the details of
Memory
CustErr(Database tdc)    Stores all details of Errors
occurred
Attachments(Database tdc)   Stores the details of
customer Id, deviceid and
location

3.6.5 Screen Functionality

 This screen allows the customer to log a complaint against the problem faced.
 Channel name and schedule passed as query string are accessed here.
 Using the session variable of Problem area new problem or existing problem is identified.
 For existing problem possible solution is displayed in the list.
 For the new problem user is allowed to the problem details.
  Even after following the given solution, the problem exists then customer can log
complaint by clicking on the Log a Complaint button.
 On click of the complaint button, a random ticket no is generated and the details in the
diagnostics xml file are accessed into a dataset and then inserted into corresponding
tables.
 The customer is shown the Complaint Id for future correspondence.
 These details give the clear picture to the help desk agent to provide appropriate solution
to the customer.
 The customer can check the status of his ticket by logging into the TDCSelfhelp Portal.

3.6.6 Screen GUI Field description

Screen Field Field Field Type Screen Mapping DB Mapping DB DB field DB

Name Description Field Column Name Table Name type field
Size size
Try following Try following TVLabel NA NA NA NA NA
options options
List List of Options to TVlistview NA Padescdet TDCPaDesc Varchar 50
solve the problem with Dst
TVButtons
Click n If the Problem TVLabel NA NA NA NA NA
complain persists? Click
and complain
Log A Log A Complaint TVButton NA NA NA NA NA
Complaint
4 Database Design
There are a total of seven tables in this database.
 EPGChinfo. (IPTVtest EPG Channel Info)
 EpgProdetails (IPTVtest EPG Program Details)
 EPGSchedules (IPTVtest EPG Program Schedule)
 GetAllMediaDescriptions (IPTVtest Media Descriptions)
 GetCallLetters (IPTVtest Channel call Letters)
 TDCPa (IPTVtest Problem Area Details)
 TDCPaDesc (IPTVtest Problem Type Description Details)
 TDCPaDescDst (IPTVtest Problem Solution Details)
 STB_param (tdc STB Parameters Details)
 Network_Param (tdc Network Parameters Details)
 Mem_Param (tdc Memory Parameters Details)
 CustErr (tdc Customer Errors Details)
 Attachments (tdc Attachments Details)

Below is a detailed description of each of these tables.

4.1 EPGChinfo

Table Name: EPGChinfo (Electronic Program Guide Channel Information)

Field Data Type(size) Null/Not Null Description

Name
Channel Id. Primary
Chid varchar(50) Null Key.
Short cut for
Callletter varchar(50) NotNull channel name
l varchar(50) NotNull Call letter
d varchar(50) NotNull Channel Description
t varchar(50) NotNull Type of the program
iso3166 varchar(50) NotNull
Order. This tells
whether this
Program is ordered
ordr int NotNull or not

Table Description:
 The table EPGChinfo (IPTVtest EPG Channel info) stores all the information regarding
the Electronic Program Guide Channel information.
 The information includes channel id, shortcut for channel name, channel call letter,
channel description, iso3166, and Order details.
 Channel Id would be the Primary Key.
 The screens that access this table are Select Channel, Channel Schedule.

4.2 EpgProdetails
Table Name: EpgProdetails (IPTVtest EPG Program Details)

Field Name Data Type(size) Null/Not Null Description

 Pid varchar(100) Null Program Id, Primary key
t varchar(100) Not Null Channel text
rt varchar(100) Not Null Reference Text

Table Description:
 The table EpgProdetails (IPTVtest EPG Program Details) stores program Details.
 The details include Program Id, Program text, and Program reference text.
 Program Id is the Primary Key.
 The screens that access this table are select channel and Channel Schedule.

4.3 EPGSchedules
Table Name: EPGSchedules (IPTVtest EPG Program Schedule)

Field Name Data Type(size) Null/Not Null Description

Scheduletime datetime Not Null Program Schedule

Time
Duration int Not Null Duration of the
Program
Proid varchar(100) Not Null Reference from
EPGProdetails Table
Chid varchar(50) Not Null Reference from
EPGChinfo Table
id int Null Schedule Id

Table Description:
 This table gets the data from xml file named epgpub.xml.
 The Details include Schedule Time, Duration, Program id, channel id and Schedule id.
 Program Id is referenced from EPGProdetails.
 Channel id is referenced from EPGChinfo.

4.4 GetAllMediaDescriptions
Table Name: GetAllMediaDescriptions (IPTVtest Media Descriptions)

Field Name Data Type(size) Null/Not Null Description

idno int Not Null EPG Media

Description Id
EpgId nvarchar(MAX) Null EPG Program Id
Id nvarchar(MAX) Null
ServiceCollectionId nvarchar(MAX) Null Service Collection Id
ServiceCollectionName nvarchar(MAX) Null Service Collection
 Name
DisableDvrSkip char(5) Null DVR inputs

Table Description:
 This table stores all the Media Descriptions of Electronic Program Guide.
 The various columns include EPG id, service Collection Id, service collection name,
DVR, Id for the media descriptions etc.

4.5 GetCallLetters

Table Name: GetCallLetter (IPTVtest Channel call Letters)

Field Name Data Type(size) Null/Not Null Description

id int Not Null Call Letter Id

CallLetter nvarchar(50) Null Call Letter description
EPG Id Reference from
GetAllMediaDescriptio
EpgId nvarchar(MAX) Not Null ns

Table Description:
 This table stores all the abbreviations of channel names.
 The column Call Letter in this table contains the short form of channel name.
 Epgid is the reference from the table GetAllMediaDescriptions.

4.6 TDCPa
Table Name: TDCPa (IPTVtest Problem Area details)

Field Name Data Type(size) Null/Not Null Description

Paid int Not Null Problem Area Id

Pa varchar(500) Not Null Problem Area Name

Table Description:
 This table stores all the problem areas that are occurring frequently.
 The column Paid is the primary key and Pa is problem area description.

4.7 TDCPaDesc
Table Name: TDCPaDesc (IPTVtest Problem Type Description details)

Field Name Data Type(size) Null/Not Null Description

Padescid int Not Null Problem Area Type

 Description Id
Problem area Id
referenced from
Paid int Not Null TDCPa
Problem Area type
Padescdet nvarchar(500) Not Null Desc

Table Description:
 This table stores the details of Problem Types in the given Problem Area.
 The column Paid is the reference value from table TDCPa.
 The Padescdet is description of Problem type.

4.8 TDCPaDescDst
Table Name: TDCPaDescDst (IPTVtest Problem Type Description details)

Field Name Data Type(size) Null/Not Null Description

Problem Desc Id
Pdstid int Not Null Primary key
Problem Area desc
Id referenced from
Padescid int Not Null TDCPaDesc
Problem Area Desc
Padescdet nvarchar(MAX) Not Null details

Table Description:
 This table stores the details of solutions given to the specific Problem area based on the
selected Problem type.

4.9 STB_param
Table Name: STB_param (tdc STB Parameters details)

Field Name Data Type(size) Null/Not Null

BootRomVersion nvarchar(50) Not Null

ClientVersion nvarchar(50) Not Null
CurrentTime datetime Not Null
LastRebootTime datetime Not Null
ServiceID nvarchar(50) Not Null
CurrentPageName nvarchar(50) Not Null
ChannelNumber nvarchar(50) Not Null
ServiceSubstitutionFailedSignatureCount nvarchar(50) Not Null
IsBlockedByDRM nvarchar(50) Not Null
IsBlockedByPCon nvarchar(50) Not Null
 Receiver_BytesReceived nvarchar(50) Not Null
Receiver_EncodedPictureSize nvarchar(50) Not Null
Receiver_PixelAspectRatio nchar(10) Not Null
Receiver_BitRate nvarchar(50) Not Null
Receiver_AudioAccessControlErrors nvarchar(50) Not Null
Receiver_AudioDescCryptoError nvarchar(50) Not Null
Receiver_AudioDescDecoderErrors nvarchar(50) Not Null
Receiver_AudioDataDropped nvarchar(50) Not Null
Receiver_VideoAccessControlErrors nvarchar(50) Not Null
Tuner_PacketsExpired nvarchar(50) Not Null
Tuner_SrcUnavailableReceived nvarchar(50) Not Null
Tuner_MulticastAddress nvarchar(50) Not Null
Tuner_UnicastAddress nvarchar(50) Not Null
StbID nvarchar(50) Not Null

Table Description:
 This table stores the details of STB Parameters, stbID is the primary Key.

4.10 Mem_Param
Table Name: Mem_Param (tdc Memory Parameters Details)

Field Name Data Type(size) Null/Not Null

AvlPhysicalMemor
y nvarchar(50) Not Null
AvlVirtualMemory nvarchar(50) Not Null
AvlVideoMemory nvarchar(50) Not Null
DrivePresent bit Not Null
StbID nvarchar(50) Not Null

Table Description:
 This table stores the details of STB Memory Parameters.

4.11 Network_Param
Table Name: Network_Param (tdc Network parameters Details)

Field Name Data Type(size) Null/Not Null

Eth_CRC_Err_Count nvarchar(50) Not Null

Eth_Drop_Pack nvarchar(50) Not Null
Eth_Traffic_In nvarchar(50) Not Null
Eth_Traffic_Out nvarchar(50) Not Null
IpAddress nvarchar(50) Not Null
SubnetMask nvarchar(50) Not Null
 DHCPLeaseTimeRe
m nvarchar(50) Not Null
DefaultGateway nvarchar(50) Not Null
DNSServers nvarchar(50) Not Null
StbID nvarchar(50) Not Null

Table Description:
 This table stores the details of Network Parameters, stb id is reference from
STB_Params .

4.12 CustErr
Table Name: CustErr( tdc Customer Errors Details)

Field Name Data Type(size) Null/Not Null

CustID nvarchar(150) Not Null

ErrLogTime datetime Not Null
ErrorCategory nvarchar(50) Not Null
DevID nvarchar(50) Not Null
Status nvarchar(50) Not Null
FolderID int Not Null
ChannelName nvarchar(50) Not Null
ChannelNo nvarchar(50) Not Null
progname nvarchar(50) Not Null
TransID nvarchar(MAX) Not Null
Description nvarchar(MAX) Null

Table Description:
 This table stores the details of Customer Errors.

4.13 Attachments
Table Name: Attachments (tdc Attachment Details)

Field Name Data Type(size) Null/Not Null

AttachementID int Not Null

CustID varchar(50) Not Null
StbID varchar(50) Not Null
Location nvarchar(200) Not Null

Table Description:
 This table stores the details of Attachments with STB, Customer and Location.