IP Library Granted Patent US 12,445,216
Granted Patent B2
US 12,445,216 · App. 18/307,779 · Granted Oct 14, 2025

Predicting telecommunications network performance at venues of events

Inventor: Nicholas Andrew Locke (McKinney, TX)
Assignee: T-Mobile USA, Inc.
H04B17/373H04W16/22H04W24/08
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,445,216
App. No.
18/307,779
Filed
Apr 26, 2023
Granted
Oct 14, 2025
Kind
B2
Art Unit
2475
USPC
370/252
Abstract

A method to predict performance of different telecommunications technologies at a venue by obtaining event data of one or more events. The method can identify a geocode and a profile of a venue. The method can generate a coverage heatmap that includes network coverage of the venue by different telecommunications network technologies. The method can identify one or more network access nodes of the different telecommunications networks configured to provide coverage to the venue. The method can predict performance of the different telecommunications network technologies for a particular event indicated in the event data based on performance of the one or more network access nodes. The method can cause display, on a display device, of a performance prediction dashboard including data about the predicted performance.

Claims (100)

1. A method performed by a system configured to predict performance of different telecommunications networks at a venue, the method comprising:

obtaining event data that comprises an indication of one or more events,

wherein each event occurs in a particular venue, at a particular location, and during a particular time;

identifying a geocode and a profile of a venue,

wherein the geocode includes geographic coordinates for the venue, and

wherein the profile includes a diagram of the venue;

generating a coverage heatmap that includes network coverage of the venue by different telecommunications network technologies,

wherein the coverage heatmap is generated based on measurements of signal characteristics from handset-reported data, and

wherein the measurements are weighted based on bin density of a quantity of subscribers connected to the different telecommunications networks;

identifying one or more network access nodes of the different telecommunications networks configured to provide coverage to the venue,

wherein the one or more network access nodes are identified based on the geographic coordinates of the geocode;

predicting performance of the different telecommunications network technologies for a particular event indicated in the event data based on performance of the one or more network access nodes,

wherein the predicted performance includes values for one or more key performance indicators (KPIs), and

wherein the one or more KPIs are weighted based on radio resource control (RRC) users, and

wherein the RRC-connected users include a bin density of a quantity of subscribers at the particular event; and

causing display, on a display device, of a performance prediction dashboard,

wherein the performance prediction dashboard includes the coverage heatmap overlayed on the diagram of the venue, an indication of the predicted performance, or the values for the one or more KPIs.

2. The method of claim 1 further comprises:

identifying congestion scenarios at events based on a process including:

establishing a threshold based on prior events at the geographic coordinates;

determining an expected attendance at the particular event;

determining that the expected attendance at the particular event will exceed the threshold; and

tagging the particular event as a congestion scenario to prioritize manual review.

3. The method of claim 1 , wherein predicting performance of the different telecommunications network technologies for the particular event comprises:

segmenting the diagram of the venue into one or more zones,

wherein each zone in the one or more zones includes a portion of the diagram, and

wherein each zone in the one or more zones is associated with one or more network access nodes; and

calculating performance metrics in each of the one or more zones by performing a process including:

retrieving performance KPIs from each network access node of the one or more network access nodes;

generating aggregated performance KPIs by aggregating the performance KPIs from each network access node of the one or more network access nodes; and

weighting the aggregated performance KPIs using an RRC.

4. The method of claim 1 further comprising:

generating, after the particular event lapses, a performance review dashboard,

wherein the performance review dashboard includes an actual coverage heatmap overlayed on the diagram of the venue, an actual performance metric, and the one or more KPIs.

5. The method of claim 1 , wherein generating the measurements of signal characteristics for the coverage heatmap comprises:

identifying a busiest day,

wherein the busiest day is a calendar date within a time period that represents the calendar date with a highest number of subscribers at a venue;

identifying KPI data for the busiest day or a comparable day; and

using the KPI data corresponding to the busiest day as the measurements for the coverage heatmap.

6. The method of claim 5 , wherein identifying the KPI data for a most recent day includes weighting a reference signal received power (RSRP) sample based on the user density at the venue, wherein the RSRP sample is a received power level.

7. The method of claim 5 , wherein identifying the KPI data for a most recent day includes weighting a signal-to-interference-plus-noise ratio (SINR) sample based on the user density at the venue, wherein the SINR sample is a theoretical maximum rate that information can be transferred between a wireless device and a Network Access Node.

