Towards cross-domain mobility management in the edge

Control and User Plane Separation (CUPS) allows placing the control plane separately from the actual user plane executor. This allows deploying user plane instances closer to the end-user: traffic serving can be more effortless, and end-to-end latency can be decreased. Mobile IPv6 can also be divided into control and user plane parts. This article will show what this separation presumably will look like in connection with Mobile IPv6. In a dynamic cloud environment, standard Mobile IPv6 must be part of the overall orchestration flow. This is where Cloud-native Mobile IPv6 comes into the picture. This paper presents how ordinary and cloud-native Mobile IPv6 architectures should be refactored with corresponding signaling flows to fit into the CUPS concept. We also show by measurements the latency budget we can gain using localized user-plane instances to connect to a distributed application.