01-02 Principle of FTTB and FTTC Data Plan

Superfast Copper Solution
FTTB and FTTC Configuration Guide 2 Principle of FTTB and FTTC Data Plan
2 Principle of FTTB and FTTC Data Plan
This topic describes principles of data plan for various FTTB and FTTC networking diagrams
in terms of device management, QoS, services, and security. The examples in this topic are
based on these principles to plan data.
2.1 Principle of Device Management Data Plan

The device management plan includes the channel management plan and the IP address plan.
2.2 Principle of QoS Planning
QoS planning for FTTB is in E2E mode, and it can be divided into the following policies:
traffic classification, marking, and scheduling, traffic monitoring, and DBA policies.
2.3 Principle of Internet Access Service Data Plan
The Internet access service plan mainly includes the plan of the VLAN and VLAN translation
policy in different network scenarios.
2.4 Principle of VoIP Service Data Plan
The VoIP service plan mainly includes the plan of VLANs and VLAN translation policy in
different network scenarios, and the plan of voice protocols.
2.5 Principle of IPTV Service Data Plan
The IPTV service plan mainly includes the plan of VLANs and VLAN translation policies in
different network scenarios, and the plan of IPTV services. IPTV services include multicast
service and VoD service. These two services have relationships and independence in VLAN
planning.
2.6 Principle of Security Data Plan
The security plan involves system security plan, user security plan, and service security plan.
Security policy ensures service security from different aspects.
2.1 Principle of Device Management Data Plan

The device management plan includes the channel management plan and the IP address plan.
Plan Device/Service Introduction
Management OLT Use a single S-VLAN as the equipment

channel management VLAN of the OLT and that of all
other equipment in the network.
Issue 02 (2019-05-08) Copyright © Huawei Technologies Co., Ltd. 4

Plan Device/Service Introduction
ONU/MDU/GE Use a single S-VLAN as the equipment

remote extended management VLAN of the ONU and that of all
subrack other equipment in the network.
HGW Use a single S-VLAN as the management

VLAN of the HGW that is managed by the
items.
Set a management VLAN for an entire network,
an OLT, a PON board, or a PON port for
identifying services and physical locations. It is
recommended that you set different HGW
management VLANs for the OLTs connected to
one SR to avoid an excessively large broadcast
domain of the SR and convergence switch.
IP address Device management It is recommended that you use private network

plan IP addresses as the management IP address of
the OLT and MDU for securing network
devices.
Internet access service A PC obtains a public network IP address using

PPPoE dialup for Internet access.
The HGW obtains a public network IP address
using PPPoE dialup.
A PC obtains a private network IP address using
DHCP.
VoIP service If an MDU has a built-in voice module, the

MDU functions as a DHCP client and obtains IP
addresses using DHCP. Multiple POTS ports on
the MDU share one public network IP address.
If an HGW has a built-in voice module, the
HGW obtains IP address using DHCP.
IPTV service An STB obtains a public network IP address

using DHCP and the subscriber can order
programs. The MDU is only used for transparent
transmission.
TR069 service For scenarios in which TR069 is used for

management, maintenance, and service
provisioning, the HGW functions as a DHCP
client, obtains a public network IP address using
DHCP, and connects to the TR069 server (ACS).
2.2 Principle of QoS Planning

QoS planning for FTTB is in E2E mode, and it can be divided into the following policies:
traffic classification, marking, and scheduling, traffic monitoring, and DBA policies.

Traffic Classification, Marking, and Scheduling Policies

Service 802.1p Queue OLT ONT Queue ID
Type Priority Scheduling Queue ID
Method (8 Queues) Supporting Supporting
Eight Four
Queues Queues
Management 6 PQ 6 6 3
service
VoIP service 5 PQ 5 5 2
IPTV 4 PQ 4 4 2
service
Internet 0 PQ 0 0 0
access
service
Note
l Different service packets are distinguished by different VLAN IDs. GEM ports are
mapped based on 802.1p priorities for the GPON system.
l Service priorities in this table are recommended values. The service priorities are
arranged according to the carriers' actual plan.
Traffic Monitoring and DBA Policies