8. The method of claim 5 , wherein identifying the KPI data corresponding to the busiest day includes weighting throughput based on the busiest day at the venue, wherein the throughput is an actual rate at which information is transferred.

9. The method of claim 5 , wherein identifying the KPI data corresponding to the busiest day includes weighting latency based on the busiest day at the venue, wherein the latency is a delay between a sender sending a packet and a receiver decoding it.

10. The method of claim 5 , wherein identifying the KPI data corresponding to the busiest day includes weighting jitter based on the busiest day at the venue, wherein the jitter is a variation in packet delay at a receiver.

11. The method of claim 5 , wherein identifying the KPI data corresponding to the busiest day includes weighting error rate based on the busiest day at the venue, wherein the error rate is a frequency at which errors occur in data transmission between a wireless device and a Network Access Node.

12. The method of claim 1 further comprising:

generating prospective aggregate performance KPIs by identifying a date of a recent network upgrade,

wherein the recent network upgrade describes a modification to the network that results in a change to a KPI; and

increasing accuracy of the generated prospective performance summary based on KPI after the date of the recent network upgrade.

13. The method of claim 1 , wherein obtaining event data that includes an indication of one or more events further comprises:

using a web scraper to identify events, wherein the web scraper is configured to:

identifying a webpage that contains event data;

extracting event details from the webpage,

wherein the event details include information about an event contained in event data including the particular venue at the particular location and during the particular time;

generating a set of events based on the events that are occurring within a time period; and

storing the set of events as the event data.

14. The method of claim 1 , wherein obtaining event data that includes an indication of one or more events further comprises:

aggregating data submissions to identify events by performing a process comprising:

receiving events from multiple entities;

generating a set of events based on the events from the multiple entities; and

storing the set of events as the event data.

15. The method of claim 1 , wherein identifying one or more network access nodes of the different telecommunications networks configured to provide coverage to the venue further comprises:

using handset-reported data,

wherein the handset-reported data is geolocated, and

wherein the handset-reported data is used to identify which network elements are serving the venue and identify the coverage in the venue.

16. At least one non-transitory computer-readable storage medium storing instructions, which, when executed by at least one data processor of a system, cause the system to:

obtain event data that includes an indication of one or more events,

wherein each event occurs in a particular venue at a particular location and during a particular time;

identify a geocode and a profile of a venue,

wherein the geocode includes geographic coordinates for the venue, and

wherein the profile includes a diagram of the venue;

generate a coverage heatmap that includes network coverage of the venue by different telecommunications network technologies,

wherein the coverage heatmap is generated based on measurements of signal characteristics from handset-reported data, and

wherein the measurements are weighted based on bin density of a quantity of subscribers connected to the different telecommunications networks or located in different parts of the venue;

identify one or more network access nodes of the different telecommunications networks configured to provide coverage to the venue,

wherein the one or more network access nodes are identified based on the geographic coordinates of the geocode;

predict performance of the different telecommunications network technologies for a particular event indicated in the event data based on performance of the one or more network access nodes,

wherein the predicted performance includes values for one or more key performance indicators (KPIs), and

wherein the one or more KPIs are weighted based on RRC users at the particular event.

17. The at least one non-transitory computer-readable storage medium of claim 16 , wherein the system is further caused to:

identify traffic scenarios by causing the system to:

establish a threshold based on prior events at the geographic coordinates;

determine an expected attendance at the particular event; and

determine that the expected attendance at the particular event exceeds the threshold.

18. The at least one non-transitory computer-readable storage medium of claim 16 , wherein to predict performance comprises causing the system to:

segment the diagram of the venue into one or more zones,

wherein each zone in the one or more zones includes a portion of the diagram, and

wherein each zone in the one or more zones includes one or more network access nodes; and

calculate performance metrics in each of the one or more zones by causing the system to:

retrieve performance data from each network access node of the one or more network access nodes;

generate aggregated performance data by aggregating the performance data from each network access node of the one or more network access nodes; and

weight the aggregated performance data using a radio resource control (RRC).

19. The at least one non-transitory computer-readable storage medium of claim 16 , wherein the system is further caused to:

generate, after the particular event lapses, a performance review dashboard,

wherein the performance review dashboard includes an actual coverage heatmap overlayed on the diagram of the venue, an actual performance metric, or the one or more KPIs.

