This invention relates to enabling communications between subscribers and message applications by means of wireless devices. This invention primarily supports the wireless and standardized Short Message Service (SMS); however, it can be applied to any mobile messaging technology.
Currently, the most pervasive wireless data technology in the U.S. and Canada is short message services (SMS). SMS is primarily used to support the following types of subscriber data services:
Each of these data services uses distinctly different addressing schemes:
Examples of value-added messaging applications are those that allow the subscriber to play games, answer quiz questions, or receive promotional offers.
Wireless carriers can use short codes to deliver text services. A wireless carrier that wants to deploy a pull application will select a sequence of digits that are not a valid NANP number. Their network equipment, usually an SMSC (Short Messaging Service Center) can then be programmed to detect messages sent to these short codes and map them to message services. This solution is very customer friendly and has been used successfully by many wireless carriers. But this technique is not practical for an external entity like a brand. An external entity will want to use the same short code across all wireless carriers to reach their target population. Unfortunately, short codes are not yet standardized and carriers do not use the same numbering plan for short codes.
Another method is to use a wireless mobile device, such as a PCMCIA (Personal Computer Memory Card International Association) card that is connected to a computer device. Instead of having a subscriber receiving the messages, the messages are processed by an automated service. The service is identified by the directory number used by the mobile device, and hence is a regular NANP number. With the recent introduction of interoperability between wireless carriers, the Mobile Originated (MO) message from most wireless carrier will be received by the mobile device. Responses can be sent back using SMTP (Simple Mail Transfer Protocol) or SMPP (Short Message Peer To Peer) directly to the subscriber wireless provider, so effectively the mobile device is only needed for MO messages. But the drawbacks of this technique are many. Mobile devices do not have the scalability required of most campaigns. They usually can only handle a few messages per second. Their reliability is not high as these are consumer grade equipment. Worse, there is currently a lot of latency in the current US interoperability implementation, which impacts the usability of the solution. This is simply not a viable approach for most marketing campaigns.
A network element can also directly receive messages sent to it using wireless carrier SS7 (Signaling System 7) connections. For example, network elements within the PSTN (Public Switched Telecommunications/Telephone Network) SS7 network that combines the functionality of an HLR (Home Location Register), MSC (Mobile Switching Center) and SMSC. It can be configured to receive messages to any valid NANP range assigned to it. This solution is highly scalable. But it has drawbacks. Such equipment, purchased new, can be quite expensive. In addition, it requires that the operator of this system be part of the SS7 network. Few wireless carriers allow third parties to be part of the SS7 network. In addition, this system, being part of the PSTN needs to have the same kind of reliability and operations team required of the PSTN. This means it's expensive to maintain.
In summary, none of the existing methods is practical in markets that have not standardized short codes or achieved subscriber acceptance of the short codes as SACs. As will be described in further detail below, the present invention is a unique and innovative solution that overcomes the aforementioned problems of the prior art.
Certain advantages of the present invention include, but are not limited to the following:
Further objects and advantages of this present invention will become apparent from a consideration of the drawings and ensuing description.
Subscribers can access independent message based application platforms using SACs for routing. The use of SACs enables mobile subscribers from any wireless network in World Zone 1 to originate messages for interaction with value-added message-based applications. These applications can reside within a wireless carrier network or external to the network. The use of SACs has many advantages, such as ubiquitous access, roaming access and culturally accepted address familiarity to subscribers. SACs can also be used by mobile subscribers as the mobile terminating address for messages destined for message-based application systems. As in standard dialable voice calls, SACs require special treatment when used as message addresses.
The use of SACs for message addressing and message routing enables access to application platforms that use SMS as communications transport. Any mobile subscriber can access these applications since the wireless networks and SMS support the address format. This address format is supported by both Global System for Mobile communications (GSM) and American National Standards Institute-41 (ANSI-41) (i.e., Time Division Multiple Access (TDMA) and Code Division Multiple Access (CDMA) networks). The accessible applications could be either within existing wireless carrier networks, or can be provided independent of these wireless networks. The applications can also be operated and maintained by external Application Service Providers (ASPs).
In one embodiment, the format of the SAC will be of the form N000-NXX-XXXX (where N is any number 2-9, and X is any number 0-9) as defined by the Alliance for Telecommunications Industry Solution. These codes have been designated for non-geographic Service Access Codes for a variety of services, such as toll-free (800-numbers) and premium pay numbers (900-numbers). 500-numbers have been defined specifically for wireless Personal Communications Services (PCS). In an alternative embodiment, any NANP number that is designated for non-geographic services can be used, even if they do not match the current N000-N-XX format.
As a purely functional solution, use of SAC-based addresses enables a great deal of freedom for the deployment of value-added mobile messaging applications. These applications can be ubiquitous and seamless, as they are dependent only on data network connectivity (e.g., the Internet), which is essentially ubiquitous today. SAC-based addresses (for example, 500-NXX-X) are especially appropriate for value-added mobile messaging services, since 500-numbers have been defined for PCS.
SAC-based addresses for the use of value-added mobile messaging services does not preclude the use of these numbers for voice calls as well. Mobile Identification Numbers (MINs for ANSI-41) and Mobile Station ISDN Numbers (MSISDNs for GSM) are both MDNs and based on the NANP and wireless subscribers use their unique numbers as addresses for both voice calls and messaging. This has the advantage of enabling applications to be message-based, call-based or a hybrid of both, with no functional changes to existing wireless networks.
This invention applies to any mobile message based services that can use the public telephony addressing scheme, for example SMS, Enhanced Messaging Services (EMS), Multimedia Messaging Services (MMS), Internet Protocol (IP) based technologies using ENUM (RFC 2916), etc.
Aspects, features and advantages of exemplary embodiments of the present invention will become better understood with regard to the following description in connection with the accompanying drawing(s). It should be apparent to those skilled in the art that the described embodiments of the present invention provided herein are illustrative only and not limiting, having been presented by way of example only. All features disclosed in this description may be replaced by alternative features serving the same or similar purpose, unless expressly stated otherwise. Therefore, numerous other embodiments of the modifications thereof are contemplated as falling within the scope of the present invention as defined herein and equivalents thereto. Hence, use of absolute terms, such as, for example, “will,” “will not,” “shall,” “shall not,” “must,” and “must not,” are not meant to limit the scope of the present invention as the embodiments disclosed herein are merely exemplary.
Turning to
There are multiple exemplary embodiments of a message center system. In one exemplary embodiment, the message center system is composed of a message center 106 and a message center gateway 108. The message center maintains routing tables to deliver the message. These routing tables map the logical wireless routing address (for example, 500-NXX-XXX) to the physical or logical data network address (e.g., an internet protocol address or domain name service address) of the message application receiving the message. The message center gateway is configured to queue and deliver the message by means of the data network 110 to the message application 112. In another exemplary embodiment, the message center 110 and the message center gateway 108 are the same component. The presented embodiments for the message center system are illustrative only and not limited to the ones presented. Numerous other embodiments of the message center system 104 are contemplated as falling within the scope of this invention.
Turning to
To deploy message applications that make use of this invention, the following exemplary steps are carried out:
Any protocol that's mutually agreed upon with the carrier can be used. Short Message Peer-to-Peer (SMPP) is one such common protocol.
In an alternative embodiment, thus invention is used in any country that has reserved part of its numbering plan for non-geographic based services using logical numbered addresses.
The subscriber initiates a mobile-originated message to a SAC address (for example a 500-NX-XXXX) (step 200). The message is forwarded to the serving base station via the message channel (202). The mobile-originated message is forwarded to the wireless network 102. The message is forwarded directly to the message center system 104 for physical routing to the message destination (204). The message center system 104 maintains routing tables to deliver the message. These routing tables map the logical routing address (for example, 500-NXX-XXXX) to the physical or logical data network address (e.g., an internet protocol address, or a DNS address) of the application receiving the message. The message center system 104 routes the message to the data network 110 based on the translated data network (e.g., IP) address (step 206). The message is encapsulated within lower layers of the protocol and routed as a layer 3 IP packets. The data network 110 (e.g., public Internet or private intranet) routes the message to the destination where the mobile message application(s) 112 resides (step 208). The mobile message application(s) 112 receive(s) the message and processes it accordingly (step 210,
Having now described one or more exemplary embodiments of the invention, it should be apparent to those skilled in the art that the foregoing is illustrative only and not limiting, having been presented by way of example only. All the features disclosed in this specification (including any accompanying claims, abstract, and drawings) may be replaced by alternative features serving the same purpose, and equivalents or similar purpose, unless expressly stated otherwise. Therefore, numerous other embodiments of the modifications thereof are contemplated as falling within the scope of the present invention as defined by the appended claims and equivalents thereto.
For example, the techniques may be implemented in hardware or software, or a combination of the two. In one embodiment, the techniques are implemented in computer programs executing on programmable computers that each include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device and one or more output devices. Program code is applied to data entered using the input device to perform the functions described and to generate output information. The output information is applied to one or more output devices.
Each program may be implemented in a high level procedural or object oriented programming language to communicate with a computer system, however, the programs can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language.
Each such computer program may be stored on a storage medium or device (e.g., CD-ROM, hard disk or magnetic diskette) that is readable by a general or special purpose programmable computer for configuring and operating the computer when the storage medium or device is read by the computer to perform the procedures described in this document. The system may also be considered to be implemented as a computer-readable storage medium, configured with a computer program, where the storage medium so configured causes a computer to operate in a specific and predefined manner.
This application claims the benefit of priority of U.S. application No. 60/396,959, filed Jul. 18, 2002, the entire contents of which are incorporated by reference as if set forth at length herein.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/US03/23643 | 7/18/2003 | WO | 00 | 2/23/2007 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2004/010267 | 1/29/2004 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
5768358 | Venier et al. | Jun 1998 | A |
5974133 | Fleischer, III et al. | Oct 1999 | A |
5999525 | Krishnaswamy et al. | Dec 1999 | A |
6011834 | Jeong | Jan 2000 | A |
6073165 | Narasimhan et al. | Jun 2000 | A |
6175618 | Shah et al. | Jan 2001 | B1 |
6226373 | Zhu et al. | May 2001 | B1 |
6275490 | Mattaway et al. | Aug 2001 | B1 |
6611516 | Pirkola et al. | Aug 2003 | B1 |
6678265 | Kung et al. | Jan 2004 | B1 |
6956831 | Mahr | Oct 2005 | B1 |
7003307 | Kupsh et al. | Feb 2006 | B1 |
7010303 | Lewis et al. | Mar 2006 | B2 |
7068772 | Widger et al. | Jun 2006 | B1 |
7079524 | Bantukul et al. | Jul 2006 | B2 |
7116994 | Hatch | Oct 2006 | B2 |
7120441 | Tuomi | Oct 2006 | B1 |
7164488 | Henry | Jan 2007 | B2 |
7366530 | McCann et al. | Apr 2008 | B2 |
7403788 | Trioano | Jul 2008 | B2 |
8155677 | Hewes | Apr 2012 | B2 |
20020016175 | Marce | Feb 2002 | A1 |
20020019243 | Zhang et al. | Feb 2002 | A1 |
20020173319 | Fostick | Nov 2002 | A1 |
20020196924 | Dahari | Dec 2002 | A1 |
20040014454 | Burgess | Jan 2004 | A1 |
20040102201 | Levin | May 2004 | A1 |
20040142707 | Midkiff et al. | Jul 2004 | A1 |
20040244102 | Benzon et al. | Dec 2004 | A1 |
20040266462 | Chava | Dec 2004 | A1 |
20050003837 | Midkiff | Jan 2005 | A1 |
20050020270 | Buckley | Jan 2005 | A1 |
20050277430 | Meisl | Dec 2005 | A1 |
Number | Date | Country | |
---|---|---|---|
20080119210 A1 | May 2008 | US |
Number | Date | Country | |
---|---|---|---|
60396959 | Jul 2002 | US |