ta Internet perspective: DNS, CDN logs, etc. Internet site logs, accessibility Core network data Core network perspective: Deep packet VNF control stats Core network performance aspects inspection data per network function, e.g., latency, Billing/call detail congestion, signaling records Radio access data Radio perspective: RAN vendor-specific User/device/application collected data performance VS. radio characteristics, and location Device data User perspective: Device diagnostic Collect across multiple radio access collection software networks (e.g., WiFi, cellular) Device-dependent performance captured (applications, resets) Collects no-service, and other network access issues The radio access data contain a wealth of device reported data containing the interactions of the device and the radio network, as well as corresponding radio access node (RAN) data. These data help characterize network optimization and performance issues as a function of the radio link and node itself (e.g., good/bad coverage, good/bad interference, radio congestion, congestion between the radio node and core node). In addition, devices traditionally provide the radio network data in "Network Measurement Reports (NMRs)" related to their location-from coarse location data such as "what cell site a device is connected to," to time delay of arrival data from multiple cell sites that can help triangulate a given device to a much finer location area. Cell change updates (CCU) record data from devices as devices move from cell to cell, regardless as to whether a call or data session is in place, which makes these data particularly useful for visibility of all devices. Since the RANs are traditionally proprietary, access to these data is based on what the vendors will provide, or, alterna- tively what can be "probed" between the radio and core network connections. The core network data contain data related to all nodes/functions within the more central core network nodes. Tapping these data allows visibility into not only core network node perf