Network Working Group D. Liu Internet-Draft China Mobile Intended status: Informational H. Chan Expires: August 18, 2014 Huawei Technologies H. Deng China Mobile February 14, 2014 DMM Deployment Scenario draft-liu-dmm-deployment-scenario-00 Abstract This document discusses the deployment scenario of distributed mobility management. The purpose of this document is to trigger the discussion in the group to understnad the DMM deployment scenario and consideration from the operator's perspective. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on August 18, 2014. Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of Liu, et al. Expires August 18, 2014 [Page 1] Internet-Draft cloud mobile February 2014 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Conventions used in this document . . . . . . . . . . . . . . 2 3. Deployment Scenario and Model of DMM . . . . . . . . . . . . 2 4. Network Function Virtualization Scenario . . . . . . . . . . 3 5. Problem statement of network function virtualization deployment model . . . . . . . . . . . . . . . . . . . . . . 4 5.1. Control and data plane separation . . . . . . . . . . . . 4 5.2. Mobility management . . . . . . . . . . . . . . . . . . . 4 6. SIPTO deployment scenario . . . . . . . . . . . . . . . . . . 4 7. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 5 8. Security Considerations . . . . . . . . . . . . . . . . . . . 5 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 5 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 12. Normative References . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction Distributed mobility management aims at solving the centralized mobility anchor problems of the tranditional mobility management protocol. The benefit of DMM solution is that the data plane traffic does not need to traverse the centralized anchoring point. This document discusses the potential deployment scenario of DMM. The purpose of this document is to help the group to reach consensus regarding the deployment model of DMM and then develop the DMM solution based on the deployment model. 2. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL","SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 3. Deployment Scenario and Model of DMM As discussed in the DMM requirement document, the centralized mobility management has several drawbacks. The main problem of the centralized mobility management protocols is that all the traffic need to anchor to a centralized anchor point. This approach does not cause any problem in current mobile network deployment but in the scenario that will be discussed later in this document, centralized Liu, et al. Expires August 18, 2014 [Page 2] Internet-Draft cloud mobile February 2014 mobility management protocols will have many drawbacks and it is believed that DMM is more suitable in that scenario. The main deployment scenario discussed in this document is divided into two types. The first one is the network function virtualization scenario. In this scenario, the mobile core network's control plane function is centralized in the mobile cloud. Apparently, deploying the data plane function also in the same centralized mobile cloud is not optimized from the traffic routing's perspective. Another deployment scenario is the SIPTO/LIPA scenario which is discussed in 3GPP. In this scenario, DMM can provide optimized traffic offloading solution. 4. Network Function Virtualization Scenario This section discusses network function virtualization scenario. Mobile Cloud ........... (' ') ( ))) ((( +-----------+ ))) (( |Mobile Core| ))) ((( +-----------+ ))) ('..............') | | IP Transit Network (.........) ( )) MN-Internet communication ( ^ )) ^ > > >( ^ ))> > > > > > > > > ^ (( ^ ) v ^ (.........^.) v ^ +-------| | ^| v ^ | | ^+--------------+ v ^ | | < < | v MN-MN communication ^ | | ^ | v +--------------+ +--------------+ +--------------+ |Access Network| |Access Network| |Access Network| +--------------+ +--------------+ +--------------+ ^ ^ v ^ ^ v +---------+ +---------+ +---------+ | MN | | MN | | MN | +---------+ +---------+ +---------+ Liu, et al. Expires August 18, 2014 [Page 3] Internet-Draft cloud mobile February 2014 Figure 1: Network function virtualization deployment architecture In this architecture, the mobile core network is located in the cloud /data center, which can be the operator's private cloud. The access network is connected through an IP transit network. The mobile core network can run in a virtualized platform in the cloud/datacenter. 5. Problem statement of network function virtualization deployment model 5.1. Control and data plane separation The cloud based mobile core network architecture implies separation of the control and data plane. The control plane is located in the cloud and the data plane should be distributed. Otherwise, all the data traffic will go through the cloud which is obviously not optimized for the mobile node to mobile node communication. For the mobile node to Internet communication, the Internet access point is normally located in the metro IP transit network. In this case, the mobile node to Internet traffic should also go through the Internet access point instead of the mobile core in the cloud. However, in some deployment scenario, the operator may choose to put the mobile core cloud in the convergence layer of IP metro network. In this case, the Internet access point may co-located with the mobile core cloud. In this case, the mobile node to Internet traffic may go through the mobile core cloud. 5.2. Mobility management Since the control plane and data plane are separated and the data plane is distributed, traditional mobility management can not meet this requirement. Distributed mobility management or SDN based mobility management may be used in this architecture to meet the traffic routing requirement (e.g. MN to MN and MN to Internet traffic should not go through from the mobile core cloud.). 6. SIPTO deployment scenario Another deployment scenario is the SIPTO scenario which is discussed in 3GPP. DMM is believed to be able to provide dynamic anchoring. It allows the mobile node to have several anchoring points and to change the anchoring point according to the requirment of application. In SIPTO scenario, the gateway function is located very near to the access network and to the user. If using current Liu, et al. Expires August 18, 2014 [Page 4] Internet-Draft cloud mobile February 2014 centralized mobility management, the traffic will need to tunnel back to the previous anchor point even when the mobile node has changed the point of attachment to a new one. 7. Conclusion This document discusses the deployment scenario of DMM. Two types of deployment scenario is discussed in this document. Further types of deployment scenario can be added to this document according to the progress of the group's discussion. 8. Security Considerations N/A 9. IANA Considerations N/A 10. Contributors 11. Acknowledgements 12. Normative References [IEEE-802.11.2012] March 2012. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. Authors' Addresses Dapeng Liu China Mobile No.32 Xuanwumen West Street Beijing 100053 China Email: liudapeng@chinamobile.com Liu, et al. Expires August 18, 2014 [Page 5] Internet-Draft cloud mobile February 2014 H Anthony Chan Huawei Technologies 5340 Legacy Dr. Building 3 Plano, TX 75024 USA Email: h.a.chan@ieee.org Hui Deng China Mobile No.32 Xuanwumen West Street Beijing 100053 China Email: denghui@chinamobile.com Liu, et al. Expires August 18, 2014 [Page 6]