20. The at least one non-transitory computer-readable storage medium of claim 16 , wherein generating the measurements of signal characteristics for the coverage heatmap comprises causing the system to:

identify a type of day,

wherein the type of day is a calendar date within a time period that represents the calendar date with a highest number of subscribers at a venue;

identifying the KPI data corresponding to the type of day; and

using the KPI data corresponding to the type of day as the measurements for the coverage heatmap.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 27, 2023
From: LOCKE, NICHOLAS ANDREW
To: T-MOBILE USA, INC.
Reel/Frame 063465/0704 →
Continuity (1)
Related Publication 20240364439A1 · Oct 31, 2024
References Cited (50)
US 7831384B2 · Bill · 2010 [cited by applicant]
US 7962797B2 · Goldszmidt et al. · 2011 [cited by applicant]
US 8234150B1 · Pickton et al. · 2012 [cited by applicant]
US 8964582B2 · Wilkinson · 2015 [cited by applicant]
US 8966055B2 · Mittal et al. · 2015 [cited by applicant]
US 9578519B2 · Jaldén et al. · 2017 [cited by applicant]
US 9590877B2 · Choudhary et al. · 2017 [cited by applicant]
US 9596647B2 · Bostick et al. · 2017 [cited by applicant]
US 9762455B2 · Bingham et al. · 2017 [cited by applicant]
US 9798984B2 · Paleja et al. · 2017 [cited by applicant]
US 9999805B2 · Ahuja et al. · 2018 [cited by applicant]
US 10091679B1 · Munar et al. · 2018 [cited by applicant]
US 10360127B1 · Mcsweeney et al. · 2019 [cited by applicant]
US 10439919B2 · Coleman et al. · 2019 [cited by applicant]
US 10448261B2 · Sofuoglu · 2019 [cited by applicant]
US 10489711B1 · Inbar et al. · 2019 [cited by applicant]
US 10652699B1 · Poer et al. · 2020 [cited by applicant]
US 10909479B2 · Walters et al. · 2021 [cited by applicant]
US 10966099B2 · Vanek et al. · 2021 [cited by applicant]
US 10992397B2 · Singh et al. · 2021 [cited by applicant]
US 11012864B2 · Das · 2021 [cited by applicant]
US 11018958B2 · Tapia · 2021 [cited by applicant]
US 11023295B2 · Ding et al. · 2021 [cited by applicant]
US 11223566B2 · Serrano Garcia et al. · 2022 [cited by applicant]
US 11259191B2 · Chen et al. · 2022 [cited by applicant]
US 11271960B2 · Bharrat et al. · 2022 [cited by applicant]
US 11275488B2 · Bettles et al. · 2022 [cited by applicant]
US 11388077B2 · Shah · 2022 [cited by applicant]
US 11575583B2 · Hooli et al. · 2023 [cited by applicant]
US 20090227251A1 · Lei et al. · 2009 [cited by applicant]
US 20130218612A1 · Hunt · 2013 [cited by applicant]
US 20150146616A1 · Báder · 2015 [cited by applicant]
US 20160302089A1 · Schmidt et al. · 2016 [cited by applicant]
US 20180025371A1 · Perriman et al. · 2018 [cited by applicant]
US 20180025373A1 · Perriman et al. · 2018 [cited by applicant]
US 20180040038A1 · Vanslette et al. · 2018 [cited by applicant]
US 20180352386A1 · Gunasekara · 2018 [cited by examiner]
US 20190215700A1 · Sofuoglu · 2019 [cited by examiner]
US 20190259033A1 · Reddy et al. · 2019 [cited by applicant]
US 20190311367A1 · Reddy et al. · 2019 [cited by applicant]
US 20190318288A1 · Noskov et al. · 2019 [cited by applicant]
US 20190340704A1 · Walters et al. · 2019 [cited by applicant]
US 20200404523A1 · Yoon · 2020 [cited by examiner]
US 20210221247A1 · Daniel et al. · 2021 [cited by applicant]
US 20210377788A1 · Yoon · 2021 [cited by examiner]
US 20220116265A1 · Boyle et al. · 2022 [cited by applicant]
US 20230062037A1 · Horemuz et al. · 2023 [cited by applicant]
EP 3516583B1 · 2023 [cited by applicant]
KR 101566022B1 · 2015 [cited by applicant]
WO 2017108106A1 · 2017 [cited by applicant]