Project Implementation Plan

for Nevron IPTV system

All rights reserved. The information contained in this document is confidential and may also be proprietary and trade secret. Without prior
written approval from Nevron d.o.o. no part of this document may be reproduced or transmitted in any form or by any means, including
but not limited to electronic, mechanical, photocopying or recording or stored in any retrieval system of whatever nature. Us e of any
copyright notice does not imply unrestricted public access to any part of this document. Nevron d.o.o. trade names used in this document
are trademarks of Nevron d.o.o. Other trademarks are acknowledged as the property of their rightful owners. Copyright 2020
Contents
1. Introduction .............................................................................................................................. 3
2. System overview........................................................................................................................ 3
2.1 System components ........................................................................................................... 3
Middleware servers ................................................................................................................... 3
Streamer servers ....................................................................................................................... 3
Devices ...................................................................................................................................... 3
2.2 System structure ................................................................................................................ 4
2.3 Assumptions and Constraints ............................................................................................. 5
2.4 Glossary ............................................................................................................................. 5
3. Management overview .............................................................................................................. 5
3.1 Description of implementation ........................................................................................... 5
3.2 Points of contact ................................................................................................................ 6
3.3 Major tasks ........................................................................................................................ 6
3.3.1 Planning the installation ............................................................................................. 6
3.3.2 Gathering data before installation .............................................................................. 6
3.3.3 Pre-installation requirements ............................................................................................ 7
3.3.4 PHASE 1: Setting IPTV with tv channels working ............................................................. 10
3.3.5 Preparation for phase 2 ................................................................................................... 12
PHASE 2: Setting full content on TV .......................................................................................... 13
4. Acceptance criteria .................................................................................................................. 14
5. Documents available................................................................................................................ 14
6. Appendix 1: System Hardware Inventory ................................................................................. 14
7. Appendix 2: System Software Inventory ................................................................................... 15

2
 1. Introduction

Purpose of this plan is to optimize the implementation of IPTV system in new property location. We
will present our plan which you can follow, along with guidance’s how to troubleshoot common
issues that may occur. IPTV system comes preinstalled on servers which means that this plan is
focused on how to set/connect IPTV system in your environment, not on how to install IPTV
software on servers.

2. System overview

2.1 System components

In this section you can see what IPTV equipment is and what was provided to the client. IPTV
equipment comes preinstalled which means that all required software is already installed on servers.

Middleware servers
Middleware (short: MW) is software that provides common services and capabilities to applications
outside of what is offered by the operating system. Data management, application services,
messaging, authentication, and API management are all commonly handled by middleware. From
our middleware runs all software for devices. Only live streams run from Streamer server and
sometimes we install this on that server too. Depends on size of project.

Number of units on this project: _______

Streamer servers
A streaming server or gateway server (short: GW) delivers live or on-demand multimedia content to
client devices. Server runs on Centos OS and on top of that is our own made product Streamer
Manager that can capture live TV from various sources (depends on cards inserted) and transforms
them to multicast streams. In case live streams are delivered from other gateways server or Telco
provider then our streamer server is not needed.

Number of units on this project: ________

Devices
Client devices is a piece of computer hardware or software that accesses a service. In our case this
are Android Set top boxes, Smart TVs (models confirmed by Nevron), Windows PCs or Mobile
phones.

Number of units on this project: ______

Type of devices on this project: _____________________

3
 2.2 System structure

Each IPTV server has two network cards, one (usually eth0 or em1) is for public access and second
(eth1 or em2) is for IPTV network where devices and live streams run. We label ports if equipment is
sent from our preparation office.

All IPTV servers are connected with IPTV port to same network that is isolated from other networks
on location. On that IPTV network are connected only IPTV devices and IPTV servers and only one
DHCP runs in it. DHCP and DNS run from IPTV MW server. Client can set own DHCP but in that case
we need to close our DHCP and client need to set proper DNS linking.

Basic IPTV schema over ethernet cable:

Example of network with more devices:

4
 2.3 Assumptions and Constraints
