Sat-IP

[2] The main difference of SAT>IP to other IP-based multi-media distribution systems such as IP-TV and DLNA is that the SAT>IP client does not select a program from a server specific list, but has to specify the DVB reception parameters such as the signal source (typically the satellite number in a DiSEqC switch), frequency, polarisation, Modulation system and type, the wanted PIDs and others.

SAT>IP is particularly aimed at satellite TV distribution in the home but can be applied to large multi-dwelling and hospitality reception systems too.

Multiple SAT>IP servers and clients can operate on the same network with both free-to-air and encrypted pay-TV transmissions.

At this time, the SAT>IP Alliance founding members were SES, Hispasat, Panasonic, Nagra, ALi Corporation, and MaxLinear.

Converted to IP, the satellite TV signals can be distributed over any IP network, depending on the configuration of the server, using wired Ethernet, wireless (WLAN, 4G), “Power Line” home networks, optical fibre, plastic fibre, coax, twisted pair (xDSL) or visible light technologies.

[2] In the control plane, clients request access to satellites, transponders and MPEG streams using RTSP or HTTP.

This is easy when the client is a device with CAS/CAM hardware support (like a television or set-top-box), but it's unclear how to do it in a PC, mobile or tablet.

Software applications to use computers and display devices as SAT>IP clients have been produced by a number of companies.

DVBViewer Pro is a digital TV viewer and recorder software application for Windows PCs which has been extended to use SAT>IP.

The installation and distribution cost can also be significantly reduced by using the Multicast and Unicast features in SMATV systems in hotels and flats.

[26] Minisatip is an open source software implementing a SAT>IP server application that runs under Linux.

SatPI is an open source project that implements a SAT>IP server application that runs under Linux.

The IP-LNB incorporates eight-channel satellite-to-IP bridging technology to deliver eight concurrent channels via IP unicast or multicast to fixed and portable client devices.

The SAT>IP logo
Example of a SAT>IP server: Telestar R1 A connecting to four satellite LNB feeds and an Ethernet connection to distribute satellite TV programs around the network.
SAT>IP reception over a Wi-Fi home network from a Telestar R1 server and fixed dish on a Nexus 7 Android tablet using Elgato SAT>IP app.
The Telestar B1 client receiver displays SAT>IP channels from a SAT>IP server as well as acting as a media player for data from the USB and SD sockets in the side of the unit.
The rear panel of the Telestar B1 client receiver showing the HDMI, S/PDIF, and AV jack outputs, USB for PVR recording and the Ethernet connection to the IP network.
The Android Elgato SAT>IP app running on a Nexus 7 receiving channels and EPG data from a Telesar R1 SAT>IP server.