IP Library › Granted Patent US 12,483,653
Granted Patent B2
US 12,483,653 · App. 18/330,291 · Granted Nov 25, 2025

Customization of CNAM information for calls placed to mobile devices

Inventors: Brandon Wayne Murphy (Little Rock, AR); Robert Collin Seely (Little Rock, AR); Aaron Christopher Jacobi (Little Rock, AR); Benjamin Michael Lavigne (Little Rock, AR); Mark Bradley McHenry (Vilonia, AR); John Cooper Gillespie (Beebe, AR); Matthew Jack Beckham (Conway, AR); Kristen Chipolla Sanchez (Bryant, AR); Lyndsay Michelle Norcross (Little Rock, AR); Jay Todd Callaway (Conway, AR)
Assignee: FIRST ORION CORP.
H04M3/42059H04L45/20H04L61/106H04M3/2254H04M3/42042H04M3/436
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,483,653
App. No.
18/330,291
Granted
Nov 25, 2025
Kind
B2
Abstract

One example method of operation may include identifying a call from a calling device destined for a mobile device, identifying a calling device number associated with the calling device and a mobile device number associated with the mobile device, determining whether a stored calling relationship exists between the calling device number and the mobile device number, and appending one of a plurality of caller identification names (CNAM) to the call based on the determination as to whether there is a stored calling relationship.

Claims (40)

1 . A method comprising:

identifying by a content delivery device a call from a calling device to a mobile device;

identifying by the content delivery device a calling device number associated with the calling device and a mobile device number associated with the mobile device;

identifying by the content delivery device whether a relationship exists between the calling device number and the mobile device number;

assigning by the content delivery device a caller identification name (CNAM) to the call,

wherein when the relationship does not exist, the CNAM that is assigned is a default CNAM corresponding to the mobile device number, and when the relationship does exist, the CNAM that is assigned is a previous CNAM that was previously assigned to the mobile device number;

communicating by the content delivery device the CNAM to a carrier network for communication to the mobile device; and

responsive to the CNAM being communicated to the carrier network, receiving telemetry data by the content delivery device, including aggregated data associated with the CNAM, wherein responsive to the CNAM being communicated to the carrier network, receiving by the content delivery device a flag indicating that the telemetry data is for a purpose of demonstration or a live call.

2 . The method of claim 1 , further comprising: retrieving the previous CNAM from a call content application programming interface (API) by the content delivery device.

3 . The method of claim 1 , comprising: transmitting the previous CNAM by the content delivery device for display by the mobile device when the call is connecting the calling device and the mobile device.

4 . The method of claim 1 , comprising: transmitting the default CNAM by the content delivery device to the mobile device for display when the call is connecting the calling device and the mobile device.

5 . The method of claim 1 , wherein the CNAM is an electronic CNAM (ECNAM) comprising at least one of: a one to fifteen-character alphanumeric message, a uniform resource locator (URL) link, image data, video data, or audio data.

6 . The method of claim 1 , wherein the identifying whether the relationship exists, comprises: identifying contextual information associated with a previously logged transaction that identifies transaction information linked to the mobile device number and the calling device number, and wherein the assigning the CNAM to the call comprises: assigning the CNAM to a push API based on the identified contextual information.

7 . A system comprising:

a computing device configured to:

identify a call from a calling device to a mobile device;

identify a calling device number associated with the calling device and a mobile device number associated with the mobile device;

identify whether a relationship exists between the calling device number and the mobile device number;

assign a caller identification name (CNAM) to the call, wherein when the relationship does not exist, the CNAM that is assigned is a default CNAM corresponding to the mobile device number, and when the relationship does exist, the CNAM that is assigned is a previous CNAM that was previously assigned to the mobile device number; communicate the CNAM to a carrier network for communication to the mobile device; and responsive to the CNAM being communicated to the carrier network, receive telemetry data, including aggregated data associated with the CNAM, wherein responsive to the CNAM being communicated to the carrier network, receive by the content delivery device, a flag that indicated the telemetry data is for a purpose of demonstration or a live call.

8 . The system of claim 7 , wherein computing device is further configured to: retrieve the previous CNAM from a call content application programming interface (API).

9 . The system of claim 7 , wherein the computing device is configured to: transmit the previous CNAM by the content delivery device for display by the mobile device when the call is connecting the calling device and the mobile device.

10 . The system of claim 7 , wherein the computing device is configured to: transmit the default CNAM by the content delivery device to the mobile device for display when the call is connecting the calling device and the mobile device.

11 . The system of claim 7 , wherein the CNAM is an electronic CNAM (ECNAM) comprising at least one of: a one to fifteen-character alphanumeric message, a uniform resource locator (URL) link, image data, video data, or audio data.

12 . The system of claim 7 , wherein when the computing device identifies whether the relationship exists, the computing device is further configured to:

identify contextual information associated with a previously logged transaction that identifies transaction information linked to the mobile device number and the calling device number, and wherein when the computing device assigns the CNAM to the call, the computing device is further configured to: assign the CNAM to a push API based on the identified contextual information.