Item Management Internet VoIP Service IPTV Service
Service Access
Service
T-CONT (used Use different T-CONTs for different services.

only in GPON
networks)
DBA type Select a suitable DBA type based on the service type. For example,
select Type1 for the management and voice services, and Type3 or
Type4 for the Internet access and IPTV services.
DBA Configure the DBA bandwidth according to the user's bandwidth

bandwidth package.
planning The assured bandwidth is the maximum bandwidth required by
management packets, VoIP, and IPTV upstream packets. The maximum
bandwidth is greater than or equal to the maximum bandwidth that users
apply.
Downstream No rate Configure rate No rate No rate

rate limitation limitation limitation by a limitation limitation
on the OLT traffic profile as
required.
[Remark 1]

Item Management Internet VoIP Service IPTV Service

Service Access
Service
Rate limitation Set ONU port rate limitation or xDSL line rate limitation as required.
on the ONU [Remark 1]
upstream port
Rate limitation Set ONU port rate limitation or xDSL line rate limitation as required.
on the ONU [Remark 1]
downstream
port
Remark 1: For details about the reference service bandwidth of each service for each user, see
Table 2-1.
Table 2-1 Reference service bandwidth of each service for each user
Service Upstrea Downstream Bandwidth Description
Type m Bandwidth
Bandwi
dth
Internet Determi Determined based Available bandwidth of Internet access

access ned on the tariff package. service = Committed bandwidth of the tariff
service based on package - VoIP bandwidth - IPTV
the tariff bandwidth
package.

Service Upstrea Downstream Bandwidth Description

Type m Bandwidth
Bandwi
dth
VoIP 200 200 kbit/s The VoIP service has symmetrical upstream
service kbit/s (Bandwidth of 200 and downstream bandwidth. The actual
(Bandwi kbit/s meets the bandwidth is related to the coding and
dth of requirements of decoding formats used by both
200 most application communication parties. (Assume that each
kbit/s scenarios. For G.711 user uses 2 POTS ports.)
meets 10 ms packetization,
the the required
requirem bandwidth is
ents of approximately 240
most kbit/s.)
applicati
on
scenario
s. For G.
711 10
ms
packetiz
ation,
the
required
bandwid
th is
approxi
mately
240
kbit/s.)
IPTV N/A 2.5 Mbit/s per The IPTV service mainly occupies the
service channel downstream bandwidth. The actual
(commo bandwidth depends on the coding format
n used by the IPTV headend device, the
program picture in picture information, and other
) factors. In addition, 10% bandwidth burst
traffic and the number of programs that can
IPTV N/A 9.7 Mbit/s per be concurrently watched by one user (in the
service channel case of multi-STB access) are taken in to
(high consideration.
definitio
n The upstream bandwidth is mainly used for
program IGMP packet transmission, which requires
) less bandwidth. Therefore, the occupied
upstream bandwidth can be neglected.

The preceding bandwidth for each service is obtained based on historical statistics in most
scenarios, which is for reference only. The bandwidth for a device does not completely
depend on the access device, and is not a fixed value. For example, the IPTV service
bandwidth depends on the IPTV headend service. Therefore, the carrier needs to obtain the
required bandwidth range from the supplier of the IPTV headend device.
Note
l Rate limitation on the BRAS or SR is recommended. OLTs and ONUs do not limit rates
on service flows. If the BRAS does not support rate limitation, OLTs can limit rates on
service flows using traffic profiles.
l The sum of assured bandwidth of all ONUs under a PON port and the fixed bandwidth of
OMCI management channel must be smaller than the GPON upstream bandwidth. Some
bandwidth must be reserved for future service expansion.
2.3 Principle of Internet Access Service Data Plan

The Internet access service plan mainly includes the plan of the VLAN and VLAN translation
policy in different network scenarios.
Note
This configuration guide is written based on solution scenarios, covering the E2E service
configuration process for the OLT, ONU, and HGW.
This guide provides guidance for service configuration in fiber to the building (FTTB) and
fiber to the curb (FTTC) involving the OLT and ONUs of different models.
l OLTs are required in all FTTB and FTTC scenarios. When reading this guide, OLT
customers can select required information based on scenarios.
l ONUs used in different FTTB and FTTC scenarios may be different. When reading this
guide, ONU customers can select required information based on actual network planning
or ONU application scenarios.
VLAN Planning and VLAN Translation Policy on PON Networks

