# US 11,910,265 B2 · Hyper-localization based edge-converged telemetry > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,910,265 B2 - Document ID: US11910265B2 - Status: Granted - Kind: B2 - Application number: 17/026,973 - Filed: 2020-09-21 - Published: 2021-03-04 - Granted: 2024-02-20 - Earliest claimed: 2019-09-03 - Assignees: Cox Communications, Inc. - Applicants: Cox Communications, Inc. - Inventors: Keith Alan Rothschild; Dipan Patel; Ron Lev; Steve Malenfant - Web page: https://patentgrep.com/patent/US11910265B2 ## CPC - G06F 16/909: using geographical or spatial information, e.g. location (spatiotemporally dependent retrieval from the web G06F16/9537) - H04W 4/021: Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences - G06F 16/29: Geographical information databases - G06F 16/9035: Filtering based on additional data, e.g. user or group profiles - G06F 16/9537: Spatial or temporal dependent retrieval, e.g. spatiotemporal queries - H04W 4/023: {using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds} - H04W 8/20: Transfer of user or subscriber data - H04W 84/18: Self-organising networks, e.g. ad-hoc networks or sensor networks - G06F 9/541: {via adapters, e.g. between incompatible applications} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Edge-converged telemetry is provided. A system, method, and computer readable storage device are provided for collecting telemetry data from a plurality of telemetry sources in an edge network, determining geolocations of the telemetry, tagging the telemetry with geolocation metadata corresponding to the determined geolocations, correlating telemetry based at least in part on the geolocation, converging the telemetry, and providing the edge-converged telemetry to a client decisioning system that is enabled to use the converged telemetry for making or influencing decisions made by the system. In an example aspect, the decisioning system is configured to make decisions for controlling a device, wherein the decisions are based at least in part on telemetry data. Accordingly, edge-converged telemetry enhance capabilities of the decisioning system by providing data that may have not been previously available to the system and/or by providing a more comprehensive representation of the environment in which the system is operating. ## Claims ### Claim 1 A system comprising: a communication network including an edge network; and a telemetry convergence system to: collect telemetry data associated with a plurality of telemetry data sources; associate geolocation information with the collected telemetry data; identify relevant telemetry data from the collected telemetry data according to the geolocation information for a local telemetry-based decision of at least one client; and transmit the relevant telemetry data to the at least one client for the local telemetry-based decision. ### Claim 2 (depends on 1) The system of claim 1, the telemetry convergence system further to: determine the geolocation information based in part on one or more geolocations of one or more network elements of the communication network through which the telemetry data are communicated; and associate the geolocation information of the one or more network elements the collected telemetry. ### Claim 3 (depends on 1) The system of claim 1, the telemetry convergence system further to determine the relevant telemetry data based on the geolocation of a network node with respect to the at least one client. ### Claim 4 (depends on 1) The system of claim 1, the telemetry convergence system further to identify local sources of telemetry associated with the at least one client. ### Claim 5 (depends on 1) The system of claim 1, the telemetry convergence system further to identify the relevant telemetry data from the collected telemetry data based on a type of telemetry data and/or a type of client. ### Claim 6 (depends on 1) The system of claim 1, the telemetry convergence system further to anonymize the relevant telemetry data before transmission of the relevant telemetry data to the at least one client. ### Claim 7 (depends on 1) The system of claim 1, the telemetry convergence system further to source the relevant telemetry data from outside a local network of the at least one client. ### Claim 8 (depends on 1) The system of claim 1, the telemetry convergence system further to receive registration data associated with one or more of the plurality of telemetry sources contributing to the collected telemetry data. ### Claim 9 (depends on 1) The system of claim 1, the telemetry convergence system further to receive one or more of: an identifier of each telemetry source, an identifier of each sensor, an identifier of a telemetry data type associated with each telemetry source. ### Claim 10 (depends on 1) The system of claim 1, the telemetry convergence system further to receive an identifier and/or a time-date stamp associated with each relevant telemetry source. ### Claim 11 (depends on 1) The system of claim 1, the telemetry convergence system further to inspect one or more telemetry data packets may include a shallow packet inspection that identifies network addressing information included in one or more of the telemetry data packets. ### Claim 12 (depends on 1) The system of claim 1, the telemetry convergence system further to determine the geolocation information of a network node or a client router as a source node of a telemetry data packet. ### Claim 13 A method of collecting telemetry data for local telemetry-based decisions comprising: collecting telemetry data associated with a plurality of telemetry data sources; associating geolocation information with the collected telemetry data; identifying relevant telemetry data from the collected telemetry data according to the geolocation information for a local telemetry-based decision of at least one client; anonymizing the relevant telemetry data; and transmitting the anonymized relevant telemetry data to the at least one client for the local telemetry-based decision. ### Claim 14 (depends on 13) The method of claim 13, further comprising determining the geolocation information of a network node or a client router as a source node of a telemetry data packet. ### Claim 15 (depends on 13) The method of claim 13, further comprising identifying the relevant telemetry data from the collected telemetry data based on a type of telemetry data and/or a type of client. ### Claim 16 (depends on 13) The method of claim 13, further comprising sourcing the relevant telemetry data from outside a local network of the at least one client. ### Claim 17 (depends on 13) The method of claim 13, further comprising predicting one or more events based in part on the collected telemetry data. ### Claim 18 System comprising: a local network; and a client device coupled to the local network, the client device to: receive relevant telemetry data via the local network, wherein the relevant telemetry data was collected from a plurality of telemetry data sources and identified as being relevant according to geolocation information associated with each of the plurality of telemetry data sources; and determine whether to execute a telemetry-based decision according to the relevant telemetry data received via the local network. ### Claim 19 (depends on 18) The system of claim 18, wherein the client device is further to receive anonymized relevant telemetry data. ### Claim 20 (depends on 18) The system of claim 18, wherein the client device operates as part of an automation system that utilizes the relevant telemetry data to control one or more devices coupled to the local network.