Setting up IPTV system at location we split in two phases. Goal of first phase is to get live TV
channels working on devices. Second phase is to get additional content appear on TV screens in
connection with PMS/HIS systems.

First phase is usually done in one day if client has all necessary requirements and resources. Second
phase usually takes from weeks to months to gather all content for IPTV.

On the day of installation is required that network and cable companies are present at location or
available to help remotely in case the pre-installation requirements were not set properly or were
not understood correctly.

2.4 Glossary
- MW, IPTV MW – middleware server
- GW , IPTV GW – gateway server
- Streamer = gateway = head-end (different terminology ) -gateway server
- STB – Set top box = encoder
- Smart TV – smart TVs that support connecting to other IPTV MW servers

3. Management overview

3.1 Description of implementation

Installation of IPTV system will use Phase approach. We will split installation in two phases, Phase 1:
TV only on TV, and Phase 2: Full content on TV.

Phase 1: All servers are connected and all devices are connected on their final locations (rooms) and
live channels are running on those devices. This can be done in one day. Usually it takes 10min to
connect one device in room and this can help you calculate how many people you need to schedule
for this task.

Here we must emphasize and will do on many occasions that support of network and cable company
is required. They know how they set their equipment and they can solve issues/questions quickly.
Also support of client is necessary that provides enough staff to help with realisation.

Phase 2: At the end of phase 1 we again present the demo content and advise client to prepare own
content. We also as for IP and port to connect to PMS in phase 1, so we get info till phase 2 starts.
After client prepares content (pictures, text, prices) we set training with them to help them structure
the content on IPTV and help them with first steps. Phase 2 is completed when content is set and
PMS is connected. Can take from 2 weeks till months till content is prepared. If it’s existing project
then content is easier to gather from webpage or brochures, while in new constructions it takes
much longer.

5
 3.2 Points of contact
In this section we will list all responsible persons that needs to be involved for successful and quick
implementation.

Role on this project Name Contact (email , skype or

phone..)
Property manager
Site implementation
representative
Project partner
Nevron representative Sonia Malavasic support@nevron.eu
System maintainer at location
Network representative
person
PMS/HIS representative
person
Signal cable representative
person

3.3 Major tasks

3.3.1 Planning the installation
3.3.1.1 Plan with client and all companies involved what time is most suitable to do installation

Explain to client what needs to be done in installation process and what resources you will need
from them. With new building is easier because only pre-instillment requirements needs to be met.
With already running property it’s trickier and ask client when would be the most suitable time for
them, then try to get other companies involved to accommodate this date. For running hotel would
be suitable to do installation on the day that they have low check-ins, or in low season.

3.3.1.2 Plan how many people you can get to help and what would be optimum number

You already know the size of project and based on that you can calculate how long would it take to
install all devices in rooms. If you want it done faster, you can try to get more people to do the job.

It is important you talk to client to give you access to the rooms and all support you will need. If it is
running property, then they should give you cleaning ladies or other staff to escort the other
workers.

3.3.2 Gathering data before installation

3.3.2.1 Provide new IP addresses, DHCP range, Gateway , netmask data if different then default.

On the day of installation, we need to have this information so we can set it on server. Each server
comes with two network cards, one is for public access (we set DHCP client) and one is for IPTV
network (we set default static IP 192.168.200.254/24). If you want we set different, please provide
us info for public network: IP, NETMASK, GATEWAY. For IPTV network we need IP, NETMASK, DHCP
RANGE. On IPTV network is no gateway needed. We need this data for all servers. Well DHCP we
need to set only from MW server.

6
3.3.2.2 Provide list of all rooms in property (excel)

On the day of installation, we need list of all rooms that are in PMS or HIS system. This we need in
order to print out list of rooms and later installer will write MAC of device that is in that room. This
way devices will be identified in which room are taken. Later we will link MACs in system with proper
room. They could write on their own papers, but they will not know if any room was skipped or not
done so it is better to start with full list.

3.3.2.3 Provide a list of all satellites used: names, degrees, is multi-switch used?