Application VLAN Plan VLAN Translation
Scenario
ONU OLT
FTTB networking Two-tagged The inner C-VLAN is The OLT translates

(without HGWs) VLAN (S-VLAN mapped based on user VLANs and adds an
+C-VLAN) ports to ensure that S-VLAN. C'-VLAN
ONUs under the same <-> S-VLAN + C-
PON board do not VLAN
have the same C-
VLAN.

Application VLAN Plan VLAN Translation

Scenario
ONU OLT
FTTB/FTTC+HGW HGWs (LAN

networking (ONU upstream
providing the VoIP transmission)
service) l Untagged
FTTB/FTTC+HGW upstream packets
networking (HGW of HGWs: ONUs
providing the VoIP map C-VLANs
service) based on user
ports.
l Tagged upstream
packets of HGWs:
ONUs translate
user VLANs to C'-
VLANs.
[Remark 1]
HGWs (xDSL
upstream
transmission): ONUs
translate PVCs to C'-
VLANs.
Note
l To ensure traceability of users and finer-grained QoS control and management of users
and services, plan per user per service per VLAN (PUPSPV) for the Internet access
service. Considering OLT capacity and VLAN scalability, use dual VLANs (S-VLAN
+C-VLAN) on the OLT to differentiate users for the Internet access service.
l The outer S-VLAN, which identifies services and physical location, can be allocated
based on the OLT, PON board (recommended), or PON port (recommended). The inner
C-VLAN identifies users. User C-VLANs are unique in one S-VLAN.
NOTE
It is recommended that you associate C-VLAN IDs with PON ports, optical splitters, and ONU
ports to ensure C-VLAN uniqueness and to facilitate location. Example: C-VLAN ID = 256 x
PON port ID + 32 x Split ratio x (Optical port ID - 1) + ONU port ID + 1
l It is recommended that you use stacking VLANs as S-VLANs so that security features,
such as PPPoE+/option 82, anti-MAC attack, and anti-MAC spoofing can be easily
deployed.

VLAN Planning and VLAN Translation Policy on Ethernet Cascading Networks

Application VLAN VLAN Translation
Scenario Plan
MDU/GE Remote Extended Subrack OLT/
Master
Subrac
k
FTTB or FTTC Two-tag Without HGWs: The outer S-VLAN is The

Ethernet cascading VLAN planned based on MDUs and the inner C- OLT
(MDUs serving as solution VLAN identifies a user. Ensure that the C- transmit
independent nodes) VLANs of users using the same S-VLAN do s
not repeat each other. packets
LAN access using HGWs: transpar
ently.
l Untagged upstream packets of HGWs:
MDUs map C-VLANs based on user
ports and add S-VLANs to packets.
l Tagged upstream packets of HGWs:
MDUs translate user VLANs to C-
VLANs (user VLAN <-> C-VLAN) and
add S-VLANs to packets.
xDSL access using HGWs:
l Asynchronous transfer mode (ATM)
upstream transmission: MDUs translate
PVCs to C-VLANs (PVC <-> C-VLAN)
and add S-VLANs to packets. Ensure
that the C-VLANs of users using the
same S-VLAN do not repeat each other.
l Packet transfer mode (PTM) upstream
transmission: Untagged upstream packets
of HGWs: MDUs map C-VLANs based
on user ports and add S-VLANs to
packets. Tagged upstream packets of
HGWs: MDUs translate user VLANs to
C-VLANs (user VLAN <-> C-VLAN)
and add S-VLANs to packets. Ensure
same S-VLAN do not repeat each other.


Scenario Plan
MDU/GE Remote Extended Subrack OLT/
Master
Subrac
k
FTTB and FTTC l Without HGWs: The extended subrack The

Ethernet cascading maps inner C-VLANs based on user master
(centralized ports and adds S-VLANs to packets. subrack
management for GE Ensure that the C-VLANs of users using transmit
remote extended the same S-VLAN do not repeat each s
subracks) other. packets
l xDSL access using HGWs: transpar
ently.
– ATM upstream transmission: The
extended subrack translates PVCs to
C-VLANs (PVC <-> C-VLAN) and
adds S-VLANs to packets. Ensure
same S-VLAN do not repeat each
other.
– PTM upstream transmission:
Untagged upstream packets of
HGWs: The extended subrack maps
C-VLANs based on user ports and
adds S-VLANs to packets. User-
VLAN-tagged upstream packets of
HGWs: The extended subrack
translates user VLANs to C-VLANs
(user VLAN <-> C-VLAN) and adds
S-VLANs to packets. Ensure that the
C-VLANs of users using the same S-
VLAN do not repeat each other.
2.4 Principle of VoIP Service Data Plan

