Live migration in Mobile Edge Computing (MEC)
Download as PPTX, PDF4 likes1,134 views
The document discusses the challenges of user mobility in Multi-access Edge Computing (MEC) systems, emphasizing the lack of a central anchor for session information. It highlights that when a user moves between MEC systems, session data is often lost, leading to limited mobility. The solution proposed involves establishing mobility groups and services to maintain user app context as users transition between MEC systems.
Live migration in Mobile Edge Computing (MEC)
- 2. Mobility today The core network is the session anchor. When a user moves, the session is rerouted from the core network. EPC Internet SGi S1
- 3. The mobility challenge for MEC EPC Internet SGi S1 MEC system App App MEC system App App Today, MEC operates as discrete systems. With no central anchor Session information is lost in the transition Mobility is limited.
- 4. MEC and mobility – the problem User1 is connected to App1 inside MEC System 1 VM App1 NFV + MEC U1 User 1 VM ? NFV + MEC MEC System 1 MEC System 2 eNodeB 1 eNodeB 2 Is App1 instantiated in the new MEC system? User1 is now connected MEC System 2……but What happens to the session information?
- 5. Mobility Groups & Mobility Services Each ME has its own mobility groupME ME ME ME ME ME ME ME ME ME ME ME ME ME ME ME ME Host VM App VM App Mobility Services Mesh connectivity within each group Mobility services added to the ME host
- 7. VM App1 U1 Mobilizing ME Mobility services: Use the Mobility Group mesh to connect the ME systems Stream the user app context from the previous ME to the new ME ME 1 User 1 eNodeB 1 eNodeB 2 Mobility Services NFV + MEC VM App1 U1 Mobility Services NFV + MEC ME 2 Copy the user context to the new ME Operate directly from the new ME