Determining an international destination address

• US 7,774,502 B2
• Filed: 10/26/2004
• Issued: 08/10/2010
• Est. Priority Date: 10/25/2000
• Status: Active Grant

• Current Assignee: Syniverse ICX LLC
• Original Assignee: Syniverse ICX Corp. (Syniverse Corp.)
• Inventors: Reddy, Rajesh Tanamala Srivivas, Murthy, Vikas Sanathana, Shetty, Mony
• Primary Examiner(s): PHILLIPS, HASSAN A
• Application Number:
  US10/972,712
• Publication Number:
  US 20050055461A1
• Time in Patent Office: 2,114 Days
• Field of Search: None
• US Class Current: 709/245
• 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. A method for determining an international destination address for a text message, comprising:

electronically receiving a text message identifying a valid requested address, wherein the valid requested address (a) comprises at least a portion of an international telephone address, (b) originates from a source network, (c) does not comprise a network identifier, wherein a network identifier is required to route the text message to a proper destination address, and (d) is associated with a destination party at a destination network that is different from the source network;

in response to receiving the text message identifying the valid requested address;

(a) automatically determining the proper destination address based on the valid requested address, wherein the proper destination address comprises at least the valid requested address, a network identifier, and a device identifier, and

(b) electronically sending the text message to the proper destination address.

2. The method of claim 1, wherein the proper destination address further includes a carrier identifier and a gateway identifier.

3. The method of claim 2, wherein the proper destination address further includes a plurality of device-capability identifiers.

4. The method of claim 1, wherein said automatically determining the proper destination address further comprises:

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

in response to a determination that the carrier type is a single-match carrier type, setting a proper destination address associated with the destination party as a valid destination address; and

in response to a determination that the carrier type is a multiple-match carrier type, validating each of a plurality of candidate destination addresses associated with the destination party to determine whether one or more of the plurality of candidate destination addresses are the valid destination address.

5. The method of claim 4, wherein said electronically sending the text message includes electronically sending the text message to the proper destination address from the plurality of candidate destination addresses that are validated by said validating.

6. The method of claim 4, wherein said validating comprises:

sending an availability request to each candidate destination address from a plurality of candidate destination addresses, the plurality of candidate destination addresses being correlated with a destination party;

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

recording, for each received response, a value associated with the candidate destination address associated with that received response, the value indicating (a) one from the group of a valid destination address and (b) an invalid destination address based on the received response associated with that candidate destination address.