The VoIP service plan mainly includes the plan of VLANs and VLAN translation policy in
different network scenarios, and the plan of voice protocols.
Note

VLAN Planning and VLAN Translation Policy on PON Networks

Application VLAN VLAN Translation Remarks
Scenario Plan
ONU OLT
FTTB Single- ONUs provide Transparently -

networking tagged the VoIP service transmits packets.
(without VLAN and use the same
HGWs) S-VLAN.
FTTB+HGW Single- ONUs provide Transparently This solution is

networking tagged the VoIP service transmits packets. recommended.
(ONU VLAN and use the same
providing the S-VLAN.
VoIP service)
Double- ONUs provide The OLT adds This solution is
tagged the VoIP service one S-VLAN tag: used only when
VLAN (S- and use the same C-VLAN <-> S- double-tagged
VLAN+C- C-VLAN. VLAN+C- VLANs are
VLAN) VLAN. planned.
FTTB+HGW Single- When packets Transparently This solution is

networking tagged sent from the transmits packets. recommended.
(HGW VLAN HGW using LAN
providing the upstream
VoIP service) Double- transmission The OLT adds This solution is
tagged carries user one S-VLAN tag: used only when
VLAN (S- VLANs, the C-VLAN <-> S- double-tagged
VLAN+C- ONU translates VLAN+C- VLANs are
VLAN) user VLANs to VLAN. planned.
C-VLANs.
HGWs (xDSL
upstream
transmission):
ONUs translate
PVCs to C'-
VLANs.
Note
l The VoIP service is a closed service self-operated by carriers. The single-tagged S-
VLAN is the mainstream application and is recommended.
l Set an S-VLAN for an entire network, an OLT, a PON board, or a PON port for
identifying services and physical locations. It is recommended that you set different VoIP
VLANs for the OLTs connected to one VoIP SR to avoid an excessively large broadcast
domain of the VoIP SR and convergence switch.

l The outer S-VLAN, which identifies services and physical locations, can be allocated
based on the OLT, PON board, or PON port. The inner C-VLAN identifies services or
users.
VLAN Planning and VLAN Translation Policy on Ethernet Cascading Networks

Scenario Plan
MDU/GE Remote OLT/Master Subrack
Extended Subrack
FTTB or FTTC One-tag Without HGWs and with The OLT transmits
Ethernet cascading VLAN voice services provided packets transparently.
(MDUs serving as solution by the MDU: Each MDU
independent nodes) uses the same S-VLAN
for its voice users.
LAN access with voice
services provided by
HGWs: MDUs translate
user VLANs to C-
VLANs.
xDSL access with voice
services provided by
HGWs:
l ATM upstream
transmission: MDUs
translate PVCs to C-
VLANs (PVC <-> C-
VLAN).
l PTM upstream
transmission:
Untagged upstream
packets of HGWs:
MDUs map C-VLANs
based on user ports.
User-VLAN-tagged
upstream packets of
HGWs: MDUs
translate user VLANs
to C-VLANs (user
VLAN <-> C-VLAN).


Scenario Plan
MDU/GE Remote OLT/Master Subrack
Extended Subrack
FTTB or FTTC xDSL access with voice The master subrack

Ethernet cascading services provided by transmits packets
(centralized HGWs: transparently.
management for GE l ATM upstream
remote extended transmission: The
subracks) extended subrack
translates PVCs to C-
VLANs (PVC <-> C-
VLAN).
l PTM upstream
transmission:
Untagged upstream
packets of HGWs: The
extended subrack
maps C-VLANs based
on user ports. User-
VLAN-tagged
upstream packets of
HGWs: The extended
subrack translates user
VLANs to C-VLANs
(user VLAN <-> C-
VLAN).
VoIP data plan based on H.248 or SIP

Item Remarks
MG Media Media and Upstream VLANs of the VoIP service

