MiriMON 3 18 Specification V1C Draft

MiriMON v3.18 Product Specification

Document Version: 1.0 Draft C

Document Number: 500/001/059/318

Author: Alex Dick, updated by Vicky Messer

Date: 24 September 2012

Copyright Notice

Copyright © 2012 Mirifice Ltd. All Rights Reserved. All copyrights and trademarks acknowledged.This document is the intellectual property of Mirifice Limited, UK and contains confidential information.

All reproduction and communication to third parties without prior written consent is prohibited.

MiriMON v3.18 Product Specification Version 1.0 Draft C

Table of Contents

Table of Contents1. Introduction......................................................................................................................72. MiriMON User Interface...................................................................................................92.1. Standard Access..............................................................................................................92.2. Access Using LDAP..........................................................................................................92.3. Access Using HTTPS .....................................................................................................103. MiriMON Core................................................................................................................113.1. Device Management Application Dashboards.............................................................113.1.1. Subscriber Selection Dashboard............................................................................................113.1.2. Device Summary Dashboard.................................................................................................123.1.3. Device Health Dashboard......................................................................................................133.1.4. Event Logs Dashboard...........................................................................................................143.2. KPI Executive Application Dashboards.........................................................................153.3. MiriMON Status Dashboard.........................................................................................164. Optional MiriMON Applications.....................................................................................184.1. Network Management Application..............................................................................184.1.1. Central Office Status Dashboard...........................................................................................184.1.2. DVB Transmitter Status Dashboard.......................................................................................194.1.3. VOD Server Status Dashboard...............................................................................................204.1.4. Network Alarms Dashboard..................................................................................................214.1.5. KPI Statistics Dashboard........................................................................................................224.1.6. Network SNMP Alarms..........................................................................................................224.2. Service Management Application.................................................................................234.2.1. Channel Dashboards..............................................................................................................234.2.2. VOD Asset Dashboard...........................................................................................................234.2.3. Service History Dashboard....................................................................................................244.2.4. KPI Statistics Dashboard........................................................................................................244.3. Network/Service Analysis Screens................................................................................244.3.1. Additional Analysis Screens from Network Management.....................................................254.3.2. Additional Analysis Screens from Service Management .......................................................254.4. Customer Care Application...........................................................................................254.4.1. Home Status Dashboard........................................................................................................264.4.2. Service Faults.........................................................................................................................274.4.3. Device Health Graphs............................................................................................................274.5. Consumer Insight Application.......................................................................................274.5.1. Channel Popularity Dashboard..............................................................................................284.5.2. VOD Popularity Dashboard....................................................................................................285. MiriMON Reports...........................................................................................................295.1.1. Network Central Office Report..............................................................................................29Confidential Page 2 of 45 © 2012 Mirifice Ltd


5.1.2. Customers in Jeopardy of Churn Report................................................................................295.1.3. Multicast Average Channel Change Time Report..................................................................295.1.4. DVB Average Channel Change Time Report..........................................................................305.1.5. Channel Peak Viewing Figures Report...................................................................................305.1.6. Channel Consumption by Duration Report............................................................................305.1.7. Channel Consumption by Band Report ................................................................................305.1.8. Channel Consumption by Subscriber Category Report..........................................................315.1.9. Channel Unique Viewers Count Report.................................................................................315.1.10. Time-shifted Consumption of Channels Report....................................................................315.1.11. VOD Purchases per Subscriber Report..................................................................................315.1.12. Overall VOD Consumption Report ........................................................................................315.1.13. VOD by Customer Usage Report ...........................................................................................325.1.14. VOD by Genre .......................................................................................................................325.1.15. VOD Purchases per Subscriber .............................................................................................325.1.16. VOD Revenue........................................................................................................................325.1.17. AV Quality of Service Over Time Report................................................................................335.1.18. Maximum Peak Viewers Across all Channels Report.............................................................335.1.19. HLS Rate Over Time Report...................................................................................................335.1.20. HLS Rate By Channel Report..................................................................................................335.1.21. HLS Rate Change Activity Report...........................................................................................336. MiriMON Monitoring Features.......................................................................................346.1. Standard Agent Configurations....................................................................................347. MiriMON Administration................................................................................................357.1. User Account Dashboard..............................................................................................357.2. Session Audit.................................................................................................................357.3. Dashboard Configuration..............................................................................................357.4. Report Configuration....................................................................................................357.5. Report Creation............................................................................................................367.6. Provisioning of Operator Supplied Data.......................................................................367.7. Creating an Agent Configuration..................................................................................377.8. Agent Configuration Tuning..........................................................................................377.9. Distributing an Agent Configuration.............................................................................377.10. Agent Remote Control..................................................................................................378. MiriMON Integration Interfaces.....................................................................................388.1. MiriMON Web Services................................................................................................388.1.1. Network Status......................................................................................................................388.1.2. System Alarms.......................................................................................................................408.1.3. System Status........................................................................................................................408.1.4. Consumer Insight..................................................................................................................418.1.5. Customer Device Summary...................................................................................................428.1.6. Device Events........................................................................................................................44

Confidential Page 3 of 45 © 2012 Mirifice Ltd


8.1.7. Device Service Faults.............................................................................................................448.1.8. Device Health........................................................................................................................448.1.9. Subscriber Search..................................................................................................................458.2. SNMP Traps and MIB....................................................................................................458.3. SMTP Report Delivery...................................................................................................459. MiriMON Security...........................................................................................................469.1. Agent Server Reporting................................................................................................469.2. User Sessions................................................................................................................46



Glossary

AV Audio Visual OS Operating SystemBER Bit Error Rate PDF Portable Document FormatCC Continuity Counter PRD Product Requirement DocumentCCT Channel Change Time PVR Personal Video RecorderCO Central Office QoE Quality of ExperienceCGI Common Gateway Interface QoS Quality of ServiceCPU Central Processing Unit RDB Raw event Data BufferDRM Digital Rights Management RDBMS Relational Database Management

SystemDVB Digital Video Broadcasting RFC Request for CommentsDVB-S Digital Video Broadcasting -

SatelliteRTP Real time Transport Protocol

DVB-T Digital Video Broadcasting - Terrestrial

RTSP Real Time Streaming Protocol

EPG Electronic Program Guide SAT System Acceptance TestEVO Brand for Espial Middleware

ProductSE Significant Event

FIFO First In First Out SMART Self-Monitoring, Analysis and Reporting Technology

GUI Graphical User Interface SMTP Simple Mail Transfer ProtocolHDCP High-Bandwidth Digital Content

ProtectionSNMP Simple Network Management

ProtocolSNR Signal to Noise Ratio

HDD Hard Disc Drive SOAP Simple Object Access ProtocolHDMI High Definition Multimedia

InterfaceSSH Secure Shell

HLS HTTP Live Streaming STB Set Top BoxID Identifier TCP Transmission Control ProtocolIGMP Internet Group Management

ProtocolUBC Uncorrectable Block CountUCS Universal Character Set

IP Internet Protocol UDP User Datagram ProtocolKPI Key Performance Indicator URL Uniform Resource LocatorLAN Local Area Network UTF8 UCS Transformation FormatLDAP Lightweight Directory Access

ProtocolVOD Video On DemandWAN Wide Area Network

MIB Management Information Base XML Extensible Mark-Up LanguageXR Extended Report

MPEG Moving Pictures Expert Group XSD XML Schema DefinitionNIC Network Interface ControllerNMS Network Management System



1.IntroductionThis specification describes Version 3.18 of the MiriMON monitoring solution from Mirifice. The key update to v3.18 compared to v3.16 release is the introduction of HLS reports as part of HLS phase 1, reports generated in .xls format and SNMP trap alarms on device service degradation/down. Phase 2 HLS functionality including dashboard support is targeted for 3.20 release. Figure 1 shows the MiriMON architecture:

Figure 1 MiriMON System Architecture

The MiriMON solution monitors media devices (e.g. set-top boxes) in the homes of subscribers via a broadband network. MiriMON can only monitor devices with a ‘return-path’ i.e. connected via a 2-way data link to the MiriMON server (conventionally hosted in the operator’s central facility).Telemetry data is collected on the media device via an intelligent MiriMON software agent. The agent can be soft configured, in order to tune reporting, as required.The MiriMON Server collects and processes telemetry data from the device, and then renders it as meaningful information, thus helping network operators and service providers improve the service experience they provide.The MiriMON Server provides information via Applications, each specific to an operator function:

• The Core Application provides a simple view of telemetry measures, events and metrics for each device (also essential to underpin other applications)

o Device Management Application o KPI Executive Application

• Optional Applications (modular additions to the MiriMON Core) can be purchased to provide more sophisticated data analysis and presentation of derived information specifically for different functions:

o Network Management Applicationo Service Management Application



o Customer Care Application o Customer Insight Application

MiriMON Applications can correlate individual device errors to network elements or service elements to which they are attached and use thresholds to generate alarms for those elements when a significant number of attached devices are in error.The MiriMON 3.18 functionality, including from optional applications is described in this Specification.The actual functionality provided to an operator may vary from this specification as not all features may be available (check contract for details), for example:

