{'fraction_non_alphanumeric': 0.02092675635276532, 'fraction_numerical': 0.0, 'mean_word_length': 5.563725490196078, '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}}
Multimedia bridging: a structured view

Multimedia, multipoint applications require the processing and coordination of audio, video and data, to unsure that each participant or user receives the proper media traffic mix in the expected format at the expected time. Such a requirement is met by multimedia bridging, which encompasses many functions, including, event ordering, multimedia synchronization, network-user interfacing, media processing and distribution. In practice, bridging functions are either implicitly embedded in the software of distributed multipoint applications or they are centrally located on a hardware component embedded in the network, called a "bridge", usually designed to support a single multipoint application, such as teleconferencing. This paper presents a structured view of the multimedia bridging problem. Our premise is that a bridge should be viewed as a logical entity which provides a set off functions that are transparently accessible to many multipoint applications. Whether bridging functions are physically resident at an end-point or in a network, and whether they are implemented in software or in hardware is a matter of performance, efficiency and cost trade-offs which remain to be evaluated. We believe that this is a first step towards developing more flexible bridging infrastructures.