interface/SI and signaling
P interface signalin upstream VLAN
data g
NOTE paramet Media and Upstream ports of the VoIP service
(Must be ers signaling
the same as upstream port
that on the
MGC or Media IP address Separating media streams from signaling
IMS core and signaling IP streams
network address
device.)
Default IP address Next hop IP address from an ONU/HGW to
of the MG an MGC/IMS
MG interface/SIP interface ID -
Signaling port ID Choose the transmission mode according to

the requirement on the MGC/IMS side.

Item Remarks
IP address of primary MGC When dual homing is not configured, the

(H.248)/IP address of primary parameters of the primary MGC need to be
IMS device (SIP) configured. When dual homing is
configured, the IP address and the port ID
Port ID of primary MGC of the secondary MGC must also be
(H248)/port ID of primary configured.
IMS device (SIP)
Codec mode The codec mode is selected according to

the requirements on the MGC/IMS side.
Generally, the text mode is used.
Transmission mode The transmission mode is selected

according to the requirements on the
MGC/IMS side. Generally, UDP is used.
Home domain name (SIP) -
Profile index (SIP) -
H.248 version used for V1, V2 or V3 (default value). The interface

starting negotiation may fail to be registered because some
softswitches do not support V3.
VoIP user Phone number H.248: The phone numbers allocated by the
configuratio MGC need to be determined, and the
n data paging numbers for users' emergency
standalone need to be planned if the
emergency standalone function is provided.
SIP: The phone number that the IMS core
network device allocates to the user must
be configured.
TID (H.248) If the TID template with which the PSTN

user is bound does not support terminal
layering, this parameter needs to be
configured.
User priority According to the service requirements, user

priorities must be specified. The user
priorities include the following:
l cat1: government1 (category 1
government users)
l cat2: government2 (category 2
government users)
l cat3: normal (common users). This is
the default value.

Item Remarks
User type According to the service requirements, user

type needs to be specified. The user type
includes the following:
l DEL: direct exchange lines (default)
l ECPBX: earth calling PBX
l LCPBX: loop calling PBX
l PayPhone: pay phone
Common System parameter The system parameters, including the

Parameter international version flag and message
waiting indication (MWI) mode, need to be
configured according to local standards to
ensure that the response of the user terminal
complies with the local standards.
International parameters The attributes such as the upper and lower

thresholds of the flash-hooking duration
need to be configured according to the local
standards to ensure that the response of the
user terminal complies with the local
standards.
PSTN port attributes If the PSTN port needs to support the

polarity reversal accounting, the PSTN port
needs to be configured to support the
polarity reversal pulse. Other attributes do
not need to be modified if there is no
special requirement.
Ringing current attributes When the attributes of ring current are

changed, ring volume is changed. This
parameter needs to be modified according
to the local standard only when the default
ring current attribute does not comply with
the local standard.
2.5 Principle of IPTV Service Data Plan

The IPTV service plan mainly includes the plan of VLANs and VLAN translation policies in
different network scenarios, and the plan of IPTV services. IPTV services include multicast
service and VoD service. These two services have relationships and independence in VLAN
planning.
Note


VLAN and VLAN translation policy

Applicatio Servic VLA VLAN Translation Remarks
n Scenario e N
Type Plan ONU OLT
Scenario 1: Multic One- 1. The multicast l Upstream This solution is

FTTB ast tagged VLAN (M- IGMP: The recommended
+HGW service VLA VLAN) of the OLT because carriers
networking N HGW is performs will define a
(ONU different from IGMP proxy unified M-
providing the network-side to terminate VLAN on the
the VoIP M-VLAN. IGMP HGW.
service) l Upstream packets
and IGMP: The transmitted
ONU from the user
Scenario 2: side and
FTTB performs
IGMP proxy encapsulate
+HGW IGMP
networking to terminate
IGMP packets
(HGW transmitted
providing packets
transmitted by network-
the VoIP side M-
service) from the user
side and VLANs.
encapsulate l The OLT
IGMP replicates
packets multicast
transmitted packets
by network- based on
side M- PON ports
VLANs. with M-
l Downstream VLANs
multicast unchanged.
service flows:
The ONU
replicates
multicast
packets based
on user ports
and
multicasts
downstream
multicast
packets
across
VLANs: user
VLAN <->
M-VLAN


n Scenario e N
Type Plan ONU OLT
Multic One- VLAN Transparently This solution is

