# US 2019/0356635 A1 · Detecting aggressive or attacking behaviors in ims sip signaling

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

- Number: US 2019/0356635 A1
- Document ID: US20190356635A1
- Status: Published application
- Kind: A1
- Application number: 16/121,249
- Filed: 2018-09-04
- Published: 2019-11-21
- Earliest claimed: 2018-05-18
- Assignees: T-Mobile USA, Inc.
- Applicants: T-Mobile USA, Inc.
- Inventors: Hsin-Fu Henry Chiang; Mohammed Al-Mehdar
- Web page: https://patentgrep.com/patent/US20190356635A1

## CPC

- H04L 63/0281: {Proxies}
- H04L 43/16: Threshold monitoring
- H04L 63/1408: {by monitoring network traffic (monitoring network traffic per se H04L43/00)}
- H04L 63/1466: {Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks}
- H04L 65/1073: Registration or de-registration
- H04L 65/1104: Session initiation protocol [SIP]
- H04W 12/122: Counter-measures against attacks; Protection against rogue devices
- H04W 12/61: Time-dependent
- H04L 65/1016: IP multimedia subsystem [IMS]
- H04L 65/1045: Proxies, e.g. for session initiation protocol [SIP]
- H04L 65/1046: Call controllers; Call servers
- H04W 88/02: Terminal devices
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Systems and methods for preventing aggressive or abusing signaling on networks are disclosed. When a user equipment (UE), such as a cell phone, sends a request to a network (e.g., a REGISTER, SUBSCRIBE, or PUBLISH request), a network entity can start a “guard timer” and/or increment a “guard counter.” The guard timer can comprise a predetermined amount of time within which one or more additional requests from the same UE will be ignored. Similarly, the guard timer can be used in conjunction with a guard counter. The guard counter can enable a UE to make a predetermined number of requests before the guard timer expires. If the UE exceeds the guard counter before the guard timer expires, any additional requests will be ignored. When the guard timer expires, the guard counter is reset to zero to enable the UE to make additional requests.

## Claims

### Claim 1

A method comprising:
receiving, at a transceiver of a network entity, a first request from a user equipment (UE);
sending, at the transceiver, a first response to the UE;
starting, at a processor of the network entity, a guard timer in response to receiving the first request;
receiving, at the transceiver, a second request from the UE;
determining, at the processor, whether the guard timer has expired; and either:
sending, at the transceiver, a second reply to the UE in response to the second request when the guard timer has expired; or
deleting, at the processor, the second request when the guard timer has not expired.

### Claim 2 (depends on 1)

The method of claim 1, wherein the second request is deleted, the method further comprising:
receiving, at the transceiver, a third request from the UE;
determining, at the processor, that the guard timer has expired; and
sending, at the transceiver, a second reply to the UE in response to the third request.

### Claim 3 (depends on 1)

The method of claim 1, wherein the second request is deleted, the method further comprising:
receiving, at the transceiver, a third request from the UE;
determining, at the processor, that the guard timer has not expired; and
deleting, at the processor, the third request.

### Claim 4 (depends on 1)

The method of claim 1, wherein the first request and the second request comprise one of a REGISTER, SUBSCRIBE, or PUBLISH session initiation protocol (SIP) message.

### Claim 5 (depends on 1)

The method of claim 1, wherein the network entity comprises a proxy call session control function (P-CSCF).

### Claim 6 (depends on 1)

The method of claim 1, wherein the network entity comprises a serving call session control function (S-CSCF).

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
determining, at the processor, whether the UE is registered with a network associated with the network entity; and either:
setting, with the processor, the guard timer equal to a first time when the UE is registered with the network; or
setting, with the processor, the guard timer equal to a second time when the UE is not registered with the network;
wherein the first time is shorter than the second time.

### Claim 8

