If you can't read please download the document
Upload
elden
View
35
Download
0
Tags:
Embed Size (px)
DESCRIPTION
Use case scenarios for Distributed Mobility Management. Hidetoshi Yokota , KDDI Lab Pierrick Seite , France Telecom-Orange Elena Demaria , Telecom Italia Zhen Cao , China Mobile Dapeng Liu , China Mobile H. Anthony Chan , Huawei Technologies Charlie Perkins , Tellabs - PowerPoint PPT Presentation
Citation preview
Use case scenarios for Distributed Mobility ManagementHidetoshi Yokota, KDDI LabPierrick Seite, France Telecom-OrangeElena Demaria, Telecom ItaliaZhen Cao, China MobileDapeng Liu, China MobileH. Anthony Chan, Huawei TechnologiesCharlie Perkins, TellabsTelemaco Meria, Alcatel-Lucent Bell LabsHui Deng, China MobileWassim Haddad, EricssonIETF79 MEXT WG*
IETF79 MEXT WG
Background and motivationMobile data is literally growing exponentiallySmartphones generate much more traffic than plain old mobile phonesMobile operators are starting to offload mobile traffic to WiFi networks and deploy local Content Delivery NetworkStandardization for mobile data offload is underway in other SDOs3GPP LIPA/SIPTOThis issue is not only for one SDO, but for the whole InternetRenovate the conventional mobile networkMore distributed and scalable modelIETF79 MEXT WG*
IETF79 MEXT WG
Where to distribute?IETF79 MEXT WG*Core-levelAR-levelAccess-levelMobileCoreNetworkAccessNetworkHost-level
IETF79 MEXT WG
Core-level distributionKeep existing hierarchyTraffic and mobility bindings are distributed over HA/LMAsHandover, signaling and/or routing may be needed between HAs/LMAsIETF79 MEXT WG*Core-levelAR-level
IETF79 MEXT WG
AR-level distributionRole of HA/LMA is regressedTraffic and mobility bindings are distributed over ARsSignaling and routing needed between ARsIETF79 MEXT WG*AR-level
IETF79 MEXT WG
Access-level distributionRole of mobile core is regressedPart of AR functionality is combined with APAccess Node (AN) =AP+ARDistribute traffic and mobility bindings over ANsSignaling and routing needed between ANsIETF79 MEXT WG*Access-level
IETF79 MEXT WG
Host-level distributionPeer-to-peer communication between MHsMore independent of the mobile networkSignaling and routing needed between MHsIETF79 MEXT WG*Host-level
IETF79 MEXT WG
How to distribute?Possible approaches for Distributed Mobility ManagementPartially distributed approachFully distributed approachIETF79 MEXT WG*
IETF79 MEXT WG
Partially distributed approach (I)Control and data plane separationControl plane: CentralizedData plane: DistributedIETF79 MEXT WG*MA: Mobility Anchor
IETF79 MEXT WG
Partially distributed approach (II)Dynamic mobility managementMobility is provided on demand
IETF79 MEXT WG*
IETF79 MEXT WG
Fully distributed approachBoth control and data planes are distributedIETF79 MEXT WG*MA: Mobility Anchor (including control function)Dynamic mobility management also appliesSelection of the appropriate mobility anchor is an issue
Mobility anchor selection in fully distributed approachEx.1: broadcast/multicast approachNo routing is neededGood for regional area, probably not for global
IETF79 MEXT WG*
IETF79 MEXT WG
Mobility anchor selection in fully distributed approach (contd)Ex.2: Search & deliveryEfficient look-up mechanisms exist, but still takes time to discover the corresponding MA scalability issue could remainIETF79 MEXT WG*
IETF79 MEXT WG
Analysis and proposalMore flat architecture is preferred for effective distributionFlexible and manageable routing is needed for selective traffic offload AR/Access-level distribution Scalability must be considered Partially distributed approach is likely to be more practical so far
IETF79 MEXT WG*
IETF79 MEXT WG