ast tagged translation transmits recommended.
VoD VLA policy: packets. The PSPV mode
service N l When is recommended
packets sent for the VoD
from the service because
HGW using the service
LAN requires fewer
upstream VLANs.
transmission
carries user
VLANs, the
ONU
translates
user VLANs
to C-VLANs.
l When
packets are
sent from the
HGW using
xDSL
upstream
transmission,
the ONU
translates
PVCs to C-
VLANs.


n Scenario e N
Type Plan ONU OLT
FTTB or Multic One- l Upstream l Upstream This solution is

FTTC ast tag IGMP IGMP recommended.
Ethernet service VLA packets: The packets: The
cascading N MDU OLT
(MDUs soluti performs performs
serving as on IGMP proxy IGMP proxy
independent to terminate to terminate
nodes) IGMP IGMP
packets packets
transmitted transmitted
from the user from the user
side, side,
encapsulate encapsulate
the packets the packets
with an M- with an M-
VLAN tag on VLAN tag on
the network the network
side, and side, and
send the send the
packets packets
upstream. upstream.
l Downstream l Downstream
multicast multicast
service flows: service
The MDU flows: The
replicates OLT
multicast replicates
packets based multicast
on user ports packets
and based on GE
multicasts ports with M-
downstream VLANs
packets unchanged.
among M-
VLANs.


n Scenario e N
Type Plan ONU OLT
Multic One- HGWs (LAN The OLT This solution is

ast tag upstream transmits recommended.
VoD VLA transmission): packets
service N MDUs translate transparently.
soluti user VLANs to
on C-VLANs (user
VLAN <-> C-
VLAN).
HGWs (xDSL
upstream
transmission):
l ATM
upstream
transmission:
MDUs
translate
PVCs to C-
VLANs
(PVC <-> C-
VLAN).
l PTM
upstream
transmission:
Untagged
upstream
packets of
HGWs:
MDUs map
C-VLANs
based on user
ports. User-
VLAN-
tagged
upstream
packets of
HGWs:
MDUs
translate user
VLANs to C-
VLANs (user
VLAN <->
C-VLAN).


n Scenario e N
Type Plan ONU OLT
FTTB or Multic One- HGWs (xDSL l Upstream This solution is

FTTC ast tag upstream IGMP recommended.
Ethernet service VLA transmission) packets: The
cascading N when M-VLANs master
(centralized soluti on HGW side subrack
management on and network side performs
for GE are different: IGMP proxy
remote l Upstream to terminate
extended IGMP IGMP
subracks) packets: The packets
extended transparently
subrack transmitted
performs from the
IGMP proxy extending
to terminate board and
IGMP reported by
packets the extended
transmitted subrack,
from the user encapsulate
side, the packets
encapsulate with an M-
the packets VLAN tag on
with an M- the network
VLAN tag on side, and
the network send the
side, and packets to the
send the upper-layer
packets to the network.
extending l Downstream
board. multicast
l Downstream service
multicast flows: The
service flows: control board
The extended in the master
subrack subrack
replicates replicates
multicast multicast
packets based packets
on user ports, based on
and Ethernet
multicasts the extending
packets boards, and
among M- the Ethernet
VLANs (user extending
VLAN <- M- boards
VLAN). replicate
multicast
packets


n Scenario e N
Type Plan ONU OLT
based on GE
ports with M-
VLANs
unchanged.
Multic One- HGWs (xDSL The master This solution is

ast tag upstream subrack recommended.
VoD VLA transmission): transmits
service N l ATM packets
soluti upstream transparently.
on transmission:
The extended
subrack
translates
PVCs to C-
VLANs
(PVC <-> C-
VLAN).
l PTM
upstream
transmission:
Untagged
upstream
packets of
HGWs: The
extended
subrack maps
C-VLANs
based on user
ports. User-
VLAN-
tagged
upstream
packets of
HGWs: The
extended
subrack
translates
user VLANs
to C-VLANs
(user VLAN
<-> C-
VLAN).
Note
l IPTV service is a closed service self-operated by carriers, and single—tagged S-VLAN
is recommended.