To avoid hassle at installation and figuring out what satellite is on roof, we would like to get the
information from cable company. They should deliver signal cables to the server room and be ready
to connect to IPTV gateway server. When they handover their work, they should write down all
names of satellites that are used and their degrees.

3.3.2.4 Provide a list of all TV channels client require.(excel file)

After signal cables will be inserted in the IPTV gateway we can start scanning for tv channels. We
could set some random channels that we scan in order to test signal and network, but it would save
time if we set real channels from start. We need a list of channels client wants to use. Mandatory data
is channel name, but it would be also helpful to get from which satellite, frequency if possible,
language of channel for later grouping, logo picture.

3.3.2.5 Provide the content (service titles, images, text, prices,…)if possible for phase 2.

Usually before project is even bought the client gets presentation from our sales about what
everything is possible to set and do with IPTV system (live presentation, PDFs, screenshots). Based
on that data client can already start preparing the content. Later during installation in Phase 1 they
can check demo content on real device there and imagine again how their content will look like.

3.3.2.6 Check how devices can be mounted on location.

By now you know what cables you have. You need to check with property if they have some special
or limited space for devices to be mounted and how they will be mounted. Usually the best way is
Velcro tape that mounts STB to TV. If client bought Smart TVs then no extra devices needed behind
TV.

3.3.2.6 Provide IP and port of PMS/HIS that IPTV will connect to it. Ask if they support FIAS standard.

You can ask client upfront what is IP and port of PMS/HIS system to which we will later connect.
Sometimes to gather this info takes time.

3.3.3 Pre-installation requirements

3.3.3.1 Network prepared

In order to transmit television streams, the data network must be properly designed, and various
switches must be set properly so the multicast packages can be correctly administrated.

Each IPTV server has two network cards, one (usually eth0 or em1) is for public access and second
(eth1 or em2) is for IPTV network where devices and live streams run. We label ports if equipment is
sent from our preparation office.

7
IPTV network is isolated network without any other DHCP or DNS. Only one should be in charge to
dedicate IPs to devices in this particular network. DHCP and DNS run from IPTV MW server. Client
can set own DHCP but in that case we need to close our DHCP and client need to set proper DNS
linking.

Main or Core switch must be layer 3 which handles IGMP queries (IGMPv2 or IGMPv3), other floor
switches can be layer 2 with IGMP snooping enabled. This way we avoid flooding the network with
streams and only requested stream will come to device that requested it, not all at once. We suggest
using Cisco or HP. Usually main switch is 1GB while floor switches can be 100MB.

Multicast streaming also help reduce the bandwidth usage, so that each channel is only sent once. If
we assume that Standard Definition (SD) TV channels typically use 2-5 MBIt/s and High Definition
(HD) channels use 4-10 Mbit/s, a Head-end IPTV server delivering 10x SD channels to 100 users via
unicast will use: 100 x 5 Mbits = 500 Mbit/s total network bandwidth. With using multicast, 10 SD
channels will now use: 10x 5Mbits = 50 Mbit/s total network bandwidth.

Once broadcast by the head-end, a network that is configured to support multicast will distribute
that stream only to users that request it. You need to calculate the bandwidth you will need at the
end point and set proper switches accordingly. As we mentioned, usually main switch is 1GB while
floor switches can be 100MB. No gateway on IPTV network. We set network bridge between public
network and IPTV network on server so devices have internet.

PoE STBs: If you use switches that will power also STBS PoE, then calculate consumption
accordingly. One stb needs approximately 10W.

Known issues related to network:

- On installation day people won’t be able to confirm if STB works ok in room if network won’t
allow stb to connect to IPTV server. If they just set STB there, it will mean they will need to
test it later which means lost time.
- If network not set properly or some other DNCP, DNS in network it may happen that stbs
won’t work because they will connect to other network. Tracking server log helps see what
is going on.
- If IGMP query not set on switches, then live streams will start to freeze when you set large
amount of them. We have a command to check how many streams comes to STB and we
can prove flooding. You can also check with Wireshark on your PC. Write on
support@nevron.eu for this command.