• Additional measurements have been implemented following an operator request• A measurement is not appropriate for the specific network or service offering• A measurement is not appropriate for one or more devices managed• A measurement is not available for the device firmware deployed

Note: Some information reported by the MiriMON Agent is obtained from 3rd party components on the Consumer Device. Mirifice is dependent upon these 3rd party component vendors for the correct measurement/calculation of such telemetry. In such a situation the MiriMON agent will accurately report this telemetry, or values derived from it, to the MiriMON server. In the event that a 3rd party measurement/calculation is shown to be incorrect, Mirifice will support the operator in obtaining a rectification from the 3rd party. Mirifice will not be held liable for incorrect values resulting from errors in 3rd party components on the Consumer Device and cannot directly rectify such faults.Note: Where DVB measurements are given these apply to the type of DVB network being monitored and can be DVB-T/T2, DVB-S/S2 or DVB-C.Note: Where the term 'STB' is mentioned this may equally apply to other types of monitored device.



2.MiriMON User InterfaceMiriMON Applications can render information as follows:

• An interactive Web Dashboard (a graphical view accessed via an approved Browser), which displays:

o Metrics, which are refreshed with real-time information updates (default 10 seconds).

o Individual Events, which are displayed in real-time, as they are generated• A static Report (rendered in Portable Document Format) which provides historical analysis

and trending over a selected time period. o By default, Reports are delivered by email to a distribution list.o Reports can be viewed using the freely available Adobe (or equivalent) Portable

Document Format reader.o The Reporting period, Report generation frequency and generation time are

configurable.All text displayed will be in UK English except for localised channel names and VOD asset names. The dashboards shall support the display of UTF8 characters for channel/VOD asset names where they appear in the dashboards. All dates and times will be displayed in the Customer/Operators local time.User access to Applications is based on account permissions granted by a MiriMON Administrator. Users may not be able to access some installed MiriMON applications due to account restrictions.On-line help pages are available for MiriMON dashboards. The following Manuals are also provided:

• MiriMON Dashboards Manual (Document Reference 500/001/039)• MiriMON Reports Manual (Document Reference 500/001/040)• MiriMON Installation and Administrator's Manual (Document Reference 500/001/035)

The dashboards shall contain Mirifice branding (graphics and logos) and shall use standard Mirifice colours where appropriate. Individual Dashboards are accessed via drop down menus at the top of the Screen. At the bottom right corner of every dashboard is a status bar showing the name of the server and a connection status icon. Buttons are provided (‘forward’ and ‘back’) to navigate to the previous dashboard viewed and forward again.

2.1. Standard AccessAt the start of each dashboard session, successful login with an authorised user name and password shall be required. Once logged in, the user shall be able to log out to end the session. No time-based automatic expiration of a session will apply.

2.2. Access Using LDAPA corporate LDAP directory can be used to provide authentication services (as an option). LDAP provides for secure transmission of usernames and passwords from the client, through the CGI and to the LDAP server. The MiriMON implementation provides the following features;

• Password based authentication against the password stored in the LDAP directory, via an LDAP Bind

• Automatic population of the MiriMON user database with default settings for any new users (with first user defaulting to have administrative rights)

• Cookie based session management for any subsequent CGI communications, including session expiration and extension



• Support for HTTPS communications between client and MiriMON server

2.3. Access Using HTTPSDashboard access and communications can be configured to use HTTPS to avoid eavesdropping and protect session data. (This is mandatory when using LDAP access.) The login page version number will include an 's' if HTTPS is being used.



3.MiriMON CoreThe MiriMON Core consists of:

• The underlying technology platform to manage devices, collect, process and render telemetry data as meaningful information

• A set of standard Application functionality, providing data presentationThe measurements provided by MiriMON are obtained from individual Consumer Devices. A number of measurements on the device are obtained from 3rd party components on the device, for example:

• AV and QoS measures are retrieved from the AV core (player/codecs etc.)• Network measurements are retrieved from the OS and Network Interface Driver (traffic

metrics, packet loss etc.)• Device measures are retrieved from the OS and Manufacturer Integration Layer (CPU,

Memory, HDD etc.)• Service signalling and events are retrieved from the Manufacturer Integration Layer

A number of optional Applications are also available, as modular additions to the MiriMON core, and are described in Section 4 of this document.The Metrics, Dashboards and Reports provided as part of the Core Application are specified in the following sections.The following sections describe the baseline functionality for these Applications. The actual functionality provided may vary in the following circumstances:

• Additional measurements have been configured following an operator request• A measurement is not appropriate for the specific network or service offering• A measurement is not appropriate for one or more devices managed

3.1. Device Management Application DashboardsThe following Dashboards described show telemetry values, events and metrics for an individual device. They are accessed via the Device Management Application Menu and are a standard (mandatory) part of the MiriMON Core offering. Where the term 'STB' is mentioned this may equally apply to other types of monitored device.

3.1.1. Subscriber Selection DashboardThis Dashboard provides a means to select an individual device on the network through specification of a unique subscriber number. When this is specified (or partly specified) a list auto-populates with possible subscriber numbers. The device information screens will not be available until a device has been selected and the device has automatically registered with MiriMON for the first time.Selection of the device, unless otherwise agreed, shall be via one of:

• Subscriber account identifier• MAC address (or other unique equipment identifier)• Device IP address

Sub-string matching shall be performed if no exact match is found.Additionally, an optional validity date criteria can be supported to select only accounts provisioned on the specified date. The results can be sorted by account number/text, unique equipment identifier, IP address, valid from or valid until dates by clicking on the column heading. Clicking on a results column heading twice will toggle the sort order between ascending and descending.



To select a subscriber, whose account has expired, or to investigate devices that were allocated to a customer on a particular date, the Valid On date can be set to a period when the desired subscriber equipment was active.

3.1.2. Device Summary DashboardThis Dashboard provides the following information for an individual Device:

• A Device Unique Identifier• A Subscriber Identifier (This is a provisioning dependency on the operator)• Current Device Status

o The MiriMON Agent Configuration applied to the deviceo The Network Region (Central Office or equivalent) to which the device is attached.o Currently Viewing Status: PVR(where supported), Channel, VOD, Time-shifted

viewing, Idle, Unknown• Customer QoE indicated by Device status colour (red, amber, green)• Current Device health status (network traffic, CPU utilisation)• The current Device Configuration (displays the file base name and numeric identifier)

Event List ComponentBy default, this panel shows, in summary format, the live data received from the STB in the last hour. The panel can be toggled between:

• a log of errors• a list of events

Earlier events or errors can be viewed by using the ‘Earlier’ button. From an ‘earlier’ view the user can move to ‘later’ events using a ‘Later’ button.The screen updates the event or error list by appending data as it is received.More detailed information about these events can be viewed in the Event Logs Dashboard. Device Statistics ComponentThe Statistics panel provides the following metrics for the Device:

• Installation Status (device health)o Last reported Memory Available (in Kbytes) to the operating system. This does not

include memory that is available from swap space.o CPU load average (%): Last reported CPU utilisation.o Seconds since Reset: Device uptime since reset (since a reported device reset, so can

be zero for a ‘new’ device)o Last reported uptime (seconds)o Last reported Hard Drive Temperature (where supported)o Last reported CPU Temperature (where supported)o PVR recording on/off state (where supported)

• Tuner RF (DVB statistics)o Reported Frequency (MHz)o BERo SNRo UBC

• Device AV QoS for Multicast IP and VOD



o Video frame losso Video frame erroro Video buffer overflowo Video buffer underflowo Audio buffer overflowo Audio buffer underflowo Video absento Audio absento Total A/V error episodes

• Device IP Network QoSo RX TCP Stack Errorso TX TCP stack errorso TCP TX Packets Droppedo TCP RX packets droppedo RX Frame Alignment Errorso RX FIFO Overrun Errorso TX collisionso TX FIFO overrun errorso Total errorso UDP packets receivedo TCP packets transmittedo Received bandwidth used (kbps)o Transmitted bandwidth used o IP packets receivedo IP packets transmittedo IP packets corrupto Datalink bytes transmittedo Datalink frames receivedo Datalink bytes receivedo Datalink CRC erroro Datalink collisionso IGMP groups joined

• Device SNMP trap alarm status for if IPTV service is severely degraded or down • Device Statistics

o Channel Changeso Time-shift Play Requestso VOD Play Requests

3.1.3. Device Health DashboardThis Dashboard provides a number of graphs (with explanatory keys) that present a recent historical record of STB status (loading, traffic) for the selected subscriber. The time period can be specified.The default Device Health Graphs are:



• CPU utilisation (load average)• Memory utilisation (exact values are shown in Event Logs, Section 3.1.4)

o Memory in useo Free memory (available for application use). (Note: This is not a measure of

middleware memory buffer management.)• Network stack statistics• Channel Play-out Status• VOD Play-out Status

The information will be displayed to a minimum range of one hour up to a maximum of seven days, updated over the period. The live information displayed will be updated every 10 seconds (default).

