{'fraction_non_alphanumeric': 0.021137393054856568, 'fraction_numerical': 0.0010065425264217413, 'mean_word_length': 4.68, '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}}
Channelization for Publish-Subscribe Systems

Publish-subscribe systems are becoming a popular way to disseminate information. They are a type of push-based system. Push technology comes from a very simple idea: rather than users explicitly requesting (pulling) the information they need, data can be sent without them specifically asking for it. In the publish-subscribe model we describe in this paper, users subscribe to updates published by a data source. The model has several important characteristics. It is event-driven as data items are sent as soon as they are updated. Updates are broadcast (1-to-N ) and data transmission is aperiodic as there is no pre-defined schedule for sending or updating data. We are most concerned with publish-subscribe systems that have a large number of users who have significant overlap in their interests. Advances in broadcast technology have enabled publish-subscribe. Broadcast technology has a long history of use. We have seen it used in radio and television for many years and more recently have benefited from its use in satellite broadcast and multicast. The major advantage of broadcast is its ability to do 1-to-N transmission where the transmission of a single item can satisfy an arbitrary number of clients. Also, its scalability permits little or no incremental cost for each additional user. Essential to any publish-subscribe system are profiles. A profile describes a user’s interest in the data at the data source. In our system it indicates the specific items that a client wants to receive when those items are updated. The profile is stored at the data source and can be thought of as a continually evaluated query. Our publish-subscribe system will depend on broadcast channels to deliver data updates to users. The specific problem that we attempt to solve is the assignment of users and data items to these channels so as to make efficient use of the network resources and minimize delivery of superfluous data to users.