About Service Profiles
A Gigabit passive optical network (GPON) topology consists of an optical line termination (OLT) device that is connected to multiple optical network terminals (ONTs) through an optical splitter.
Downstream traffic is the traffic flowing from an OLT to a specific ONT. The OLT receives and transmits the Ethernet services to the GPON Encapsulation Method (GEM) ports. Each GEM port is identified by a unique ID called port ID. The GEM ports encapsulate the Ethernet services into GEM frames, add the port ID, and broadcast the GEM frames to all the connected ONTs. The ONT then filters the GEM frames based on the port ID, decapsulates the GEM frames to Ethernet services, and transmits the services to end users.
Upstream traffic is the traffic flowing from all the ONTs to the OLT. Because all the ONTs share the same transmission channel, only one ONT is allocated the bandwidth to transmit data at a given point in time. Bandwidth allocation is based on the type of transmission container (T-CONT). A T-CONT is a buffer for transmitting the upstream service flow in the GPON system, and is identified by an allocation ID. The ONT encapsulates the Ethernet services to the GEM frames, and buffers the GEM frames into the T-CONT that is waiting for the uplink data forwarding time. Multiple GEM ports are multiplexed into a T-CONT. The OLT receives the GEM frames through the GEM ports, decapsulates the GEM frames to Ethernet services, and transmits the services to the access layer device.
Service profile deployment allows you to configure various profile templates. The following table lists the various profile templates that you can configure.
Configuration Task |
Type of Traffic |
Required or Optional |
---|---|---|
VLAN profiles |
Upstream and downstream traffic |
Required |
DBA profiles |
Upstream traffic only |
Required |
Uplink traffic profiles |
Upstream traffic only |
Optional |
Downlink traffic profile |
Downstream traffic only |
Optional |
Line profiles |
Upstream traffic only |
Required |
Rule profiles |
Upstream traffic only |
Required |
Unique profiles |
Upstream traffic only |
Optional |
You can specify a default service profile and bind multiple service profiles to a rule. The device type configuration in multiple service profiles vary. After an ONT is registered, the OLT checks the service profiles based on the device type reported by the ONT. If the device type in the service profile matches the device type reported by the ONT, the OLT sends the service profile to the ONT. If the device type does not match, the OLT checks whether the default service profile exists and sends the default service profile to the ONT.
About VLAN Profiles
You can configure VLAN application modes to the traffic flow between the OLT and the ONT. The OLT supports both the N:1 and 1:1 VLAN application modes for flexible and variable VLAN service applications.
The OLT implements GEM port-based VLAN transformation rules through the VLAN profile template configuration. A VLAN profile template can be configured with the following transformation rules:
-
Add rule: This rule is used to configure VLAN stacking rules. After a rule is configured and applied, in the upstream direction, the OLT adds an outer-VLAN tag to the inner-VLAN tag of the service flow originating from the ONT and carried by the corresponding GEM port. In the downstream direction, the OLT strips the ingress traffic outer-VLAN tag from the uplink device and forwards it to the ONT through the corresponding GEM port. Each VLAN profile template can be configured with 32 VLAN stacking rules, but the inner-VLAN tag (a combination of VLAN ID and priority) should be unique in each rule. After the template is configured, it is referenced by the GEM port configured in the line profile template or unique profile template.
-
Add default rule: This rule is used to configure VLAN tagging rules. After a rule is configured and applied, in the upstream direction, the OLT adds a default VLAN tag to the untagged service flow originating from the ONT and carried by the corresponding GEM port. In the downstream direction, the OLT strips the default VLAN of the service flow from the uplink port and forwards it to the ONT through the corresponding GEM port. Only one default VLAN tag rule can be configured for each VLAN profile template. After the template is configured, it is referenced by the GEM port configured in the line profile template or unique profile template.
-
Translate rule: This rule is used to configure VLAN translation rules. After a rule is configured and applied, in the upstream direction, the OLT converts the old-VLAN tag to the new-VLAN tag of the service flow originating from the ONT and carried by the corresponding GEM port. In the downstream direction, the OLT converts the new-VLAN tag of the service flow to the old-VLAN tag and forwards it to the ONT through the corresponding GEM port. Each VLAN template can be configured with 32 VLAN conversion rules, but the old-VLAN tag (a combination of VLAN ID and priority) should be unique in each rule. After the template is configured, it is referenced by the GEM port configured in the line profile template or unique profile template.
After the VLAN template is referenced, the VLAN translation and the stacking rules are compared for an upstream packet with a VLAN tag. The VLAN tag rule is compared for an upstream packet without a VLAN tag from an ONT GEM port. The packet is discarded if there is no corresponding matching rule.
About DBA Profiles
For upstream traffic, only one ONT is allowed to transmit data at a given point in time because all the ONTs share the same transmission channel. The upstream traffic is handled by scheduling a dynamic bandwidth assignment (DBA) profile.
Bandwidth allocation is based on the configured T-CONT for transmitting upstream traffic. Each T-CONT type provides a certain Quality of Service (QoS).
The following table lists the different types of T-CONT, the relationship between each type of T-CONT, and bandwidth allocation and service application for each T-CONT type
T-CONT Type |
Traffic Descriptor Component |
Description |
---|---|---|
Type 1 |
Fixed bandwidth |
Provides only fixed bandwidth. Configured for carrying traffic that is sensitive to delay or jitter, for example, VoIP services. |
Type 2 |
Assured bandwidth |
Provides only assured bandwidth. Configured for carrying on or off type traffic without strict delay and jitter requirements, for example, IPTV multicast services. |
Type 3 |
Assured bandwidth Maximum bandwidth |
Provides both assured bandwidth as well as nonassured bandwidth. Configured for carrying variable-rate burst traffic. |
Type 4 |
Maximum bandwidth |
Provides best-effort bandwidth. Configured for carrying variable-rate burst traffic that does not exhibit delay sensitivity, for example, internet data services. |
Type 5 |
Fixed bandwidth Assured bandwidth Maximum bandwidth |
Provides a combination of fixed, assured, and best-effort bandwidth. Configured for carrying general traffic. |
The following are the characteristics of aDBA profile:
-
In all types of T_CONT, bandwidth allocation is prioritized in the following order:
-
Fixed bandwidth
-
Assured bandwidth
-
Nonassured bandwidth
-
Best-effort bandwidth
-
-
Fixed bandwidth assured bandwidth together comprise the basic bandwidth. The sum of the fixed bandwidth and the assured bandwidth of all T-CONT configurations under the same PON port cannot exceed the total uplink bandwidth of the corresponding PON port.
-
Nonassured and best-effort bandwidth together comprise the additional bandwidth.
About Uplink Traffic Profiles
Uplink traffic flow is scheduled based on the GEM port. The following are the two types of scheduling modes:
-
Flow control mode: The flow is controlled by the GEM port rate limitation configured on the GEM port.
-
Priority queue scheduling mode: The flow is controlled by the GEM port priority.
The uplink traffic profile configuration is applied only if the ONT supports it. After the uplink traffic profile template is applied, it is referenced based on the GEM port in the line profile template or unique profile template. The GEM port traffic is scheduled by the ONT based on the uplink traffic profile configuration.
About Downlink Traffic Profiles
Downlink traffic flow is scheduled using the flow control mode.
Only one downstream traffic flow schedule can be configured in a GEM port. After the downlink traffic profile template is applied, it is referenced based on the GEM port in the line profile template or unique profile template.
About Line Profiles
A line profile allows you to map the ONT service flow to the OLT. The following are the parameters required to create a line profile:
-
Device type
Define a device type. Each connected ONT must have its own specific device type name. When the ONT is registered to go online, the OLT delivers a specific line profile template configuration according to the device type reported. In the line profile configuration, the device type must be configured first. The device type cannot be modified after the line profile is configured. The entire line profile configuration must be removed when the device type is deleted or modified.
-
T-CONT
Create a T-CONT and configure the binding relationship between the T-CONT and the DBA profile template.
-
GEM port
Create a GEM port and configure the GEM port parameters, as detailed below:
-
Configure a GEM port and map it to the T-CONT.
-
Map the GEM port to the VLAN profile configuration. The OLT must support the GEM port-based VLAN translate rule.
-
Map the GEM port to the uplink traffic profile. The upstream traffic scheduling parameters are configured in the upstream traffic profile.
-
Map the GEM port to the downlink traffic profile. The downlink bandwidth rate limit configured in the downlink traffic profile is implemented by the OLT ACL resources.
-
-
Mapping rule
Configure mapping rules between the GEM port and user interface data flows, as detailed below:
-
A mapping mode is required to configure mapping between the GEM port and the data flowing from the user interface. The following are the various mapping modes available:
-
Port
-
VLAN ID
-
802.1P priority
-
Port + VLAN ID
-
Port + 802.1P priority
-
VLAN ID+802.1P priority
-
Port+VLAN ID+802.1P priority
Note
Only one mapping mode can be configured for the same service profile. The default mapping mode is based on VLAN ID mapping.
-
-
A mapping table establishes the mapping relationship between the GEM port and the upstream data flowing into the ONT user interface. After the mapping relationship is established, the corresponding GEM port can be used to carry the service.
Note
The parameters of the mapping mode must be the same as those configured in the mapping table configuration.
-
-
Flow rule
Configure flow rules, as detailed below:
-
Service flows are distinguished by the ONT based on the packet Ethernet type and the port the packets are received into.
Packets that receive ports are classified into the following types:
-
Ethernet interface (Eth): The Ethernet interface refers to the LAN port of the ONT.
-
Virtual Ethernet interface (VEIP): The virtual Ethernet interface refers to the WAN interface of the ONT.
-
Voice IP interface (IPhost): The voice IP interface is applicable to ONTs that supports voice service.
-
-
The VLAN tag processing policy of the ONT flow. Based on the flow rules configured, the ONT applies the VLAN processing rule on the service flow. The following are the VLAN tag processes:
-
Transparent
-
Default
-
Keep
-
Translate
-
Add
-
-
-
Rule profile
Configure a rule profile. Configure a rule profile, as detailed below:
-
Configure the ONT authentication rule and bind the line profile to the related ONTs. An OLT supports the following authentication modes:
-
Serial number authentication
-
Password authentication
-
Combination of serial number and password authentication
-
Logical ONT ID (LOID) authentication
-
LOID password authentication
-
Combination of LOID and LOID password authentication.
Serial number authentication, password authentication, and a combination of serial number and password authentication are ITU-defined ONT authentication methods.
-
-
Configure the ONT discovery mode. This can be configured with password authentication mode, a combination of serial number and password authentication mode, and all LOID related authentication modes. There are two types of ONT discovery modes:
-
Always-on mode: This mode indicates that even after the ONT passes the authentication, if the serial number changes, the ONT goes online. By default, the ONT discovery mode is in always-on mode.
-
Once-on mode: This mode indicates that the ONT must be authenticated and registered within the specified time after the configuration of the profile is completed. If ONT authentication succeeds, the serial number cannot be modified. The specified time can be set either by no aging time and aging time. A no-aging time means that the timeout period is not set and the ONT can always be authenticated.
-
-
After the ONT authentication rule is configured, the service profile is applied to the ONT.
About Unique Profiles
Each ONT is configured differently based on the service flow attribute and each of its service flow application. For example, for voice service flow, the flow attribute is a telephone number. You can configure a line profile and a unique profile on an OLT, based on the ONT service application. The following are the conditions for configuring line profile and unique profile as well as the advantages and disadvantages of each method.
-
If the ONT service flow attributes are not distinguished, different line profiles are directly configured for each ONT. Although this method allows for clear configurations, a large number of line profiles can occupy space in the configuration file.
-
If the ONT service flow attributes are distinguished, the common service flow attributes are configured as a line profile, and the different service flow attributes are configured as a unique profile. Although this method allows for simpler configuration, it is difficult to modify the ONT configurations because they are unclear.
Perform the following configuration steps to create a unique profile:
-
Configure the ONT description. This description can be used to describe the geographic location of the terminal according to the user. If a terminal fails, its location can be located quickly for troubleshooting nased on its description.
-
Bind the traffic profile and VLAN profile to the ONT GEM port using the GEM port profile. The ONT GEM port can only be created in the line profile. The ONT GEM port binding relationship to the traffic profile and VLAN profile can be configured either in the line profile or the unique profile.
Note
If there is a GEM port profile binding configuration in both the line profile and the unique profile, the unique profile configuration takes precedence.
-
Configure the ONT SIP service, including the SIP proxy attributes, SIP interface attributes, SIP number attributes, and digitmap attributes.