# US 11,115,522 B2 · Customization of CNAM information for calls placed to mobile devices

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 11,115,522 B2
- Document ID: US11115522B2
- Status: Granted
- Kind: B2
- Application number: 16/565,077
- Filed: 2019-09-09
- Published: 2021-03-11
- Granted: 2021-09-07
- Earliest claimed: 2019-09-09
- Assignees: First Orion Corp.
- Applicants: First Orion Corp.
- Inventors: Brandon Wayne Murphy; Robert Collin Seely; Aaron Christopher Jacobi; Benjamin Michael Lavigne; Mark Bradley McHenry; John Cooper Gillespie; Matthew Jack Beckham; Kristen Chipolla Sanchez; Lyndsay Michelle Eddy; Jay Todd Callaway
- Web page: https://patentgrep.com/patent/US11115522B2

## CPC

- H04M 3/42059: {Making use of the calling party identifier}
- H04L 45/20: {Hop count for routing purposes, e.g. TTL}
- H04L 61/106: across networks, e.g. mapping telephone numbers to data network addresses
- H04M 3/2254: {in networks}
- H04M 3/42042: {Notifying the called party of information on the calling party (details within substation equipment H04M1/57, signalling details H04Q3/72)}
- H04M 3/436: Arrangements for screening incoming calls {, i.e. evaluating the characteristics of a call before deciding whether to answer it (based on the calling party profile H04M3/42059; based on location H04M3/42348; based on presence H04M3/42365; diversion H04M3/54)}
- H04M 15/06: Recording class or number of calling {, i.e. A-party} or called party {, i.e. B-party}
- H04M 2201/14: Delay circuits; Timers
- H04M 2203/2038: Call context notifications
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

One example method of operation may include identifying a call from a calling device destined for a mobile device, responsive to identifying a calling device number assigned to the calling device, accessing a call content application programming interface (API), operated by a content delivery device, configured to deliver to the mobile device a first caller identification name (CNAM) or a second CNAM, assigned to the calling device number, determining a context assigned to a mobile device number assigned to the mobile device, selecting one of the first CNAM and the second CNAM based on the context, and assigning the selected CNAM to the call.

## Claims

### Claim 1

A method comprising:
identifying, via a content delivery device, a call from a calling device destined for a called device;
identifying, via the content delivery device, a calling device number assigned to the calling device;
receiving, via the content delivery device, a first caller identification name (CNAM) or a second CNAM from a call content application programming interface (API), where one of the first CNAM or the second CNAM is to be assigned to the calling device number and provided to a called device;
determining whether to assign the first CNAM or the second CNAM to the calling device number based on contextual information associated with a previously logged transaction identifying transaction information linked to the called device number and the calling device number;
assigning the first CNAM or the second CNAM to a push API based on the identified contextual identification;
receiving, via the content delivery device, the assignment of one of the first CNAM or the second CNAM; and
communicating, via the content delivery device, the assigned CNAM to a carrier network for communication to the called device.

### Claim 2 (depends on 1)

The method of claim 1, comprising:
displaying the assigned CNAM on the called device.

### Claim 3 (depends on 1)

The method of claim 1, comprising:
identifying a time-to-live (TTL) parameter associated with the assigned CNAM; and
when the time and date are active, applying the assigned CNAM to the call.

### Claim 4 (depends on 3)

The method of claim 3, wherein the TTL comprises at least one of:
a start date and a start time, and a period of time until the TTL expires.

### Claim 5 (depends on 1)

The method of claim 1, wherein the context comprises:
one or more parameters linked to the assigned CNAM and associated with the called device.

### Claim 6 (depends on 1)

The method of claim 1, wherein each of the first CNAM and the second CNAM comprise:
a one to fifteen character alphanumeric message.

### Claim 7 (depends on 1)

The method of claim 1, wherein each of the first CNAM and the second CNAM is an electronic CNAM (ECNAM) that comprises at least one of:
a one to fifteen character alphanumeric message, a uniform resource locator (URL) link, image data, video data, and audio data.

### Claim 8

A system comprising:
a computing device configured to:
identify a call from a calling device destined for a called device;
identify a calling device number assigned to the calling device;
receive a first caller identification name (CNAM) or a second CNAM from a call content application programming interface (API), where one of the first CNAM or the second CNAM is to be assigned to the calling device number and provided to the called device;
determine whether to assign the first CNAM or the second CNAM to the calling device number based on contextual information associated with a previously logged transaction identifying transaction information linked to the called device number and the calling device number;
assign the first CNAM or the second CNAM to a push API based on the identified contextual identification;
receive the assignment of one of the first CNAM or the second CNAM; and
communicate the assigned one of the first CNAM or the second CNAM to a carrier network for communication to the called device.

### Claim 9 (depends on 8)

The system of claim 8, wherein the computing device is further configured to:
display the assigned CNAM on the called device.

### Claim 10 (depends on 8)

The system of claim 8, wherein the computing device is further configured to:
identify a time-to-live (TTL) parameter associated with the assigned CNAM; and
when the time and date are active, apply the selected CNAM to the call.

### Claim 11 (depends on 10)

The system of claim 10, wherein the TTL comprises at least one of:
a start date and a start time, and a period of time until the TTL expires.

### Claim 12 (depends on 8)

The system of claim 8, wherein the context comprises:
one or more parameters linked to the assigned CNAM and associated with the called device.

### Claim 13 (depends on 8)

The system of claim 8, wherein each of the first CNAM and the second CNAM comprise:
a one to fifteen character alphanumeric message.

### Claim 14 (depends on 8)

The system of claim 8 wherein each of the first CNAM and the second CNAM is an electronic CNAM (ECNAM) that comprises at least one of:
a one to fifteen character alphanumeric message, a uniform resource locator (URL) link, image data, video data and audio data.

### Claim 15

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, via a content delivery device, a call from a calling device destined for a called device;
identifying, via the content delivery device, a calling device number assigned to the calling device;
receiving, via the content delivery device, a first caller identification name (CNAM) or a second CNAM from a call content application programming interface (API), where one of the first CNAM or the second CNAM is to be assigned to the calling device number and provided to a called device;
determining whether to assign the first CNAM or the second CNAM to the calling device number based on contextual information associated with a previously logged transaction identifying transaction information linked to the called device number and the calling device number;
assigning the first CNAM or the second CNAM to a push API based on the identified contextual identification;
receiving, via the content delivery device, the assignment of one of the first CNAM or the second CNAM; and
communicating, via the content delivery device, the assigned CNAM to a carrier network for communication to the called device.

### Claim 16 (depends on 15)

The non-transitory computer readable storage medium of claim 15, wherein the one or more instructions further cause the processor to perform:
displaying the assigned CNAM on the called device.

### Claim 17 (depends on 15)

The non-transitory computer readable storage medium of claim 15, wherein the one or more instructions further cause the processor to perform:
identifying a time-to-live (TTL) parameter associated with the selected CNAM; and
when the time and date are active, applying the selected CNAM to the call.

### Claim 18 (depends on 17)

The non-transitory computer readable storage medium of claim 17, wherein the TTL comprises at least one of:
a start date and a start time, and a period of time until the TTL expires.

### Claim 19 (depends on 15)

The non-transitory computer readable storage medium of claim 15, wherein the context comprises:
one or more parameters linked to the assigned CNAM and associated with the called device.

### Claim 20 (depends on 15)

The non-transitory computer readable storage medium of claim 15, wherein each of the first CNAM and the second CNAM comprise:
a one to fifteen character alphanumeric message.