# US 6,243,453 B1 · Programmable call processing system and method

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

- Number: US 6,243,453 B1
- Document ID: US6243453B1
- Status: Granted
- Kind: B1
- Application number: 09/352,836
- Filed: 1999-07-13
- Granted: 2001-06-05
- Earliest claimed: 1996-07-17
- Assignees: Alcatel USA Sourcing, L.P.
- Inventors: James L. Bunch; Ronald A. Iovine; Samuel O. Perry, III; Leo J. Putchinski; Walter C. Robertson, Jr.; Ronald L. Ward
- Web page: https://patentgrep.com/patent/US6243453B1

## CPC

- H04Q 3/54533: {Configuration data, translation, passwords, databases}
- H04Q 3/0029: {Provisions for intelligent networking}
- H04Q 3/54583: {Software development, e.g. procedural, object oriented, software generation, software testing}
- H04Q 2213/13057: Object-oriented software
- H04Q 2213/13547: subscriber, e.g. profile, database, database access
- H04Q 2213/13548: call modeling, e.g. Basic Call State Model
- H04Q: SELECTING (switches, relays, selectors H01H; wireless communication networks H04W)

## Abstract

A programmable call processing system (52) provides a standard call processing process (80) performing call processing according to industry standard call models, at least one database (84, 86) storing call processing data accessible by the set of standard call processing process (80), and at least one customized call logic program (92) for implementing extended subscriber features on the telecommunications switching system (10, 30). Further, an application program interface (56, 94) provides access by the at least one customized call logic program (92) to the at least one call processing database (84, 86) and further interrupting the standard call processing process (80) to execute the customized call logic program (92).

## Claims

### Claim 1

A method of detecting a trigger condition during processing of a call, comprising:
identifying a particular point in a traversal of the call;
accessing a trigger rule item pointer associated with the particular point in the call traversal;
locating a trigger rule item in response to the trigger rule item pointer, the trigger rule item corresponding to a decision tree to identify the trigger condition;
accessing a criteria node associated with the trigger rule item, the criteria node including information to identify the trigger condition for its associated trigger rule item;
identifying a list of match values associated with the criteria node;
comparing the match values with information associated with the particular point in the call traversal;
accessing a trigger data index in response to one of the match values being successfully compared to the particular point in the call traversal;
determining an occurrence of the trigger condition in response to the trigger data index.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
resuming call processing of the call at the particular point in the call traversal in response to a null value for the trigger rule item pointer, the null value indicating that a trigger condition was not detected.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
accessing a trigger rule item index in response to not finding a match in the list of match values.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
resuming call processing of the call at the particular point in the call traversal in response to a null value for the trigger rule item index, the null value indicating that a trigger condition was not detected.

### Claim 5 (depends on 3)

The method of claim 3, further comprising:
locating a trigger rule item in response to a non-null value for the trigger rule item index.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
accessing a trigger rule item index in response to a null value for the trigger data index.

### Claim 7 (depends on 6)

The method of claim 6, further comprising:
resuming call processing of the call at the particular point in the call traversal in response to a null value for the trigger rule item index, the null value indicating that a trigger condition was not detected.

### Claim 8 (depends on 6)

The method of claim 6, further comprising:
locating another trigger rule item in response to a non-null value for the trigger rule item index.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
returning trigger data associated with the trigger data index, the trigger data determining further traversal of the call.

### Claim 10 (depends on 9)

The method of claim 9, further comprising:
generating a query message in response to the trigger data.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
transferring the query message to a service control point in response to the trigger data.

### Claim 12 (depends on 11)

The method of claim 11, wherein the query message includes a non-null value for either a global title translation field or a point code field in the query message according to the trigger data.

### Claim 13 (depends on 10)

The method of claim 10, further comprising:
transferring the query message to a call logic program.

### Claim 14 (depends on 13)

The method of claim 13, wherein the query message includes null values for a global title translation field, a point code field, and a subsystem number field within the query message.