8
Network requirements quick list:

- Servers needs to be connected in server room and set internet access for remote support
- Ports in rooms needs to be properly configured to reach IPTV server.
- IGMP query needs to be set on core switch and IGMP snooping on floor switches
- It’s good that cable company is present on day of installation.

3.3.3.2 Signal cables set in server room

In the sales process the client usually provide channel list or at least know how many channels they
want in order to get the proper amount of DVB cards inserted in server. This is needed if Gateway
server is also bought from us.

Cable company also got that info what channels client need in order to provide proper satellites or
antennas. The final result is a lot of cables waiting in server room to be connected to the gateway
server.

How it works: One frequency per transponder (dvb-s or dvb-t) and on one frequency can be many
channels. Analog (s-video) and HDMI cards has one channel per transponder. If client have local
provider (telco) where stream output is multicast, then no cards are needed.

For more satellite streams we recommend multIswitch. You need to check what multi-switch goes to
what LNB. We recommend Triax and Fracarro multi-switches. Useful link:

http://shop.tbsdtv.com/blog/what-is-differenct-between-quatro-lnb-and-quad-lnb.html

Why multi-switch: Multi-switch helps you to easily find channels on satellites and to easily change
them. You can set up to 4 satellites on 4 antennas (1-4) so in our system you just select from which
antenna you want to make scan. Also doesn’t matter if channel has vertical or horizontal
polarization, both should work on same card. That is multi-switch job to handle it. If no multi-switch,
then you need to know what comes over particular signal cable (which satellite, which polarization)
and only channels matching that settings will work. It’s frustrating to handle without multi-switch.

Good resource for satellites frequencies: www.lyngsat.com

Signal requirements quick list:

- We need info what satellites or terrestrial antennas are installed on roof , name of satellites
and their degrees (Example: Nilesat 7°W)
- If local oscillator is used, we need the freq. info so we can recalculate from universal one
- List of channels client wants to scan
- If client has crypted channels the client should already buy CAM and smart card from
channel provider and they should be inserted in the back of server.
- All signal cables should be connected from multi-switch to Gateway server
- It’s good that cable company is present on day of installation so we can quickly solve
problems.

9
3.3.4 PHASE 1: Setting IPTV with tv channels working
3.3.4.1 Setting servers in server room

Preinstalled is in our offices so it just needs to be connected in client’s network. Our servers have 2
network ports, one is for public internet (eth0 or em1) and one is for IPTV network (eth1 or em2).
There are labels on the back of server. Our system is preconfigured that way so please connect
cables in that order.
On public is DHCP client so your router will give IP to it. Then set server to have internet access. On
IPTV network is fixed ip 192.168.200.254. DHCP on it is limited so only registered devices will allow
to connect. In IPTV Administration the mac of device that wants to connect needs to be written in
System -> Device settings -> Device registration.

Gateway server has same network ports, one for public and one for IPTV. There you also need to
insert all signal cables that cable company provided.

Approximate time needed: around 15min for MW server and 30min for GW server

3.3.4.2 Configuration of servers

IPTV server comes preinstalled with public network set to DHCP client and IPTV network set to
192.168.200.254/24 and DHCP range 192.168.200.10-192.168.200.240. If client needs different IP,
they need to provide it that day or before. After devices are already set is more work to change IP to
every device, that why this configuration is done before devices are connected.

To change IP of public network we need:

- New IP
- Netmask
- Gateway IP

To change IP of IPTV network we need:

- NEW IP
- Netmask
- DHCP range

Approximate time needed: around 10 min per server

3.3.4.3 Testing Servers – test if devices connect

After servers are set up and running you can connect one device to the server room (on switch
where all server all) or later at some room and test if device connects to the server. This way you
check if server is configured properly before major deployment of all devices in rooms.

Two demo streams already run from MW server so TV menu does stream some channels.

Approximate time needed: around 30 min

10
3.3.4.4 Preparation for major deploy of devices in rooms

- Get a list of all rooms and print out for installers

