# US 2025/0158945 A1 · Using commercially available user devices for mms messaging capacity testing

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

- Number: US 2025/0158945 A1
- Document ID: US20250158945A1
- Status: Published application
- Kind: A1
- Application number: 18/507,997
- Filed: 2023-11-13
- Published: 2025-05-15
- Earliest claimed: 2023-11-13
- Assignees: DISH Wireless L.L.C.
- Applicants: DISH Wireless L.L.C.
- Inventors: Dawood Shahdad; Prakash Patel
- Web page: https://patentgrep.com/patent/US20250158945A1

## CPC

- H04L 51/10: Multimedia information
- H04L 51/212: using filtering or selective blocking
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Described herein are embodiments of testing MMS messaging capacity of a wireless network using commercially available client devices. An exemplary method includes receiving, at a multimedia messaging service center (MMSC) of the wireless network, a plurality of seed MMS messages from one or more client devices. Each of the plurality of seed MMS messages is targeted at one of a plurality of destination numbers, none of the plurality of destination numbers is associated with any database that the MMSC uses for routing determination, and each of the plurality of seed MMS messages gets stuck in an infinite loop and keeps generating MMS messages. The method further includes capturing at least a portion of the seed messages and the generated MMS messages; determining that the number of captured MMS messages reaches a predetermined number; and in response to such determination, terminating each of the infinite loops.

## Claims

### Claim 1

A method of testing multimedia messaging service (MMS) messaging capacity of a wireless network and performed by a multimedia messaging service center (MMSC) of the wireless network, the method comprising:
receiving a plurality of seed MMS messages from one or more client devices, wherein each of the plurality of seed MMS messages is targeted at one of a plurality of destination numbers, wherein none of the plurality of destination numbers is associated with any database that the MMSC uses for routing determination, wherein each of the plurality of seed MMS messages gets stuck in a respective infinite loop of a plurality of infinite loops associated with the plurality of seed MMS messages, and keeps generating MMS messages;
capturing at least a portion of the seed messages and the generated MMS messages;
determining that a number of captured MMS messages reaches a predetermined threshold; and
in response to determining that the number of captured MMS messages reaches a predetermined number, terminating each of the infinite loops.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
monitoring and analyzing utilization of one or more system resources of the MMSC prior to terminating the infinite loops, wherein the system resources include CPU, memory, network bandwidth, and storage.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
performing an analysis of the captured MMS messages in view of one or more of a plurality of metrics, wherein the plurality of metrics include a message throughput and an average response time.

### Claim 4 (depends on 1)

The method of claim 1, where the any database is one of an E.164 number mapping system (ENUM) or a home subscriber server (HSS).

### Claim 5 (depends on 4)

The method of claim 4, wherein each of the loops is created when the MMSC receives a negative response from the ENUM and receives an MMS message from an intercarrier gateway.

### Claim 6 (depends on 5)

The method of claim 5, wherein the terminating of each of the loops includes:
skip querying the ENUM after the MMS message is routed back to the MMSC from the intercarrier gateway.

### Claim 7 (depends on 6)

The method of claim 6, wherein the terminating of each of the loops further includes:
checking an incoming interface and an outgoing interface of an MMS message passing through the MMSC; and
in response to determining that both the incoming interface and the outgoing interface of the MMS message is an MM4 interface, blocking the MMS message.

### Claim 8 (depends on 1)

The method of claim 1, wherein each of the one or more client devices is a subscriber of the wireless network.

### Claim 9 (depends on 1)

The method of claim 1, wherein each of the plurality of destination numbers is a phone number that is a fictional number, or a real number that used to be associated with a subscriber of the wireless network.

### Claim 10

A system for testing multimedia messaging service (MMS) capacity of a wireless network, comprising:
one or more processors;
one or more memories that are coupled to the one or more processors and storing program instructions, which, when executed by the one or more processors, cause the system to perform operations comprising:
receiving a plurality of seed MMS messages from one or more client devices, wherein each of the plurality of seed MMS messages is targeted at one of a plurality of destination numbers, wherein none of the plurality of destination numbers is associated with any database that a multimedia messaging service center (MMSC) of the wireless network uses for routing determination, wherein each of the plurality of seed MMS messages gets stuck in a respective infinite loop of a plurality of infinite loops associated with the plurality of seed MMS messages, and keeps generating MMS messages;
capturing at least a portion of the seed messages and the generated MMS messages;
determining that the number of captured MMS messages reaches a predetermined threshold; and
in response to determining that the number of captured MMS messages reaches a predetermined number, terminating each of the infinite loops.

### Claim 11 (depends on 10)

The system of claim 10, wherein the operations further comprise:
monitoring and analyzing utilization of one or more system resources of the MMSC prior to terminating the infinite loops, wherein the system resources include CPU, memory, network bandwidth, and storage.

### Claim 12 (depends on 10)

The system of claim 10, wherein the operations further comprise:
performing an analysis of the captured MMS messages in view of one or more of a plurality of performance metrics, wherein the plurality of performance metrics include a message throughput and an average response time.

### Claim 13 (depends on 10)

The system of claim 10, wherein the any database is one of an E.164 number mapping system (ENUM) or a home subscriber server (HSS).

### Claim 14 (depends on 13)

The system of claim 13, wherein each of the loops is created when the MMSC receives a negative response from the ENUM and receives an MMS message from an intercarrier gateway.

### Claim 15 (depends on 14)

The system of claim 14, wherein the terminating of each of the loops includes:
skip querying the ENUM after the MMS message is routed back to the MMSC from the intercarrier gateway.

### Claim 16 (depends on 15)

The system of claim 15, wherein the terminating of each of the loops further includes:
checking an incoming interface and an outgoing interface of an MMS message passing through the MMSC; and
in response to determining that both the incoming interface and the outgoing interface of the MMS message is an MM4 interface, blocking the MMS message.

### Claim 17 (depends on 10)

The system of claim 10, wherein each of the one or more client devices is a subscriber of the wireless network.

### Claim 18 (depends on 10)

The system of claim 10, wherein each of the plurality of destination numbers is a phone number that is a fictional number or a real number that used to be associated with a subscriber of the wireless network.

### Claim 19

A non-transitory computer-readable storage medium storing program instructions for testing multimedia messaging service (MMS) capacity of a wireless network, wherein the program instructions, when executed by one or more processors of a multimedia messaging service center (MMSC) of the wireless network, cause the MMSC to perform operations comprising:
receiving a plurality of seed MMS messages from one or more client devices, wherein each of the plurality of seed MMS messages is targeted at one of a plurality of destination numbers, wherein none of the plurality of destination numbers is associated with any database that a multimedia messaging service center (MMSC) of the wireless network uses for routing determination, wherein each of the plurality of seed MMS messages gets stuck in a respective infinite loop of a plurality of infinite loops associated with the plurality of seed MMS messages, and keeps generating MMS messages;
capturing at least a portion of the seed messages and the generated MMS messages;
determining that the number of captured MMS messages reaches a predetermined threshold; and
in response to determining that the number of captured MMS messages reaches a predetermined number, terminating each of the infinite loops.

### Claim 20 (depends on 19)

The non-transitory computer-readable storage medium of claim 19, wherein the operations further comprise:
monitoring and analyzing utilization of one or more system resources of the MMSC prior to terminating the infinitive loops, wherein the system resources include CPU, memory, network bandwidth, and storage.
