{'fraction_non_alphanumeric': 0.022156573116691284, 'fraction_numerical': 0.004431314623338257, 'mean_word_length': 5.087640449438203, '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}}
Demonstration of MBMS video streaming over GERAN

3GPP has introduced Multimedia Broadcast/Multicast Services (MBMS) in Release 6, targeting simultaneous distribution of multimedia content to many mobiles within a serving area. For new services to be successful, it is essential that (i) sufficient benefits compared to existing services are obvious to network operators and customers, (ii) the time-to-market is sufficiently low, and (iii) the costs are minimal requiring the re-use of existing infrastructure as much as possible. However, existing wireless communication systems have been optimized for point-to-point (p-t-p) data transfer. Several modifications to standards and products have therefore been necessary to provide efficient multicast services. To overcome the problem of low reliability due to heterogeneous receiving conditions and limited feedback capabilities, several proposals of additional FEC schemes have been considered in the MBMS standardization. Recently, 3GPP has mandated and standardized application layer (AL) FEC on top of UDP layer using Raptor Codes as an additional mean to provide reliability. In addition, in GERAN RLC layer some modifications have been added to support the transmission of multicast/broadcast transmission. In this work, we focus on the streaming delivery in MBMS; specifically the transmission of H.264/AVC coded video is presented. The framework for streaming delivery as shown in Fig. 1 builds on the appropriate processing of compliant RTP packets, incoming at same or different UDP ports. Fig. 1 shows the processing of RTP packets and the interaction of the different protocol entities within sender and receiver. A FEC layer, placed on top of the UDP layer, constructs FEC source packets by appending a FEC source payload ID field at the end of each RTP packet. These packets are then forwarded to UDP layer which, after UDP encapsulation, are transmitted to the receiver via an IP-based bearer in UTRAN or GERAN. Also a copy of these packets is forwarded to the FEC encoder to generate parity symbols for a block of usually several or many RTP packets. The generated IP packets are forwarded to the UTRAN or GERAN layer where additional parameters can be changed to optimize the transmission. At the receiver, the additional redundancy symbols allow to recover most of the information even is some original RTP packets are lost. Most of the technical standardization work of MBMS for Release 6 has been completed just recently. During the standardization phase, a significant effort has been spent in identifying the cooperation of content delivery protocols and applications with underlying MBMS bearers for GERAN and NAL units H.264 Encoder