This determines the service or flow type between the two terminations. The translation type as the flow passes the termination points from Customer edge to provider edge are detailed below : < Device + < < |(PE)| |(CE)| + noTranslation(1) :- The ingress flow might contain any kind of frames, untagged or single or double tagged. The egress flow will be exactly the same, no translation is done. untaggedUntagged(2) :- The traffic should be untagged, all tagged frames will be discarded. The traffic that egress the device contain the untagged flow without any modification. untaggedSingleTagged(3) :- At the CE the traffic should be untagged. At the PE the traffic will contain a single tag with the VID specified in tnVlanServiceVIDForTag. singleTaggedSingleTagged(4) :- The traffic should be single tagged on ingress and on egress with no translation. singleTaggedTranslation(5) :- The traffic should be single tagged on ingress and on egress. The only changes from the singleTaggedSingleTagged(4), there is a translation. The Vlan Id that came on ingress is translated to a different Vlan Id on egress. singleTaggedDoubleTagged(6) :- At the CE the traffic should be single tagged. At the PE the traffic will contain an extra tag with the VID specified in tnVlanServiceVIDForTag. doubleTaggedDoubleTagged(7) :- The traffic should be double tagged on ingress and on egress with no translation. doubleTaggedTranslation(8) :- The traffic should be double tagged on ingress and on egress. The only changes from the doubleTaggedDoubleTagged(7), there is a translation. The Vlan Id in outer tag that came on CE is translated to a different Vlan Id on PE. The inner tag remains intact. addProviderTag(9) :- This option adds an extra tag on the PE interface, no matter what kind of traffic at CE. This strips the outer tag for traffic from PE interface egressing the CE interface.