City Media is a technical partner of Pallycon Multi-DRM encryption service Provider and developed the DRM Application Server to meet the TRAI regulatory specifications. The DRM Server is integrated with Multi-DRM Key server with Site ID, Site Key and Access Key.
DRM do not have any facility to activate and deactivate a Subscriber directly from the Graphical User Interface (GUI) terminal of DRM. All activation, de-activations, bouquets and channel assignments are done only in SMS and the data is pushed to DRM server.
The system is built on robust Linux operating system. The application and database servers can be independently hosted for scalability. Realtime scalable options like Openstack and Kubernetes can be deployed for unlimited expansion.
• The Subscriber Management System provides multi-level reseller management and revenue sharing with all the stakeholders. It also includes enhanced CRM features for customer satisfaction. Android and iOS mobile apps are available for subscription management and instant activations.
• API integration with popular broadband billing systems offers combo packs with IPTV bouquets. Additionally, API integration to the DRM Application server enables the real-time push of subscription data and customer information to meet regulatory compliances.
• The system is built on a robust Linux operating system. The application and database servers can be independently hosted for scalability. Real-time scalable options like OpenStack and Kubernetes can be deployed for unlimited expansion.
Pallycon is a Multi-DRM product of INKA networks who is a pioneer in the field of Digital Rights Management Software.
It supports Google Widevine, Apple Fairplay, Microsoft Playready. Rcast DRM server is currently using only Google Widevine.
Authorizations tokens were issued to the subscribers for each channel access as per the subscription status of the subscriber in the DRM Application Server which is pushed from the SMS server at the time of subscription activations.
The token log server maintains the logs with subscriber id, device id, channel id, with time stamps. These logs provide subscriber viewership analysis of channels for rating of the channels which is authentic.
Pallycon provides forensic watermarking, Key rotation, Blacklisting and whitelisting of Device IDs used by subscribers.
Rcast token server logs were maintained locally and in the cloud by Pallycon.
Transcoding and Encryption is implemented in a single process. The output streams are connected to the distribution Streaming / CDN servers.
If the Encoders deployed are already supported with the required codec and file format only Encryption can be implemented saving GPU resources.
The Transcoding / Encryption Servers can accept almost all types of input streams from the Encoders.
IRDs which includes Multicast/Unicast, MPTS/SPTS, MPEG-2, MPEG-4, H.264, H.265, MPEG-TS, HLS, MPEG-DASH etc.
Professional Nvidia GPUs are used in Transcoder Servers and support 100 to 300 streams per server as per the Server and GPU specifications.
N+1 Servers are recommended for redundancy and the configurations can be backed up and restored in the Spare Server.
Web browser based configuration and management of the channels is available. The Server and GPU resources also can be monitored remotely.
All the Channels status including the bitrates can be monitored to ensure 24/7 operation.
Streaming/CDN Server
Streaming/CDN(Content Delivery Network) Servers play a major role in distribution of IPTV services. We use opensource Ubuntu 24.04 Ubuntu server Operating System. All X86-64 hardware are supported and Network Ports capacity should meet the output requirement.
Hardware estimate for the concurrent subscriber connections to the CDN Server is 500 to 1000 subscribers per Core of the CPU provided network port capacity is available. Minimum RAM of 8Gb and 16Gb of storage is required.
CDN servers can be cascaded without effecting any loss of quality. CDN servers are addressable from the central monitoring system with live view of the input and output stream information.
CDN servers pull the source streams only when requested by any of the user hence saving the bandwidth of the trunk line. The same input stream source is multiplied to all the requested subscribers on demand.