We need room list in IPTV system and print out in PDF or in excel. Print out so many copies as you
will have installers that will install devices in rooms.

In IPTV administration under System -> Device settings- Devices you can insert all rooms that are in
property. Usually is an export file of PMS system. Then Export list to PDF.

Why: If they have list of all rooms then they can easily see which one they didn’t install yet. Next to
each room they need to write device MAC which they put in that room. Later in system they will link
with that room. If any other anomalies in room or they weren’t able to set device, they need to write
comment to that room.

- Give instructions to installers

Gather all people that you got to help you install the devices in rooms. Go to one room and
demonstrate how device should be connected (what cables) and how need to be mounted on the TV
or wall (Velcro tape).

- Tell them to write MAC of device that is in room. STB or Smart TV. We need to identify
device in room so it will be properly linked with IPTV and PMS system.
- STB needs to be connected to the TV that way, that side with breathing slots is on outer
side. STB needs to breathe, don’t cover the holes. Glue the other side that doesn’t have
holes.
- Put cables the way they hide behind TV. No one likes to see cables hanging down in all
directions.
- Program remote control to room’s TV. Power button, mute, source, volume is
programmable to original TV remote so you record the codes from original TV remote
and then you need only our remote in room. If you will use rs232 communication, then
programming is not needed. Manual provided.
- When device connected, move away from TV and try if STB remote works with arrow
keys and power on/off. If yes, the room is properly set.
- If live channels work or not is not important because in parallel someone is setting live
channels up. Meantime two demo channels work just so installers can see something
playing.
- On STB is possible to check MAC with STB keys if stb works ok. Press: red, 7, 5, 3, green
- On Smart TVs you need to get to hidden menu and check network settings to see MAC.
- If you have more people to help, set each person on each floor. They take box of
equipment to the floor and start installing room by room.
- If they need to take down TV, ten assign two persons per room
- If rooms are occupied or running hotel, find staff that will go along to open doors. In that
case reception is notified of works and can inform guests if the call for malfunction or
other questions.

Approximate time needed: around 30 min to show and explain

11
3.3.4.5 Setting Devices in all rooms (This task can be done in parallel)

- Connecting all devices in rooms

Each person takes a box of equipment and go installing devices in rooms.

Approximate time needed: around 10 min per stb, depends how many cables you have and how
hard is to mount TV back.

- Setting all live streams in gateway. (about 1h for 25 channels)

Meantime people are installing devices in rooms, one person can set up live channels. Inside
Streamer manager there is a list of detected cards and you need to make scan on each tuner/card to
get channels. Manual for Streamer manager is provided. We prefer we do quick test of scan to
confirm if multi-switch is set then we give instructions how to configure the rest of channels. This
way is easier for all involved.

Approximate time needed: around 1h for 25 channels. If cable company provided all data is faster,
otherwise we do test scans and see what we detect.

3.3.5 Preparation for phase 2

3.3.5.1 PMS data

In order to show welcome message greeting in guest name, we need to connect to PMS system that
will give us data about active guests. Ask client for IP and port of PMS. We need to ping IP of PMS
from public network or IPTV, it doesn’t matter. Usually is on public. We need to get info if we didn’t
get till now, if PMS supports FIAS standard and what encoding they use. If wrong encoding, then
some special character won’t be seen. Important is to get IP:port, other info we can collect later if it
wouldn’t work as intended. We will perform PMS test when connected to verify that features we
need are working.

What info we need to get:

- IP and port of PMS

- Does PMS support FIAS
- what king of keep alive message they use LS/LA.
- what kind of encoding they use (uft-8, windows-1250,…)

3.3.5.2 On one device set full demo content and show it to client.

When the installation is in process or after it’s finished, we set on one device all demo menus so
client can see the content again. Point of this is that client can see the content and get better image
how the need to prepare their own. They get the feeling what everything is possible to put on TV
screen.

In general, the person who bought system is not the same person that is responsible for providing
content that why we show again. Sometimes there are months or year between when system was
bought, and they need a refresh of memory. We do have PDF presentations of eServices which were
probably provided upon buying the system.

