Application interface for global mobile message delivery

• US 8,107,470 B2
• Filed: 10/31/2007
• Issued: 01/31/2012
• Est. Priority Date: 10/31/2007
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Yahoo! Inc. (Apollo Global Management, Inc.)
• Inventors: Zhu, Tong, Jiang, Zhaowei Charlie, Kim, Ben, Ho, Kenneth Tsz, Gan, Jiuhe, Yerubandi, Venkata Narasimha Rao, Woods, Daniel John
• Primary Examiner(s): Vu, Huy
• Assistant Examiner(s): Renner, Brandon
• Application Number:
  US11/981,980
• Publication Number:
  US 20090109978A1
• Time in Patent Office: 1,553 Days
• Field of Search: 455456-466
• US Class Current: 370/389
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements

Abstract

A device, system, and method are directed towards communicating mobile information over a network. A mobile message (MM) is generated by an Internet Protocol (IP) enabled application interface. The MM may include advertising information. The MM is received at a routing server and comprises a destination phone number and/or advertising information. If the MM is determined to be locally processed, the routing server selectively routes the MM to a destination carrier associated with the destination phone number. If the MM is determined to be remotely processed, the MM is recursively forwarded until the MM reaches another routing server associated with the destination phone number. The other routing server is configured to selectively route the MM to the destination carrier. A response MM may be received at a boundary routing server. The response MM may be sent to the API if at least a portion of the response MM matches information associated with the MM.

Claims

1. A system for communicating information over a network, comprising:

a plurality of application interfaces configured to be communicated over the network;

a routing server located in a geographic region, wherein the routing server is in communication with the plurality of application interfaces, and wherein the routing server is configured to perform operations comprising;

receiving a mobile message (MM) at the routing server, prior to receiving the MM at a Message Service Center (MSC), from at least one of the plurality of application interfaces, wherein the MM comprises a destination phone number;

determining at the routing server whether the MM is to be locally processed by a MSC within the geographic region or remotely processed by a MSC in another geographic region by analyzing the destination phone number to determine a geographic location associated with the destination phone number;

if the MM is determined to be locally processed by a MSC in the geographic region, determining to route the MM to a local aggregator or to a MSC; and

if the MM is determined to be remotely processed by a MSC in another geographic region, recursively forwarding the MM to another routing server located within the other geographic region associated with the destination phone number;

the local aggregator in communication with the routing server, wherein the local aggregator is configured to forward the MM to a plurality of carriers;

the MSC in communication with the routing server, wherein the MSC is configured to send the MM to a destination carrier, wherein the destination carrier is configured to send a version of the MM to a mobile device for display on the mobile device; and

the other routing server in communication with the routing server, wherein the other routing server is configured to perform operations comprising;

storing a session mapping between at least a portion of a sender phone number, at least a portion of the destination phone number, and at least one of a plurality of application interfaces, wherein the sender phone number comprises a short-code and an extension;

selectively routing the MM to another local aggregator or another MSC;

receiving, from the MSC, another MM addressed to the short-code;

retrieving the session mapping based on a match of at least a portion of another sender phone number of the other MM with the at least a portion of the destination phone number, and a match of at least a portion of another destination phone number of the other MM with the at least the portion of the sender phone number; and

forwarding the other MM to the at least one of the plurality of application interfaces based on the session mapping.

2. The system of claim 1, wherein selectively routing further comprises:

determining the destination carrier based on a Subscriber Number (SN) portion of the destination phone number.