# US 2023/0275995 A1 · Device, system and method for routing botnet calls to a botnet call-answer queue

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

- Number: US 2023/0275995 A1
- Document ID: US20230275995A1
- Status: Published application
- Kind: A1
- Application number: 18/015,991
- Filed: 2020-09-01
- Published: 2023-08-31
- Earliest claimed: 2020-09-01
- Assignees: Motorola Solutions, Inc.
- Applicants: Motorola Solutions, Inc.
- Inventors: Bing Qin LIM; Ming Yeh KOH; Wei Ling Cecilia LIAW; Christo YOHANNAN; Andrzej BUKOWSKI; Christopher S. GORDON; Moh Lim SIM
- Web page: https://patentgrep.com/patent/US20230275995A1

## CPC

- H04L 65/1079: {of unsolicited session attempts, e.g. SPIT}
- H04M 3/4365: {based on information specified by the calling party, e.g. priority or subject}
- H04M 1/663: Preventing unauthorised calls to a telephone set
- 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)}
- G10L 25/51: for comparison or discrimination
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- G10L: SPEECH ANALYSIS TECHNIQUES OR SPEECH SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING TECHNIQUES; SPEECH OR AUDIO CODING OR DECODING

## Abstract

A device, system and method for routing botnet calls to a botnet call-answer queue. A device, such as a call answering point (CAP) and/or a public-safety answering point (PSAP) router device, receives a call and determines an audio signature of the call. The device compares the audio signature of the call with one or more botnet audio signatures stored at a memory. In response to the audio signature of the call matching at least one of the one or more botnet audio signatures, the device: identifies the call as a botnet call that has been placed by a botnet; and cause the call to be routed to a botnet call-answer queue.

## Claims

### Claim 1

A method comprising:
receiving, at a call answering point (CAP) router device, a call;
determining, at the CAP router device, an audio signature of the call;
comparing, at the CAP router device, the audio signature of the call with one or more botnet audio signatures stored a memory;
in response to the audio signature of the call matching at least one of the one or more botnet audio signatures:
identifying, at the CAP router device, the call as a botnet call that has been placed by a botnet; and
causing, via the CAP router device, the call to be routed to a botnet call-answer queue.

### Claim 2 (depends on 1)

The method of claim 1, wherein the audio signature and the one or more botnet audio signatures comprise at least one of: respective identified voice signatures; respective identified audio content; and respective ambient audio signatures.

### Claim 3 (depends on 1)

The method of claim 1, further comprising, in response to the audio signature of the call matching at least one of the one or more botnet audio signatures:
causing, via the CAP router device, a notification to be transmitted to one or more of: a police device; and a service provider device.

### Claim 4 (depends on 1)

The method of claim 1, further comprising, in response to the audio signature of the call matching at least one of the one or more botnet audio signatures:
identifying an originating location of the botnet call.

### Claim 5 (depends on 1)

The method of claim 1, further comprising, in response to the audio signature of the call not matching at least one of the one or more botnet audio signatures:
causing, via the CAP router device, the call to be routed to a CAP operator device that includes an input device for manually identifying the call as a botnet-initiated call, such that when input is received from the input device, the call is routed to the botnet call-answer queue, a respective audio signature of the call is generated and stored at the memory as a botnet audio signature.

### Claim 6 (depends on 1)

The method of claim 1, further comprising, in response to the audio signature of the call not matching at least one of the one or more botnet audio signatures:
storing the audio signature at the memory;
counting further calls having respective audio signatures that match the audio signature; and
when a number of the further calls reaches a threshold number within a given time period:
identifying the audio signature as a botnet audio signature; and causing yet further calls having the botnet audio signature to be routed to the botnet call-answer queue.

### Claim 7 (depends on 1)

