# US 2015/0149648 A1 · Systems and Methods for Processing SIP Message Flows

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

- Number: US 2015/0149648 A1
- Document ID: US20150149648A1
- Status: Published application
- Kind: A1
- Application number: 14/087,311
- Filed: 2013-11-22
- Published: 2015-05-28
- Earliest claimed: 2013-11-22
- Assignees: Genband US LLC
- Applicants: Genband US LLC
- Inventors: Paul Phillips; Ian Macfarlane; Sumit Garg
- Web page: https://patentgrep.com/patent/US20150149648A1

## CPC

- H04L 65/1104: Session initiation protocol [SIP]
- H04L 65/1045: Proxies, e.g. for session initiation protocol [SIP]
- H04L 65/1086: {session scope modification}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems, methods, and computer program products are provided for modifying a Session Initiation Protocol (SIP) messages. The method includes providing a scripting-type computer programming language that includes contexts that reference pre-defined portions of data of a SIP message and variables that store data associated with a SIP message flow. An interface for configuring rules to be executed when processing SIP messages is provided. Each rule includes an action that describes a modification to be made to a particular SIP message. When a SIP message is received, it is parsed to determine at least a context of a portion of the message. The parsing includes associating the portion of the message with a particular context. It is then determined whether a rule should be applied to the data associated referenced by the contexts, and if so, the SIP message is modified based on the actions associated with the rule.

## Claims

### Claim 1

A computer-implemented method for modifying a Session Initiation Protocol (SIP) message included in a series of SIP messages associated with a SIP message flow comprising:
providing a scripting-type computer programming language with contexts that reference pre-defined portions of data of a SIP message and variables for storing data associated with a particular SIP message flow;
providing an interface for configuring one or more rules by the scripting language, wherein the rules are executed when processing one or more SIP messages in the SIP message flow, and wherein each of the one or more rules includes at least one action, the action describing a modification to be made to a particular SIP message in the SIP message flow;
receiving, by at least one or more processors, a particular SIP message included in the series of SIP messages;
parsing the particular SIP message to determine one or more contexts corresponding to one or more particular portions of the particular SIP message, the parsing including associating a particular portion of the particular SIP message with a particular pre-defined context;
determining whether criteria associated with each rule applies to at least the data referenced by one of the contexts; and
when data referenced by a particular context meets the criteria associated with a particular rule, modifying the particular SIP message based on the one or more actions associated with the particular rule.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein a particular rule includes at least one trigger, wherein one or more actions associated with the rule are processed when a particular SIP message meets a criterion that satisfies the trigger.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein a particular rule includes at least one trigger, wherein one or more actions associated with the rule are processed when a particular variable meets a criterion that satisfies the trigger.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein modifying the particular SIP message includes modifying a portion of the SIP message based on a trigger associated with the action's rule.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, wherein one or more rules are associated with a profile, the profile associated with a scope of processing SIP messages where the one or more rules are to be processed.

### Claim 6 (depends on 5)

The computer-implemented method of claim 5, wherein the profile is associated with a particular scope including a system processing level, a realm processing level, a group processing level, or an endpoint processing level.

### Claim 7 (depends on 6)

The computer-implemented method of claim 6, wherein the profile is further associated with a scope including a SIP message ingress point of a particular processing level.

### Claim 8 (depends on 5)

The computer-implemented method of claim 5, wherein the profile is further associated with a scope including a SIP message egress point of a particular processing level.

### Claim 9 (depends on 1)

The computer-implemented method of claim 1, wherein a particular rule includes a trigger that is required to be satisfied in order to execute the particular rule's associated actions, and wherein satisfying the trigger depends on a portion of data includes in a SIP message and is selected from a SIP request line, a SIP status line, a SIP header, a SIP generic-body, or a SIP message body headers.

### Claim 10

A computer system for modifying a Session Initiation Protocol (SIP) message included in a SIP message flow comprising:
a rule definition engine configured to:
provide a scripting-type computer programming language with contexts that reference pre-defined portions of data of a SIP message and variables for storing data associated with a particular SIP message flow;
provide a user interface for configuring one or more rules by the scripting language, wherein the rules are executed when processing one or more SIP messages in the SIP message flow, and wherein each of the one or more rules includes at least one action, the action describing a modification to be made to a particular SIP message in the SIP message flow; and
a rule processor configured to:
receive a particular SIP message included in the series of SIP messages;
parse the particular SIP message to determine one or more contexts corresponding to one or more particular portions of the particular SIP message, the parsing including associating a particular portion of the particular SIP message with a particular pre-defined context;
determine whether criteria associated with each rule applies to at least the data referenced by one of the contexts; and
when data referenced by a particular context meets the criteria associated with a particular rule, modify the particular SIP message based on the one or more actions associated with the particular rule.

### Claim 11 (depends on 10)

The computer system of claim 10, wherein a particular rule includes at least one trigger, and wherein one or more actions associated with the rule are processed when a particular SIP message meets a criterion that satisfies the trigger.

### Claim 12 (depends on 10)

The computer system of claim 10, wherein a particular rule includes at least one trigger, and wherein one or more actions associated with the rule are processed when a particular variable meets a criterion that satisfies the trigger.

### Claim 13 (depends on 10)

The computer system of claim 10, wherein the rule processor is further configured to modify a portion of the SIP message based on a trigger associated with the action's rule.

### Claim 14 (depends on 10)

The computer system of claim 10, wherein one or more rules are associated with a profile, the profile associated with a scope of processing SIP messages where the one or more rules are to be processed.

### Claim 15 (depends on 14)

The computer system of claim 14, wherein the profile is associated with a particular scope including a system processing level, a realm processing level, a group processing level, or an endpoint processing level.

### Claim 16 (depends on 15)

The computer system of claim 15, wherein the profile is further associated with a scope including a SIP message ingress point of a particular processing level.

### Claim 17 (depends on 14)

The computer system of claim 14, wherein the profile is further associated with a scope including a SIP message egress point of a particular processing level.

### Claim 18 (depends on 10)

The computer system of claim 10, wherein a particular rule includes a trigger that is required to be satisfied in order to execute the particular rule's associated actions, and wherein satisfying the trigger depends on a portion of data includes in a SIP message and is selected from a SIP request line, a SIP status line, a SIP header, a SIP generic-body, or a SIP message body headers.

### Claim 19

A session boarder controller for modifying a Session Initiation Protocol (SIP) message included in a SIP message flow comprising:
a rule definition engine configured to:
provide a scripting-type computer programming language, the scripting language including contexts that are configured to reference pre-defined portions of data of a SIP message and variables that are configured to store data based on processing a SIP message flow;
provide a user interface for configuring one or more rules by the scripting language, wherein each rule includes at least one trigger that determines the SIP messages the rule is applied to, and at least one action that describes how to process the SIP message; and
store rules entered by a user in a rule database such that the rules are retrieved and applied to SIP messages as the SIP messages are processed by the session boarder controller; and
a rule processor configured to:
receive a particular SIP message included in the SIP message flow;
parse the particular SIP message to determine one or more contexts that each correspond pre-defined portions of the particular SIP message;
determine whether the trigger associated with a particular rule applies to the particular SIP message, wherein the determining is based on comparing the trigger to at least one context referencing the particular SIP message; and
when data referenced by a particular context meets the trigger associated with the particular rule, modify the particular SIP message based on one or more actions associated with the particular rule.

### Claim 20 (depends on 19)

The session boarder controller of claim 19, wherein the rule processor is further configured to modify one or more variables associated with the SIP message flow based on actions associated with the particular rule.
