Our DVB PSI/SI Generator Software is designed to work with a wide range of broadcasting equipment and systems. Whether you’re operating a small local station or a large network, our software integrates effortlessly to enhance your workflow.
Stay ahead of the game with real-time data updates.Our software ensures that your PSI/SI tables are always current, reflecting the latest program schedules, network changes, and service updates instantaneously.
Compared to other PSI/SI generators, our solution focuses on simplicity. You never have to set up redundant information; Smartcaster always references the necessary datasets.
Manage all network information through a central UI. Smartcaster lets you create, modify, or remove transport streams and services with minimal effort. Stay ahead with real-time data updates—our software ensures that your PSI/SI tables are always current, reflecting the latest state as declared on the UI.
After clicking the Add new TS button, You have to set up the parameters of the newly created TS. Physical details must aligh with the multiplexer's / edge-QAM's configuration.
You can also define DAA parameters for the TS in this window, on the DAA details tab.
EPG information can be loaded from:
XML sources can be added/edited easily by using the context menu. In the edit window You can define an internal name, the URL of the XML feed optionally with authentication, select the parser, and click Validate.
Upon a successful validation You can see how many channels are found in the XML source, and after clicking Apply You can one-by-one select the changes You want to make in the system.
EPG information is parsed and loaded into an internal data format known as the EPG Repository. This repository is designed to logically store the EPG information for any channel, connected to an input XML file. When an XML file is reloaded, the content is seamlessly integrated into the appropriate repository, ensuring efficient and organized EPG data management.
The rise of DAA has steered us in a new development direction.
Although standard DVB features remain essential for operator networks, an increasing
number of service providers are migrating to a distributed platform. To efficiently service
these systems, a centralized Video Core is needed to program and maintain video services
on remote PHY devices.
Since Smartcaster manages all the essential information (transport stream details such as TS IDs, frequencies, modulations and symbol rates) required to bring up an RPD (Remote PHY Device), it is a straightforward decision to use this element as a Video Aux Core.
Utilizing digital optics instead of analog links we achieve better signal qualities on the network, which allows better throughput, and better service for the customers.
No need for a separate edge-QAM: the same remote PHY device can provide DOCSIS and DVB channels. There is also no need for any analog combining in the headends.
With less devices operators can save significant cost by migrating to a DAA based technology.
Principal core is a central and most important element of a DAA system. There is always 1 dedicated active principal core in the architecture (backups can be added). Principal core is responsible for initializing a remote PHY device by setting mandatory system parameters such as PTP clocks, and also for optionally receiving logs and telemetry informations from them. A principal core is usually CCAP which also configures DOCSIS services, but this is not q requirement.
All other cores, other than the principal, are called AUX cores, which provide auxiliary functions for a system, such as video services. A video AUX core is responsible to connect to a remote PHY device and provision the necessary RF channels and set up the networks streams which should be forwarded to those channels. The video AUX core does’t do any data stream processing, it is just a control plane entity.
The video input streams delivered to a remote PHY device must conform with the DOCSIS DEPI specifications. This means that all the widely used MPEG TS multicast UDP streams should be properly encapsulated into L2TPv3 format.. To do this encapsulation operators can use any kind of compatible 3rd party devices (some multiplexers have this functionality), or they can also use Smartcaster’s own video pipe solution which will be available in 2024 Q4.
Smartcaster is able to act as a principal core for remote PHY devices. By this feature operators have the ability to operate an RPD only with video without DOCSIS service, like an Edge-QAM.
Sometimes operators have very similar network regions with only slight differences between them. To support their setups Smartcaster supports parameter override groups, aka. flavors which can be assigned to a specific group of RPDs. These flavors can change the default settings read from the network structure database and customize a pre-defined set of details which should be different between the deployed RPDs.
Onboarding of a remote PHY device is automatic. Every RPD which tries to communicate with Smartcaster's Video Aux Core module gets enlisted in the RPD database. On this view operators can see the list of known RPDs and the actual operational status of them.
Assigning an RPD to a network is very easy: just right click the network which You want to pair with the RPD, select Edit RPD assignments and add/remove any number of RPDs to Your network.
As soon as the RPD reboots or reaches core connection state, the RPD status is being represented on the GUI along with the actual IP address of the connected RPD.