Typical FTTH Networking
Networking Scenario
|
Description
|
Bridging ONT + HGW Network Scenario
|
The HGW integrating an IAD provides Internet, voice over Internet Protocol (VoIP), and Internet Protocol television (IPTV) services to users.
Services are implemented on the HGW, and the bridging ONT works with the OLT to provide Layer 2 channels.
|
Bridging+Voice ONT Network Scenario
|
The ONT integrating an integrated access device (IAD) provides Internet, VoIP, and IPTV services to users.
The bridging+voice ONT provides Layer 2 data and voice services. This scenario provides transparent transmission channels and requires simple service configuration, so this scenario applies to Layer 2 networking.
· For data services, a PC directly performs dial-up. Then, the upper-layer broadband remote access server (BRAS) device authenticates and accesses the PC. The PC can also access the Internet using the Dynamic Host Configuration Protocol (DHCP) or static IP address.
· The ONT with a built-in voice module encapsulates voice service packets, and the OLT transmits them to the upstream next generation network (NGN) or IP multimedia subsystem (IMS).
|
Gateway ONT Network Scenario
|
The ONT integrating an IAD provides Internet, VoIP, and IPTV services to users.
The HGW ONT facilitates interconnection of home devices by providing Layer 3 services, such as Point-to-Point Protocol over Ethernet (PPPoE)/DHCP dial-up, network address translation (NAT), and Internet Group Management Protocol (IGMP) snooping. This scenario provides fine-grained management channels and service control, and applies to Layer 3 networking.
|
FTTH Deployment Schemes
FTTH service application includes the deployment process and service provisioning process. The FTTH deployment process includes OLT deployment (configuration) and configuration of basic data. No deployment, however, is required on the ONT and the ONT is plug and play once services are provisioned.
Pre-configuration
|
Service Provisioning
| |
Scheme
|
· On the NMS: Profiles can be issued in batches.
· Using commands on the OLT: Configuration scripts containing commands can be imported to the OLT.
|
· Using the OSS: This method is recommended and it can implement automatic service provisioning, and eliminate problems caused by manual service provisioning, such as large workload, low efficiency, and difficult management.
· Using OSS+ITMS: This method is recommended if the multiple private nodes are customized for carriers. Using a TR069 server, new gateways and value-added voice services can be simply added.
§ Layer 2 configuration data is issued on the NMS or OLT.
§ Other configuration data such as voice, Layer 3, and Wi-Fi data is issued using the ITMS.
· On the NMS: It applies to the scenario when no OSS is available and services need to be provisioned manually on the NMS.
· On the ONT web page: When it is not feasible to provision services on the OSS or NMS, you can log in to the ONT web page and configure or modify parameters to provision services.
|
Parameter
|
· DBA profile
· Line profile
· Service profile
· IP traffic profile
· Service level profile
· Global OLT configurations (rather than FTTH user configurations) such as multicast VLAN, multicast mode, and policy of forwarding unknown packets
· FTTH user service VLAN configurations including adding VLANs, setting the attributes of VLANs, and adding upstream ports for VLANs
|
ONT service provisioning parameters are classified into common parameters and customized parameters:
· Customized parameters are usually issued by the upper-layer system during service provisioning.
· Common parameters are usually configured at delivery or during data pre-configuration.
|
Parameter Type
|
Layer 2
|
Voice
|
Above Layer 2 (Layer 3, Wi-Fi, and User Security)
|
Customized parameters
|
Parameters for adding ONTs, adding service flows, activating ports, configuring port rate limitation, and adding multicast users
|
· Registration information: IP address and port number of the local end and the proxy
· User data: SIP user name and H.248 TID
|
Login user name and password
|
Common parameters
|
Various pre-configured profile data
|
· Digitmap: includes the digitmap timer and digitmap character strings.
· Time configuration: includes registration heartbeat and protocol timers.
· Encoding and decoding: includes voice encoding and decoding priorities and packetization period, G.711/G.729/G.722.
· Fax/Modem
· Service permission and service data
· VAG: implements multiple virtual AG devices on one physical device.
· Configurations for the interconnection between IMSs of softswitches of different specifications
|
· WAN port configurations (routes, bridge WANs, and VLANs)
· LAN/WAN binding
· IGMP mode
· URL for the ITMS
· NTP server
· Default Wi-Fi configurations
· Local login IP address
|
ONT type
|
· Bridging ONTs (SFUs)
· Bridging+voice ONTs
· Gateway-type ONTs (HGUs)
|
· Bridging+voice ONTs
· Gateway-type ONTs
|
Gateway-type ONTs
|
The following describes the involved configuration scenarios:
· Service configuration on the NMS: Pre-configurations and service provisioning are implemented on the NMS.
· Service configuration using commands: Pre-configurations are implemented using commands, and service provisioning is implemented on the ONT web pages.
· Service provisioning on the ITMS: Pre-configurations are implemented on the NMS or using commands, and Layer 3 and voice services are provisioned on the ITMS. Huawei U2560 is used as an example to describe how to provision the services on the ITMS.
More related:
No comments:
Post a Comment