IP Library Granted Patent US 12,224,878
Granted Patent B2
US 12,224,878 · App. 17/984,358 · Granted Feb 11, 2025

Limiting content of travel-related messages

Inventors: Amit Deshpande (Cincinnati, OH); Jeffrey Lee Littlejohn (Cincinnati, OH); Abineshraj Rajagopal (Maineville, OH)
Assignee: iHeart Media Management Services, Inc.
H04L12/1877H04H20/55H04L12/1845H04L12/189H04L67/1014H04H2201/18H04H2201/90
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,224,878
App. No.
17/984,358
Granted
Feb 11, 2025
Kind
B2
Abstract

A boundary specifying a bounded geographic area for which travel information is to be reported is generated. Flow section information associated with flow sections located within the boundary is obtained. The flow sections represent portions of one or more roadways assigned relevant functional road classes (FRCs). The flow section information includes information about traffic flow associated with the flow sections. FRC current traffic messages, which include non-predictive traffic information associated with roadway portions that are in the bounded geographic area and are assigned relevant FRCs, are combined with the flow section information to generate a first data group. The first data group is streamed to a first traffic message service.

Claims (57)

1. A method comprising:

generating a boundary specifying a bounded geographic area for which travel information is to be reported;

defining the bounded geographic area based on market configuration parameters;

obtaining flow section information associated with flow sections located within the boundary, wherein the flow sections represent portions of one or more roadways assigned relevant functional road classes (FRCs), and the flow section information includes information about traffic flow associated with the flow sections;

combining FRC current traffic messages and the flow section information to generate a first data group, wherein the FRC current traffic messages include non-predictive traffic information associated with roadway portions that are in the bounded geographic area and are assigned relevant FRCs;

determining whether an aggregate size of the FRC current traffic messages plus a size of FRC predictive traffic messages satisfies a message size threshold, wherein the FRC predictive traffic messages include predictive traffic information associated with the roadway portions that are in the bounded geographic area and are assigned relevant FRCs; and

streaming the first data group to a first traffic message service.

2. The method of claim 1 , further comprising:

in response to determining that the aggregate size satisfies the message size threshold, streaming at least a portion of the FRC predictive traffic messages to the first traffic message service.

3. The method of claim 1 , further comprising:

in response to determining that the aggregate size fails to satisfy the message size threshold:

adding the FRC predictive messages to a second data group; and

streaming the second data group to a second traffic message service.

4. The method of claim 3 , further comprising:

in response to determining that the aggregate size fails to satisfy the message size threshold:

removing FRC predictive traffic messages associated with at least one relevant FRC to generate a reduced number of FRC predictive traffic messages; and

streaming the reduced number of FRC predictive traffic messages to the first traffic message service.

5. The method of claim 1 , further comprising:

setting the message size threshold based on a Transport Protocol Expert Group message-size limitation.

6. The method of claim 1 , further comprising:

determining whether a particular FRC is relevant based on a time of day.

7. A device comprising:

a processor;

memory coupled to the processor, the memory storing a program of instructions configured to be executed by the processor, the program of instructions including:

at least one instruction to generate a boundary specifying a bounded geographic area for which travel information is to be reported, wherein the bounded geographic area is defined based on market configuration parameters;

at least one instruction to obtain flow section information associated with flow sections located within the boundary, wherein the flow sections represent portions of one or more roadways assigned relevant functional road classes (FRCs), and the flow section information includes information about traffic flow associated with the flow sections;

at least one instruction to combine FRC current traffic messages and the flow section information to generate a first data group, wherein the FRC current traffic messages include non-predictive traffic information associated with roadway portions that are in the bounded geographic area and are assigned relevant FRCs;

at least one instruction to determine whether an aggregate size of the FRC current traffic messages plus a size of FRC predictive traffic messages satisfies a message size threshold, wherein the FRC predictive traffic messages include predictive traffic information associated with the roadway portions that are in the bounded geographic area and are assigned relevant FRCs; and

at least one instruction to stream the first data group to a first traffic message service.

8. The device of claim 7 , wherein the program of instructions further includes:

at least one instruction to stream at least a portion of the FRC predictive traffic messages to the first traffic message service in response to determining that the aggregate size satisfies the message size threshold.

9. The device of claim 7 , wherein the program of instructions further includes:

at least one instruction to add the FRC predictive messages to a second data group in response to determining that the aggregate size fails to satisfy the message size threshold; and

at least one instruction to stream the second data group to a second traffic message service.

10. The device of claim 9 , wherein the program of instructions further includes:

at least one instruction to remove FRC predictive traffic messages associated with at least one relevant FRC to generate a reduced number of FRC predictive traffic messages in response to determining that the aggregate size fails to satisfy the message size threshold; and

at least one instruction to stream the reduced number of FRC predictive traffic messages to the first traffic message service.

11. The device of claim 7 , wherein the program of instructions further includes:

at least one instruction to set the message size threshold based on a Transport Protocol Expert Group message-size limitation.

12. The device of claim 7 , wherein the program of instructions further includes:

at least one instruction to determine whether a particular FRC is relevant based on a time of day.

13. A non-transitory computer readable medium including a program of instructions configured to be stored in a memory and executed by a processor, the program of instructions comprising:

at least one instruction to generate a boundary specifying a bounded geographic area for which travel information is to be reported, wherein the bounded geographic area is defined based on market configuration parameters;

at least one instruction to obtain flow section information associated with flow sections located within the boundary, wherein the flow sections represent portions of one or more roadways assigned relevant functional road classes (FRCs), and the flow section information includes information about traffic flow associated with the flow sections;

at least one instruction to combine FRC current traffic messages and the flow section information to generate a first data group, wherein the FRC current traffic messages include non-predictive traffic information associated with roadway portions that are in the bounded geographic area and are assigned relevant FRCs;

at least one instruction to determine whether an aggregate size of the FRC current traffic messages plus a size of FRC predictive traffic messages satisfies a message size threshold, wherein the FRC predictive traffic messages include predictive traffic information associated with the roadway portions that are in the bounded geographic area and are assigned relevant FRCs; and

at least one instruction to stream the first data group to a first traffic message service.

14. The non-transitory computer readable medium of claim 13 , wherein the program of instructions further includes:

at least one instruction to stream at least a portion of the FRC predictive traffic messages to the first traffic message service in response to determining that the aggregate size satisfies the message size threshold.

15. The non-transitory computer readable medium of claim 13 , wherein the program of instructions further includes:

at least one instruction to add the FRC predictive messages to a second data group in response to determining that the aggregate size fails to satisfy the message size threshold; and

at least one instruction to stream the second data group to a second traffic message service.

16. The non-transitory computer readable medium of claim 15 , wherein the program of instructions further includes:

at least one instruction to remove FRC predictive traffic messages associated with at least one relevant FRC to generate a reduced number of FRC predictive traffic messages in response to determining that the aggregate size fails to satisfy the message size threshold; and

at least one instruction to stream the reduced number of FRC predictive traffic messages to the first traffic message service.

17. The non-transitory computer readable medium of claim 13 , wherein the program of instructions further includes:

at least one instruction to set the message size threshold based on a Transport Protocol Expert Group message-size limitation.

