re Throttling Inputs Current State Compute (4) Policies (5) Controllers PRB utilization Current networks The DCAE Policy engine pulls VNF packet bandwidth counts, from assert QoS-based microanalytics down throttling gateway or VNF traffic VNF edge nodes allocation of for throttling microanalytics MSP receives a shaping going into resources for determines results from data bus command via the requested session historical PRB and applied specific data bus with Data rates per (MIME) types on utilization per policies as follows. radio ID and Internet domain proprietary base station radio For those base throttling level (bytes/time) nodes and the station radios having (based on PRB generally PRB utilization is associated high estimated loading level) to observed at a sent directly session count per current PRB invoke throttling VNF packet from proprietary hour, per day of utilization, insert e.g., "radio_X, gateway or nodes to DCAE week. It also TCP/IP packet time throttle class Y" multiservice determines delays at the proxy (MSP) current number "controllers," which also going into of active data are the VNF packet sessions and gateway or VNF estimate likely multiservice proxy current load as a function of All results are session or MIME placed onto data type for that radio. For instance, if a radio is heavily loaded, we can set up policies to throttle adaptive bit rate video, but not a* .jpg file transmissions Policy results/ commands are placed on to data bus 8.4.4 UTILIZING SDN TO MINIMIZE ROBOCALLING Combatting robocalling is an ever-increasing task in wireless networks whose solution also lends itself to software-defined networking. In this case, the SDN needs to identify robocallers using a "seeded" list of known robocaller phone numbers, and call detail attributes, and then subsequently by using ML to predict other robocallers dynamically. After detection, the suspected robocallers can either be sent to an operator for confirmation, or subsequently reprogram the network to block calls from suspected robocaller 