Just wanted to see if any smaller providers here were doing IPTV over the cmts. I believe static multicast is the correct term. I'm just interested in finding out what it would take to simulcast an analog lineup. Should be a mostly typical analog headend with some receivers having gig-e outputs and others only asi. Very new to this and very stumped. Is encryption required or does restricting access through the modem work well enough? Hardware wise what is involved in the headend and cpe. Middleware? Do you send out a single program stream per ip or multiple streams?
We replaced our analog TV headend with IPTV
Multicast linear (live) TV. 1 channel per IP.
Unicast VOD from a CDN
STB/PVR for above, with FTA antenna inputs also
MPEG4
We gave up sourcing our own feeds, and buy this all as a package from the TV provider. Basically went from like 5 or 6 racks full of modulators, combiners, encryption gear etc to none. It all is now done with just an IP x-connect to the provider.
Theoretically, any device can receive any of the multicast or VOD, however all this content is encrypted, and the STB will only decrypt items that the subscriber is paying for. If you view the content in VLC or whatever, it is unwatchable due to green macroblocking/scrambling.
The multicast aspect works well (subs have 8X tuner modems and we "span" the multicast across multiple mac-domains on the 2nd block of 4 DS). However it seems like unicast is taking over (Netflix, Youtube etc), so probably at some point the in the future we will give up the complexity and bandwidth savings of the multicast implementation, and just make everything unicast.
Basically what you are doing is SPTS (a.k.a. Single Program Transport Stream) for TV, one per IP, same like the VOD is done. It has a lot of advantages if you need to send the service to ADSL customers or GPON also, as the service will be unified.
Regarding the multicast via the CMTS, there would be an issue if you convert to unicast, it will instantly overload the CMTS network. There is a big difference between Netflix/Youtube as that service is on demand, people use it rarely, compared to the TV where customers have the TV running all day long, even multiple TVs per household. I would go for a NONO for unicast via CMTS. Unless it is Docsis 3.1.
Thanks for the info. I'm really ignorant on this stuff. It seems like the ideal solution is a mix of both multicast and unicast. Multi for the really popular stuff and uni for the less popular feeds but I have no idea of the complexities involved. I'm really unsure of the costs involved in converting the asi to ip, seems pretty expensive per asi port so I'm just trying to figure out what the options are. As for the newer IRDs with gig outputs, for a single channel is it just a matter of selecting the program stream and setting the output to SPTS for those?
Could you guys recommend some providers like mbowe mentioned? That sounds like a nice solution as well.
Well, it depends on the country. If I am not mistaken, Michael is from Australia and I am pretty sure you are not interested in such a service with Australian TV channels. You need also to discuss the option with your TV channel providers, most of them should provide an IP stream also. I know Discovery does it, for example. And the Discovery group for example has maybe 10+ TV channels. It also needs to be a service somehow close to your country.
For a 10.000 subscribers, I think the CAPEX will not be easy. You should look into a load for 5-10 years. Just a guess, I would say it would go for 200K to 500K, in my opinion. Also, the OPEX, as Michael said, is something you need to take into consideration. 4-6 racks of devices, electricity, cooling, etc.
ASI ports number will be lower than actual TV channels, as many TV channels come into a single stream. You could also look into teaming with other small providers, after you have the setup, you can redistribute the streams almost for no cost.
Just look for IPTV in your country, and discuss with them the option to take a copy of the streams. I think this would be the cheapest solution. It depends on the stability you are looking for, it that IPTV setup is done by some youngsters with VLC knowledge, expect a lot of downtime.
I am a bit confused on what are you trying to achieve.
I can tell from my experience the following:
I worked on something similar for a small operator: On DOCSIS network, only Digital Television, MPTS sent by an EdgeQAM, incoming to the E-QAM were STPS streams on Ethernet. The SPTS streams were also introduced into multicast for the Ethernet customers. The EdgeQAM was also receiving the CAS table for scrambling and creating the MPTS streams from multiple SPTS as needed. The output of the E-QAM was injected on the DOCSIS network as Digital Television.
This is also the deployment I saw at the biggest players on the market, US and Europe also. E-QAM is the way to go if you want to introduce television into the RF network.
This deployment requires RF STBs at the customer side. There are some which are really cheap, like 10-20 USD retail, docsis 2.0 modem.
---
I also saw small deployments with multicast via CMTS, where the channel is replicated in each Service Group, and the modem has a static join, there are TLVs related to multicast, you should take a look into the MULPI specification.
This deployment is more for a hotel deployment for example, where you want to broadcast internal information.
I never heard of a multicast via CMTS deployed by an MSO. Technically it is possible, but from an architecture point of view there are many limitations in scaling.
For this one, I heard about bridged modems, and an IP STB behind the modem, which was doing the Multicast JOIN. I did a lot of work on this setup as the second JOIN was crashing the kernel of the modem, a very weird modem bug.
---
Middleware, you will need the input stream. If you can buy the stream via internet, that would be awesome. Otherwise, take the stream from satellite, as you said ASI ports and convert the streams to ethernet. Next is just architecture if you do MPTS in one place, or multiplexing at the E-QAM level. For scrambling (there is no encryption in video), you will need the CAS tables generated somewhere. Either go with something similar to Nagra if you can afford it, otherwise just buy CAS tables from someone, I know there is a company in Hungary selling this kind of service via the internet. Cheap.
Regarding your question with restriction, it depends what you want to restrict. Most of the countries require scrambling for adult channels, that would be mandatory. If you do not need to comply with scrambling for your service, you could do filters, you need to check MULPI TLVs for that.
I hope it helps.
I appreciate the info. I'm just looking around at all the stuff going on with IPTV and it seems pretty amazing compared to "traditional" digital set tops. I've admittedly got a heap to learn on the subject but it's almost to the point where a set top for IPTV is nothing but an app on whatever device you want to watch it on. I've got some studying to do!
The idea of IPTV is nice, but again, NOT for DOCSIS. It makes no sense compared to Edge-QAM setups. 4096QAM modulated Edge-QAM devices exist since 3-5 years, you just need to give it a try.
I am interested in this as well. Anyone have any experience with Vubiquity's streaming service(in the US)?
From a service provider view, we used vubiquitys terrestial service for one of our headends, while the video feeds were fine, i.e. looked good, we were completely unhappy with the service we got from them and Toner (who helped us set up our headend) and we ended up switching back to a HITS headend within a year even though the toner/vubiquity/verimatrix headend cost $100k to setup.
Vubiquity service was mostly hampered by Verimatrix and Toner (our encryption and settop manufacturers respectively) so word to the wise, the combo of Verimatrix/Toner/Vubiquity is not good, stay away from that.
Toner -- as a settop provider -- stay away from (I have a warehouse full of settops that are basically useless)
Verimatrix -- Emerging technology be prepared for emerging technology problems, e.g. breaking API changes, requiring replacing all smartcards in all settops
Vubiquity -- Emerging technology, service was very reliable, but they discontinued their terrestial service 6 months after signing us up to it on a year contract with only 60 days warning. No experience with their fiber feeds. They are not cable video feed providers for most part (strictly ip video) so they change pids, program numbers frequently and with impunity. Makes remuxing more like a game, also had issues with duplicate pids (PMTS) in feeds, i.e. music channels all had same pmt so had to remux them to be able to deliver to SEMS, APEXes which require every PMT to be unique per mux.
I had some dealings with Vubiquity around the time they transitioned from Avail. Our contract wasn't up when they shut the satellite feeds down either. How is Hits? Are they converting more to mpeg4 or still a lot of mpeg2? Also, when they deliver the feed, is it encrypted or do you encrypt it?
Hits is still mpeg2 and is likely to stay that way for foreseeable future. As much as I would love to use mpeg4, we have way too many mpeg2 settops deployed to switch without massive $$. Someday I would love to switch our HD feeds to mpeg4 but until it is about the same price as mpeg2 it will be a no go....
The feeds you get from HITS are unencrypted, at least when you get them, and are encrypted in our case, by the SEM/APEX (onsite) which is controlled by HITS.