< draft-fu-dmm-vcpe-models-00.txt   draft-fu-dmm-vcpe-models-01.txt >
Internet Engineering Task Force Q. Fu, Ed. Internet Engineering Task Force Q. Fu, Ed.
Internet-Draft China Mobile Internet-Draft H. Deng
Intended status: Informational S. Gundavelli Intended status: Informational China Mobile
Expires: January 2, 2016 Cisco Expires: April 21, 2016 October 19, 2015
H. Deng
China Mobile
July 2015
Motivations, usecases and Models of VCPE Motivations, usecases and Models of VCPE
draft-fu-dmm-vcpe-models-00 draft-fu-dmm-vcpe-models-01
Abstract Abstract
This document introduces the concept of Virtual Customer Premises This document introduces the concept of Virtual Customer Premises
Equipment (VCPE). Such concept was first proposed in Broadband Forum Equipment (VCPE). Such concept was first proposed in Broadband Forum
(BBF) as Network Enhanced Residential Gateway (NERG). The VCPE is (BBF) as Network Enhanced Residential Gateway (NERG). The concept is
the Home Agent (HA) of the Mobile Nodes (MN) attached to the physical further expanded as not only referring to virtual CPE of residential
CPE (pCPE). In this document, we explain the motivation and network, but all the virtual network and service functions shifted
advantages of VCPE. Three usecases of VCPE is further discussed in from the customer side to the operator side. Deployment of VCPE in
the enterprise network, the residential network, and the Internet of some typical DMM (Distributed Mobility Management) scenarios brings
Things (IoT) Network. Two models of field deployment of VCPE are specific requirements and even protocol extension in DMM. In this
discussed afterwards. The models of VCPE decompose the Control Plane document, we will first explain the motivation and advantages of
(CP) and the Data Plane (DP), which makes it easier for the VCPE. A usecases of VCPE in the community Wi-Fi deployment is
deployment of the distributed mobility model. further discussed so as to explain the deployment of VCPE in a DMM
scenario. Three models of field deployment of VCPE are discussed
afterwards to indicate the possible CP/DP decomposition requirement
and protocol extension.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 2, 2016. This Internet-Draft will expire on April 21, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 22 skipping to change at page 2, line 22
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Motivation and Advantage of VCPE . . . . . . . . . . . . . . 3 3. Motivation and Advantage of VCPE . . . . . . . . . . . . . . 3
4. Use case of VCPE . . . . . . . . . . . . . . . . . . . . . . 4 4. Use case of VCPE . . . . . . . . . . . . . . . . . . . . . . 4
5. Models of VCPE Deployment . . . . . . . . . . . . . . . . . . 5 5. Models of VCPE Deployment . . . . . . . . . . . . . . . . . . 5
6. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 8 6. VCPE Deployment for Community Wi-Fi . . . . . . . . . . . . . 8
7. Informative References . . . . . . . . . . . . . . . . . . . 8 7. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 8. Informative References . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
This document introduces the concept of VCPE. The concept of VCPE is This document introduces the concept of VCPE. The concept of VCPE is
to shift most of the networking and service functionalities from the to shift most of the networking and service functionalities from the
customer side to the network side. In this way, the customer side's customer side to the network side. In this way, the customer side's
equipment, that is the pCPE (Physical Customer Premises Equiptment), equipment, that is the pCPE (Physical Customer Premises Equiptment),
can be simplified. The VCPE refers to one or a set of equipments at can be simplified. The VCPE refers to one or a set of equipments at
the network side to execute the networking and service the network side to execute the networking and service
functionalities used to be executed at the CPE. In such functionalities used to be executed at the CPE. In such
architecture, the CPE can be a simple L2 switch, which is only architecture, the CPE can be a simple L2 switch, which is only
responsible for forwarding packets to a certain next hop. The responsible for forwarding packets to a certain next hop. The
concept of VCPE was first introduced in BBF as NERG (WT-317), which concept of VCPE was first introduced in BBF as NERG (WT-317), which
mainly focuses on shifting some of the functionalities of a mainly focuses on shifting some of the functionalities of a
residential gateway to the operator's network, for enabling network residential gateway to the operator's network, for enabling network
based features. The aim is to facilitate the deployment, maintenance based features. The aim is to facilitate the deployment, maintenance
and evolution of both existing and new capabilities without adding and evolution of both existing and new capabilities without adding
complexity to the RG and/or the home network. complexity to the RG and/or the home network.
Figure 1 shows the architecture of the pCPE and the VCPE. In this Figure 1 shows the architecture of the pCPE and the VCPE.
architecture, the VCPE is the HA for the mobile nodes adhear to the
pCPE at the network side.
+---+ +-----+ +-----+
|MN1|====|pCPE1|================|VCPE1|
+---+ +-----+ +-----+
+-----+
|pCPE2|
+-----+
+---+ +-----+ +-----+ ............... ..............
|MN2|====|pCPE3|================|vCPE2| :Customer side: :Network side:
+---+ +-----+ +-----+ : +-----+ : : +-----+ :
: |pCPE |================|VCPE | :
: +-----+ : : +-----+ :
..............: .............:
Figure 1: VCPE Architecture Figure 1: VCPE Architecture
In this document, we would like to further propose such concept in In this document, we would like to further propose such concept in
the following aspects: the following aspects:
(1) Motivation and advantages of VCPE. (1) Motivation and advantages of VCPE.
(2) Usecases of VCPE. We propose three usecases, including the (2) Usecases of VCPE. A usecase of VCPE in the community Wi-Fi is
enterprise network, the residential network, and the IoT (Internet of explained in detail.
things) network.
(3) Models of VCPE deployment. We propose two models for the field (3) Models of VCPE deployment. We propose three models for the field
deployment of VCPE. Such models can be used for deployments in deployment of VCPE.
multiple scenarios, including both residential network and enterprise
network.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Motivation and Advantage of VCPE 3. Motivation and Advantage of VCPE
The motivation and advantage of introduting VCPE can be concluded as The motivation and advantage of introduting VCPE can be concluded as
follows: follows:
(1) It will reduce the cost of manufacturing and maintaining of the (1) It will greatly speed up the service launching period. Since
pCPE. By shifting most of the complicated functions from the
customer's side to the operator's side, the cost of the pCPE can be
reduced significantly. Such redunction can be remarkable in the
enterprise network, since network functions, such as Firewall and
NAT(Network Address Translator) at the customer side can be
expensive. In the meantime, deployment of VCPE can also reducing the
OPEX of operators. Orders of on-site repair can be reduced because
of the simplicity of the customer equiptments.
(2) It will avoid complicating the pCPE devices when providing value-
added L3-L7 services to the customers. Take the transport network as
example. Traditionally, pCPEs at the enterprise customer side are
simple L2 devices in the transport network. In order to meet the
requirements for value-added L3-L7 services from the customers, the
pCPEs should be redesigned to become L3 or even more complicated
devices. Such devices will not only result in an increase of
manufacture and maintenance cost, and will also request addtional
efforts for frequent update to meet the constantly increased
requirements of the customers. Nevertheless, by utilizing the VCPE
achitecture, pCPE can remain to be a simple L2 device, which is only
responsible for L2 forwarding. In this way, frequent update of these
pCPEs is not necessary, which will greatly decrease both CAPEX and
OPEX of the network operators.
(3) It will greatly speed up the service launching period. Since
most of the complicated functions are located at the VCPE in the most of the complicated functions are located at the VCPE in the
network side, operators have more power over services. Benefitting network side, operators have more power over services. Benefitting
from the recent NFV (Network Function Virtualization) and cloud from the recent NFV (Network Function Virtualization) and cloud
technologies, VCPE can be accomplished using SFC in the virtual technologies, VCPE can be accomplished using SFC in the virtual
network, where different services can act as different VNFs (Virtual network, where different services can act as different VNFs (Virtual
Network Functions). Operators only need to add new VNFs on the VCPE Network Functions). Operators only need to add new VNFs on the VCPE
side to launch new services to the customers. In this way, Operators side to launch new services to the customers. In this way, Operators
can provide a variety of services through the network. can provide a variety of services through the network.
(2) It will reduce the cost of the pCPE. By shifting most of the
complicated functions from the customer's side to the operator's
side, the cost of the pCPE can be reduced significantly. Such
redunction can be remarkable in the enterprise network, since network
functions, such as Firewall and NAT(Network Address Translator) at
the customer side can be expensive. In the meantime, the cost of
upgrading tens of thousands of pCPE when launching new services can
be saved, since only software upgrade at the VCPE side is required.
(3) It will simplify the maintainance of the pCPE. Since most of the
complicated functionalities are shifted to the network side, the
maintainance of the pCPE can be greatly simplified. On-line
maintainance is possible in lots of cases since the pCPE is only a L2
devices and can be considered transparent to the operators.
(4) It will provide user-define-network experience. By introducing (4) It will provide user-define-network experience. By introducing
SFC concept into the VCPE, users can define his own service order and SFC concept into the VCPE, users can define his own service order and
sequence. Therefore, enterprise customers can enjoy the self-defined sequence. Therefore, customers can enjoy the self-defined services
services over the public network. over the public network.
4. Use case of VCPE 4. Use case of VCPE
The concept of VCPE can be used in multiple scenarios. In this The concept of VCPE can be used in multiple scenarios. In this
section, we will propose two use cases of VCPE, one in residential section, we will propose a usecase of VCPE when deploying community
network, and the other in the enterprise network. Wi-Fi.
(1) Use Case of VCPE in the Enterprise network.
Traditional enterprise network uses the tranport network access.
Multiple network functions, including Firewall (FW) and NAT, are
deployed at the enterprise customer's side. Such deployment not only
increases the cost of the equiptment at the customer side, but also
makes it difficult for both the enterprise customers and the service
providers operating and maintaining the functions.
By introducing VCPE into the transport network, functions such as FW
and NAT can be shifted to the aggregate network or core network,
acting as VCPE at the service provider's side. Moreover, value-added
services can be provided. For example, by deploying a virtual Deep
Packet Inspection (vDPI), service providers can provide fine grained
data control to the enterprise customers.
(2) Use case of VCPE in the residential network.
In the residential network, traditionally, pCPE locates at the
customer premises terminates the home network and connect the LAN
devices to the Internet or to some service platforms through the
broadband access network. With the expansion of the broadband access
and the development of the OTT (Over The Top) industry, the quantity
and requirements of addtional functions of pCPE increases rapidly.
By shifting most of the complicated functions to VCPE, the cost of
the largely deployed CPE can be saved. In the meantime, deployment
of new features by service providers can be accelerated.
Taking PPPoE access as example. By shifting PPPoE client to VCPE, The community Wi-Fi is a new service that operators provide to
pCPE can be a simple L2 device. In this case, VCPE takes the leverage unused capacity on existing residential Wi-Fi infrastructure
responsibility to initiate PPPoE request to BRAS once receiving to offer Wi-Fi network access to visitors and passers by near the
traffic flow from the customers. When receiving the certification neighbourhood. An operator can also use this excess capacity to
from BRAS, VCPE will act as DHCP server by assigning IP address to offer services to retail and roaming-parter operators' subscribers.
the traffic generating port. Such approach can also be used for IPv6 The residential subscribers accessing the network from inside their
upgrade,in which case VCPE can act as IPv6 DHCP relay. homes have prioritized access to the Wi-Fi resources. The
residential Wi-Fi infrastructure is configured in a manner that
allows for a secure and independent access channel to retain service
quality, safety, and privacy for both residential and visitor
customers. Roaming users are only allowed to use the Wi-Fi network
capacity that is not currently used by the subscriber at home.
(3) Use case of VCPE in the IoT (Internet of Things) network. Basically, the wireless Access Point (AP) in the home will provide
two networks: a private one for the home owner/subscriber, and a
community network for on-the-go subscribers passing through the
neighborhood. Home users can have all of their Wi-Fi devices
(smartphone, tablet, etc.) automatically connect to the private
network. In the meantime users travel outside can connect to the
community network, and can roaming through different APs supporting
community Wi-Fi as he/she is moving. The community Wi-Fi service is
a typical usecase of DMM.
VCPE can also be used in the IoT network. So far, multiple wireless Deploying community Wi-Fi on the pCPE means upgrading tens of
communication standards, including Wi-Fi, Zigbee, Blue Tooth, and thousands of existing pCPE devices at the customer side, which is not
etc., exist for the connection of the IoT devices to the GW. The IoT cost-effective and may bring extra complexity for maintainance.
GW is responsible for decomposing the L2 packets from the devices, Therefore VCPE becomes an optimized solution for such deployment. In
composing them into L3 packets and transferring to the Internet such deployment, the private users access to the pCPE (which is the
Server. Due to these various wireless communication standards, AP at home) as usual. The public users are roaming through different
multiple IoT GWs have to be deployed at users' home to support pCPEs. The traffic all goes though the tunnel from the pCPE to the
different IoT devices. By shifting the packet transforming function VCPE. The deployment of VCPE in the community Wi-Fi sencario brings
to VCPE, IoT GW can be a simple and unified L2 forwarding GW, while specific requirement and protocol extensions to DMM. The deployment
VCPE will support different standard stacks and is responsible for model of VCPE and its possible influence to DMM is further discussed
transforming packets following different communication standards to in the following section.
IP packets.
5. Models of VCPE Deployment 5. Models of VCPE Deployment
There are multiple models when deploying VCPE in use cases as are There are multiple models when deploying VCPE in use cases as are
discussed in the previous section. In this document, we conclude the discussed in the previous section. In this document, we conclude the
deployment of VCPE into two models. In the first model, a logical deployment of VCPE into three models. In the first model, a logical
instance of VCPE is deployed in the cloud for each pCPE instance. instance of VCPE is deployed in the cloud for each pCPE instance.
All traffic from pCPE goes through the vCPE. In the second model, That is, the pCPE and VCPE is deployed in an 1:1 manner. All traffic
the VCPE is based on service chains attached to BNG. The classifier from pCPE goes through the vCPE.
on BNG puts the pCPE traffic through the correct set of service
functions. Both of these two models can easily introduce CP/DP
decompositon at the VCPE side, and the DMM protocol can be used.
Figure 1 and Figure 2 show the two models of VCPE deployment. For
the first model, logical instance of VCPE is deployed. Such logical
instance can be a seperate instance deployed before or after the BNG,
as is shown in Figure 1(a) and Figure 1(b). It can also be deployed
by upgrading the traditional BNG to include the functions of VCPE, as
is shown in Figure 1(c).
+------+ +------+ +------+
| pCPE +--------+ | pCPE +-----| VCPE |-----+
+------+ | +------+ +------+ |
| +------+ ________ | +------+ ________
+------+ +--+---+ +-----+ |SFC in| / \ +------+ +------+ +-+---+ |SFC in| / \
| pCPE +-----+ VCPE +---+ BNG +-----+WAN DC+---+ Internet | | pCPE +-----+ VCPE +---+ BNG +-----+WAN DC+---+ Internet |
+------+ +--+---+ +-----+ +------+ \________/ +------+ +------+ +-+---+ +------+ \________/
| |
+------+ | +------+ +------+ |
| pCPE +--------+ | pCPE +-----| VCPE |-----+
+------+ +------+ +------+
Figure 1(a) VCPE instance deployed before BNG
+------+ Figure 2: VCPE deployment model NO.1: Logical Instance of VCPE
| pCPE +--------+
+------+ |
| +------+ ________
+------+ +--+---+ +-----+ |SFC in| / \
| pCPE +-----+ BNG +---+VCPE +-----+WAN DC+---+ Internet |
+------+ +--+---+ +-----+ +------+ \________/
|
+------+ |
| pCPE +--------+
+------+
Figure 1(b) VCPE instance deployed after BNG
+------+ In the second model, vCPE is modeled service function chains in Gi-
| pCPE +--------+ LAN. BNG knows how to classify the traffic from a given CPE with the
+------+ | help of the control plane, and run it through the service chain. In
+--+---------+ +------+ ________ such model, the CP/DP interface should be used between the control
+------+ |BNG +-----+ | |SFC in| / \ plane (which might be the controller) and the pCPE.
| pCPE +-----+ |VCPE | +---+WAN DC+---+ Internet |
+------+ + +-----+ | +------+ \________/
+--+---------+
+------+ |
| pCPE +--------+
+------+
Figure 1(c) VCPE instance deployed through upgrading BNG
Figure 2: VCPE deployment model NO.1: Logical Instance of VCPE +----------+
+Controller|
+--+-------+
+CP/DP interface .......................
+ :VCPE :
+ +---+--+ : +-----------------\ :
++++ pCPE +--------+ :|SFP1:DPI->FW->NAT + :
+ +------+ | : +-----------------/ :
+ | : :
+ +------+ +--+--+ : +------------\ :
++++ pCPE +-----+ BNG +---+SFP2:FW->NAT + :
+ +------+ +--+--+ : +------------/ :
+ | : :
+ +------+ | : +--------\ :
++++ pCPE +--------+ : |SFP3:NAT + :
+------+ : +--------/ :
.......................
For the second models, no logical instance exists as VCPE. VCPE is Figure 3: VCPE deployment model NO.2: VCPE as SFC
realized as a sequence of service function chaining (SFC) in the WAN
DC. In this model, BNG is acting as the classifier of SFC. Such The third model is almost the same with the second one, except that
classfication should be based on user profile, in which case, users the BNG is also CP/DP decomposed. In this model, The control plane
can define his own VCPE service. is composed of the controller of the pCPE and the control plane of
the BNG. The CP/DP interface is used between the controller and the
pCPE, and between the control plane and the data plane of the BNG.
Both of model No.2 and No.3 may have specific requirement and protoco
extensions for the CP/DP interface due to the usecase of VCPE.
.................................
: Control Plane :
: +----------+ +------+ :
: +++++++Controller| |BNG CP| :
: + +----------+ +--+---+ :
..+......................+......:
+ CP/DP interface + .......................
+ + :VCPE :
+ +---+--+ + : +-----------------\ :
++++ pCPE +-------+ + :|SFP1:DPI->FW->NAT + :
+ +------+ | + : +-----------------/ :
+ | + : :
+ +------+ +-+----+-+ : +------------\ :
++++ pCPE +-----+ BNG DP +----+SFP2:FW->NAT + :
+ +------+ +-+------+ : +------------/ :
+ | : :
+ +------+ | : +--------\ :
++++ pCPE +-------+ : |SFP3:NAT + :
+------+ : +--------/ :
.......................
Figure 4: VCPE deployment model NO.3: VCPE as SFC, with CP/DP
decomposition of BNG
SDN (Software Define Network) controllers can also be introduced in SDN (Software Define Network) controllers can also be introduced in
the second model. In which case, all of the pCPEs and the BNG data the third model. In which case, all of the pCPEs and the BNG data
plane (BNG-dp) can be controlled by the SDN-controller (also acting plane (BNG DP) can be controlled by the SDN-controller. When the
as the BNG control plane(BNG-cp)), as is shown in Figure 3. When the
customer selects a set of services, the SDN-controller will inform customer selects a set of services, the SDN-controller will inform
the pCPE and the BNG-dp to direct the traffic flow to a certain SFC. the pCPE and the BNG DP to direct the traffic flow to a certain SFC.
the Service Classification Function (SCF) is located in the BNG,
responsible for classifing traffic from different customer/network/
service. The SCF is controlled by the SDN-controller. When a packet
arrives, the SCF will ask the controller which Service Founction Path
(SFP) this flow should follow, and put corresponding SFC
encapsulation into the packet. The packet then goes into the service
founction region, and will be directed to different Service
Founctions (SF) based on the encapsulation.
+------+ ............... .................................
| pCPE +--------+ : VCPE : : Control Plane :
+------+ | : +----+ : : +--------------+ :
| : +--+sfp1+-----------+ : +++++++SDN Controller|++ :
+------+ +--+---+ : | +----+ : ___|____ : + +--------------+ + :
| pCPE +-----+ BNG +----| +----+ : / \ ..+......................+......:
+------+ +--+---+ : +--+sfp2+------+ Internet | + CP/DP interface + .......................
| : | +----+ : \________/ + + :VCPE :
+------+ | : | +----+ : | + +---+--+ + : +-----------------\ :
| pCPE +--------+ : +--+sfp3+-----------+ ++++ pCPE +-------+ + :|SFP1:DPI->FW->NAT + :
+------+ : +----+ : + +------+ | + : +-----------------/ :
:.............: + | + : :
+ +------+ +-+----+-+ : +------------\ :
++++ pCPE +-----+ BNG DP +----+SFP2:FW->NAT + :
+ +------+ +-+------+ : +------------/ :
+ | : :
+ +------+ | : +--------\ :
++++ pCPE +-------+ : |SFP3:NAT + :
+------+ : +--------/ :
.......................
Figure 3: VCPE deployment model NO.2: SFC realization of VCPE Figure 5: VCPE deployment model NO.3: SFC realization of VCPE, with
SDN controller as control plane
6. Conclusion 6. VCPE Deployment for Community Wi-Fi
In this section, we will discuss about the VCPE deployment for
Community Wi-Fi in detail. In the following deployment, we assume
the VCPE is deployed following the third model we discussed in
section 5. That is, the VCPE is a bounch of SFCs at the operator
side behind the BNG. The pCPEs and BNG-DP are all controlled by a
mutual control plane. The FPC protocol is used between the control
plane and the pCPEs, and that and the BNG-DP.
As we discussed in section 4, Community Wi-Fi can be deployed with
the help of deploying VCPE. In order to provide the Community Wi-Fi
service, the pCPE should provide two SSIDs, one for the pubic Wi-Fi
users, and the other for the private Wi-Fi users. Packets from
different SSID are marked with different VLAN ID. The VCPE should
know of the corresponding relation between the SSID and the VLAN ID,
so as to provide distinguished services to the publice users and the
private users. For instance, the private users should experience a
better QoS than the publice ones. In the meantime, the private users
and the public users may choose different SFC in the VCPE. All of
these different services are classified based on the VLAN ID.
Such deployment requirs the FPC client to support the following task:
1) The FPC client should be able to set specific VLAN to each SSID.
2) The FPC client should be able to set the QoS for specific VLAN ID.
3) The FPC client should be able to inform the agent the specific SFC
for each VLAN ID.
4) The FPC client should be capable of instruct the agent to handle
the MN hand-over of the public Wi-Fi users.
In the meantime, such deployment requirs the FPC agent to support the
following task:
1) The FPC agent should be able to set specific VLAN to each SSID
following the command from the client.
2) The FPC agent should be able to set the QoS for specific VLAN ID
following the command from the client.
3) The FPC agent should be able to direct the traffic for specific
VLAN ID to a certain SFC following the command of the client.
4) The FPC agent should be able to handle the MN hand-over of the
public Wi-Fi users.
7. Conclusion
In this document, the concept of VCPE is illustrated in detail. The In this document, the concept of VCPE is illustrated in detail. The
basic concept of VCPE is to shift the complicated functions from the basic concept of VCPE is to shift the complicated functions from the
pCPE at the customer side to the VCPE at the service provider side. pCPE at the customer side to the VCPE at the service provider side.
The motivation of such shifting can be concluded as reducing the The motivation of such shifting can be concluded as providing quick
Capex and Opex of the pCPE, and providing quick launched customer launched customer defined services, reducing the Capex and Opex of
defined services in the meantime. Three use cases are proposed for the pCPE, and simlify the maintainance of both pCPE and VCPE. A use
VCPE, including scenarios in the enterprise network, the residential cases of community Wi-Fi is proposed for VCPE, which is a typical
network and the IoT network. Two models are then discussed for the scenario for DMM. Three models are then discussed for the field
field deployment of VCPE. deployment of VCPE. And CP/DP interface is suggested to be utilized
in the deployment models.
7. Informative References 8. Informative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
Authors' Addresses Authors' Addresses
Qiao Fu (editor) Qiao Fu (editor)
China Mobile China Mobile
Xuanwumenxi Ave. No.32 Xuanwumenxi Ave. No.32
Beijing Beijing
China China
Email: fuqiao1@outlook.com Email: fuqiao1@outlook.com
Sri Gundavelli
Cisco
Email: sgundave@cisco.com
Hui Deng Hui Deng
China Mobile China Mobile
Xuanwumenxi Ave. No.32 Xuanwumenxi Ave. No.32
Beijing Beijing
China China
Email: denghui@chinamobile.com Email: denghui@chinamobile.com
 End of changes. 33 change blocks. 
212 lines changed or deleted 239 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/