3.1.4. Event Logs DashboardThis Dashboard presents a time-ordered list of telemetry events (e.g. internal status changes, network traffic) from a selected individual device. All Device events will be displayed in this Dashboard. The ordering of the events displayed shall be controlled as follows:

• Clicking on a column heading shall select that field as the sort key• Clicking on a column heading a second time shall reverse the sort order (ascending /

descendingEach event shall have the following fields displayed:

• Timestamp for when the event was raised• Event severity• Event text

The following options are provided to control the event time window:• From a specified date and time• To a specified date and time• Around a specified date and time• To the current time• In a day(s) or hour(s) range up to eight days• A number of events (defaults to 50)

The following options are provided to filter the events retrieved and displayed:• All events at a specified severity or higher• All events of a specified type• All events associated with a specified content type• All events associated with a specified multicast channel, time-shifted programme, or VOD

asset.Filter pre-sets are provided to select events generated while the STB was playing

• VOD content (optionally with specified asset ID)• Broadcast channel content (optionally with specified channel number)• Time-shifted programme content (where supported - optionally with specified programme

ID)Controls to pause and resume the display of events are provided. Controls to copy all events, or the selected events, to the system clipboard are provided. Where no data is available, a visual indication is provided. While data is loading, a visual indication is provided.



3.2. KPI Executive Application DashboardsMiriMON provides Overview KPI Statistics for all on-line devices managed by MiriMON. This Dashboard is a part of the MiriMON core offering. The following KPIs, representing service quality, are refreshed every 10 seconds (default):IP Channel Timing: (when services are delivered over IP Multicast)

• Time to join a multicast stream (arithmetic mean and standard deviation)• Time to display video frames (arithmetic mean and standard deviation)• Time to play audio stream (arithmetic mean and standard deviation)• Time to complete the channel change (arithmetic mean and standard deviation)

VOD Session Timings: (when RTSP protocol is used for communications)• Time to receive RTP stream after sending RTSP request (arithmetic mean and standard

deviation)• Time to start of Download from Request (arithmetic mean and standard deviation)• Time to display video frames (arithmetic mean and standard deviation)• Time to play audio stream (arithmetic mean and standard deviation)• Time to complete the session start-up (arithmetic mean and standard deviation)

DVB Channel Timings: (when services are delivered over DVB multiplexes)• Time to Carrier Detect (arithmetic mean and standard deviation)• Time to Tuner Lock (arithmetic mean and standard deviation)• Time to Display Video Frames (arithmetic mean and standard deviation)• Time to Play Audio Stream (arithmetic mean and standard deviation)• Time to Complete Channel Change (arithmetic mean and standard deviation)

Device Operation Counts• Total MiriMON Enabled devices that have connected to the server• MiriMON Enabled devices that are currently online and connected• Number of Idle devices that are connected but not using any service

Network QoS: (when services are delivered over IP)• Average performance of MiriMON-enabled devices that are on-line:

o TCP Stack errors (arithmetic mean to 3 decimal places) [C]o Packets dropped (arithmetic mean to 3 decimal places) [D]o Frame alignment errors (arithmetic mean to 3 decimal places) [E]o FIFO overrun errors (arithmetic mean to 3 decimal places) [F]

• Average network error rate score (for MiriMON-enabled devices on-line to 3 decimal places)o Calculated as 100 * (C + D + E + F) / (A + B)

DVB AV QoS Performance (when services delivered over DVB)• Number of DVB STBs• Percentage of on-line DVB STBs with no AV QoS errors (to 3 decimal places)• Percentage of on-line DVB STBs with the following AV QoS errors (to 3 decimal places)

o Video frame losso Video frame erroro Video buffer overflowo Video buffer underflowo Audio buffer overflowo Audio buffer underflowo Video absent



o Audio absent

VOD AV QoS Performance (Progressive download)• Number of VOD Session STBs• Percentage of on-line VOD Session STBs with no AV QoS errors (to 3 decimal places)• Percentage of on-line VOD Session STBs with the following errors (to 3 decimal places)

o Buffer Underflowo Request Fails

VOD AV QoS performance (Streamed):• Number of Unicast STBs• Percentage of on-line Unicast STBs with no AV QoS errors (to 3 decimal places)• Percentage of on-line Unicast STBs with the following AV QoS errors (to 3 decimal places)

o Video frame losso Video frame erroro Video buffer overflowo Video buffer underflowo Audio buffer overflowo Audio buffer underflowo Video absento Audio absent

Multicast AV QoS performance: (when services delivered over IP multicasts)• Number of Multicast Devices• Percentage of on-line Multicast STBs with no AV QoS errors (to 3 decimal places)• Percentage of on-line Multicast STBs with the following AV QoS errors (to 3 decimal places)

o Video frame losso Video frame erroro Video buffer overflowo Video buffer underflowo Audio buffer overflowo Audio buffer underflowo Video absento Audio absent

Subscriber Counts• Valid Subscriber Device Count

Device IPTV service degradation/down alarm• SNMP trap alarm status statistics for devices with IPTV service is severely degraded or down

Additional KPIs may be displayed that are either delivered as part of a purchased Optional Application or are implemented as an Operator specific measure.

3.3. MiriMON Status DashboardThis Dashboard presents a MiriMON status summary, including

• Live event rate per second• Total significant events (SEs) processed



• MiriMON Uptime (days)• Number of connected MiriMON clients• Days until licence expiry

Note: The MiriMON Status Dashboard is accessed via the Executive KPIs.



4.Optional MiriMON ApplicationsThis section the number MiriMON Applications, available as modular additions to the MiriMON core, as follows:

• Network Management Application• Service Management Application• Customer Care Application• Consumer Insight Application

The Metrics, Dashboards and Reports provided as part of these Applications are specified in the following sections, which only apply if these modules have been purchased.The following Sections describe the baseline functionality for these Applications. The actual functionality provided may vary in the following circumstances:

• Additional measurements have been implemented following an operator request• A measurement is not appropriate for the operator’s specific network or service offering • A measurement is not appropriate for one or more consumer devices monitored

The Standard Applications provide the following information:

4.1. Network Management ApplicationThis section describes the functionality of the Standard Network Management Application, which features the following components:

• Central Office Status Dashboard• DVB Transmitter Status Dashboard• VOD Server Status Dashboard• Network Alarms Dashboard• KPI Statistics Dashboard• Network Central Office Report (details in section 5.1.1)• Network SNMP Alarms

4.1.1. Central Office Status DashboardThis Dashboard presents a matrix of Central Office (CO) mimics, which display the following information:

• The CO Name or unique identifier• A colour coded mimic status (red, amber, green and grey) based on the percentage of the

attached devices that are ‘in error’ (this is any device experiencing AV errors in the last 300 seconds).

o The default thresholds for CO mimic status, based on ‘in error’ devices are: Green = <5%, Amber = 5-10%, Red = >10%, Grey = Not Applicable (example: no devices attached).

• Further information will be provided, as the display sizing allows, from the information displayed in the mouse-over pop-up over.

More CO information is available via a mouse-over pop-up. Statistics displayed in the pop-up are:• The CO Name or unique identifier• Multicast STB Count (number of devices consuming a Multicast Service)• Unicast STB Count (number of devices consuming a Unicast Service)



• Online STB Count (number of devices currently online)• Total STB Count (number of devices in total)

• Total Unicast Bytes (ten minute average ) for all Devices associated with the region• Total Multicast Bytes (ten minute average) for all Devices associated with the region• Percentage of viewing seconds without AV disruption (ten minute average) (representing the

service quality of the region)• Percentage of error free devices (devices with no AV disruption)

The Dashboard allows the User to sort the matrix by Identifier or Metric (the sort order can be reversed).By clicking on a control button on the matrix mimic, a more detailed Information View for an individual mimic can be displayed in the lower section of the dashboard. Up to three detailed Information Views can be displayed simultaneously. A control on the detailed information view allows any individual information view to be deselected (hidden). This provides the same information show in the mouse-over pop-up.The Dashboard allows a User to suppress an individual CO from contributing to the overall Live Channel Status dashboard matrix. A CO in suppressed mode will be identified on the matrix by a black border around the mimic. After 5 minutes (default, configurable) the applied suppression(s) will automatically be cleared.The CO Mimics Dashboard provides click-through buttons to select:

• Network History (Alarms) Dashboard, filtered to display events for the selected CO only• The Network/Service Analysis Screens (if both the Network Management Application and

Service Management Application) have been purchased, specified in Section 4.3• The Subscriber Selection Screen, configured to show devices currently attached to the

selected CO (this can be filtered to show devices currently viewing the selected CO and experiencing AV errors)

Where no CO name is provisioned for the CO, the CO shall be labelled with its provisioned Identifier or discovered sub-net IP address (defaulted to decimal dotted format).

4.1.2. DVB Transmitter Status DashboardThis Dashboard presents a matrix of DVB Multiplex (Mux) mimics which display the following information:

• The DVB Transmitter/Mux name or unique identifier• A colour coded mimic status (red, amber, green and grey) based on the percentage of the

attached devices that are ‘in error’ (this is any device experiencing AV errors in the last five minutes).

o The default thresholds for DVB Transmitter/Mux mimic status, based on ‘in error’ devices are: Green = <30%, Amber = 30% - 70%, Red = >70% , Grey = Not Applicable.


More DVB Transmitter/Mux information is available via a mouse-over pop-up. Statistics displayed in the pop-up are:

• The DVB Transmitter/Mux Name or Frequency• Tuned STB Count (number of attached devices)• Viewers in Error. (number of attached devices with an AV errors)• Requested Frequency (the requested tuning frequency of the multiplex in MHz)



• Maximum Reported Frequency (the maximum reported lock frequency of the multiplex in MHz)

• Minimum Reported Frequency (the minimum reported lock frequency of the multiplex in MHz)

• Bit Error Rate (the average bit error rate across all attached devices)• Un-correctable Block Count (a count of block errors)• Signal to Noise Ratio (the average SNR across all attached devices)

The Dashboard allows the User to sort the matrix by Identifier or Metric (the sort order can be reversed).By clicking on a control button on the matrix mimic, a more detailed Information View for an individual mimic can be displayed in the lower section of the dashboard. Up to three detailed Information Views can be displayed simultaneously. A control on the detailed information view allows any individual information view to be deselected (hidden). This provides the same information show in the mouse-over pop-up.The Dashboard allows a User to suppress an individual DVB Transmitter/Mux from contributing to the overall Live channel Status dashboard matrix. A DVB Transmitter/Mux in suppressed mode will be identified on the matrix by a black border around the mimic. After 5 minutes (default) the applied suppression(s) will automatically be cleared.The DVB Transmitter/Mux Dashboard provides click-through buttons to select:

• Network History (Alarms) Dashboard, filtered to display events for the selected DVB Transmitter/Mux only

• The Network/Service Analysis Screens (if both the Network Management Application and Service Management Application) have been purchased, specified in Section 4.3.

• The Subscriber Selection Screen, configured to show devices currently attached to the selected DVB Transmitter/Mux (this can be filtered to show devices currently attached to the selected DVB Transmitter/Mux and experiencing AV errors)

Where no Transmitter/Mux name is provisioned, the Transmitter/Mux Mimic shall be labelled with its frequency in MHz.

4.1.3. VOD Server Status DashboardThis Dashboard presents a matrix of VOD server mimics, which display the following information:

• The VOD Server name or IP Address• A colour coded mimic status (red, amber, green and grey) based on the percentage of the

attached devices that are ‘in error’ (this is any device experiencing AV errors in the last 300 seconds).

o The default thresholds for VOD Server mimic status, based on ‘in error’ devices are: Green = <30%, Amber = 30-70%, Red = >70%, Grey = Not Applicable (example: no devices attached).


More VOD Server information is available via a mouse-over pop-up. Statistics displayed in the pop-up are:

• VOD Sessions in progress (number of attached device consuming VOD).• VOD Sessions in error (number of VOD sessions in error on the VOD Server Node).• VOD Session that failed to start (percentage of sessions that failed to start, within 10

seconds, on this VOD Server Node)



• Average start up time (average time for attached devices to commence VOD Asset play out)• Error free viewers (percentage of viewers who are error free on this VOD Server Node)

The Dashboard allows the User to sort the matrix by Identifier or Metric (the sort order can be reversed).By clicking on a control button on the matrix mimic, a more detailed Information View for an individual mimic can be displayed in the lower section of the dashboard. Up to three detailed Information Views can be displayed simultaneously. A control on the detailed information view allows any individual information view to be deselected (hidden).The Dashboard allows a User to suppress an individual VOD Server from contributing to the overall Live VOD Asset Status dashboard matrix. A VOD Server in suppressed mode will be identified on the matrix by a black border around the mimic. After 5 minutes (default, configurable) the applied suppression(s) will automatically be cleared.The VOD Server Status Dashboard provides click-through buttons to select:

• Network History (Alarms) Dashboard, filtered to display events for the selected VOD Server only

• The Network/Service Analysis Screens (if both the Network Management Application and Service Management Application) have been purchased, specified in Section 4.3.

• The Subscriber Selection Screen, configured to show devices currently attached to the selected VOD Server (this can be filtered to show devices currently viewing the selected VOD Server and experiencing AV errors)

Where no VOD Server name is provisioned for the VOD Server, the VOD Server shall be labelled with its IP address in dotted decimal format.

4.1.4. Network Alarms DashboardThis Dashboard presents two configurable lists of Network Alarms: the upper list contains Major Alarms and the lower list Minor Alarms. The Alarms are generated against CO, VOD Server, DVB Transmitter and potentially other network regions depending on Customer-specific Configuration. The lists can also show Service Alarms (if the Service Management Application has been purchased).The following information is provided in the Alarm List:

• Alarm history Controlo Displays or hides a threaded history of alarms (distinctive presentation, to avoid

confusion with current Alarms)• Alarm Time (timestamp when raised)• Alarm Severity

o Erroro Warningo Clearance

• Alarm Description• Alarm status

o Newo Clearedo Updatedo Overridden

• Alarm Cleared Timestamp



The user shall be able to sort the alarms displayed by any of the above fields, in either increasing or decreasing order.The alarm severities “Error”, “Warning” and “Clearance” shall correspond to the channel states described in the live channel status screen above, representing decreasing severity respectively. An error or warning alarm will be represented as cleared when a subsequent associated lower-severity alarm has been raised. The list of channel status alarms displayed shall be updated in real-time.Each Alarm is colour coded (defaults) based on the Alarm Severity, as follows:

• Error : Red• Warning : Amber• Error - Cleared or Overridden : Purple• Warning - Cleared or Overridden : Dark Amber/green

Aggregated major alarms are generated, which encompass multiple contributing alarms. Arrowhead tabs on each major alarm allow the hidden contributing alarms to be displayed. When a Major alarm is raised, all the related Minor alarms are cleared with a status of ‘Overridden’. A ‘quick-find’ facility allows the user search for alarms based on typed-in text strings.The user can filter the alarms displayed using one of the following criteria:

• Latest events• Last n events• The previous n days / hours / minutes• Specified date

o n days / hours / minutes around the date after the date before the date

The following additional filter option shall be supported• Channel name, either “all” or specified channel

4.1.5. KPI Statistics DashboardThe Network Management Application allows the User to view the KPI Statistics Dashboard described in Section 3.2.

4.1.6. Network SNMP AlarmsOn any CO status change (also rendered as a mimic colour change in the CO Matrix Dashboard) an SNMP Trap is sent to the NMS. A CO SNMP trap contains the following information:

• CO Identifier• Percentage of attached devices in error• Severity Level

o Erroro Warningo Clearance

Additionally the MiriMON server supports a MIB, allowing a 3rd party NMS to query the status of a Central Office. The following parameters are available, per CO, from the MIB:

• CO Identifier• Number of attached Devices using a Multicast Service



• Number of attached Devices using a Unicast Service• Number of Disrupted Seconds of AV delivered via the CO• Percentage of attached devices with no errors• CO Suppressed State

4.2. Service Management ApplicationThis section describes the functionality of the Standard Service Management Application, which features the following components:

• Channel Dashboards• VOD Asset Dashboard• Service History Dashboard• KPI Statistics Dashboard

4.2.1. Channel DashboardsThis Dashboard presents a matrix of Channel mimics. The display matrix can be scaled, via a ‘zoom-in’ control, to provide fewer mimics with more information or vice versa.Set for maximum information, the Channel mimics display the following information:

• The Channel Identifier/Number• The Channel Name (first characters)

o The full name of the channel shall be displayed in a mouse-over pop-up• Number of attached devices (active viewers)• Number of attached devices in error (experiencing AV errors in the last 5 minutes)• A colour coded mimic status (red, amber, green, grey) based on the percentage of the

attached devices that are ‘in error’ i.e. experienced AV errors in the last 5 minuteso The default thresholds for Channel mimic status, based on ‘in error’ devices are:

Green = <30%, Amber = <70%, Red = 70% and above, Grey = Not Applicable (example: no devices attached).

When set for more mimics on screen, any information hidden to allow scaling is available in the mouse-over pop-up.The Dashboard allows the User to sort the matrix by Identifier or Metric (the sort order can be reversed):

• channel number in ascending order• number of viewers in descending order• number of viewers in error in descending order

The following links are available from a zoomed-in Channel matrix view or from the mouse-over pop-up:

• Service History (Alarms) Dashboard, filtered to display events for the selected Channel only• The Network/Service Analysis Screens (if both the Network Management Application and

Service Management Application) have been purchased, specified in Section 4.3.• The Subscriber Selection Screen, configured to show devices currently viewing the selected

Channel (this can be filtered to show devices currently viewing the selected Channel and experiencing AV errors)

4.2.2. VOD Asset DashboardThis Dashboard presents a matrix of VOD Asset mimics, which display the following information:Confidential Page 22 of 45 © 2012 Mirifice Ltd


• The VOD Asset Identifier• An abbreviated VOD Asset name (first characters)

o The full name of the channel shall be displayed in a mouse-over pop-up• Number of attached devices (active viewers)• Number of attached devices in error (experiencing AV errors in the last 5 minutes)• A colour coded mimic status (red, amber, green, grey) based on the percentage of the

attached devices that are ‘in error’ i.e. experienced AV errors in the last 5 minuteso The default thresholds for Channel mimic status, based on ‘in error’ devices are:

Green = <30%, Amber = 30-70%, Red = >70%, Grey = Not Applicable (example: no devices attached).

When set for more mimics on screen, any information hidden to allow scaling is available in the mouse-over pop-up.The Dashboard allows the User to sort the matrix by Identifier or Metric (the sort order can be reversed):

• VOD Asset ID in ascending order• number of viewers in descending order• number of viewers in error in descending order

The following links are available from a zoomed-in VOD Asset matrix view or from the mouse-over pop-up:

• Service History (Alarms) Dashboard, filtered to display events for the selected VOD Asset only• The Network/Service Analysis Screens• The Subscriber Selection Screen, configured to show devices currently viewing the selected

VOD Asset (this can be filtered to show devices currently viewing the selected VOD Asset and experiencing AV errors)

4.2.3. Service History DashboardThis Dashboard presents two configurable lists of Service Alarms. The lists can also show Channel Alarms, VOD Asset Alarms and Network Region Alarms (if the Network Management Application has been purchased).The functionality offered is as described in the Network Alarms Dashboard, Section 4.1.4.

4.2.4. KPI Statistics DashboardThe Network Management Application allows the User to view the KPI Statistics Dashboard described in Section 3.2.

4.3. Network/Service Analysis ScreensIf the customer has purchase both the Network Management Application and the Service Management Application the additional functionality described in this section is provided.The Network/Service Analysis Screens allow the user to view:

• Service performance by Network Region• Network Region performance by Service

The additional views described in this Section are accessible form the Network Management Application and the Service Management Application dashboards.



Additional Network/Service Analysis Screens can be created to support Customer specific configurations of MiriMON that introduce additional Network Regions and Service Types. Note: For Customer specific configurations of MiriMON that introduce a large number of provisioned Network Regions and Service Types, a modification to the system hardware requirement may be necessary to support the additional processing load. Alternatively, the available Network/Service Analysis Screens may be limited to avoid the need for modifications.

4.3.1. Additional Analysis Screens from Network Management• From the CO Status Dashboard

o Click-through from an individual CO to view a VOD Server Status Dashboard for that specific CO

o Click-through from an individual CO to view a Channel Status Dashboard for that specific CO

• From the DVB Transmitter/Mux Status Dashboardo Click-through from an individual DVB Transmitter/Mux to view a Channel Status

Dashboard for that specific DVB Transmitter/Mux• From the VOD Server Status Dashboard

o Click-through from an individual VOD Server to view a VOD Asset Status Dashboard for that specific VOD Server

4.3.2. Additional Analysis Screens from Service Management • From the Channel Status Dashboard

o Click-through from an individual Channel to view a CO Status Dashboard for that specific Channel

o Click-through from an individual Channel to view a DVB Transmitter/Mux Status Dashboard for that specific Channel

• From the VOD Asset Status Dashboardo Click-through from an individual VOD Asset to view a VOD Server Status Dashboard

for that specific VOD Asset

4.4. Customer Care ApplicationThis section describes the functionality of the Standard Customer Care Application. The Customer Care Application provides direct access to a number of screens which are provided as part of the MiriMON Core (accessed via the Device Management Menu). These are:

• Subscriber Selection Dashboard – Section 3.1.1• STB Summary Dashboard – Section Error: Reference source not found• STB Health Dashboard – Section Error: Reference source not found• Event Logs Dashboard – Section 3.1.4

In addition to these dashboards, the Customer Care Application provides the following information:• Home Status Dashboard• Service Faults• Customers in Jeopardy of Churn Report (details in section 5.1.2)



4.4.1. Home Status DashboardThe home status dashboard presents a graphical and colour coded view of the customer home and services, for the most recently selected subscriber or device. Information is presented through mimics, which can be selected to open a Dashboard that provides further information.Signal Strength and Content play outThe dashboard presents a clear graphical view of the internal status of signal strength and content play out on the device, through the following mimics:

• DVB Signal Healtho Links to STB Summary

• Home Network Status – Errors above Thresholdo Links to STB Summary

• DVB Channel play-out performance – Errors above Thresholdo Links to STB Summary

• VOD play-out performance – Errors above Thresholdo Links to STB Summary

• IP Multicast play-out performance – Errors above Thresholdo Links to STB Summary

• PVR content play-out performance – Errors above Thresholdo Links to STB Summary

This information is measured on the individual device.Home Network and the Device HealthThe dashboard presents a clear graphical view of the internal status of the home network and the device health

• Device On-line Status – No Device communications in the last 10 minutes (default) o Links to STB Summary

• Hard Drive Temperature – Above Thresholdo Links to STB Health

• CPU Temperature – Above Thresholdo Links to STB Health

• CPU Load – Above Thresholdo Links to STB Health

• Memory Levels – Above Thresholdo Links to STB Health

This information is measured on the individual device.Delivery Network and Service HealthThe dashboard presents a clear graphical view of the external status of the specific network path(s) and service(s) used by the device, including:

• DVB Transmitter/Mux Error Status• CO Error Status• VOD Server Error Status• DVB Channel Error Status



• IP Channel Error Status• VOD Asset Error Status

Selecting any of the listed mimics in this section will navigate to the matrix for the sub-population of which the device is a current member with the membership selected.This information is derived from the peer groups of devices that are accessing the same service or reside in the same network region (MiriMON supports multiple hierarchical network regions as a Customer-specific configuration option).

4.4.2. Service FaultsThis Dashboard displays a list of all reported errors for AV QoS and network statistics for VOD assets, time-shifted programmes and multicast channels. The list of errors is sorted in time order, most recent error last. The time period covered can be specified.Each list entry has the following fields:

• Time: The date and time at which the event was raised by the subscriber equipment.• ID: The multicast channel number followed by (M), or the VOD asset ID followed by (V), or

the time-shifted programme followed by (TS), from which the disruption originated.• Channel/VOD title: The name of the Multicast Channel, DVB Channel or of the VOD asset.• Programme: The name of the programme for time-shifted programmes.• Description: An explanation of what the event represents in term of equipment and stream

failure.The mapping of names to asset IDs, programme IDs and multicast channel numbers is configurable.The viewing time period can be configured on the Dashboard.

4.4.3. Device Health GraphsThe dashboard displays a number of graphs ploting information for an individual device. The graphs can display historical data for up to 7 days and 23 hours into the past.The following measurements are provided:

• Device CPU Load• Device Memory Utilisation• Device IP Network Traffic• VOD Start-up Time• IP/DVB Channel Start-up Time

4.5. Consumer Insight ApplicationThis section describes the functionality of the Standard Consumer Insight Application. The Standard Application provides the following information:

• IP Channel Popularity Dashboard• VOD Popularity Dashboard• Average Channel Change Time Report (details in section 5.1.3)• Channel Peak Viewing Figures Report (details in section 5.1.5)• Channel Consumption by Duration Report (details in section 5.1.6)• Channel Consumption by Band Report (details in section 5.1.7)• Channel Consumption by Subscriber Category Report (details in section 5.1.8)



• Channel Unique Viewers Count Report (details in section 5.1.9)• Time-shifted Consumption of Channels Report (details in section 5.1.10)• VOD Purchases per Subscriber Report (details in section 5.1.11)• Overall VOD Consumption Report (details in section 5.1.12)• AV Quality of Service Over Time Report (details in section 5.1.17)• Maximum Peak Viewers Across all Channels Report (details in section 5.1.18)

4.5.1. Channel Popularity DashboardPresents a live ordered list of the 50 (default) most popular and 50 (default) least popular IP channels, as ranked by the current number of viewers, detailing

• Ranking Position• Current number of viewers• Channel number• Channel name• Percentage of all broadcast channel viewers currently watching this channel.

4.5.2. VOD Popularity DashboardPresents a live ordered list of the 50 (default) most popular and 50 (default) least popular VOD assets, as ranked by the current number of viewers, detailing:

• Ranking Position• Current number of viewers• Asset number• Asset name• Percentage of all broadcast channel viewers currently watching this asset.



5.MiriMON ReportsMiriMON generates a set of standard reports, according to the applications installed. The reports are generated as pdf and xls (csv) format. Further information about report configuration and generation is found in 7.4 and 7.5.

5.1.1. Network Central Office ReportThis Report provides information about the performance of each Central Office over a 24 hour time period (default). The report shall graph the following metrics for each CO over the 24 hour period, at 5 minute intervals:

• Active STB count (unicast)• Active STB count (multicast)• AV quality (% of AV seconds not in error)• AV quality (% of STBs without an AV error)• Total network traffic (multicast)• Total network traffic (unicast)

5.1.2. Customers in Jeopardy of Churn ReportThis report identifies a proportion of customers that have experienced a poor Quality of Experience and hence may reduce their service consumption and ultimately leave the network operator.In addition to the reporting period, the following parameters shall be specifiable for generation of the report data:

• Slow channel change time threshold (default 6 seconds)• Fast channel change time threshold (default 1 second)• Target channel change time (default 2.5 seconds)

For each customer for which data is available during the reporting period, the following information shall be generated for use within the report:

• Number of VOD purchases• Total length of VOD sessions (minutes)• Percentage of VOD session playback that was free of AV errors• Count of AV QoS error counts during the VOD sessions• MiriMON Opinion Score (MOS) for the customer's VOD sessions• Number of multicast channels viewed• Mean channel change time (seconds)• Count of slow channel changes, where a channel change is categorised as slow if longer than

the threshold above• Total length of channel viewing (seconds)• Percentage of channel viewing that was free of AV errors• MiriMON Opinion Score (MOS) for the customer's channel change timings• MiriMON Opinion Score (MOS) for the customer's channel AV QoS

The report shall include a configurable number of customers with the highest churn index for each subscriber category.The report shall group the customer data presented by subscriber category.

5.1.3. Multicast Average Channel Change Time ReportThis report examines the time to change to each multicast channel, over the specified reporting period. The report provides the following for each multicast channel:



• The arithmetic mean and standard deviation values for each of:o Time to join IGMP multicast stream;o Time to start video buffer playback;o Time to start audio buffer playback;o Time to complete the channel change.

• The fastest channel change time achieved by a STB• The percentage of channel changes that failed to complete within the MiriMON Agent

configured threshold of 6 seconds.The report supports the specification of the expected minimum and maximum channel time thresholds, outside of which the channel will be identified in the report summary as being either above or below expectation accordingly.

5.1.4. DVB Average Channel Change Time ReportThis report examines the time to change to each DVB channel, over the specified reporting period. The report provides the following for each DVB channel:

• An arithmetic mean and standard deviationo Time to Carrier Detecto Time to Tuner Lock o Time to Display Video Frameso Time to Play Audio Streamo Time to Complete Channel Change

• The fastest channel change time achieved by a STB• The percentage of channel changes that failed to complete within the MiriMON Agent

configured threshold of 6 seconds.The report supports the specification of the expected minimum and maximum channel time thresholds, outside of which the channel will be identified in the report summary as being either above or below expectation accordingly.

5.1.5. Channel Peak Viewing Figures ReportThis report identifies the maximum number of subscribers viewing each multicast channel, for the specified day. The report identifies, for each multicast channel:

• the maximum number of (MiriMON enabled) subscribers viewing the channel for each hour within the 24 hour reporting period

• the peak number of viewers attained over the 24 hour reporting period

5.1.6. Channel Consumption by Duration ReportThis report determines the average time spent watching each multicast channel continuously, over the specified reporting period. The report provides, for each multicast channel, the arithmetic mean and standard deviation values for the time spent watching the channel continuously, excluding sessions shorter than 10 seconds.

5.1.7. Channel Consumption by Band ReportThis report determines for each multicast channel the percentage of viewers watching the channel by duration band, where the bands are defined as 0-4 minutes, 5-9 minutes etc. as below. The report provides, for each multicast channel, the percentage of viewers who watched the channel continuously for an average of:



• 0 minutes to less than 5 minutes;• 5 minutes to less than 10 minutes;• 10 minutes to less than 20 minutes;• 20 minutes to less than 30 minutes;• 30 minutes to less than 40 minutes;• 40 minutes to less than 60 minutes;• 60 minutes to less than 90 minutes;• 90 minutes or more.

Sessions shorter than 10 seconds shall be excluded from the report.

5.1.8. Channel Consumption by Subscriber Category ReportThis report delivers the total length of time viewed for each multicast channel within the report period. Total consumption time is calculated as the sum of all viewing sessions longer than 10 seconds. The report lists the following for each multicast channel:

• Total time viewed for all subscribers in each subscriber category• Total time viewed for all subscribers across all subscriber categories

5.1.9. Channel Unique Viewers Count ReportThis report provides a count of the unique number of viewers (“eyeballs”) for each multicast channel within the report period. The report provides the following information for each multicast channel:

• Total number of unique viewing devices

5.1.10. Time-shifted Consumption of Channels ReportThis report delivers, for each multicast channel, the total length of time for which the channel was viewed as time-shifted within the report period. The report provides the following information for each multicast channel:

• Total time viewed as time-shifted programmes.

5.1.11. VOD Purchases per Subscriber ReportThis report delivers VOD usage figures over the specified reporting period. The report provides the total and percentage of all MiriMON-enabled subscribers who have purchased the following number of VOD titles:

• 0• 1• 2-5• 6-9• 10+

5.1.12. Overall VOD Consumption ReportThis report provides a summary of the popularity and performance of each VOD asset, over the specified reporting period. The report provides the following information for each VOD asset:

• Total number of purchases• Total number of views• VOD title



• Arithmetic mean error rate (where the error rate of an asset is calculated as the percentage of the asset play out time that experienced AV QoS errors)

• Arithmetic mean and standard deviation for the time to start play out of the asset from invocation.

5.1.13. VOD by Customer Usage Report

This report provides usage details for each active VOD asset. The report provides the following information for each VOD asset.

• Total number of views• Total number of views per purchase• VOD title• Number of viewers who watched more than 30 seconds• Number of viewers who watched more than 1 minute• Number of viewers who watched more than 10 minutes• Number of viewers who watched more than 60 minutes• Number of viewers who watched the full VOD asset

5.1.14. VOD by Genre This report provides VOD asset viewing summary data grouped by Genre.The report provides the following information for each VOD asset.

• Total purchased• Total number of views• VOD title• Average Percentage watched• Total of full viewings• Total Revenue

5.1.15. VOD Purchases per Subscriber This report provides a breakdown of the number and percentage of subscribers who have purchased VOD assets. The report provides the following information:

• The number and percentage of subscribers that have never bought an asset• The number and percentage of subscribers that have only bought 1 asset• The number and percentage of subscribers that have bought 2 to 5 assets• The number and percentage of subscribers that have bought 6 to 9 assets• The number and percentage of subscribers that have bought more than 10 assets

5.1.16. VOD RevenueThis report provides a summary of the revenue generated for each VOD assetsThe report provides bar charts showing the assets that generated the most and least revenue.The following information is provided in a tabular form:



• Vod title• Revenue• Number of Purchases• Provisioned Cost• Actual Cost

5.1.17. AV Quality of Service Over Time ReportThis report tracks the AV quality of service for each multicast channel. The report graphs the percentage of play out that is free of AV errors, for each known channel at hourly intervals over the report period, with the following conditions:

• A channel-viewing session by a subscriber shall contribute to the report from the start of successful channel change to channel stop

5.1.18. Maximum Peak Viewers Across all Channels ReportThis report shows the maximum consumption of broadcast services over time. The report graphs the maximum number of viewers across all channels over the report period, at hourly intervals

5.1.19. HLS Rate Over Time ReportThe HLS Rate Over Time report presents four graphs showing how the adoption of each HLS rate varies over time, comparing the rates by proportion, bandwidth used, session count, and an alternative view of session count. This report is provided for all channels.

5.1.20. HLS Rate By Channel ReportThe HLS Rate by Channel report presents graphs showing how the adoption of each HLS rate varies over time, channel by channel, comparing the adoption rates by proportion, total bandwidth used, and session count. The report is provided over a specified time period.

5.1.21. HLS Rate Change Activity ReportReport includes a count of HLS bandwidth changes against time by HLS bandwidth, for all channels, showing the HLS rate change activity. The graphs includes absolute and relative counts of session starts and stops over time, counts of rate changes up over time , counts of rate changes down over time and counts of rate change reverts.



6.MiriMON Monitoring FeaturesAgent-Server Communications use HTTP and TCP.The Agent processes and aggregates the raw telemetry and only sends meaningful data to the MiriMON Server.Default MiriMON configurations instruct the Agent to report meaningful data to the Server in real-time. The configuration can be modified to instruct the Agent to cache all events and measurements and to report them periodically. Periodic telemetry measurement on the device and Server reporting can also be configured (e.g. a periodic Agent Heartbeat). In the event that the MiriMON Server is unreachable (i.e. no connection or transmission acknowledgement received – due to a network outage) the Agent buffers the reporting data and periodically retries to transmit to the MiriMON Server.MiriMON Configurations can be ‘soft’ updated on a device without any interruption to the normal operation of the device. Updating of the MiriMON agent is achieved through a conventional Firmware upgrade.

6.1. Standard Agent ConfigurationsMirifice will deliver a standard reference configuration (per Consumer Device model), which will provide the following reporting profile:

• Standard Reporting Configuration - a balance between error reporting detail and bandwidth)• Real-time reporting of important information and errors• Periodic reporting of measurements• Reporting ‘back-off’ in the case that the server cannot be contacted, including caching of

