This read-only counter tracks the total number of CLNP PDUs that local upper-layer protocols on this entity handed down to CLNP for transmission, explicitly excluding any PDUs that are being forwarded through rather than originated locally. An admin uses this to measure how much CLNP traffic this device itself is generating, as distinct from transit traffic captured separately in clnpForwPDUs. For example, a spike in this counter without a corresponding spike in clnpForwPDUs would tell the admin the increase in outbound traffic is coming from applications on this device itself, not from routed transit packets.