# US 2004/0057419 A1 · Optimistic caching for address translations

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

- Number: US 2004/0057419 A1
- Document ID: US20040057419A1
- Status: Published application
- Kind: A1
- Application number: 10/254,484
- Filed: 2002-09-24
- Published: 2004-03-25
- Earliest claimed: 2002-09-24
- Assignees: Intel Corporation
- Inventors: Michael Stanford
- Web page: https://patentgrep.com/patent/US20040057419A1

## CPC

- H04M 1/2535: {adapted for voice communication over an Internet Protocol [IP] network (Voice over Internet Protocol (VoIP) network equipment and services H04M7/006; implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] H04L69/16)}
- H04M 7/006: {Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer (H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42)}
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)

## Abstract

A method and apparatus to manage a call connection is described.

## Claims

### Claim 1

A method to manage a call connection, comprising:
receiving a first identifier for a call;
retrieving a second identifier associated with said first identifier;
Initiating a first call connection using said second identifier;
determining whether said second identifier is valid; and
completing said call connection in accordance with said determination.

### Claim 2 (depends on 1)

The method of claim 1, wherein said first identifier comprises an E. 164 number.

### Claim 3 (depends on 1)

The method of claim 1, wherein said second identifier comprises one of a telephone number, a network address, an Internet Protocol (IP) address, an electronic mail address, a facsimile number, a pager number, and a mobile telephone number.

### Claim 4 (depends on 1)

The method of claim 1, wherein said determining comprises:
sending a request to an Authoritative Directory (AD) server;
receiving a third identifier in response to said request; and
comparing said second and third identifiers.

### Claim 5 (depends on 4)

The method of claim 4, further comprising determining that said second identifier is valid if said second and third identifiers match.

### Claim 6 (depends on 5)

The method of claim 5, wherein said sending comprises:
converting said first identifier into a fourth identifier; and
sending said fourth identifier to said AD server.

### Claim 7 (depends on 6)

The method of claim 6, wherein said third identifier comprises one of a telephone number, a network address, an Internet Protocol (IP) address, an electronic mail address, a facsimile number, a pager number, and a mobile telephone number.

### Claim 8 (depends on 7)

The method of claim 7, wherein said fourth identifier is an ENUM Uniform Resource Identifier (URI).

### Claim 9 (depends on 1)

The method of claim 1, wherein said completing comprises:
determining that said second identifier is invalid;
terminating said first call connection; and
initiating a second call connection using a third identifier.

### Claim 10 (depends on 1)

The method of claim 1, wherein said retrieving comprises:
searching a cache using said first identifier; and
retrieving said second identifier from said cache.

### Claim 11 (depends on 1)

The method of claim 1, wherein said second identifier comprises an identifier from a Naming Authority Pointer (NAPTR) Domain Name System (DNS) resource record.

### Claim 12

An article comprising:
a storage medium;
said storage medium including stored instructions that, when executed by a processor, result in managing a call connection by receiving a first identifier for a call, retrieving a second identifier associated with said first identifier, initiating a first call connection using said second identifier, determining whether said second identifier is valid, and completing said call connection in accordance with said determination.

### Claim 13 (depends on 12)

The article of claim 12, wherein the stored instructions, when executed by a processor, further result in said determining by sending a request to an AD server, receiving a third identifier in response to said request, and comparing said second and third identifiers.

### Claim 14 (depends on 12)

The article of claim 12, wherein the stored instructions, when executed by a processor, further result in determining that said second identifier is valid if said second and third identifiers match.

### Claim 15 (depends on 13)

The article of claim 13, wherein the stored instructions, when executed by a processor, further result in said sending by converting said first identifier into a fourth identifier, and sending said fourth identifier to said AD server.

### Claim 16 (depends on 12)

The article of claim 12, wherein the stored instructions, when executed by a processor, further result in said completing by determining that said second identifier is invalid, terminating said first call connection, and initiating a second call connection using a third identifier.

### Claim 17 (depends on 12)

The article of claim 12, wherein the stored instructions, when executed by a processor, further result in said retrieving by searching a cache using said first identifier, and retrieving said second identifier from said cache.

### Claim 18

A system, comprising:
a computing platform adapted to manage a call connection;
said platform being further adapted to receiving a first identifier for a call, retrieving a second identifier associated with said first identifier, initiating a first call connection using said second identifier, determining whether said second identifier is valid, and completing said call connection in accordance with said determination.

### Claim 19 (depends on 18)

The system of claim 18, wherein said platform is further adapted to perform said determining by sending a request to an AD server, receiving a third identifier in response to said request, and comparing said second and third identifiers.

### Claim 20 (depends on 18)

The system of claim 18, wherein said platform is further adapted to determine that said second identifier is valid if said second and third identifiers match.

### Claim 21 (depends on 19)

The system of claim 19, wherein said platform is further adapted to perform said sending by converting said first identifier into a fourth identifier, and sending said fourth identifier to said AD server.

### Claim 22 (depends on 18)

The system of claim 18, wherein said platform is further adapted to perform said completing by determining that said second identifier is invalid, terminating said first call connection, and initiating a second call connection using a third identifier.

### Claim 23 (depends on 18)

The system of claim 18, wherein said platform is further adapted to perform said retrieving by searching a cache using said first identifier, and retrieving said second identifier from said cache.

### Claim 24

A system to manage a call connection, comprising:
a call terminal to receive an E. 164 number;
a Call Management Module (CMM) to retrieve an identifier associated with said E. 164 number, and initiate a first call connection using said identifier;
an AD server to validate said identifier, with said CMM terminating said first call connection if said identifier is invalid.

### Claim 25 (depends on 24)

The system of claim 24, wherein said CMM initiates a second call connection if said identifier is invalid.

### Claim 26 (depends on 24)

The system of claim 24, wherein said CMM converts said identifier to an ENUM URI prior to validation by said AD server.