Events until the Server can be contacted.o In the case of a prolonged outage, the event store (sized at 125 events) may fill. In

this circumstance the oldest event will be replaced when a new event is generated.



7.MiriMON AdministrationThe following sections describe the standard MiriMON System Administration interfaces and tools.

7.1. User Account DashboardThe User Account administration screen presents options to update permissions and details of the MiriMON system users. Users can be added, deleted and updated. The following User attributes can be edited:

• Username• Full name• E-mail address• Start page• Password (change)

The following Application Access Permissions can be granted (by selecting a checkbox to grant access):

• Network Management• Service Management• Device Management• Customer Care• Executive KPIs• Consumer Insight• User Administration

7.2. Session AuditMiriMON maintains an access log for simple user login and logout.

7.3. Dashboard ConfigurationThe error state or alarm state thresholds can be configured by Mirifice to levels specified by an operator.The text labels associated with error state or alarm state thresholds can be configured by Mirifice to strings specified by an operator.The status of all channels shall be updated at a configurable frequency (default 10 seconds).Operators can make minor modifications to the Dashboards (graphics and layout position, via JavaScript changes). The operator is responsible for replicating any minor modifications to the Dashboards following the installation of a new MiriMON release.Operators cannot implement new Dashboard Screens, KPIs or Matrix/Mimics. Mirifice can implement new Dashboard KPIs or Matrix/Mimics (driven by sub-population analysis) on a Change Request or Roadmap Acceleration basis.

