{'fraction_non_alphanumeric': 0.019835841313269494, 'fraction_numerical': 0.0, 'mean_word_length': 5.4734513274336285, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Algorithms and Trade-Offs in Multicast Service Overlay Design

The Multicast Service Overlay Network (MSON) has been recently introduced to address some of the deployment and maintenance problems of IP multicast and application-level multicast. An MSON is essentially a backbone service overlay provisioned by an MSON provider and designed to “multiplex” multiple-user overlays. It consists of service nodes or proxies deployed by the provider. The proxies are strategically deployed to form a backbone overlay and provide multicasting functionalities for supporting many user groups simultaneously. The MSON provider designs the backbone overlay for a large user population and can therefore enjoy large-scale economies and benefits. Since the deployment of an MSON is a capital-intensive investment, it is very imperative to carefully design the MSON so that the provider can make the best revenue out of this investment. In this article, the authors formulate the MSON design problem by taking into account operational costs of the MSON provider. They then explore three subproblems: overlay proxy placement, overlay link selection, and bandwidth dimensioning. For each of these subproblems, the authors present several algorithms and discuss their design trade-offs. By simulations, they investigate the effectiveness of different overlay design algorithms, analyze their impact on multicast performance, and suggest some practical solutions for MSON design.