12
At that point client gets all necessary manuals on how to prepare content, what and which sizes.
Then depends on them how fast they will provide the content. Minimum is around week and
sometimes takes months. If property is ruining, it’s easier to collect content from webpage or
brochures. In new property we usually need to wait longer.

Approximate time needed: 1h training to show menus or they check PDF

PHASE 2: Setting full content on TV

- Filing content

At the end of phase 1 client got introduction and instructions to prepare content. They can start
filing if as soon as they got it. System was ready to fill when it was set up. We just won’t show it to
guests until it’s ready and confirmed.

Please dedicate one person who will be responsible for filing the content on IPTV and we train that
person. Filing content is client responsibility, we can do upon additional charge.

We can schedule 1h training or ask questions on support@nevron.eu if you encounter troubles. We

also have online Knowledge base. To check the content on device you can set one device to Public
mode and enable all menus to be visible in that mode. While other rooms are in suite mode and see
different menus-limited version. It’s also possible to see preview in browse on certain link. Ask us to
help you set up the link. After all content is inserted and manager approve it, you can enable to all
guests.

Approximate time needed: week or months

- Mapping STB to room in IPTV

By now the rooms needs to be inserted in the IPTV system and properly lined with PMS. Usually
room name provided to us is the same name that is used in PMS, so we set HIS ID to be the same
name.

In end of Phase 1 we collected all lists where installers wrote down which MAC they put in which
room. Then we link the MAC with room in IPTV system.

Linking is important so that welcome greeting text will show in guest name in proper room. You
don’t want to show wrong guest name or bill info in room.

Approximate time needed: 1h for 200 devices

- Establish PMS connection

Immediately when we get IP and port of PMS, we can test if we get connection to it. Usually they
need to open port on firewall. Then when connection is successfully established and rooms linked,
we schedule time to perform PMS test. It’s a list of tasks to verify if all features we need work
properly. We need two vacant rooms and very cooperative receptionist to follow our instructions.
Manual provided.

Approximate time needed: 1h

13
 4. Acceptance criteria
- Phase 1: In this phase all devices needs to be installed in rooms and all required channels
are working on them.
- Phase 2: In this phase guest is inserted through PMS and in IPTV he gets greeting in his
name. On Dashboard screen he sees all eServices available for him (what content client
enabled). If client allowed to services be ordered, then he can make an order.

5. Documents available
Nevron_Axon_portal-eServices_description-2020.pdf and

Nevron-Axon-Content-preparation_instructions.pdf:

https://nevron.atlassian.net/wiki/spaces/SDKB/pages/1080131613/Axon+features+and+content+pr
eparation

Nevron_StreamerManagement-2020.pdf:
https://nevron.atlassian.net/wiki/spaces/SDKB/pages/248217659/Streamron+Manager

Nevron_PMS_Interface_Testing.pdf:

https://nevron.atlassian.net/wiki/spaces/SDKB/pages/258768898/Integrations+to+other+systems+o
r+services

Manuals for programming STB remote:

https://nevron.atlassian.net/wiki/spaces/SDKB/pages/925040645/Remote+controls+-
+programming+STB+remote

Manual for smart TV configuration:

https://nevron.atlassian.net/wiki/spaces/SDKB/pages/431095921/Smart+TVs+supported+on+IPTV

6. Appendix 1: System Hardware Inventory

Usual default configuration for IPTV servers when we deliver equipment.

DVB Gateway 1 IP/mask Gateway DHCP DNS

LAN1 (mng-public VLAN) Dhcp client NO NO
LAN2 (STB-IPTV Vlan) 192.168.200.253 NO NO
idrac

IPTV middleware IP/mask Gateway DHCP DNS

LAN1 (mng VLAN) DHCP client NO NO
LAN2 (STB Vlan) 192.168.200.254/24 YES YES
DHCP IP Range 192.168.200.10-240
Idrac

14
 7. Appendix 2: System Software Inventory

OS version
Middlware version
Device FW
Application on devices

15