7.4. Report ConfigurationThe MiriMON Server stores MiriMON information within Foundation tables, held within the MiriMON Foundation RDBMS. This Bridging and Reports table data is maintained in a separate RDBMS to the MiriMON Foundation RDBMS. The MiriMON Reports server provides a web-based framework for the generation and management of report sets, which are used to organise the bridging tables. Provided with MiriMON are Crystal Reports template files, which are used to define



the exact rendering of the report data. The Crystal Reports template files can be edited by the customer. Support for the use of Logicity is provided in order to be able to offer an automated, turnkey solutionThe system shall generate a summary email message after generation of each report set, indicating success or failure of the operation.The system supports the generation of a set of reports, either as a one-off activity, or according to a repeating schedule.The following attributes can be configured for each report set:

• Description;• Report frequency: one-off or repeating;• Distribution list as a set of email addresses;• Reports to be included in the reports set.

One-off report sets support a start date and an end date for the reporting period, where the period starts at 00:00:00 on the start date and finishes at 23:59:59 on the end date.Repeating report sets shall support a repeat interval specifiable as one of daily, weekly or monthly. Repeating report sets shall support specification of the time of day at which the report set will be regenerated. Each Crystal Report template may support additional configuration according to its design, including thresholds for expected performance.Reports are also generated in spreadsheet (.xls) format to allow .csv inport to other tools, and further data manipulation.

