First and foremost SDN&Openflow are not the same. We can have a SDN model without openflow protocol,this is exactly what NSX-v is doing,however openflow is one of building block of SDN. In a openflow deployment - controllers and switches communicate via openflow protocol and build their flow table(Can be proactive also ) to update,delete ,add flows .Below picture depicts NSX architecture.

1)Communication between NSX manager and vCenter Server is through vSphere API (VIM API )
2)Communication between NSX manager and Controller – HTTPS ( query and config )
3)Communication between NSX manager and Edge – VIX API Guest VM running on a host(
- VIX is used for vShield/NSX Edge if ESXi host is not prepared otherwise is would be message bus
4)Edge and Controller – HTTPS
Note: ESXi hosts and NSX Edge Logical Router VMs learn network information, which is then reported to the Controller via User World Agent (UWA) residing on each host, also Learnt Routes are pushed to the Controller cluster for distribution and controllers send routing updates to ESXI host and kernel module and later kernel module on host handles the data plane traffic.
Below figure is showing few SDN controllers and their relation with ODL (opendaylight)

So NSX-v certainly leverage SDN architecture,however there is no openflow protocol communication between Management/Control/data plane.