To better understand the configuration and operation tasks performed on a VTM, it is useful to place the VTM within the context of a Distributed Access Architecture (DAA) environment. Employing a DAA dual-core environment to support video and high-speed data services is a key strategy for service operators who need to realign their network bandwidth to continue to deliver quality video services, and free up bandwidth for increased data service capacity. The growth in demand for more data services is the key driver in the industry’s system evolution.
The choice between RPD and RMD is operator-specific and is primarily driven by data-side considerations. For purposes of this User Guide, noting that the video services are not dependent on the MAC layer, use of RxD is a reference to either RPD or RMD in the context of video management. Where a specific configurable item is available for RMD, it is noted.
When an RxD is deployed, the Principal Core is responsible for the overall lifecycle configuration management (turn-up, time source identification, code updates, etc.) which are also facilitated by the Domain Manager. The Principal Core function specifically related to VTM is identifying the IP address of the Auxiliary Core which is then used to deliver video configuration.
VTM
VTM facilitates managing video configurations within the VUE, enables and eases definition of video services, and simplifies building service groups to reduce your burden of data set management.
A Service Group consists of a common set of transport stream and channel configurations, which are to be applied to a population of RxDs (usually based on a criterion such as hub location, Ad Zone, and so on), to receive the same configuration. Additionally, VTM interfaces with the Digital Addressable Controller (DAC) to receive all channel information for the region. This information defines service group information for the RxDs configured by the VUE’s regional ACCP sub-system.
A single instance of VTM can administer the entire DAA topology.
VUE
The Video Unified Edge (VUE) provides the network and RF information between the video sources and the RxDs. It is a highly independent scalable solution designed to replace legacy headend video gear and functions as an auxiliary core. VUE is a containerized application which can be used in both bare-metal and virtualized environments.
- Define Services
- The definition of services in a Service Group is done through Sources and Service Catalogs defined in VTM.
- Build the Pipes
- QAM and modulation configurations are defined for each service group using channel information. This information imported from the Digital Addressable Controller (DAC) 6000 can be used to assist with the creation of service groups.
- Fill the Pipes
- Services are either mapped to the appropriate destination or pass-thrus are defined as needed.
- Distribute Pipes
- Appropriate RxD assignment(s) in the service groups are performed and passed to VUE.
CIN
The Converged Interconnect Network (CIN) is the network between the CCAP Core and the RxD, including outside plant and in-hub connectivity.
RPD/RMD
Remote PHY Devices (RPDs) and/or Remote MAC PHY Devices (RMDs) plug into traditional HFC nodes and convert the digital signals to RF/QAM, performing functions that used to be in the headend CCAP. RxDs have a network interface fed by fiber northbound, and RF interfaces southbound towards customer premises. Traditional video edge QAMs and RF combiner networks are eliminated in the hub/headend.
During service group configuration, the RxD inventory in the VTM is presented to the operator. This information is received through the Domain Manager or a compatible API. You can configure the interval of the synchronization of this information. In addition, you have the option to remove the RxD from the system once a synchronization is performed.