Address recognition database

• US 9,143,477 B2
• Filed: 10/26/2004
• Issued: 09/22/2015
• Est. Priority Date: 10/25/2000
• Status: Active Grant

• Current Assignee: Syniverse ICX LLC
• Original Assignee: Syniverse ICX Corp. (Syniverse Corp.)
• Inventors: Murthy, Vikas Sanathana, Reddy, Rajesh Tanamala Srivivas, Shetty, Mony
• Primary Examiner(s): Pham, Khanh
• Assistant Examiner(s): HARPER, ELIYAH STONE
• Application Number:
  US10/972,388
• Publication Number:
  US 20050086378A1
• Time in Patent Office: 3,983 Days
• Field of Search: 707/104.1, 707/100, 707/10, 707/999.002, 707/999.003, 707/999.004, 707/705, 707/802, 707/999.101, 707/999.102, 707/609
• US Class Current: 1/1
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 61/4547 for personal communications, i.e. using a personal identifier
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A valid destination address is determined. An availability request is sent to each destination address from a set of destination addresses. The destination addresses are correlated with a destination party. At least one response to the sent availability requests is received. Each received response is uniquely associated with its own destination address from the destination addresses. Each received response indicates either a valid destination address or an invalid destination address. For each received response, a value associated with the destination address that is associated with that received response is recorded. The value indicates either a valid destination address or an invalid destination address based on the received response associated with that destination address.

Claims

1. An automated method for developing a universal address-recognition database having a plurality of carrier prefixes, comprising:

electronically reading, via a first computing entity, a computer database having a plurality of carrier prefixes, each carrier prefix being associated with an operating company and a network type;

mapping, via the first computing entity, for each carrier prefix from a subset of carrier prefixes from the plurality of carrier prefixes, the associated operating company and associated network type to a current carrier identifier and a current network identifier, respectively, based on at least one public carrier map; and

dynamically updating, for each remaining carrier prefix from the plurality of carrier prefixes, said associated current carrier identifier and said current network identifier, wherein said dynamically updating comprises;

electronically transmitting availability requests over one or more carrier communication networks to a plurality of computing entities respectively associated with each candidate destination address from a plurality of candidate destination addresses, the plurality of candidate destination addresses being correlated with a destination party;

electronically receiving at least one response to the sent availability requests originating from at least one of the plurality of computing entities, each received response (a) being uniquely associated with its own candidate destination address from the plurality of candidate destination addresses and (b) indicating one selected from the group comprising of (i) a valid destination address and (ii) an invalid destination address; and

electronically recording in the computer database, for each received response, a value associated with the candidate destination address associated with that received response, the value indicating one from the group of a valid destination address and an invalid destination address based on the received response associated with that candidate destination address.

3. The method of claim 1, wherein said dynamically updating comprises:

determining a destination country associated with the requested address; and

verifying that the requested address is not an invalid address based on at least a portion of the requested address and based on at least one predetermined invalid address associated with the determined destination country.

5. The method of claim 1, wherein at least one of the plurality of computing entities comprises a text-capable device.

6. The method of claim 1, wherein at least one of the plurality of computing entities is a wireless device.

2. An automated method for developing a universal address-recognition database having a plurality of carrier prefixes, comprising:

electronically reading a computer database having a plurality of carrier prefixes, each carrier prefix being associated with an operating company and a network type;

mapping, for each carrier prefix from a subset of carrier prefixes from the plurality of carrier prefixes, the associated operating company and associated network type to a current carrier identifier and a current network identifier, respectively, based on at least one public carrier map; and

dynamically updating in the computer database, for each remaining carrier prefix from the plurality of carrier prefixes, said an associated current carrier identifier and said current network identifier, wherein said dynamically updating comprises;

determining a carrier type based on a requested address associated with a destination party;

in response to the determined carrier type comprising a single-match carrier type, setting a destination address associated with the destination party as a valid destination address; and

in response to the determined carrier type comprising a multiple-match carrier type, validating each of a plurality of candidate destination addresses associated with the destination party, wherein validating comprises (a) determining which of the plurality of candidate destination addresses is the valid destination address by sending an availability request to each candidate destination address over one or more carrier communication networks and (b) setting the determined candidate destination address as the valid destination address.

4. The method of claim 2, wherein the multiple-match carrier type includes at least one from the group of an embedded-carrier-information destination address and portable destination address.