s" data from list-1234" and collected with cells can "nbhr_ network node XYZ every X follows "ANR the DCAE handoff measurements" seconds, and publish results to controller" "batch or between each data from the the data bus policy real-time other). These data bus and Analytics computation policy rule collectors" results are computes "best "ANR_analytics": which collect stored in neighbor The analytics layer should data as defined relations" the compute the "best neighbor by the Data topology layer Analytics relations" per cell-pair based on Collector Computation the number of times a given cell Policy= Policy rule was seen for each serving cell. It "ANR_collect" "ANR" stack ranks the cell pairs, and (see far right performs a cutoff of the top N column) cell pair. If these are different than the existing neighbor list stored in the topology function (retrieved via API), then the analytics layer publishes the new "new_best neighbor_list" to the data bus Actions policy "ANR_actions": the policy function shall inspect the data bus for the "new_best_ neighbor_list-1234," and publish "implement_nbhr_list-1234" the data bus intended for the "radio_access_Controller" to take action per ANR Controller policy "ANR_controller" Controller upon seeing "implement_nbhr_list-1234" publishes "new_nbhr_list" the radio access network and if successful, updates topology with new neighbor relations session is being conducted by each of the mobile devices. Lastly, we must selectively insert time delays in the TCP/IP data flows for those device's data sessions. To the extent that congestion cannot be measured in real time but only after a small delay, then historical data can be used to compare relative radio loading to estimate whether the radio is in or likely to be in congestion. Figure 8.18 and Table 8.9 illustrate how this SDN feature may be implemented. Network Data and Optimization TABLE 8.9 Traffic Shaping Feature Functional Mapping to DCAE D2 Traffic (1) Primary Data (2) Network Shaping Used For Topology, (3) Analytics to Featu