The method of claim 1, further comprising, in response to the audio signature of the call not matching at least one of the one or more botnet audio signatures:
determining that the call comprises one or more of a non-service initiated call and an anonymous call; and, in response:
storing the audio signature at the memory;
counting further calls having respective audio signatures that match the audio signature; and
when a number of the further calls reaches a threshold number:
identifying the audio signature as a given botnet audio signature at the memory; and
causing yet further calls having the given botnet audio signature to be routed to the botnet call-answer queue.

### Claim 8 (depends on 1)

The method of claim 1, wherein the botnet call-answer queue comprises a queue at which the botnet call is held indefinitely.

### Claim 9 (depends on 1)

The method of claim 1, wherein the botnet call-answer queue comprises a queue operated by one or more of law enforcement entity and a service provider entity.

### Claim 10 (depends on 1)

The method of claim 1, wherein at the botnet call-answer queue, analysis of the botnet call occurs, the analysis including one or more of:
identifying an originating location of the botnet call;
identifying a call identifier of the call; and
identifying a device identifier of an originating communication device.

### Claim 11

A device comprising:
a communication unit; and
a controller in communication with a memory and the communication unit, the controller configured to:
receive a call;
determine an audio signature of the call;
compare the audio signature of the call with one or more botnet audio signatures stored at the memory;
in response to the audio signature of the call matching at least one of the one or more botnet audio signatures:
identify the call as a botnet call that has been placed by a botnet; and
cause the call to be routed to a botnet call-answer queue.

### Claim 12 (depends on 11)

The device of claim 11, wherein the audio signature and the one or more botnet audio signatures comprise at least one of: respective identified voice signatures; respective identified audio content; and respective ambient audio signatures.

### Claim 13 (depends on 11)

The device of claim 11, wherein the controller is further configured to, in response to the audio signature of the call matching at least one of the one or more botnet audio signatures:
cause a notification to be transmitted to one or more of: a police device; and a service provider device.

### Claim 14 (depends on 11)

The device of claim 11, wherein the controller is further configured to, in response to the audio signature of the call matching at least one of the one or more botnet audio signatures:
identify an originating location of the botnet call.

### Claim 15 (depends on 11)

The device of claim 11, wherein the controller is further configured to, in response to the audio signature of the call not matching at least one of the one or more botnet audio signatures:
cause the call to be routed to a CAP operator device that includes an input device for manually identifying the call as a botnet-initiated call, such that when input is received from the input device, the call is routed to the botnet call-answer queue, a respective audio signature of the call is generated and stored at the memory as a botnet audio signature.

### Claim 16 (depends on 11)

The device of claim 11, wherein the controller is further configured to, in response to the audio signature of the call not matching at least one of the one or more botnet audio signatures:
e audio signature at the memory;
count further calls having respective audio signatures that match the audio signature; and
when a number of the further calls reaches a threshold number within a given time period: identify the audio signature as a botnet audio signature; and cause yet further calls having the botnet audio signature to be routed to the botnet call-answer queue.

### Claim 17 (depends on 11)

The device of claim 11, wherein the controller is further configured to, in response to the audio signature of the call not matching at least one of the one or more botnet audio signatures:
determine that the call comprises one or more of a non-service initiated call and an anonymous call; and, in response:
store the audio signature at the memory;
count further calls having respective audio signatures that match the audio signature; and
when a number of the further calls reaches a threshold number:
identify the audio signature as a given botnet audio signature at the memory; and
cause yet further calls having the given botnet audio signature to be routed to the botnet call-answer queue.

### Claim 18 (depends on 11)

The device of claim 11, wherein the botnet call-answer queue comprises a queue at which the botnet call is held indefinitely.

### Claim 19 (depends on 11)

The device of claim 11, wherein the botnet call-answer queue comprises a queue operated by one or more of law enforcement entity and a service provider entity.

### Claim 20 (depends on 11)

The device of claim 11, wherein at the botnet call-answer queue, analysis of the botnet call occurs, the analysis including one or more of:
identifying an originating location of the botnet call;
identifying a call identifier of the call; and
identifying a device identifier of an originating communication device.