l The same S-VLAN or different S-VLANs can be used as the M-VLAN and VoD VLAN.
It is recommended that you use different S-VLANs as M-VLAN and VoD VLAN so that
the upper-layer device can easily differentiate the BTV service and VoD service.
l S-VLANs of VoD service can identify services and physical locations based on an entire
network or an OLT. It is recommended that you set different VoD VLANs for the OLTs
connected to one IPTV SR to avoid an excessively large broadcast domain of the SR and
convergence switch.
Data plan for multicast service

Data Item Remarks
Multicast protocol The OLT and ONU generally use IGMP proxy. The ONT or
HGW generally uses IGMP snooping.
IGMP version The compatibility policies of the IGMP version on access

equipment distinguish between the network side and the user
side.
1. In normal application scenarios, the device is usually the
active initiating party. The IGMP version on the multicast
router can be seamlessly degraded without packet loss.
2. The terminals are always the active initiating party and can
be seamlessly degraded without packet loss.
The recommended versions are as follows:
l If the network-side version is V2, the recommended version
for the access equipment is V2.
l If the network-side version is V3, the recommended version
for the access equipment is V2 or V3.
l If the user-side version is V2, the recommended version for
the access equipment is V2 or V3.
l If the user-side version is V3, the recommended version for
the access equipment is V3.
Multicast program Static configuration is recommended. The OLT can also

generate a multicast program library. In other words, the OLT
dynamically generates a program list according to the programs
requested by users. In this mode, the program list does not need
to be configured or maintained; however, the functions such as
program management, user multicast bandwidth management,
program preview, and program prejoin are not supported.
Multicast preview Default

profile
Multicast fast leave Enabling this function is recommended. It reduced the exchange
of IGMP packets, saving the bandwidth resources.

2.6 Principle of Security Data Plan

The security plan involves system security plan, user security plan, and service security plan.
Security policy ensures service security from different aspects.
NOTE
l The device provides complete security measures, but not all security measures need to be deployed. Only
the security measures that meet the following requirements need to be deployed:
l The security measures can be used on the live network.
l The security measures are easy to deploy.
l The security measures are effective.
l Different ONUs support different security features. Select the security feature recommended in this topic
according to actual ONU capabilities.
System Security
Security Solution Description and Usage
Vulnerability Suggestion
DoS attack Enable the anti-DoS-attack After the anti-DoS-attack function is

function for OLT and enabled, control packets are
MDU. monitored and those exceeding the
number threshold are discarded.
Use this solution for new site
deployment.
IP attack Enable the anti-IP-attack After the anti-IP-attack function is

function for OLT and enabled, a device discards the IP
MDU. packets received from the user side
whose destination IP address is the
IP address of the device, and
therefore the system is protected.
deployment.

User Security
MAC spoofing Enable the anti-MAC- After anti-MAC-duplicate is

duplicate function for OLT enabled, the system records the first
and MDU. MAC address learned from the port
and binds the MAC address to the
port and VLAN. If receiving packets
sent from the host that has the same
MAC address with the port, the
system discards the packets directly.
In this case, it can prevent users from
forging MAC addresses to perform
malicious attacks.
deployment.
MAC attack Enable the anti-MAC After anti-MAC spoofing is enabled,

spoofing function for OLT the system can prevent users from
and MDU. forging IP addresses to perform
malicious attacks.
deployment.
IP spoofing Enable the anti-IP spoofing After anti-IP spoofing is enabled, the
function for MDU. system can prevent users from
forging IP addresses to perform
malicious attacks.
deployment.

Service Security
Unauthorized DHCP option 82 is enabled In the DHCP option 82 mode, user's

broadband access of on OLT and MDU, and the physical location is added to the
small enterprises BRAS implements user option 82 field carried in the DHCP
(IPoE) authentication based on the request packet initiated by a user.
RAIO information. The physical location, used for user
authentication on the upper-layer
authentication server, can help
implement the following functions:
l The DHCP relay forwards DHCP
response packets to devices with
specified CID and RID.
l Prevents DHCP address
exhaustion.
l Achieves static allocation of
DHCP addresses.
l Implements anti-IP spoofing.
l Implements anti-user ID
spoofing.
l Implements anti-MAC spoofing.
Use this solution for the DHCP
Internet access service.
Broadband access of PPPoE+ (PITP) is enabled The BRAS responds to request