Assignments (7)
PATENT SECURITY AGREEMENT Recorded Dec 29, 2024
From: IHEARTMEDIA MANAGEMENT SERVICES, INC.
To: BANK OF AMERICA, N.A.
Reel/Frame 069795/0912 →
PATENT SECURITY AGREEMENT Recorded Dec 28, 2024
From: IHEARTMEDIA MANAGEMENT SERVICES, INC.
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 069793/0758 →
PATENT SECURITY AGREEMENT Recorded Dec 28, 2024
From: IHEARTMEDIA MANAGEMENT SERVICES, INC.
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 069794/0248 →
PATENT SECURITY AGREEMENT Recorded Dec 27, 2024
From: IHEARTMEDIA MANAGEMENT SERVICES, INC.
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 069792/0335 →
PATENT SECURITY AGREEMENT Recorded Dec 23, 2024
From: IHEARTMEDIA MANAGEMENT SERVICES, INC.
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 069762/0453 →
PATENT SECURITY AGREEMENT Recorded Dec 22, 2024
From: IHEARTMEDIA MANAGEMENT SERVICES, INC.
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION
Reel/Frame 069752/0941 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 10, 2022
From: DESHPANDE, AMIT; LITTLEJOHN, JEFFREY LEE; RAJAGOPAL, ABINESHRAJ
To: IHEARTMEDIA MANAGEMENT SERVICES, INC.
Reel/Frame 061725/0087 →
Continuity (3)
Continuation 16385169 · Apr 16, 2019
Continuation 15633943 · Jun 27, 2017
Related Publication 20230068839A1 · Mar 2, 2023
References Cited (29)
US 8264375B2 · Devries · 2012 [cited by applicant]
US 9026346B2 · Choi · 2015 [cited by applicant]
US 9148330B2 · Samsalovic · 2015 [cited by applicant]
US 9593955B2 · Pfeifle · 2017 [cited by applicant]
US 20090115632A1 · Park · 2009 [cited by applicant]
US 20100188264A1 · Devries · 2010 [cited by applicant]
US 20110298637A1 · Posner · 2011 [cited by applicant]
US 20130151134A1 · Choi · 2013 [cited by examiner]
US 20140304321A1 · Stroila · 2014 [cited by applicant]
US 20140317124A1 · Kosuru · 2014 [cited by applicant]
US 20150325124A1 · Fernback · 2015 [cited by examiner]
US 20160104377A1 · French · 2016 [cited by applicant]
US 20160216125A1 · Ahn · 2016 [cited by applicant]
US 20160313130A1 · Baselau · 2016 [cited by examiner]
US 20170045364A1 · Trivedi · 2017 [cited by examiner]
US 20180160391A1 · Flammer, III · 2018 [cited by examiner]
AVT Audio Video Technologies, Magic DAB Headend, promotional brochure, Germany. [cited by applicant]
Burfeind, Mark; Inrix TPEG Connect™ Optimizes Delivery and Reduces Costs of Providing Dynamic Traffic Info to Connected Vehicles and Devices; Jul. 28, 2010, 2 pages, http://inrix.com/press/2656/. [cited by applicant]
Consumer Electronics Association, National Association of Broadcasters, National Radio systems Committee, Broadcasting Standard NRSC-5-C, Sep. 2011, pp. 1-53, United States. [cited by applicant]
Consumer Electronics Association, National Association of Broadcasters, National Radio systems Committee, RBDS Standard NRSC-4-B, Apr. 2011, pp. 1-36, United States. [cited by applicant]
Definitions for Classes 1 through 7 of the BIA IRR Program. [cited by applicant]
Francis, Dave, TISA—building standards in Automotive Traffic Information Services, Taiwan Telematics 2012, Nov. 8, 2012, 34 pages. [cited by applicant]
Francis, Dave; TPEG Digital Radio Traffic Data, Next generation of Traffic and Travel Information Services; May 3, 2016; 23 pages. [cited by applicant]
Gardiner, P.A.O.; Implementing TPEG and Multimedia Services for Digital Radio, British Broadcasting Corporation, UK, Dec. 1999; 6 pages. [cited by applicant]
Marks, Bev, TPEG—an introduction to the growing family of standards and specifications for Traffic and Travel Information services, Jun. 10, 2009, 53 pages. [cited by applicant]
TPEG Analyser (Nov. 2015). Retrieved from http://wecantpeg.com/tpeg-analyser.html; 4 pages. [cited by applicant]
“TPEG—What is it all about”—TISA, Jan. 27, 2014 http://tisa.org/wp-content/uploads/documents/TISA14001TPEGWhatisitallabout2014.pdf. [cited by applicant]
We Can TPEG! (Oct. 2015). Retrieved from http://wecantpeg.com/TPEG_Analyser_4_1.pdf; 2 pages. [cited by applicant]
Wikipedia, TPEG, website, Apr. 20, 2016, pp. 1-17. [cited by applicant]