{'fraction_non_alphanumeric': 0.013353115727002967, 'fraction_numerical': 0.0, 'mean_word_length': 5.159817351598173, '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}}
Taking the sting out of flow update peaks in software-defined service chaining

Dynamic network service chaining allows network operators to apply network services to customer traffic on demand and in a highly flexible manner. SDN and particularly OpenFlow-based approaches have been presented that exploit the flexibility and feature richness of OpenFlow for service chaining in data center settings. These systems often use network architectures similar to MPLS, where network traffic is processed at the network edges and the network core conducts simple packet forwarding only. This approach is suitable for many use cases due to the complementary characteristics of the hardware devices used in the core and the virtual switches used at the edge on virtualization hosts. Yet, this leads to a concentration of processing flow updates solely at the network edges, which can cause lowered QoS during flow update peaks, e.g. when a virtualization host fails. To tackle this problem, in this paper a concept is presented and evaluated that offloads OpenFlow rule updates from software-based edge switches to exploit hitherto unused resources on hardware switches in the core of the network. Furthermore, an analytical model is presented that allows describing the expected gain of the approach based on characteristics of the used OpenFlow devices.