residential users on OLT and MDU, and the packets of users with specified CID
(PPPoE), user BRAS implements user and RID. In this way, the following
account theft/ authentication based on functions are implemented:
borrowing binding of the RAIO l Prevents IP address exhaustion.
information to the user
account. l Implements anti-IP spoofing.
l Implements anti-user ID
spoofing.
l Implements anti-MAC spoofing.
Use this solution for the PPPoE
Internet access service.

01-02 Principle of FTTB and FTTC Data Plan

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

01-02 Principle of FTTB and FTTC Data Plan

Uploaded by

Copyright:

Available Formats

Superfast Copper Solution

2 Principle of FTTB and FTTC Data Plan

2.1 Principle of Device Management Data Plan

2.1 Principle of Device Management Data Plan

Plan Device/Service Introduction

Management OLT Use a single S-VLAN as the equipment

Issue 02 (2019-05-08) Copyright © Huawei Technologies Co., Ltd. 4

Plan Device/Service Introduction

ONU/MDU/GE Use a single S-VLAN as the equipment

HGW Use a single S-VLAN as the management

IP address Device management It is recommended that you use private network

Internet access service A PC obtains a public network IP address using

VoIP service If an MDU has a built-in voice module, the

IPTV service An STB obtains a public network IP address

TR069 service For scenarios in which TR069 is used for

2.2 Principle of QoS Planning

Issue 02 (2019-05-08) Copyright © Huawei Technologies Co., Ltd. 5

Traffic Classification, Marking, and Scheduling Policies

Traffic Monitoring and DBA Policies

T-CONT (used Use different T-CONTs for different services.

DBA Configure the DBA bandwidth according to the user's bandwidth

Downstream No rate Configure rate No rate No rate

Issue 02 (2019-05-08) Copyright © Huawei Technologies Co., Ltd. 6

Item Management Internet VoIP Service IPTV Service

Internet Determi Determined based Available bandwidth of Internet access

Issue 02 (2019-05-08) Copyright © Huawei Technologies Co., Ltd. 7

Service Upstrea Downstream Bandwidth Description

Issue 02 (2019-05-08) Copyright © Huawei Technologies Co., Ltd. 8

2.3 Principle of Internet Access Service Data Plan

VLAN Planning and VLAN Translation Policy on PON Networks

FTTB networking Two-tagged The inner C-VLAN is The OLT translates

Issue 02 (2019-05-08) Copyright © Huawei Technologies Co., Ltd. 9

Application VLAN Plan VLAN Translation

FTTB/FTTC+HGW HGWs (LAN

Issue 02 (2019-05-08) Copyright © Huawei Technologies Co., Ltd. 10

VLAN Planning and VLAN Translation Policy on Ethernet Cascading Networks

FTTB or FTTC Two-tag Without HGWs: The outer S-VLAN is The

Issue 02 (2019-05-08) Copyright © Huawei Technologies Co., Ltd. 11

Application VLAN VLAN Translation

FTTB and FTTC l Without HGWs: The extended subrack The

2.4 Principle of VoIP Service Data Plan

Issue 02 (2019-05-08) Copyright © Huawei Technologies Co., Ltd. 12

VLAN Planning and VLAN Translation Policy on PON Networks

FTTB Single- ONUs provide Transparently -

FTTB+HGW Single- ONUs provide Transparently This solution is

FTTB+HGW Single- When packets Transparently This solution is

Issue 02 (2019-05-08) Copyright © Huawei Technologies Co., Ltd. 13

VLAN Planning and VLAN Translation Policy on Ethernet Cascading Networks

Issue 02 (2019-05-08) Copyright © Huawei Technologies Co., Ltd. 14

Application VLAN VLAN Translation

FTTB or FTTC xDSL access with voice The master subrack

VoIP data plan based on H.248 or SIP

MG Media Media and Upstream VLANs of the VoIP service

Signaling port ID Choose the transmission mode according to

Issue 02 (2019-05-08) Copyright © Huawei Technologies Co., Ltd. 15

IP address of primary MGC When dual homing is not configured, the

Codec mode The codec mode is selected according to

Transmission mode The transmission mode is selected

Home domain name (SIP) -

Profile index (SIP) -

H.248 version used for V1, V2 or V3 (default value). The interface

TID (H.248) If the TID template with which the PSTN

User priority According to the service requirements, user

Issue 02 (2019-05-08) Copyright © Huawei Technologies Co., Ltd. 16