7.5. Report CreationOperators cannot write their own Reports. If an Operator requires a new report, in addition to the standard Reports supplied with the purchased Applications, Mirifice can write the new Report for the Operator on either a Change Request or Roadmap Acceleration basis.

7.6. Provisioning of Operator Supplied DataCustomer/operator supplied data is required to enable some of MiriMON’s features. This data typically includes:

• Subscriber Identifier to Device Identifier o Without this provisioning information MiriMON is anonymous (by default) and

therefore does not compromise subscriber privacy or introduce any issues around data protection. This provisioning links an individual subscriber to the monitored consumer device. The operator is responsible for ensuring that this is acceptable to its subscribers and relevant legislators.

o This information is also a means of grouping devices by Subscriber/Household.• Channel Name to Channel Identifier• VOD Asset Name to VOD Asset Identifier• Network Location to Device Identifier (Device mapping to each reported Network Region,

with up to 16 layers of network topology. Within the schema the data provided has a number of network element types and the relationship between network elements and associated devices provides the implied dependencies between elements and the layers of the network

MiriMON provides a mechanism to import this mapping data in an XML format (and to subsequently import data updates to keep the data current). The required XML formats and import mechanisms are specified in XSD files in the MiriMON provisioning specification (ref 500/001/061).



7.7. Creating an Agent ConfigurationOperators cannot write their own agent configurations. Mirifice will provide operators with new configurations, beyond the standard configurations supplied, on a Professional Services basis.

7.8. Agent Configuration TuningThe agent configurations provided will be tuned to adjust thresholds and reporting periods during the MiriMON commissioning process.

7.9. Distributing an Agent ConfigurationOperators are free to distribute the supplied MiriMON Agent Configurations to individual, groups or all Devices.It would not be prudent to deploy a verbose configuration (with detailed and frequent telemetry event reporting) to a large population of devices as this would significantly increase the load on the network and MiriMON Server for the period in which this configuration change is applied. The Operator will receive guidance, during MiriMON training, on the appropriate distribution of the agent configurations available to the Operator.MiriMON includes a command line Agent Configuration Assignment tool (mmme) that allows a user to specify which configurations are deployed to your population of Monitored Devices.The Agent Configuration Assignment tool can display when a MiriMON-enabled Consumer Device first connected to the MiriMON Server.

7.10. Agent Remote ControlMiriMON includes a command line Agent Remote Control tool (mmarc) that allows the operator to remotely control MiriMON Agents. The two most common uses of this function are:

• Invoke an Agent Configuration update on one or more devices• Suppress reporting in the event that exceptional network conditions are provoking an

abnormally high level of Agent reportingAgents can be instructed to join or leave ARC groups.

As an alternative mechanism (where UDP broadcast is not available) the agent can be controlled remotely by an flag in the response from the MiriMON server when information is delivered. This mechanism provides a subset of the functions that are available via the Agent Remote Control tool and supports the following requests:

• Invoke an Agent Configuration update (mmreload)



8.MiriMON Integration InterfacesThe Standard MiriMON Product Interfaces are described in the main body of this Specification.The actual functionality provided to an individual operator may vary in the following circumstances:

• Additional functionality has been implemented following an operator request• Some standard functionality is not appropriate for the operator’s specific network, service

offering or consumer devices managed.Any delta from the ‘standard’ MiriMON Integration Interface functionality will be specified in the Appendices.

8.1. MiriMON Web ServicesMiriMON web services interface provides the information viewed on the web UI to 3rd party client systems via a web services interface using a request/response mechanism. (These are available as an option). MiriMON web services are independent of the implementation protocol e.g. SOAP, XML-RPC or JSON. The Web Services will be specified in their own definition specification, for example, this may take the form of a WSDL, XSD or JSON schema. The default delivery protocol is SOAP.As an example of the process, a request for a list of items, such as all Central Offices, yields a response consisting of an array of ID and name pairs. The ID is an internal representation that can be passed back to the server in a request for the full details of the specified item. The name is suitable for display to an operator. The following sections detail the information that is available to the web services interface (more details can be found in the document; MiriMON Client-Web-Services 501/001.057.

8.1.1. Network Status• Central Office (CO) Status – returns the following

o CO nameo CO IDo Number of devices listening to Multicast (per CO)o Number of devices listening to Unicast (per CO)o Number of devices online (per CO)o Total number of devices (per CO)o Number of Multicast packets (per CO)o Percentage error -free seconds (per CO)

• VOD Server Status – returns the followingo VOD server nameo Number of sessions in progress (per server)o Number of sessions in error (per server)o Number of sessions that failed to start (per server)o Average session start-up time (per server)o Seconds of disruption (per server)

• Transmitter Status – returns the followingo Name of transmitter/muxo Number of devices tuned to transmitter/mux



o Number of tuned devices in error (per TX/Mux)o Requested frequency in MHzo Maximum reported frequencyo Minimum reported frequencyo Mean bit error rate (BER)o Mean uncorrected block count (UBC)o Mean signal to noise ratio (SNR)

• Network Element (NE) Type List - returns the followingo A list of network element type names

• Network Element (NE) Listo A list of network element names

• Network Element (NE) Status – returns the followingo Network element typeo Network element nameo Total number of devices associated with network elemento Number of devices online (per NE)o Number of devices in error (per NE)

• KPI Statistics – returns the following for the whole networko VOD – mean time to receive an RTP packet after an RTSP is sent (ms) (+ standard

deviation)o VOD – mean time from request to start of download (+ standard deviation)o VOD – mean time to display video frames (+ standard deviation)o VOD – mean time to play audio (+ standard deviation)o VOD – mean time for complete session start-up sequence (+ standard deviation)o IP QoS – mean number of TCP stack errors from received packetso IP QoS – mean number of received packets droppedo IP QoS – mean number of frame alignment errors receivedo IP QoS – mean number of FIFO overrun errors receivedo IP QoS – mean number of packets transmittedo IP QoS – mean number of TCP stack errors for transmitted packetso IP QoS – mean number of transmitted packets droppedo IP QoS – mean number of transmission collisionso IP QoS – mean number of transmission overrun errorso IP Channel timing – mean time (ms) to join multicast stream (+ standard deviation)o IP Channel timing – mean time to display video frames (+ standard deviation)o IP Channel timing – mean time to play audio stream (+ standard deviation)o IP Channel timing – mean time for complete channel change sequence (+ standard

deviation)o DVB Channel timing – mean time to detect carrier signal (+ standard deviation)o DVB Channel timing – mean time to attain tuner lock (+ standard deviation)o DVB Channel timing – mean time to display video frames (+ standard deviation)o DVB Channel timing – mean time to play the audio stream (+ standard deviation)



o DVB Channel timing – mean time for complete channel change sequence (+ standard deviation)

o Device counts – total number of MiriMON enabled deviceso Device counts – total number of MiriMON enabled devices currently onlineo Device counts – total number of MiriMON enabled devices that are idleo VOD A/V QoS – total number of devices contributing to statisticso VOD A/V QoS – percentage of devices experiencing no errorso VOD A/V QoS – percentage of devices with buffer underflow errorso VOD A/V QoS – percentage of requests that have failedo IP A/V QoS – total number of devices contributing to statisticso IP A/V QoS – percentage of devices experiencing no errorso IP A/V QoS – percentage of devices experiencing frame losso IP A/V QoS – Percentage of devices experiencing frame errorso IP A/V QoS – percentage of devices experiencing video buffer overflowo IP A/V QoS – percentage of devices experiencing video buffer underflowo IP A/V QoS – percentage of devices experiencing audio buffer overflowo IP A/V QoS – percentage of devices experiencing audio buffer underflowo IP A/V QoS – percentage of devices experiencing video absent errorso IP A/V QoS – percentage of devices experiencing audio absent errorso DVB A/V QoS – total number of devices contributing to statisticso DVB A/V QoS – percentage of devices experiencing no errorso DVB A/V QoS – percentage of devices experiencing frame losso DVB A/V QoS – percentage of devices experiencing frame errorso DVB A/V QoS – percentage of devices experiencing video buffer overflowo DVB A/V QoS – percentage of devices experiencing video buffer underflowo DVB A/V QoS – percentage of devices experiencing audio buffer overflowo DVB A/V QoS – percentage of devices experiencing audio buffer underflowo DVB A/V QoS – percentage of devices experiencing video absent errorso DVB A/V QoS – percentage of devices experiencing audio absent errorso Subscriber count – count of valid subscriber deviceso SNMP trap alarm statistics for devices with IPTV service severely degraded or down

8.1.2. System Alarmso Time alarm was raisedo Alarm severityo Alarm descriptiono Alarm Statuso Time alarm was cleared (blank if still active)o Data registers

8.1.3. System Status• VOD Asset List



o VOD internal IDo VOD asset name

• VOD Asset Statuso VOD asset nameo VOD asset IDo Total number of viewerso Total number of viewers experiencing an error

• IP Channel List o IP Channel internal IDo IP Channel name

• IP Channel Statuso IP Channel nameo IP Channel IDo Total number of viewerso Total number of viewers experiencing an error

• DVB Channel Listo DVB Channel internal IDo DVB Channel name

• DVB Channel Statuso DVB Channel nameo DVB Channel IDo Total number of viewerso Total number of viewers experiencing an error

8.1.4. Consumer Insight• VOD Popularity (descending order of popularity)

o VOD asset nameo VOD asset IDo Number of viewers achieved per asseto Percentage of viewers per asset

• IP Channel Popularity (descending order of popularity)o IP Channel nameo IP Channel IDo Number of viewers achieved per channelo Percentage of viewers per channel

• DVB Channel Popularity (descending order of popularity)o DVB Channel nameo DVB Channel IDo Number of viewers achieved per channelo Percentage of viewers per channel



8.1.5. Customer Device Summary• Installation Status

o Available memory (KB)o CPU load averageo Time since last reset (seconds)o Hard drive temperature (degrees C)o CPU temperature (degrees C)o Time since reset reported by MiriMON servero Last reported uptime

• VOD A/V QoSo Total A/V frame losso Total A/V frame errorso Count of video buffer overflowo Count of video buffer underflowo Count of audio buffer overflowo Count of audio buffer underflowo Count of A/V audio errorso Count of video absent episodeso Count of audio absent episodeso Count of total A/V error episodes

• IP Network QoSo Number of packets receivedo Number of receive stack errorso Number of transmit stack errorso Number of receive frame errorso Number of receive FIFO errorso Number of transmit collisionso Number of transmit FIFO errorso Number of received UDP packetso Number of transmitted UDP packetso Number of received packets dropped by TCPo Number of transmit packets dropped by TCPo Total bandwidth used for receivingo Total bandwidth used for transmittingo Number of IP packets receivedo Number of IP packets transmittedo Number of corrupted IP packets receivedo Total number of received datalink byteso Total number of transmitted datalink byteso Number of received datalink frameso Number of CRC errors in received packets



o Number of datalink collisionso Number of IGMP groups joined

• IP Multicast A/V QoSo Number of seconds of VOD QoS disruptiono Total A/V frame losso Total A/V frame errorso Count of video buffer overflowo Count of video buffer underflowo Count of audio buffer overflowo Count of audio buffer underflowo Count of A/V audio errorso Count of video absent episodeso Count of audio absent episodeso Count of total A/V error episodes

• Device Statisticso Number of channel changeso Number of time-shift play requestso Number of VOD play requests

• Configurationo Pathname/filename of configuration file loaded into deviceo Display name of CO to which the device belongso Display name of VOD asset or channel being viewedo Display name of VOD server to which device is attached

• Configuration Networko Display name of network element within network element type to which the device

belongs• Registration

o The time the device was registered (0 if unknown)o The time the device was first connected to MiriMON (0 if unknown)o The time the device was last connected to MiriMON (0 if unknown)o Number of times the device has connected to MiriMONo Pathname of last configuration file sent to deviceo Pathname of default configuration file assigned to deviceo Hardware version reported by deviceo IP address assigned to deviceo Model number reported by deviceo Serial number reported by deviceo Software version reported by deviceo Manufacturer device codeo ID of any smartcard currently insertedo MAC address of device (primary interface)



8.1.6. Device Eventso Time alarm was raisedo Alarm severityo Information in data registerso SNMP trap alarm status for if IPTV service is severely degraded or down

8.1.7. Device Service Faultso Time fault was raisedo VOD asset ID or channel IDo Service type e.g. VOD, TV, PVRo Title of content experiencing faulto Programme ID for time-shifted or VOD contento Alarm description

8.1.8. Device Health• Device CPU Load

o Time at which readings were takeno 1 minute load averageo 5 minutes load averageo 15 minutes load average

• Device Memory Utilisationo Time at which readings were takeno RAM allocated (KB)o RAM available (KB)o Swap allocated (KB)o Swap available (KB)

• Device IP Network Traffico Time at which readings were takeno Number of packets receivedo Number of compressed packets receivedo Number of bytes received per secondo Number of bytes transmitted per second

• VOD Start-up Timeo Time at which VOD was startedo VOD session start-up time (ms)

• IP Channel Start-up Timeo Time at which IP channel was startedo Channel start-up time (ms)

• DVB Channel Start-up Timeo Time at which IP channel was startedo Channel start-up time (ms)



8.1.9. Subscriber Search• All Subscribers

o UID of subscribero UID of subscriber’s deviceo IP address of deviceo Time from which subscriber’s account is valido Time to which the subscriber’s account is valid

• Selected Subscribers (matched criteria)o UID of subscribero UID of subscriber’s deviceo IP address of deviceo Time from which subscriber’s account is valido Time to which the subscriber’s account is valid

• Subscribers by Network (matched by the following); CO, IP Channel, DVB Channel, VOD asset, VOD server, Transmitter / Multiplexer

o UID of subscribero UID of subscriber’s deviceo IP address of deviceo Time from which subscriber’s account is valido Time to which the subscriber’s account is valid

• Subscribers by Network Elemento UID of subscribero UID of subscriber’s deviceo IP address of deviceo Time from which subscriber’s account is valido Time to which the subscriber’s account is valid

8.2. SNMP Traps and MIBThe MiriMON server includes an SNMP agent to provide information to a 3rd party Network Management Systems (NMS). The specific traps and MIB records provided are specified within the relevant MiriMON Applications and Core Functionality Sections.

8.3. SMTP Report DeliveryBy default, the MiriMON server delivers Historical Reports to Users via SMTP. The specific Reports delivered are specified within the relevant MiriMON Applications Sections.Customer/Operator is required to provide suitable SMTP support to enable this feature.



9.MiriMON Security

9.1. Agent Server ReportingMiriMON Agents do not provide any external service APIs or scope for Consumer Device control.All MiriMON Server control messages (ARC tool) are sent to the MiriMON agent on the Consumer Device in a secure encrypted format (AES-128 bit).Other agent control mechanisms rely on the agent initiated HTTP event delivery sequence with the connected server and provide only a limited set of agent management actions (e.g. to reload a configuration).Agent Configurations are signed, to ensure that only a valid Configuration from the genuine MiriMON server is accepted and loaded by a MiriMON Agent.MiriMON Agent/Server messaging is subject to authentication and payload checksum controls, to avoid tampering or spoofing of communications.

9.2. User SessionsUser Sessions are controlled by conventional system login procedures.User access to MiriMON functions is controlled by conventional permissions system.Reports are distributed using SMTP to recipients defined by the MiriMON Administrator.No user, other than the Database Administrator, by default, has direct access to the database information.


Documents

MiriMON 3 18 Specification V1C Draft