13 . A non-transitory computer-readable storage medium configured to store one or more instructions that, when executed by a processor, cause the processor to perform:

identifying a call from a calling device to a mobile device;

identifying a calling device number associated with the calling device and a mobile device number associated with the mobile device;

identifying by the content delivery device whether a relationship exists between the calling device number and the mobile device number;

assigning a caller identification name (CNAM) to the call,

wherein when the relationship does not exist, the CNAM that is assigned is a default CNAM corresponding to the mobile device number, and when the relationship does exist, the CNAM that is assigned is a previous CNAM that was previously assigned to the mobile device number;

communicating the CNAM to a carrier network for communication to the mobile device; and

responsive to the CNAM being communicated to the carrier network, receiving telemetry data, including aggregated data associated with the CNAM, The non-transitory computer-readable storage medium of claim 12 , wherein responsive to the CNAM being communicated to the carrier network, receiving by the content delivery device, a flag indicating that the telemetry data is for a purpose of demonstration or a live call.

14 . The non-transitory computer-readable storage medium of claim 13 , wherein the one or more instructions further cause the processor to perform:

retrieving the previous CNAM from a call content application programming interface (API).

15 . The non-transitory computer-readable storage medium of claim 13 , wherein the one or more instructions further cause the processor to perform:

transmitting the previous CNAM by the content delivery device for display by the mobile device when the call is connecting the calling device and the mobile device.

16 . The non-transitory computer-readable storage medium of claim 13 , wherein the one or more instructions further cause the processor to perform:

transmitting the default CNAM by the content delivery device to the mobile device for display when the call is connecting the calling device and the mobile device.

17 . The non-transitory computer-readable storage medium of claim 13 , wherein the identifying whether the relationship exists, comprises: identifying contextual information associated with a previously logged transaction that identifies transaction information linked to the mobile device number and the calling device number, and wherein the assigning the CNAM to the call comprises: assigning the CNAM to a push API based on the identified contextual information.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 6, 2023
From: MURPHY, BRANDON WAYNE; SEELY, ROBERT COLLIN; JACOBI, AARON CHRISTOPHER; LAVIGNE, BENJAMIN MICHAEL; MCHENRY, MARK BRADLEY; GILLESPIE, JOHN COOPER; BECKHAM, MATTHEW JACK; SANCHEZ, KRISTEN CHIPOLLA; EDDY, LYNDSAY MICHELLE; CALLAWAY, JAY TODD
To: FIRST ORION CORP.
Reel/Frame 063872/0413 →
Continuity (3)
Continuation 17463421 · Aug 31, 2021
Continuation 16565157 · Sep 9, 2019
Related Publication 20230319183A1 · Oct 5, 2023
References Cited (30)
US 7200211B1 · Lemke · 2007 [cited by applicant]
US 8515037B2 · Ye · 2013 [cited by applicant]
US 8625760B1 · Peden et al. · 2014 [cited by applicant]
US 9203954B1 · Rensburg et al. · 2015 [cited by applicant]
US 9338289B1 · Goyal et al. · 2016 [cited by applicant]
US 10542140B1 · Tang · 2020 [cited by examiner]
US 11115522B2 · Murphy et al. · 2021 [cited by applicant]
US 11570295B2 · Murphy et al. · 2023 [cited by applicant]
US 11924373B2 · Murphy et al. · 2024 [cited by applicant]
US 20050031106A1 · Henderson · 2005 [cited by applicant]
US 20060002535A1 · Moss · 2006 [cited by examiner]
US 20070127656A1 · Citron et al. · 2007 [cited by applicant]
US 20070201684A1 · Boghani · 2007 [cited by applicant]
US 20090046839A1 · Chow et al. · 2009 [cited by applicant]
US 20090197583A1 · Penn et al. · 2009 [cited by applicant]
US 20110026689A1 · Metz · 2011 [cited by examiner]
US 20110201321A1 · Bonner · 2011 [cited by applicant]
US 20130044869A1 · Citron et al. · 2013 [cited by applicant]
US 20130084839A1 · Gosselin · 2013 [cited by examiner]
US 20130094643A1 · Österlund · 2013 [cited by applicant]
US 20150304490A1 · Huang et al. · 2015 [cited by applicant]
US 20150326691A1 · Efrati et al. · 2015 [cited by applicant]
US 20160301662A1 · Laux · 2016 [cited by examiner]
US 20160381215A1 · Goyal · 2016 [cited by examiner]
US 20170223065A1 · Fan et al. · 2017 [cited by applicant]
US 20190306322A1 · Bostick · 2019 [cited by examiner]
US 20200057946A1 · Singaraju · 2020 [cited by examiner]
US 20200151587A1 · Ahringer · 2020 [cited by examiner]
US 20200274964A1 · Ravichandran · 2020 [cited by examiner]
US 20210075885A1 · Hassan et al. · 2021 [cited by applicant]