What Is IPTV? Architecture, Components and Distribution Methods
IPTV delivers television and video services over an Internet Protocol network. A professional system combines signal acquisition, encoding or gateway conversion, service processing, managed transport and compatible receiving devices in one engineered signal chain.
What Does IPTV Mean?
Internet Protocol Television, or IPTV, uses IP networks to transport television services instead of distributing every service as a conventional RF channel throughout a building or campus. The programme may originate from satellite, terrestrial or cable broadcasting, a local HDMI or SDI source, a studio feed or an existing IP stream. IPTV describes how these services are processed and delivered through the network to their destinations.
In engineering terms, IPTV is not a single codec, protocol or product. It is a system architecture combining content sources, signal acquisition, encoding or gateway conversion, service processing, network distribution, receiving devices and—where required—middleware, access control and operational management.
IPTV and OTT Are Not Identical
Professional IPTV normally operates across a controlled network where bandwidth, switching and endpoints can be engineered. OTT video commonly traverses general IP connectivity or the public internet and therefore relies more heavily on adaptive HTTP delivery and client buffering. Some platforms support both approaches, but the underlying design assumptions differ.
LAN Distribution and WAN Streaming
LAN Distribution and WAN Streaming describe the network environment and operational boundary. Multicast and unicast describe how streams are delivered to receivers. These are separate classification axes: a system may use multicast LAN Distribution, unicast LAN delivery or unicast WAN Streaming.
LAN Distribution
Used to distribute a defined channel line-up inside a building, campus, vessel or other managed property. Multicast is common for repeated linear channels.
- Primary foundation: DVB/IP headends and DVB-to-IP gateways
- Main concerns: IGMP, VLANs, multicast routing and link capacity
WAN Streaming
Used to transport or publish media between sites, towards a platform or CDN, or across the public internet. Delivery is normally unicast.
- Primary foundation: IP Encoders & Streamers
- Main concerns: jitter, packet loss, latency, buffering, NAT and firewalls
LAN DISTRIBUTION
Controlled local network
or gateway
→
VLAN / IGMP
→
endpoints
WAN STREAMING
Remote or cross-network transport
& Streamer
→
or public internet
→
destination
Conceptual network-domain comparison. The diagram is not model-specific.
Where IP-to-IP Gateways Fit
An IP-to-IP Gateway can provide an interworking layer between transport environments—for example, accepting a WAN transport and producing a LAN-suitable output. Protocol conversion is not automatically transcoding: changing codec, resolution or bitrate requires a verified transcoding function. Detailed WAN/LAN interworking belongs to the planned IP-to-IP Gateways Technical Paper.
Reference Architecture of a Professional IPTV System
A practical IPTV system can be understood as five functional blocks. One platform may combine several blocks, so this is an engineering model rather than a requirement for five separate devices.
SOURCES
- Satellite · DVB-S/S2
- Terrestrial · DVB-T/T2
- Cable · DVB-C
- HDMI · SDI · ASI
- Existing IP streams
ACQUISITION & ENCODING
- Professional receivers
- DVB-to-IP gateways
- IP encoders
- Transcoders
SERVICE PROCESSING
- Selection & filtering
- SPTS / MPTS
- PID & service handling
- Protocol conversion
MANAGED IP NETWORK
- Ethernet switching
- Multicast / unicast
- VLAN · IGMP · QoS
- Routing & resilience
ENDPOINTS
- IPTV televisions
- Set-top boxes
- Professional decoders
- Software clients
- Monitoring positions
Conceptual architecture. Actual functions may be combined within one platform.
Sources
DVB-S/S2, DVB-T/T2, DVB-C, ASI, HDMI, SDI, DisplayPort, analogue video or existing IP streams.
Acquisition & Encoding
Receivers, DVB-to-IP gateways, encoders and transcoders prepare source services for the required signal chain.
Service Processing
Selection, filtering, SPTS/MPTS creation, PID and service handling, protocol conversion, monitoring and alarms.
Managed IP Network
Ethernet switching and routing carry the services using the planned multicast, unicast and resilience design.
Endpoints
IPTV televisions, set-top boxes, professional decoders, software clients and monitoring positions receive the services.
Hybrid RF Path
An IP-to-RF modulator can feed selected services to an existing DVB-C or DVB-T coaxial distribution network.
Main Components of an IPTV Headend
Equipment must be selected from the complete signal chain. A product name alone does not establish whether the required codec, service processing, protocol, capacity or endpoint compatibility is available.
| Component | Primary function | When it is required |
|---|---|---|
| Professional receiver or IRD | Receives and decodes a broadcast or IP service | When a source must be decoded to baseband, monitored or passed into a professional workflow |
| DVB-to-IP gateway | Demodulates DVB services and outputs selected transport streams over IP | When satellite, terrestrial or cable services are distributed without unnecessary baseband re-encoding |
| IP encoder and streamer | Encodes HDMI, SDI, DisplayPort, VGA or analogue sources into IP streams | For local channels, cameras, signage, events and other baseband sources |
| Transcoder | Changes codec, resolution, bitrate or stream profile | When existing services do not match the target network or endpoints |
| Multiplexer / IP-to-IP gateway | Selects, filters, remaps, combines or converts existing streams | When services or protocols must be reorganised without unnecessary video re-encoding |
| Managed Ethernet network | Switches and routes IPTV traffic | In every IPTV installation; multicast functions must be planned where multicast is used |
| IPTV set-top box or TV client | Selects channels and presents services to the viewer | When the television needs an external receiver or managed user interface |
| Professional IP decoder | Converts an IP stream to HDMI, SDI or another professional output | For monitoring, control rooms, return feeds and baseband integration |
| Middleware | Provides user interface, channel lists and optional interactive functions | For centrally managed or interactive services; not mandatory for every linear system |
| IP-to-RF modulator | Converts selected IP services to DVB-C or DVB-T RF | In hybrid systems retaining an existing coaxial TV network |
Multicast, Unicast and OTT Distribution
Multicast and unicast describe the delivery relationship between a source, the network and its receivers. They do not by themselves specify the codec, picture quality, security or total end-to-end latency.
MULTICAST IPTV
one group stream
→
controlled replication
→
Receivers join the channel group. The network replicates the stream toward interested receivers.
UNICAST IPTV
individual sessions
⇉
routes each stream
⇉
Each receiver has an individual delivery relationship. Aggregate traffic normally grows with concurrent sessions.
Conceptual comparison. Actual traffic depends on topology, active multicast membership, session count, bitrate and routing design.
| Criterion | Multicast IPTV | Unicast IPTV | HTTP adaptive / OTT |
|---|---|---|---|
| Typical network | Managed LAN, campus or operator network | Managed or routed IP network | General IP network or public internet |
| Stream relationship | One group stream can serve many receivers | Separate delivery per receiver or session | Separate HTTP delivery, often through a CDN |
| Bandwidth scaling | Mainly with unique channels carried on each link | Mainly with concurrent sessions | With concurrent sessions and selected bitrate profiles |
| Common use | Linear channel distribution | VOD, personalised or limited-viewer services | Browser, mobile and internet delivery |
| Engineering focus | IGMP, VLANs, multicast routing and capacity | Session capacity, routing and server/output load | Origin/CDN capacity, adaptation, buffering and internet variability |
| Latency tendency | Low when the complete chain is designed accordingly | Depends on protocol and buffering | Usually higher due to segmentation and buffering |
Formats and Protocols Used in IPTV
| Format or protocol | Role in the system | Engineering note |
|---|---|---|
| MPEG Transport Stream | Carries compressed video, audio and programme information | May carry one programme as SPTS or multiple programmes as MPTS |
| UDP | Low-overhead datagram transport | Does not itself recover lost packets or guarantee order |
| RTP | Real-time transport framing, commonly over UDP | Adds sequence numbers, timestamps and payload identification |
| RTSP | Session-control protocol | Often controls a session while media is carried separately, for example by RTP |
| SRT | Reliable, encrypted transport over unpredictable IP networks | Useful for contribution or unmanaged links; not required for every local IPTV channel |
| HLS | HTTP-based segmented media delivery | Broad client and CDN support; latency depends on segmenting and buffering |
| IGMP | IPv4 multicast group-membership protocol | Manages group membership; it is not a video transport protocol |
Verify the Complete Compatibility Chain
A supported protocol is only one layer. Codec, profile, resolution, frame rate, audio format, transport structure, operating mode and receiving-device support must all match.
IPTV Network Requirements
The network must be designed for measured peak traffic and the intended delivery method. Nominal codec labels and switch port speeds alone do not prove that a network is IPTV-ready.
Capacity
Include every unique stream expected to traverse a shared link, protocol overhead, simultaneous services, redundancy paths and a defined engineering margin.
Multicast Control
Define IGMP version, querier location, snooping behaviour, routed boundaries, group/port allocation and treatment of unknown multicast traffic.
Segmentation & QoS
VLANs can isolate television traffic. QoS may protect media under contention, but it does not replace sufficient capacity or correct multicast configuration.
Monitoring & Resilience
Monitor source presence, transport continuity, packet loss, bitrate, service information and endpoints. Define redundancy against actual failure modes.
IPTV Architecture Variants
Linear Multicast IPTV
Efficient distribution of a controlled channel line-up to many receivers within a managed property, campus or operator network.
Interactive IPTV
Adds middleware, user interfaces, authentication, messaging, billing or other application functions. It is not automatically required for simple linear television.
Hybrid IP and RF
Selected services feed DVB-C or DVB-T over existing coax while IP streams serve set-top boxes, professional decoders or other destinations.
IPTV with OTT or Contribution
A managed local system may be combined with HLS for browser/mobile delivery or SRT for external links. These are complementary layers.
How to Select an IPTV System
Select equipment from the signal chain rather than as isolated products. Define these ten inputs before choosing hardware.
Sources
DVB-S/S2, DVB-T/T2, DVB-C, ASI, HDMI, SDI or existing IP; free-to-air or encrypted.
Service Count
Input transponders, programmes and locally encoded channels.
Processing
Pass-through, filtering, multiplexing, conversion, decoding or transcoding.
Video
Resolution, frame rate, codec, bitrate range and acceptable latency.
Audio & Data
Audio codecs/tracks, languages, subtitles, EPG and programme components.
Distribution
Multicast, unicast, HTTP adaptive, RF output or hybrid combination.
Endpoints
Integrated televisions, set-top boxes, decoders, browsers or applications.
Network
Topology, VLANs, uplinks, IGMP, routed boundaries and redundancy.
Operations
Monitoring, alarms, remote management, failover and maintenance model.
Commercial Scope
Quantity, installation country, timing and required documentation.
Recognise Technical Limits Early
A DVB-to-IP gateway cannot solve an unsupported source codec unless it also transcodes. Multicast needs deliberate routed-network support. Transcoding adds processing and delay. Very low latency, maximum compression and maximum resilience are competing objectives.
Typical IPTV Applications
Hospitality
Linear channels, local information and optional interactive services in hotels and resorts.
Marine
Central reception for cruise ships and luxury yachts with IP or hybrid distribution.
Corporate & Institutional
News, internal channels, training, signage and event feeds across controlled facilities.
Broadcast & Monitoring
Contribution returns, multiview and engineering monitoring for control rooms and operations.
Residential Developments
Central headends distributing available services over IP, RF or both.
BLANKOM Equipment Across the IPTV Signal Chain
The appropriate BLANKOM combination depends on the sources, processing, distribution method and endpoints. Model-level capacity and protocol support must be verified on the current product page and Data Sheet.
DVB/IP Headends & Gateways
Receive broadcast services and provide selected IP outputs for professional local distribution.
IP Encoders & Streamers
Encode baseband sources for site-to-site links, platforms, CDNs or remote destinations.
IP-to-IP Gateways
Convert or reorganise existing streams between transport environments without assuming transcoding.
| Requirement | Relevant BLANKOM family | Explore |
|---|---|---|
| Encode HDMI, SDI, DisplayPort, VGA or analogue sources | IP Encoders & Streamers | View family → |
| Receive DVB services and place selected streams on IP | DVB-to-IP Gateways | View family → |
| Filter, reorganise or convert existing IP streams | IP-to-IP Gateways | View family → |
| Decode IP services to display or professional outputs | IP Decoders, IRDs and IPTV Set-Top Boxes | View family → |
| Feed an existing coaxial network from IP | DVB-C / DVB-T Modulators | View family → |
| Design the complete application | IPTV & Professional TV Distribution | View solution → |
Commercial boundary: BLANKOM hardware is supplied with lifetime device licensing and no mandatory recurring SLA. Interactive IPTV middleware supplied through third-party platforms such as OMNISCREEN has its own licensing and support model and is quoted separately when required.
IPTV Frequently Asked Questions
Is IPTV the same as streaming video over the internet?
No. Both use Internet Protocol, but professional IPTV normally operates over a managed network with controlled sources, bandwidth and endpoints. Internet streaming or OTT commonly operates across less predictable networks and uses adaptive HTTP delivery and more client buffering.
Is a WAN the same as the internet?
No. A WAN connects sites or network domains over distance and may be private or carrier-managed. The internet is a public inter-network environment over which one project owner does not control the complete path.
Where does an IP-to-IP Gateway fit?
It interworks between existing IP streams and transport environments. It may convert protocols, addressing, packetisation or service organisation without changing the video codec. Codec, resolution or bitrate changes require a verified transcoding function.
Does every IPTV system require middleware?
No. A simple linear system can deliver streams directly to compatible televisions, set-top boxes or decoders. Middleware is needed when the project requires a managed user interface, channel lists, authentication or interactive services.
When should multicast be used?
Multicast is typically appropriate when the same linear channels must reach many receivers on a managed network. The switches, routers and endpoints must support and be configured for the required multicast behaviour.
Is a DVB-to-IP gateway the same as an encoder?
No. A gateway normally receives an already compressed DVB service and transports selected streams over IP. An encoder compresses a baseband source such as HDMI or SDI.
Can IPTV use an existing office network?
Possibly, but capacity alone is insufficient. VLAN design, IGMP behaviour, multicast routing, uplink loading, QoS, endpoint compatibility and operational ownership must be checked.
Can IPTV coexist with an existing coaxial TV network?
Yes. Selected IP services can be converted to DVB-C or DVB-T for coaxial distribution while other services remain on IP.
What information is needed to select IPTV equipment?
Provide source types, transponder and channel counts, encryption status, required processing, output protocols, endpoint types, topology, redundancy, quantity and project location.
Build the IPTV Architecture from the Signal Chain
Send us your source signals, channel count, endpoint types and preferred distribution method. IRENIS application engineers will review the chain and identify suitable BLANKOM building blocks.
© 2026 IRENIS GmbH. All rights reserved. Unless otherwise stated, the original text, diagrams, tables and illustrations in this publication are protected by copyright. Except where permitted by applicable law, they may not be reproduced, republished, distributed, translated, adapted or used commercially, in whole or in part, without the prior written permission of IRENIS GmbH. Any permitted quotation or reference must clearly identify IRENIS GmbH as the source and, for online use, include a link to the original publication. Third-party trademarks and credited materials remain the property of their respective owners.