A method comprising:
receiving, at a transceiver of a network entity, a first request from a user equipment (UE);
sending, at the transceiver, a first response to the UE;
starting, at a processor of the network entity, a guard timer in response to the first request;
incrementing, at a processor, a guard counter by one in response to the first request;
receiving, at the transceiver, a second request from the UE;
incrementing, at the processor, the guard counter by one in response to the second request;
determining, at the processor, whether the guard counter has been exceeded and whether the guard timer has expired; and either:
sending, at the transceiver, a second reply to the UE in response to the second request when the guard counter has not been exceeded or the guard timer has expired; or
deleting, with the processor, the second request when the guard counter has been exceeded and the guard counter has not expired.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
determining, at the processor, whether the UE is registered with a network associated with the network entity; and either:
setting, at the processor, the guard counter equal to a first number when the UE is registered with the network; or
setting, at the processor, the guard counter equal to a second number when the UE is not registered with the network;
wherein the first number is higher than the second number.

### Claim 10 (depends on 8)

The method of claim 8, wherein the guard counter has not been exceeded, the method further comprising:
receiving, at the transceiver, a third request from the UE;
incrementing, at the processor, the guard counter by one in response to the third request;
determining, at the processor, that the guard counter has not been exceeded; and
sending, at the transceiver, a third response to the UE in response to the third request.

### Claim 11 (depends on 8)

The method of claim 8, wherein the guard counter has not been exceeded, the method further comprising:
receiving, at the transceiver, a third request from the UE;
incrementing, at the processor, the guard counter by one in response to the third request;
determining, at the processor, that the guard counter has been exceeded; and
deleting, at the processor, the third request.

### Claim 12 (depends on 8)

The method of claim 8, further comprising:
determining, at the processor, that the guard timer has expired; and
resetting, at the processor, the guard counter to zero.

### Claim 13 (depends on 8)

The method of claim 8, wherein the network entity comprises a proxy call session control function (P-CSCF).

### Claim 14

A network entity comprising:
a transceiver to send and receive wired transmissions, wireless transmissions, or both wired transmissions and wireless transmissions;
memory storing at least a signal monitoring application; and
a processor in communication with at least the transceiver and the memory, the signal monitoring application including computer-executable instructions to cause the processor to:
receive, at the transceiver, a first request from a user equipment (UE);
send, at the transceiver, a first response to the UE;
start, at the processor, a guard timer in response to receiving the first request;
receive, at the transceiver, a second request from the UE;
determine, at the processor, whether the guard timer has expired; and either:
send, at the transceiver, a second reply to the UE in response to the second request when the guard timer has expired; or
delete, at the processor, the second request when the guard timer has not expired.

### Claim 15 (depends on 14)

The network entity of claim 14, wherein the second request is deleted, the signal monitoring application further causing the processor to:
receive, at the transceiver, a third request from the UE;
determine, at the processor, that the guard timer has expired; and
send, at the transceiver, a second reply to the UE in response to the third request.

### Claim 16 (depends on 14)

The network entity of claim 14, wherein the second request is deleted, the signal monitoring application further causing the processor to:
receiving, at the transceiver, a third request from the UE;
determining, at the processor, that the guard timer has not expired; and
deleting, at the processor, the third request.

### Claim 17 (depends on 14)

The network entity of claim 14, wherein the network entity comprises a proxy call session control function (P-CSCF).

### Claim 18 (depends on 14)

The network entity of claim 14, wherein the network entity comprises a serving call session control function (S-CSCF).

### Claim 19 (depends on 14)

The network entity of claim 14,
wherein the first request comprises a REGISTER request;
wherein the first response comprises a SIP 200 OK; and
wherein the signal monitoring application further causes the processor to:
set, with the processor, the guard timer equal to a registered guard timer.

### Claim 20 (depends on 14)

The network entity of claim 14,
wherein the first request comprises a REGISTER request;
wherein the first response comprises an error code; and
wherein the signal monitoring application further causes the processor to:
set, with the processor, the guard timer equal to an unregistered guard timer.
