A simple example for procedure of auto ONT provision, while splitter is out of the scope.

1. OLT installation before provision

Create NE on EMS
Configure profile templates and uplink VLANs as network plan

*Note: It is important to uniform the profile templates on all OLTs to avoid confusion!
Strong recommend：virtual port for Internet data service fixes to 1
virtual port for VOIP service fixes to 2

2. Login EMS server (UDP port = 8100)

<?xml version="1.0"?>
<login_command>
<sequence id="1"/>
<access id="11"/>
<user name="root" password="public1"/>
</login_command>

*Note: password may be different.

Once login, you can continue send next commands before idle timeout.

3. Retrieve inventory of OLT device

3.1 Request EMS to generate OLT inventory file

<?xml version="1.0"?>
<get_request_gepon_inventory_data>
<sequence id="1"/>
<access id="11"/>
</get_request_gepon_inventory_data>

3.2 FTP get inventory file from EMS server ( tool )

.\GPON_Inventory_Data.csv
 Figure 1. file format

Recommend: import these data to TCS database

4. Provision ONT service

4.1 Fill in items

select NE name ( resolve to IP internally as 172.18.36.172): GPON-NODE-1
Select OLT port ID ( that ONT count should be less than 64): 1-1

4.2 Retrieve flow profile for user VLAN mapping

Note: TCS can also store profile templates of the node to database to accelerate provision next
time, along with refresh button to update them.

<?xml version="1.0"?>
<get_request_flow_profile>
<address node_addr="172.18.36.172"/>
<sequence id="1"/>
<access id="11"/>
</get_request_flow_profile>

--------EMS response
<profiles>
<profile index1="1"
index2="1"
name="data"
vlan_id_start="101"
vlan_id_stop="101"
virtual_port_id="1"/>
<profile index1="1"
index2="2"
name="voip"
vlan_id_start="4023"
vlan_id_stop="4023"
virtual_port_id="2"/>

Parameters as index1 ID/vlan_id_start/virtual_port_id are mandatory for step 4.4

And strong recommend：virtual port for Internet data service fixes to 1
virtual port for VOIP service fixes to 2
4.3 Retrieve T-CONT binding profile for user bandwidth mapping
Note: TCS can also store profile templates of the node to database to accelerate provision next
time, along with refresh button to update them.

<?xml version="1.0"?>
<get_request_t-cont_and_virtual_port_binding_profile>
<address node_addr="172.18.36.172"/>
<sequence id="1"/>
<access id="11"/>
</get_request_t-cont_and_virtual_port_binding_profile>

--------EMS response
<profile index="1"
name="data"
virtual_port_id="1"
virtual_port_service_profile_index="2"
virtual_port_service_profile_name="20M"
t-cont_id="1"
t-cont_service_profile_index="2"
t-cont_service_profile_name="20M"/>
<profile index="1"
name="voip"
virtual_port_id="2"
virtual_port_service_profile_index="3"
virtual_port_service_profile_name="512K"
t-cont_id="1"
t-cont_service_profile_index="3"
t-cont_service_profile_name="512K"/>

4.4 Base on SLA (internet, voip service, bandwidth requirement) Fill in items
ONT ID (increment ID in the list): 2
ONT SN: GPON005F2961
flow_profile_index: 1
t-cont_and_virtual_port_binding_profile_index: 1
user data vlan: 3060 + 160 (example as dual vlan)
user voip vlan: 4023 (example as single vlan)

<?xml version="1.0"?>
<set_onu_service>
<address node_addr="172.18.36.172"/>
<sequence id="1"/>
<access id="11"/>
<onu id="1-1-2"
serial_number="GPON005F2961"
flow_profile_index="1"
t-cont_and_virtual_port_binding_profile_index="1"
data_virtual_port_id="1" (node: as flow profile)
data_cvid="101" (node: as flow profile)
data_new_svid="3060" (note: outer VLAN in case of dual-VLAN)
data_new_cvid="160" (note: inner VLAN in case of dual-VLAN)
voip_virtual_port_id="2" (node: as flow profile; 0 means no voip service)
voip_cvid="4023" (node: as flow profile; 0 means no voip service)
voip_new_svid="4023" (node: as flow profile; 0 means no voip service)
voip_new_cvid="4095"/> (note: 4095 means single-VLAN )
</set_onu_service>