%% You should probably cite draft-ietf-dmm-tn-aware-mobility-09 instead of this revision. @techreport{ietf-dmm-tn-aware-mobility-02, number = {draft-ietf-dmm-tn-aware-mobility-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-dmm-tn-aware-mobility/02/}, author = {Uma Chunduri and John Kaippallimalil and Sridhar Bhaskaran and Jeff Tantsura and Praveen Muley}, title = {{Mobility aware Transport Network Slicing for 5G}}, pagetotal = 24, year = 2021, month = oct, day = 22, abstract = {This document specifies a framework and mapping of slices in 5G mobile systems to transport network slices in IP, Layer 2 or Layer 1 transport networks. Slices in 5G systems are characterized by latency bounds, reservation guarantees, jitter, data rates, availability, mobility speed, usage density, criticality and priority. These characteristics are mapped to transport network slice include bandwidth, latency and criteria such as isolation, directionality and disjoint routes. Mobile slice criteria are mapped to the appropriate transport slice and capabilities offered in backhaul, midhaul and fronthaul connectivity segments between radio side network functions and user plane function(gateway). This document describes how a mobile network slice is mapped to a slice in IP or Layer 2 transport network between 3GPP provisioning end points. The same mapping mechanisms apply during initial UE session setup and following UE mobility. Applicability of this framework and underlying transport networks, which can enable different slice properties are also discussed. This is based on mapping between mobile and transport underlays (L2, Segment Routing, IPv6, MPLS and IPv4).}, }