Method and system for efficiently routing messages

Information

  • Patent Grant
  • 8543146
  • Patent Number
    8,543,146
  • Date Filed
    Wednesday, September 28, 2011
    13 years ago
  • Date Issued
    Tuesday, September 24, 2013
    11 years ago
Abstract
Efficient routing of a message over a data network. A first communication device sends a message to a telemetry gateway or short message arbitrator. The telemetry gateway or short message arbitrator determines the communication protocol of the first communication device and the communication protocol of a second communication device. The telemetry gateway or short message arbitrator converts the message to a data format compatible with the second communication device, wherein the message is converted to one of at least three different communication protocols. The telemetry gateway or short message arbitrator then forwards the message for receipt by the second communication device. The telemetry gateway or short message arbitrator can convert and forward the message without completing a store and forward process.
Description
FIELD OF THE INVENTION

The present invention relates to the exchange of short messages between a telemetry gateway and a remote location, and more particularly to eliminating delays associated with communicating short messages through conventional short message center platforms.


BACKGROUND OF THE INVENTION

Short Message Service (SMS) is an inherent capability of most digital wireless telecommunications systems. The radio technologies associated with each of the digital wireless telecommunications systems are technically incompatible at the radio signal layer, but most are compatible at the intersystem SS7 transport layer. Currently, the differing RF technologies, e.g., time division multiple access (TDMA), code division multiple access (CDMA), and global system for mobile telecommunications (GSM), have at least partial technical compatibility over the telephone industry's SS7 inter-networking system. The partial compatibility of these RF technologies is possible because the basic transport format is specified in the SS7 standard; however, many of the messaging details are implementation specific.


Even though it is possible for current short message service center platforms (SMSC) to support all of these multiple protocols, typically, an installed SMSC only supports the protocol of the cellular telecommunication system into which it is installed. For example, if the SMSC is installed into an IS136 type TDMA system, the SMSC supports only the TDMA protocol. Similarly, if the SMSC is installed into a GSM system, then the SMSC supports only the GSM protocol. In other words, although most current SMSC's can interface with any of the currently popular digital cellular systems, the SMSC's do so on an individual basis, not all simultaneously.


For example, in one network, the nodes communicate using different data formatting standards, such as integrated services digital network (ISDN) and the Japanese X.50 standard. Each of the nodes is connected to a format converter. The format converter acts as a bi-directional converter for converting between two data formats and thus allows communication between the two nodes.


The format converter reformats the data formatted in the X.50 standard into the ISDN format. The format converter accomplishes the conversion by storing the incoming X.50 data in an aligned data RAM with offsets, to provide an appropriate alignment among the frames of the data. Then, a format conversion module reformats the data into the ISDN format one byte at a time.


In another network, a subscriber in an electronic messaging network can access messages in a variety of formats. A subscriber may receive messages through a variety of types of equipment, such as a voice mail system, an e-mail system, a facsimile machine and a telephone, all connected to a wireline network. The subscriber may access these messages through a pager, a cellular telephone, or a personal digital assistant, each connected to a different wireless network. The subscriber selects the wireline or wireless network and media format to be used for delivering messages or notifying a subscriber that a message has been received.


For example, the subscriber may elect to have notification of a voice mail or facsimile receipt directed to the personal digital assistant (PDA) in the form of an e-mail message. In accordance with the method of the network, the subscriber's selection is implemented through the personal intercommunications inter-networking system, which performs the appropriate data conversion from one protocol to another and delivers the e-mail message.


In yet another network, an intelligent signaling transfer point (ISTP) is included in a telephone network with a database for storing call processing control information. Calls from one station on the network to another are either passed through or intercepted at the ISTP and screened in accordance with criteria stored in the database, such as time of day, a certain originating area or caller, or a specified call count value.


In still another network, a data collection device is provided for use with any one of the following: TDMA; CDMA; frequency division multiple access (FDMA); GSM; and personal access communications systems (PACS) technologies. But, the data collection device does not use multiple such technologies in a single system. These systems and methods only teach conversion between two specific formats.


A further limitation with conventional SMS systems is that the SMS data transmissions are handled by the SMSC. The SMSCs use the address information contained within the data transmission to communicate with Home Location Registers (“HLRs”) and route the data to the correct recipient. The SMS text messages can originate and terminate at cellular mobile radiotelephones or at other external messaging entities coupled to the cellular network such as email, voicemail, and web-based messaging systems.


SMS data transmissions are routed from the SMSC to the recipient via one or more switches. Once an SMS data packet arrives at the receiving device, the message is extracted from its packet and formatted for delivery. For example, if the receiving unit is a cellular mobile radiotelephone, the unit formats the message for display on the unit's display screen. Alternatively, if the receiving unit is an external messaging system, an SMSC can format the message for transmission within an email message for delivery to a user external to the cellular telephone system.


The SMSCs are deployed by cellular carriers and serve the customers within the carrier's private network. For example, FIGS. 5 and 6 illustrate conventional SMS systems 500 and 600 using SMSCs operated by a local and regional carrier, respectively. In each of the conventional systems illustrated in FIGS. 5 and 6, the SMSCs 525 and 625 receive and store messages from radios 505 and 605. The SMSCs determine the destinations for the messages through a set of queries. Once there is available bandwidth, the SMSC can deliver the messages to the appropriate destination. SMSCs 525 and 625 can also receive messages from external systems, such as an email system, that are destined for radios 505 and 605. The SMSCs 525 and 625 query the HLRs 520 and 620 to determine the locations of the destination radios 505 and 605. Once there is available bandwidth, the SMSCs 525 and 625 can deliver the messages to radios 505 and 605. Significantly, all messages transmitted within each of systems 500 and 600 must use the same communication protocol. Conventional SMSCs 525 and 625 generally are not equipped to convert messages having different communication protocols.



FIGS. 7 and 8 illustrate conventional systems 700 and 800 for communicating roaming messages between different networks. FIG. 7 illustrates a home SMSC 730 coupled to HLR 735 that transmits messages to and receives messages from switch 715. FIG. 8 illustrates system 800 where a local SMSC 825 and an SMS clearinghouse 830 are used to communicate with a home SMSC 835. In each of systems 700 and 800, the switch or the SMSCs send a set of queries to the destination network in order to transmit messages. Furthermore, although the roaming messages are transmitted between different networks, the format of the messages is the same.


The SMSC of the conventional networks illustrated in FIGS. 5, 6, 7, and 8 acts as a “store and forward” system for the SMS data transmissions. The SMSC determines the routing for the data transmission and places the data in a queue for delivery to a cellular mobile radiotelephone or other messaging device. One shortcoming of conventional SMS systems is the delay in delivering the data transmissions queued at the SMSC. Typical delays for delivering messages can last minutes or hours.


One of the causes for the delay is that SMS messages are often assigned a lower delivery priority as compared to data transmissions containing voice communications. The low priority assigned to SMS messages stored in a queue at the SMSC causes a delay in their delivery. This delay is particularly noticeable when a carrier lacks sufficient bandwidth on its network. A further cause for delay are the inefficient steps an SMSC takes to route and deliver a data transmission. For example, the SMSC queries the HLR each time it is delivering a message to a mobile communication device. The HLR is a database of profiles for subscribers comprising account and service information.


Accordingly, there is a need in the art for a system that can efficiently route SMS messages from originators to recipients. Specifically, there is a need in the art to communicate more efficiently with serving switches and avoid the delays caused by an SMSC. A communication platform is needed that delivers messages promptly instead of storing them for later delivery when there is available bandwidth. The needed communication platform should also eliminate unnecessary steps as part of the communication process. There is a further need for a communication platform that can communicate with remote stations that use different digital cellular or personal communication formats.


SUMMARY OF THE INVENTION

The method and system disclosed herein is capable of efficiently routing messages without the delay typically associated with conventional technology. In an exemplary embodiment, a telemetry gateway can perform certain functions of conventional SMS systems to support the delivery of communications from incompatible networks. The telemetry gateway may communicate over a SS7 inter-networking system. It further may convert and forward messages without performing a store and forward process as required by conventional technology.


In an exemplary embodiment, a telemetry gateway can receive a message from a radio communication device; convert the message from one of several standard messaging protocols to a protocol compatible with a second communication device, such as a message service provider; and transmit the message to the second communication device. This transmission can be performed by the telemetry gateway without the store and forward delay associated with conventional technology.


In another exemplary embodiment, the telemetry gateway may receive a message from a communication device, such as a service provider; query a MSC for routing information for the message; convert the message to one of at least three different formats; and transmit the message to the MSC for delivery to a recipient without the use of a store and forward process. The recipient may be a radio communication device or other mobile device.


In a further exemplary embodiment, a short message arbitrator may provide efficient and rapid delivery of a short message. The short message arbitrator can receive a message from a first device for delivery to a second device; access a database containing a profile for the first device and the second device; analyze whether the first device and the second device communicate using incompatible data formats; and if so, convert the message at the short message arbitrator from the first format to one of at least three different data formats.


Once the message is converted, the short message arbitrator can forward the message for receipt by the second device. The step of analyzing whether the first device and the second device communicate use incompatible data formats may be performed by determining a mobile switch center for the second device; determining a class of service for the first device; determining a class of service for the second device; and determining a type of transport to use between the short message arbitrator and the second device. By determining these features, the short message arbitrator can properly prepare the message for delivery by converting the incompatible data format into a format compatible with the second device.


The above and other aspects of the system and method will be described below in connection with the drawing set and the appended specification and claim set.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram of an interconnect system according to an exemplary embodiment of the present invention.



FIG. 2 is a block diagram of an exemplary short message arbitrator of the system illustrated in FIG. 1.



FIG. 3 is a flow diagram illustrating an exemplary communications method used by the CCL to transmit data to the remote locations.



FIG. 4 is a flow diagram illustrating an exemplary communications method used by the remote locations to transmit data to the CCL.



FIG. 5 is a block diagram illustrating a prior art system for communication using a local carrier SMSC.



FIG. 6 is a block diagram illustrating a prior art system for communicating using a regional carrier SMSC.



FIG. 7 is a block diagram illustrating a prior art system for communicating where a home carrier has a direct roaming agreement with a local carrier.



FIG. 8 is a block diagram illustrating a prior art system for communicating where a local carrier uses a clearing house SMSC for roaming data.



FIG. 9 is a block diagram illustrating a system for communicating using a telemetry gateway according to an exemplary embodiment of the present invention.



FIG. 10A is a flow diagram illustrating an exemplary communications method for a message originating at a mobile radio.



FIG. 10B is a ladder diagram illustrating the sequence of communications for a message originating at a mobile radio as described in FIG. 10A according to an exemplary embodiment of the present invention.



FIG. 11A is a flow diagram illustrating an exemplary communications method for a message terminating at a mobile radio.



FIG. 11B is a ladder diagram illustrating the sequence of communications for a message terminating at a mobile radio as described in FIG. 11A according to an exemplary embodiment of the present invention.





DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

The present invention is directed to a system and method for communicating among digital cellular systems of multiple formats. A telemetry gateway allows external messaging systems to send short messages to and receive short messages from multiple remote locations using different digital cellular or PCS standards. The telemetry gateway can convert inbound short messages from the typical communication formats used in conventional wireless networks to a common telemetry protocol for forwarding to external messaging service providers. The telemetry gateway can convert outbound short messages from the common telemetry protocol to the format of the destination radio communication device. The telemetry gateway also performs certain functions of conventional SMSCs and HLRs to provide for faster and more efficient delivery of short messages.


The present invention can be implemented in a variety of different embodiments. The first exemplary embodiment described herein uses a short message arbitrator (“SMA”) to intercept, convert, and transmit messages of varying formats. The second exemplary embodiment described herein uses the telemetry gateway which is capable of both converting short messages of different formats as well as transmitting and receiving messages more quickly and efficiently than conventional SMS systems.


Exemplary SMA Embodiment


FIG. 1 shows an exemplary system for providing a flexible bi-directional data transport between a CCL 100 and one or more remote locations using wireless technologies. The CCL 100 sends and receives data to and from remote locations 123, 124, 125 and 126. Data from the CCL 100 is transferred to the SMA 104 using a public voice/data transport 102 over data circuits 101 and 103.


The SMA 104 converts the CCL's data to the proper format for transport to MSC's 109, 110, 117 and 119. The SMA 104 utilizes two routes for delivering the CCL's data to MSC's 109, 110, 117, and 119. The SMA 104 routes the CCL's data to one of the MSC's 109, 110, 117, and 119 by: 1) using a data circuit 105 to an SS7/IS41 Network 106, then over a data circuit (107, 108, 115 or 116) to the MSC (109, 110, 117, or 119) that is intended to receive the transmitted data; or 2) using a data circuit 103 back to the public voice/data transport 102, then over a data circuit (111, 112, 118, or 120) to the MSC (109, 110, 117, or 119) that is intended to receive the transmitted data.


Depending on the wireless access method used at the remote location, the CCL's data is routed to the selected wireless market. For advanced mobile phone service (AMPS) wireless communications, the data is transported from the MSC 109 to an AMPS radio 113 and finally to the remote location 123. For time division multiple access (TDMA) wireless communications, the data is transported from the MSC 117 to a TDMA radio 121 and finally to the remote location 125. For code division multiple access (CDMA) wireless communications, the data is transported from the MSC 119 to a CDMA radio 122 and finally to the remote location 126. For global system for mobile telecommunications (GSM), the data is transported from the MSC 110 to a GSM radio 114 and finally to the remote location 124.


The system of FIG. 1 provides for the bi-directional transport of data between a CCL 100 and its remote locations (123, 124, 125, or 126) using a wireless link (Cellular or PCS). The CCL 100 can use one or more methods to deliver data to the SMA 104. The various methods employ a variety of communication system is components. Below are four examples:


1) a dial-up data connection via a voice circuit 101 to the public voice/data transport 102 (public switched telephone network), then over the voice circuit 103;


2) a dial-up or dedicated data circuit 101 to the public voice/data transport 102 (Internet) then over the data circuit 103;


3) a dedicated data circuit 101 to public voice/data transport 102 (frame-relay private network) then over the data circuit 103; and


4) an ISDN circuit 101 to public voice/data transport 102 (public switched telephone network), then over the ISDN circuit 103.


After the SMA 104 receives the data from the CCL 100, it uses an identifying characteristic, such as the mobile identification number (MIN) or international mobile station identifier (IMSI), that was received with the data, to retrieve the CCL's profile 130 from a SMA database 128. The SMA determines the following from the CCL profile: 1) the MSC (109, 110, 117, or 119) serving the remote radio (113, 114, 121 or 122); 2) the wireless access method used in the MSC's market; 3) the CCL's class of service; and 4) the type of transport to use between the SMA 104 and the selected MSC (109, 110, 117, or 119). Based upon the information retrieved from the database, the SMA determines whether any alterations are required to the data or identifying characteristic to make the data compatible with a technologically dissimilar receiving unit or system.


The CCL's class of service may include one of the following: “CELLEMETRY” data service; short message system (SMS); asynchronous digital data; or data over circuit switched voice cellular. “CELLEMETRY” data service is available to AMPS (analog and digital) radios, SMS and asynchronous digital data are available to digital radios (CDMA, GSM and TDMA), and circuit switched voice cellular is available in all methods of wireless access. In addition, those skilled in the art will appreciate that other classes of service may be used with the CCL 100 of the present invention.


For simplicity only one CCL 100 is illustrated in FIG. 1. However, the SMA can support multiple CCL's. Each CCL served by the SMA has a CCL identifier that is stored in the database.



FIG. 2 shows an exemplary SMA 104 of the present invention. The controller 201 manages communication over the data circuits 103 and 105. The SMA database 128 (FIG. 1) stores a profile for each CCL 100 supported by the SMA 104. The profile provides information to support the conversion and transport of data between a central location, such as CCL 100, and its remote locations, such as remote locations 123, 124, 125, and 126. From the stored profiles the SMA determines the recipient of the communication, as well as the method of data transport and any data conversions that are necessary.


The SMA analyzes the information about the CCL and the remote device stored in the database to determine whether the CCL and the remote are using compatible or incompatible data formats. If the CCL and the remote are using incompatible data formats, then the SMA converts the data. As will be apparent to one skilled in the art, the conversion from one data format into another can be managed in any suitable way, e.g., through multiple bi-directional translators 205.


Exemplary Communication Methods with the SMA



FIGS. 3 and 4 are flow diagrams illustrating exemplary communication methods of the present invention. These figures illustrate the communication methods utilized to transfer data between the customer central location (CCL) 100 and the remote locations (123, 124, 125, and 126) of FIG. 1. The communication methods of FIGS. 3 and 4 allow the remote locations (123, 124, 125, and 126) and CCL 100 to communicate, even though they are connected by multiple wireless (e.g. digital cellular and PCS) systems using multiple, otherwise incompatible protocols or data formats. In discussing the following flow diagrams, reference will be made to the elements of FIG. 1.



FIG. 3 is a flow diagram illustrating the communications method 300 used by the CCL 100 to transfer data to a remote location (123, 124, 125, or 126). Communications method 300 begins at step 302 and proceeds to step 304. At step 304, the CCL 100 transports the data to SMA 104. The SMA 104 at step 306 receives the data and retrieves the MIN, or other identifying characteristic, transported with the data. At step 308, the SMA 104 uses the MIN to retrieve the CCL's profile 130 from the SMA database 128.


From the profile 130, the SMA 104 determines the MSC (109, 110, 117, or 119) that is serving the remote radio (113, 114, 121 or 122) identified by the MIN, the wireless access method or data format used in the MSC's market, the class of service or data format used by the CCL, and the method of transport to use between the SMA 104 and the selected MSC (109, 110, 117, or 119), in step 310. In step 311, the SMA determines whether the data formats used by the CCL and the remote are compatible. If the data formats are compatible, then the Yes branch is followed to step 313. However, if the data formats are not compatible, then the No branch is followed to step 312. At step 312, the SMA 104 converts the data to the proper format.


At step 313, the SMA transports the data to the appropriate MSC (109, 110, 117, or 119) using the method of transport specified in the database. Proceeding to step 314, the MSC (109, 110, 117, or 119) receives and transports the data to the radio (113, 114, 121, or 122) associated with the remote location (123, 124, 125, or 126). Communications method 300 then proceeds to step 316. At step 316, the radio (113, 114, 121, or 122) receives the converted data and transports it to the remote location (123, 124, 125, or 126). Finally, communications method 300 proceeds to step 318 and the method ends.



FIG. 4 is a flow diagram illustrating an exemplary remote communications method 400 used by the remote locations (123, 124, 125, or 126) to transfer data to the CCL 100. The remote communications method 400 illustrates the steps used by a remote location (123, 124, 125, or 126) to transport data to the CCL 100. Remote communications method 400 begins at step 402 and proceeds to step 404. At step 404, the remote location (123, 124, 125, or 126) commands its radio (113, 114, 121, or 122) to send data to its associated MSC (109, 110, 117, or 119). At step 406, the MSC (109, 110, 117, or 119) receives the data and transports it to the SMA 104.


The remote communications method 400 then proceeds to step 408. At step 408, the SMA 104 receives the data and retrieves the identifying characteristics, such as the MIN (or IMSI) and MSC identifier (MSCID), from the data. The SMA 104 searches the SMA database 128 using the MIN and MSCID that the MSC (109, 110, 117 or 119) transported with the data. Next, at step 410, the SMA 104 determines from the SMA database 128: 1) the CCL identifier; 2) the class of service used by the identified CCL 100; and 3) the wireless access method used by the MSC.


The SMA compares the class of service used by the CCL and the wireless access method used by the MSC to determine whether the data formats are compatible in step 411. If the data formats are compatible, then the Yes branch is followed to step 413. However, if the data formats are incompatible, then the No branch is followed to step 412 and the data is converted. Once the data is converted, the method proceeds to step 413. In step 413, the SMA delivers the data to the CCL. The SMA delivers the data to the CCL using a transmission path that is appropriate for the CCL identified by the CCL identifier. Then, remote communications method 400 proceeds to step 414 and ends.


Exemplary Communications with the SMA


The following examples are exemplary communications supported by the present invention. These examples are intended to illustrate some of the possible communication schemes, between the CCL 100 and the remote locations (123, 124, 125, and 126), that may be implemented with the present invention. These examples are in no way intended to limit the scope of the invention. Those skilled in the art will appreciate that there are many other possible schemes and protocols that may be implemented with the present invention.


In a first example, the CCL 100 sends data to the remote location 123. The remote location 123 is associated with an AMP's radio 113 and the AMP's radio is served by MSC 109. The CCL's class of service is “CELLEMETRY” Data Service. The CCL 100 sends the MIN of the AMPS radio 113 along with the data to be transported to the SMA 104. The SMA 104 determines from the SMA database 128 that the MIN corresponds to the AMP's radio 113; the class of service is “CELLEMETRY” Data Service; and the MSC 109 serves the radio 113.


Depending on the type of mobile switching center, either an IS41 inter-system page message is sent from the SMA 104 to the MSC 109 through data circuit 105, the SS7/IS41 network 106 and the data circuit 108; or a roamer-access call is made from the SMA 104 to the MSC 109 through circuit 103, public voice/data transport 102 and the data circuit 111. The SMA determines the appropriate method of transport between the SMA 104 and the MSC 109 from the database 128. The MSC 109 then broadcasts a page order, which is received by the AMPS radio 113 and delivered to the remote location 123 to complete the transaction.


In another example, the remote location 123 sends data to the CCL 100. The remote location 123 is associated with the AMP's radio 113 and the AMP's radio is served by MSC 109. The remote location 123 sends a message to the CCL 100 by commanding the AMPS radio 113 to generate a regeneration notification that is received by the MSC 109. The MSC 109 then forwards the regeneration notification to the SMA 104, via the data circuit 108, the SS7/IS41 network 106 and the data circuit 105. Once the SMA 104 receives the notification, the SMA 104 searches the SMA database 128, using the MIN and the MSCID provided by the MSC 109. From the database 128, the SMA 104 determines the following: 1) the CCL identifier for the intended recipient; 2) the class of service used by the CCL; and 3) and the wireless access method used by MSC 109. The SMA 104 compares the class of service used by the CCL 100 and the wireless access method used by MSC 109 to determine whether the data needs to be converted. If so, the SMA 104 converts the data. The data is delivered to the CCL 100 using the data circuit 103, public voice/data transport 102 and the data circuit 101.


In a further example, the CCL 100 sends data to the remote location 125. The remote location 125 is associated with a TDMA radio 121 and the TDMA radio is served by MSC 117. The CCL 100 sends the MIN of the TDMA radio 121 along with the data to the SMA 104. The SMA 104 determines from the SMA database 128 that the MIN corresponds to the TDMA radio 121; short message system (SMS) is the class of service; the MSC 117 serves the radio 121, and the method of transport between the SMA and the MSC 117. In this example, the method of transport is via data circuit 105 and SS7/IS41 network 106. Once this information is retrieved, the SMA 104 sends an IS41 SMS message to the MSC 117 through data circuit 105, the SS7/IS41 network 106, and data circuit 116. Then, MSC 117 sends a SMS message to radio 121, which in turn delivers the data to remote location 125 to complete the transaction.


In a further example, the remote location 125 sends data to the CCL 100. The remote location 125 is associated with the TDMA radio 121 and the TDMA radio is served by MSC 117. The remote location 125 commands the TDMA radio 121 to originate an SMS message, which is received by the MSC 117 and transported to the SMA 104. The SMS message is transported to the SMA 104 through circuit 116, the SS7/IS41 network 106 and, the data circuit 105. The SMA 104 then searches the SMA database, using the MIN and the MSCID provided by the MSC 117, and determines: the CCL identifier; the class of service used by the CCL identified by the CCL identifier; and the wireless access method used by the MSC 117. The SMA 104 compares the class of service used by the CCL 100 and the wireless access method used by the MSC 117 to determine whether the data needs to be converted. If so, the SMA 104 converts the data. The data is then delivered to the CCL 100 using the data circuit 103, the public voice/data transport 102 and the data circuit 101.


In yet a further example, the CCL 100 wishes to send data to the remote location 126. The remote location 126 is associated with a CDMA radio 122 and the CDMA radio is served by MSC 119. The CCL 100 sends the MIN of the CDMA radio 122 along with the data to be transported to the SMA 104. The SMA 104 determines from the SMA database 128 that the MIN corresponds to the CDMA radio 122; asynchronous digital data is the class of service; that the MSC 119 serves the CDMA radio 122; and that the method of transport from the SMA 104 to the MSC 119 is via data circuit 103 and public voice/data transport 102. Once this information is retrieved, a data message is sent from the SMA 104 to MSC 119. The message is sent through data circuit 103, public voice/data transport 102, and the data circuit 120. The data message is then sent by the MSC 119 to the CDMA radio 122, which in turn sends the data message to the remote location 126 to complete the transaction.


In a final example, the remote location 126 wishes to send data to the CCL 100. The remote location 126 is associated with a CDMA radio 122 and the CDMA radio is served by MSC 119. The remote location 126 requests that CDMA radio 122 initiate an asynchronous digital data call, which is received by the MSC 119 and transported to the SMA 104. The MSC 119 transports the data call via the data circuit 120, the public voice/data transport 102, and data circuit 103. The SMA 104 then searches the SMA database 128, using the MIN and the MSCID provided by the MSC 119, and determines: the CCL identifier for the intended recipient; the class of service used by the intended recipient; and the wireless access method used by the MSC 119. The SMA 104 compares the class of service used by the CCL 100 and the wireless access method used by the MSC 119 to determine whether the data needs to be converted. If so, the SMA 104 converts the data. The data is then delivered to the CCL 100 using the data circuit 103, the public voice/data transport 102 and the data circuit 101.


While a preferred embodiment has been set forth above, those skilled in the art who have reviewed the present disclosure will readily appreciate that other embodiments can be realized within the scope of the present invention. For example, transmission between the CCL 100 and the SMA 104 can take place through any suitable network, such as a TCP/IP Network. Also, any SMS protocol can be used.


Exemplary Telemetry Gateway Embodiment


In an alternate embodiment, the present invention can be implemented using a telemetry gateway. A telemetry gateway comprises hardware and software modules capable of communicating messages to MSCs in various digital networks. The telemetry gateway can perform certain functions of an HLR and SMSC found in conventional SMS systems, as illustrated in FIGS. 5-8. Replacing the HLR and the SMSC used in conventional SMS systems allows the telemetry gateway to provide faster and more efficient routing of messages. Specifically, instead of the “store and forward” functions performed by the SMSC that typically cause a lag of minutes or hours in the transmission of messages, the telemetry gateway does not store the messages it receives. The telemetry gateway typically processes and transmits messages in milliseconds. The telemetry gateway is more efficient than conventional SMS systems because it considers all messages as roaming and eliminates the need to query the HLR before sending a message to a mobile communication device. The telemetry gateway offers a further advantage over a conventional SMSC in that it also has the ability to convert messages having different messaging protocols.


Referring to FIG. 9, an exemplary architecture 900 is illustrated for implementing an SMS telemetry gateway 930. In the exemplary architecture 900, the SMS telemetry gateway 930 can communicate with digital networks using a variety of different wireless access formats. While exemplary architecture 900 illustrates a TDMA network, a CDMA network, and a GSM network, those skilled in the art will understand that the invention is not limited to these examples of digital networks. Similarly, while the SMS telemetry gateway 930 is shown coupled to a telemetry service provider 935, the present invention is not limited to a single service provider. The SMS telemetry gateway can communicate with service providers supporting a variety of external messaging systems including email, voicemail, paging, and Web-based messaging.


Turning to the general digital network 910, a cellular mobile radiotelephone, or radio, 905 can transmit a message via the network 910 to the MSC, or serving switch, 915. The radio 905 may be a fixed or mobile radio communication device. The serving switch 915 determines that the message is a roaming communication and transmits the message to signal transfer point 920 for routing to the SMS telemetry gateway 930 via SS7 network 925. Although the SS7 network 925 is the method for transmission to the SMS telemetry gateway 930 in the preferred embodiment illustrated in FIG. 9, other data networks can also perform the same function. Upon receipt of the message, the SMS telemetry gateway 930 converts the message to a common telemetry protocol and determines the destination service provider 935 from the message's address field. The SMS telemetry gateway 930 can also conform the converted message to any delivery preferences for the service provider 935 stored in database 933. For example, an alternate network address for the service provider 935 may be stored in database 933.


Once the delivery preferences are conformed, the SMS telemetry gateway 930 transmits the message in the common protocol to the appropriate service provider 935. In contrast to the SMSC of conventional SMS systems, the SMS telemetry gateway 930 does not store the message for later delivery. Instead, the SMS telemetry gateway 930 transmits the message to the service provider 935 as soon as the processing steps are completed. The SMS telemetry gateway typically processes and transmits messages in a few milliseconds as opposed to the minutes or hours of delay with conventional SMS systems.


When the service provider 935 receives the telemetry message, it can package the message for its subscribers in a variety of formats. For example, the service provider 935 can insert the message into an email for delivery to an email system. In another embodiment, the service provider 935 can use the message to create a voicemail which is forwarded to the subscriber. The service provider 935 can also transmit a confirmation that the message was received to the SMS telemetry gateway 930.


The SMS telemetry gateway 930 is a bidirectional system that can also transmit messages from the service provider 935 to radio 905. When the SMS telemetry gateway 930 receives a message from the service provider 935, it requests routing information from the switch 915 at the destination network 910. The SMS telemetry gateway 930 converts the message to the wireless access format used at the destination network 910 and transmits the message.


The SMS telemetry gateway's 930 direct access to the SS7 network 925, as illustrated in exemplary architecture 900, allows for faster and more efficient communication of short messages. Furthermore, its ability to convert messages from a variety of different wireless access formats enables communication with a greater number of networks.


Exemplary Communication Methods with the Telemetry Gateway



FIGS. 10A and 11A illustrate exemplary methods for communicating messages using the SMS telemetry gateway 930 in accordance with an exemplary embodiment of the present invention. FIG. 10A illustrates an exemplary communication method for a message originating at a mobile radio, whereas FIG. 11A is an example of a method for a mobile radio terminating message. Those skilled in the art will recognize that the methods illustrated in FIGS. 10A and 11A are only examples and that other messaging techniques can be implemented in other embodiments using the SMS telemetry gateway.


Referring to FIG. 10A, exemplary method 1000 is illustrated for transmitting a message originating at a mobile radio. The sequence of steps performed in exemplary method 1000 are also shown in exemplary ladder diagram 1080 illustrated in FIG. 10B. Referring to exemplary method 1000, the switch 915 receives a message, or “SM”, from the radio 905 in step 1005. The switch queries its visitor location register (“VLR”) in step 1010 to locate a profile for the radio 905. The VLR is a database comprising temporary information about subscribers of one network that are roaming into another network. The switch uses the information in the VLR to complete roaming communications.


If there is no entry in the VLR database in step 1015, the switch 915 sends a registration notification to the telemetry gateway 930 to obtain account and service information for the subscriber. The switch 915 receives the registration response with the needed information from the SMS telemetry gateway 930 in step 1025 and creates a profile in the VLR database in step 1030. The terms “registration notification” and “registration response” are used herein to refer to general steps for identifying the radio communications device. These terms do not limit the invention to particular types of networks or protocols.


Alternatively, if a VLR entry already exists in step 1015, the switch 915 can proceed directly to step 1035 and transmit the message to the signal transfer point 920 for routing to the SMS telemetry gateway 930 in step 1040. A characteristic of SMS communications includes guaranteed delivery of messages through the use of confirmation messages. For example, when the SMS telemetry gateway 930 receives the message, it returns a confirmation response to the switch 915 in step 1045. In step 1050, the SMS telemetry gateway converts the received message from the protocol used at the originating network 910 to the common telemetry protocol used by the service provider 935.


In steps 1055 and 1060 of exemplary method 1000, the SMS telemetry gateway uses the originating address field to determine the routing to the service provider 935 and to check for any delivery preferences stored in database 933. The converted message is ready for delivery to the service provider 935 in step 1065. Upon delivery, the service provider 935 typically transmits a delivery confirmation response to the SMS telemetry gateway. The SMS telemetry gateway 930 performs steps 1050-1065 in a matter of milliseconds, which is a significant improvement over the conventional “store and forward” techniques of the SMSC platforms used in SMS systems.


Turning to FIG. 11A, an exemplary method 1100 is illustrated for transmitting a message that originates at a service provider and terminates at a mobile radio. Exemplary ladder diagram 1180 shown in FIG. 11B also illustrates the sequence of steps described in exemplary process 1100. Process 1100 begins with the service provider 935 transmitting a message, or SM, to the SMS telemetry gateway 930 in step 1105. The service provider 935 receives the message from a subscriber using one of the messaging systems that the service provider 935 supports such as an email or paging system. In steps 1110 and 1115, the SMS telemetry gateway 930 sends an acknowledgment to the service provider 935 and requests routing information for the message from the switch 915 in the destination network. If there is a VLR entry for the SMS telemetry gateway in step 1120, the switch will proceed with providing the routing information in step 1135.


However, if the switch 915 does not recognize the radio 905, the switch will need to create a VLR entry in its database. The switch 915 creates a VLR entry in steps 1125 and 1130 by sending a qualification request for account and service information to the SMS telemetry gateway 930. Once the switch 915 creates a VLR entry, it can provide the routing information for the SMS telemetry gateway 930 in step 1135.


The wireless access format that the destination network employs is typically stored in a database at the SMS telemetry gateway 930. The SMS telemetry gateway 930 uses the format information to convert the message, in step 1140, to the format expected at the destination network. In steps 1145 and 1150, the SMS telemetry gateway 930 transmits the converted message to the switch 915 and the switch 915 forwards the message to the radio 905. Consistent with the guaranteed delivery of the SMS system, the switch 915 returns an acknowledgment of delivery in step 1155 and the SMS telemetry gateway 930 forwards an acknowledgment to the service provider 935 in step 1160.


In conclusion, the present invention, as represented in the foregoing exemplary embodiments, provides a system and method for communicating short messages that is more flexible and efficient than conventional SMS systems. The exemplary SMS telemetry gateway can convert messages to different message formats in order to support communication with a variety of wireless networks. The exemplary SMS telemetry gateway also performs the routing functions of components in conventional SMS systems, but does so more quickly and efficiently.


It will be appreciated that the present invention fulfills the needs of the prior art described herein and meets the above-stated objects. While there has been shown and described the preferred embodiment of the invention, it will be evident to those skilled in the art that various modifications and changes may be made thereto without departing from the spirit and the scope of the invention as set forth in the appended claims and equivalents thereof. For instance, the present invention could be implemented in data networks other than the SS7 network illustrated in exemplary architecture 900. The invention can also be adapted to support communication with messaging protocols other than the wireless access formats described herein.

Claims
  • 1. A method for communicating messages between a first device having a home network and a second device, comprising the steps of: receiving an SMS message that originated at the first device while the first device was in the home network, the SMS message comprising an identifier and having a first data format;considering the SMS message as roaming;responsive to determining the identifier of the SMS message, accessing a database to retrieve a profile for the first device and the second device;determining, based on the retrieved profile, whether the first device and the second device communicate using incompatible data formats; andconverting the SMS message from the first format to one of at least three different formats that is selected according to the retrieved profile; andtransmitting the converted SMS message for receipt by the second device.
  • 2. The method of claim 1, wherein a gateway performs the receiving, accessing, determining, converting, and transmitting steps.
  • 3. The method of claim 1, wherein substantially less than one second lapses between the receiving step and the transmitting step.
  • 4. The method of claim 1, wherein a gateway completes the receiving, accessing, determining, converting, and transmitting steps in a few milliseconds.
  • 5. The method of claim 1, wherein less than ten milliseconds passes between the receiving step and the transmitting step.
  • 6. The method of claim 1, wherein the converting step comprises processing the SMS message with a selected one of at least three translators that are coupled to the database via a controller.
  • 7. The method of claim 1, wherein the identifier comprises a mobile identification number (MIN).
  • 8. The method of claim 1, wherein the identifier comprises an international mobile station identifier (IMSI).
  • 9. The method of claim 1, wherein the first device comprises a radio communication device and the second device comprises a mobile switching center.
  • 10. The method of claim 1, wherein the step of considering the SMS message as roaming comprises querying a visitor location register for the home network regardless of whether the first device is represented in a home location register for the home network.
  • 11. The method of claim 1, wherein the receiving, accessing, determining, converting, and transmitting steps are performed at an arbitrator, and wherein the method further comprises the steps of: at the arbitrator, converting a second SMS message from the first format to a second of the at least three different formats; andat the arbitrator, converting a third SMS message from the first format to a third of the at least three formats,wherein the one of the at least three different formats, the second of the at least three different formats, and the third format of the at least three different formats are different from one another.
  • 12. The method of claim 1, wherein receiving the SMS message comprises intercepting the SMS message.
  • 13. A method comprising the steps of: based on data contained within an SMS message that has been sent from a communication device having a home network and that has a first format, determining an identifying characteristic and a destination of the SMS message;retrieving a stored profile using the determined identifying characteristic;selecting a second format from at least three different formats based on the retrieved profile;converting the SMS message from the first format to the selected second format; andwithout completing a store and forward process, forwarding the converted SMS message for delivery,wherein the SMS message was sent while the communication device was in the home network,wherein the home network has a visitor location registry, andwherein the method comprises: designating the SMS message as roaming and querying the visitor location registry;if a reply to the query indicates that the visitor location registry has an entry for the communication device, processing the SMS message according to the entry; andif the reply to the query indicates that the visitor location registry does not have an entry for the communication device, creating an entry for the communication device in the visitor location registry.
  • 14. The method of claim 13, wherein the first format comprises a wireless access format, and wherein the at least three different formats comprise a format for an email system, a format for a voicemail system, and a format for a web-based messaging system.
  • 15. The method of claim 13, wherein the first format is compatible with an email system, a voicemail system, or a web-based messaging system, and wherein the selected format comprises a wireless access format.
  • 16. The method of claim 13, wherein the determining step, the retrieving step, the selecting step, the converting step, and the forwarding step execute to completion within a time period of less than about ten milliseconds.
  • 17. The method of claim 13, wherein less than about ten milliseconds passes during the determining step, the retrieving step, the selecting step, the converting step, and the forwarding step.
  • 18. The method of claim 13, wherein designating the SMS message as roaming and querying the visitor location registry occurs without querying a home location registry of the home network, and wherein the visitor location registry comprises a database comprising temporary information about subscribers of one network that are roaming in another network, andwherein creating the entry comprises a switch creating the entry.
  • 19. The method of claim 13, wherein the determining step comprises intercepting the SMS message and determining the identifying characteristic and the destination of the intercepted SMS message.
  • 20. A method for routing a message using a gateway, comprising the steps of: at a first time at the gateway, receiving the message from a communication device;at the gateway, requesting routing information from a mobile switching center;at the gateway, receiving the requested routing information;at the gateway, converting the received message from a first format to a second format that is selected from at least three formats that are different from one another based on the received routing information; andtransmitting the converted message from the gateway to the mobile switching center at a second time that is substantially less than one second after the first time,wherein the gateway considers the received message and all other received messages as roaming.
  • 21. The method of claim 20, wherein the second time is milliseconds after the first time.
  • 22. The method of claim 20, wherein the second time is less than ten milliseconds after the first time.
  • 23. The method of claim 20, wherein the second time is within a few milliseconds of the first time.
  • 24. The method of claim 20, wherein the communication device is in a home network of the communication device.
  • 25. The method of claim 24, further comprising: determining whether a visitor location registry for the home network contains an entry for the communication device; andif the visitor location registry does not contain the entry, creating the entry.
  • 26. The method of claim 20, wherein the gateway repetitively routes messages to respective mobile communication devices without querying a home location register.
  • 27. The method of claim 20, further comprising the steps of: at the gateway, receiving a second message from a service provider;at the gateway, requesting routing information for the second message from a switch at a destination network;at the gateway, receiving the requested routing information;at the gateway, converting the second message to a wireless access format used at the destination network; andtransmitting the converted second message according to the received routing information.
  • 28. The method of claim 20, wherein the gateway considers the received message as roaming while the communication device is in a home network of the communication device when the receiving step occurs, wherein the home network has a home location registry, andwherein the gateway processes the message without querying the home location registry between the first time and the second time.
  • 29. The method of claim 20, wherein the communication device has a home network, and wherein the step of receiving the message comprises at the first time at the gateway, receiving the message from the communication device that is in the home network.
  • 30. A method comprising the steps of: based on data contained within an SMS message that has been sent and that has a first format, determining an identifying characteristic and a destination of the SMS message;retrieving a stored profile using the determined identifying characteristic;selecting a second format from at least three different formats based on the retrieved profile;converting the SMS message from the first format to the selected second format; andwithout completing a store and forward process, forwarding the converted SMS message for delivery,wherein the SMS message has been sent by a mobile communication device having a home network, andwherein the SMS message is treated as roaming regardless of whether the mobile communication device sent the SMS message while the mobile communication device was in the home network.
RELATED PATENT APPLICATION

This patent application claims priority to and is a continuation of the patent application entitled “Method and System for Efficiently Routing Messages,” filed on Feb. 11, 2010, assigned U.S. patent application Ser. No. 12/704,290, and issued as U.S. Pat. No. 8,060,067, which is a continuation of the patent application entitled “Telemetry Gateway,” filed on Jun. 12, 2007, assigned U.S. patent application Ser. No. 11/811,855, and issued as U.S. Pat. No. 7,680,505, which is a continuation of the patent application entitled “Method and System for Improved Short Message Services,” filed on Jul. 6, 2004, assigned U.S. patent application Ser. No. 10/885,445, and issued as U.S. Pat. No. 7,245,928, which is a continuation-in-part of the patent application entitled “Interconnect System and Method for Multiple Protocol Short Message Services,” filed on Oct. 27, 2000, assigned U.S. patent application Ser. No. 09/699,312, and issued as U.S. Pat. No. 6,856,808. Applicants hereby incorporate by reference herein the full disclosure of U.S. patent application Ser. Nos. 12/704,290 and 11/811,855 and U.S. Pat. Nos. 7,245,928 and 6,856,808.

US Referenced Citations (371)
Number Name Date Kind
3581019 Ryan May 1971 A
3886515 Cottin et al. May 1975 A
3973200 Akerberg Aug 1976 A
4172969 Levine et al. Oct 1979 A
4219698 Birilli et al. Aug 1980 A
4263480 Levine Apr 1981 A
4284849 Anderson et al. Aug 1981 A
4342986 Buskirk et al. Aug 1982 A
4361730 Barber et al. Nov 1982 A
4371751 Hilligoss, Jr. et al. Feb 1983 A
4412292 Sedam et al. Oct 1983 A
4454027 Fenton Jun 1984 A
4486624 Puhl et al. Dec 1984 A
4492820 Kennard et al. Jan 1985 A
4644347 Lucas et al. Feb 1987 A
4644351 Zabarsky et al. Feb 1987 A
4646082 Engel et al. Feb 1987 A
4677653 Weiner et al. Jun 1987 A
4724425 Gerhart et al. Feb 1988 A
4734928 Weiner et al. Mar 1988 A
4750197 Denekamp et al. Jun 1988 A
4766548 Cedrone et al. Aug 1988 A
4783747 Komori et al. Nov 1988 A
4791658 Simon et al. Dec 1988 A
4807225 Fitch Feb 1989 A
4814763 Nelson et al. Mar 1989 A
4823123 Siwiak Apr 1989 A
4825193 Siwiak et al. Apr 1989 A
4825457 Lebowitz Apr 1989 A
4833701 Comroe et al. May 1989 A
4837800 Freeburg et al. Jun 1989 A
4839917 Oliver Jun 1989 A
4866445 Valero et al. Sep 1989 A
4868560 Oliwa et al. Sep 1989 A
4868859 Sheffer Sep 1989 A
4875038 Siwiak et al. Oct 1989 A
4875230 Blair Oct 1989 A
4882579 Siwiak Nov 1989 A
4887290 Dop et al. Dec 1989 A
4887291 Stillwell Dec 1989 A
4890315 Bendixen et al. Dec 1989 A
4891637 Siwiak et al. Jan 1990 A
4891638 Davis Jan 1990 A
4901340 Parker et al. Feb 1990 A
4905234 Childress et al. Feb 1990 A
4914651 Lusignan Apr 1990 A
4928096 Leonardo et al. May 1990 A
4940963 Gutman et al. Jul 1990 A
4972460 Sasuta Nov 1990 A
4979169 Almond et al. Dec 1990 A
4993059 Smith et al. Feb 1991 A
5005014 Jasinski Apr 1991 A
5010584 Seki Apr 1991 A
5020091 Krolopp et al. May 1991 A
5020093 Pireh May 1991 A
5027383 Sheffer Jun 1991 A
5029098 Levasseaur Jul 1991 A
5031204 McKernan Jul 1991 A
5047763 Kuznicki et al. Sep 1991 A
5073919 Hagensick Dec 1991 A
5081667 Drori et al. Jan 1992 A
5087919 Odagawa et al. Feb 1992 A
5090051 Muppidi et al. Feb 1992 A
5117449 Metroka et al. May 1992 A
5121503 Davis Jun 1992 A
5124697 Moore Jun 1992 A
5131019 Sheffer et al. Jul 1992 A
5134644 Garton et al. Jul 1992 A
5142279 Jasinski et al. Aug 1992 A
5148473 Freeland et al. Sep 1992 A
5153582 Davis Oct 1992 A
5153902 Buhl et al. Oct 1992 A
5153903 Eastmond et al. Oct 1992 A
5159625 Zicker Oct 1992 A
5162790 Jasinski Nov 1992 A
5173933 Jabs et al. Dec 1992 A
5175758 Levanto et al. Dec 1992 A
5185779 Dop et al. Feb 1993 A
5196842 Gomez et al. Mar 1993 A
5206855 Schwendeman et al. Apr 1993 A
5207784 Schwartzendruber May 1993 A
5208756 Song May 1993 A
5210787 Hayes et al. May 1993 A
5218367 Sheffer et al. Jun 1993 A
5220599 Sasano et al. Jun 1993 A
5222123 Brown et al. Jun 1993 A
5230081 Yamada et al. Jul 1993 A
5239294 Flanders et al. Aug 1993 A
5239678 Grube et al. Aug 1993 A
5247567 Hirano Sep 1993 A
5254986 DeLuca Oct 1993 A
5255307 Mizikovsky Oct 1993 A
5265150 Helmkamp et al. Nov 1993 A
5278539 Lauterbach et al. Jan 1994 A
5278890 Beeson, Jr. et al. Jan 1994 A
5305217 Nakamura et al. Apr 1994 A
5307399 Dai et al. Apr 1994 A
5307509 Michalon et al. Apr 1994 A
5335278 Matchett et al. Aug 1994 A
5341410 Aron et al. Aug 1994 A
5363427 Ekstrom et al. Nov 1994 A
5365573 Sakamoto et al. Nov 1994 A
5369681 Boudreau et al. Nov 1994 A
5371781 Ardon Dec 1994 A
5371898 Grube et al. Dec 1994 A
5382970 Kiefl Jan 1995 A
5386209 Thomas Jan 1995 A
5396537 Schwendeman Mar 1995 A
5396539 Slekys et al. Mar 1995 A
5398277 Martin, Jr. et al. Mar 1995 A
5404392 Miller et al. Apr 1995 A
5432841 Rimer Jul 1995 A
5450329 Tanner Sep 1995 A
5453730 De-Grinis et al. Sep 1995 A
5454027 Kennedy et al. Sep 1995 A
5493722 Gunn et al. Feb 1996 A
5502761 Duncan et al. Mar 1996 A
5511072 Delprat Apr 1996 A
5511110 Drucker Apr 1996 A
5517547 Ladha et al. May 1996 A
5519756 Clift May 1996 A
5526401 Roach, Jr. et al. Jun 1996 A
5528664 Slekys et al. Jun 1996 A
5530736 Comer et al. Jun 1996 A
5533094 Sanmugam Jul 1996 A
5539810 Kennedy, III et al. Jul 1996 A
5544223 Robbins et al. Aug 1996 A
5544225 Kennedy, III et al. Aug 1996 A
5546444 Roach, Jr. et al. Aug 1996 A
5574975 Hill Nov 1996 A
5579372 Åström Nov 1996 A
5586177 Farris et al. Dec 1996 A
5594740 LaDue Jan 1997 A
5594945 Lewis et al. Jan 1997 A
5596573 Bertland Jan 1997 A
5603091 Linquist et al. Feb 1997 A
5610973 Comer Mar 1997 A
5619209 Horstein et al. Apr 1997 A
5625889 Chikkaswamy et al. Apr 1997 A
5629975 Tiedemann, Jr. et al. May 1997 A
5640139 Egeberg Jun 1997 A
5648966 Kondo et al. Jul 1997 A
5652564 Winbush Jul 1997 A
5652570 Lepkofker Jul 1997 A
5675371 Barringer Oct 1997 A
5678179 Turcotte et al. Oct 1997 A
5680551 Martino, II Oct 1997 A
5684858 Hartmann et al. Nov 1997 A
5686888 Welles, II et al. Nov 1997 A
5701302 Geiger Dec 1997 A
5722067 Fougnies et al. Feb 1998 A
5742668 Pepe et al. Apr 1998 A
5742905 Pepe et al. Apr 1998 A
5745867 Mills Apr 1998 A
5748104 Argyroudis et al. May 1998 A
5751789 Farris et al. May 1998 A
5754954 Cannon et al. May 1998 A
5758313 Shah et al. May 1998 A
5761621 Sainton Jun 1998 A
5767788 Ness Jun 1998 A
5768343 Dame et al. Jun 1998 A
5777605 Yoshinobu et al. Jul 1998 A
5781612 Choi et al. Jul 1998 A
5787149 Yousefi et al. Jul 1998 A
5787357 Salin Jul 1998 A
5790631 Minarczik et al. Aug 1998 A
5793306 Vershinin et al. Aug 1998 A
5794144 Comer et al. Aug 1998 A
5797097 Roach, Jr. et al. Aug 1998 A
5805997 Farris Sep 1998 A
5819184 Cashman Oct 1998 A
5822221 Groenteman Oct 1998 A
5822423 Jehnert et al. Oct 1998 A
5826195 Westerlage et al. Oct 1998 A
5835868 McElroy et al. Nov 1998 A
5844808 Konsmo et al. Dec 1998 A
5845203 LaDue Dec 1998 A
5845211 Roach, Jr. Dec 1998 A
5862201 Sands Jan 1999 A
5862480 Wild et al. Jan 1999 A
5862481 Kulkarni et al. Jan 1999 A
5873043 Comer Feb 1999 A
5875863 Jarvis et al. Mar 1999 A
5878351 Alanara et al. Mar 1999 A
5884216 Shah et al. Mar 1999 A
5889474 LaDue Mar 1999 A
5898917 Batni et al. Apr 1999 A
5901142 Averbuch et al. May 1999 A
5909651 Chander et al. Jun 1999 A
5913166 Buttitta et al. Jun 1999 A
5917449 Sanderford et al. Jun 1999 A
5917886 Halkio Jun 1999 A
5918172 Saunders et al. Jun 1999 A
5920822 Houde et al. Jul 1999 A
5923731 McClure Jul 1999 A
5924026 Krishnan Jul 1999 A
5933784 Gallagher et al. Aug 1999 A
5937161 Mulligan et al. Aug 1999 A
5946629 Sawyer et al. Aug 1999 A
5946630 Willars et al. Aug 1999 A
5983197 Enta Nov 1999 A
5999808 LaDue Dec 1999 A
6011321 Stancu et al. Jan 2000 A
6012013 McBurney Jan 2000 A
6012014 Koyanagi et al. Jan 2000 A
6014089 Tracy et al. Jan 2000 A
6018657 Kennedy, III et al. Jan 2000 A
6021394 Takahashi Feb 2000 A
6025774 Forbes Feb 2000 A
6026345 Shah et al. Feb 2000 A
6049273 Hess Apr 2000 A
6067454 Foti May 2000 A
6070070 Ladue May 2000 A
6072862 Srinivasan Jun 2000 A
6078811 Lin et al. Jun 2000 A
6078820 Wells et al. Jun 2000 A
6081514 Raith Jun 2000 A
6081546 Williamson et al. Jun 2000 A
6088431 LaDue Jul 2000 A
6091961 Khalil Jul 2000 A
6094578 Purcell et al. Jul 2000 A
6097951 Ernam et al. Aug 2000 A
6108537 Comer et al. Aug 2000 A
6108540 Sonti et al. Aug 2000 A
6111539 Mannings et al. Aug 2000 A
6122514 Spaur et al. Sep 2000 A
6125275 Comer et al. Sep 2000 A
6138034 Willey Oct 2000 A
6144722 Anderson et al. Nov 2000 A
6144859 LaDue Nov 2000 A
6148202 Wortham Nov 2000 A
6150955 Tracy et al. Nov 2000 A
6151507 Laiho et al. Nov 2000 A
6154648 Comer Nov 2000 A
6154658 Caci Nov 2000 A
6161020 Kim Dec 2000 A
6163701 Saleh et al. Dec 2000 A
6169895 Buhrmann et al. Jan 2001 B1
6172974 Tseng et al. Jan 2001 B1
6175732 McDaniel et al. Jan 2001 B1
6181981 Varga et al. Jan 2001 B1
6185198 LaDue Feb 2001 B1
6195546 Leung et al. Feb 2001 B1
6215404 Morales Apr 2001 B1
6233450 Seppanen May 2001 B1
6236357 Corwith May 2001 B1
6249217 Forbes Jun 2001 B1
6259405 Stewart et al. Jul 2001 B1
6259781 Crouch et al. Jul 2001 B1
6263212 Ross et al. Jul 2001 B1
6278697 Brody et al. Aug 2001 B1
6282496 Chowdhary Aug 2001 B1
6285868 LaDue Sep 2001 B1
6285953 Harrison et al. Sep 2001 B1
6292669 Meuronen et al. Sep 2001 B1
6297768 Allen, Jr. Oct 2001 B1
6298232 Marin et al. Oct 2001 B1
6311056 Sandidge Oct 2001 B1
6311060 Evans et al. Oct 2001 B1
6330452 Fattouche et al. Dec 2001 B1
6339731 Morris et al. Jan 2002 B1
6353743 Karmel Mar 2002 B1
6353745 Wehrend et al. Mar 2002 B1
6363249 Nordeman et al. Mar 2002 B1
6363254 Jones et al. Mar 2002 B1
6363324 Hildebrant Mar 2002 B1
6366791 Lin et al. Apr 2002 B1
6369719 Tracy et al. Apr 2002 B1
6370135 Gardner Apr 2002 B1
6377210 Moore Apr 2002 B1
6389289 Voce et al. May 2002 B1
6393295 Butler et al. May 2002 B1
6393296 Sabnani et al. May 2002 B1
6397056 Bugnon et al. May 2002 B1
6405033 Kennedy, III et al. Jun 2002 B1
6415156 Stadelmann Jul 2002 B1
6424828 Collins et al. Jul 2002 B1
6424841 Gustafsson Jul 2002 B1
6457038 Defosse Sep 2002 B1
6463445 Suzuki et al. Oct 2002 B1
6476763 Allen, Jr. Nov 2002 B2
6484035 Allen, Jr. Nov 2002 B2
6487602 Thakker Nov 2002 B1
6493556 Stinson Dec 2002 B1
6493558 Bernhart et al. Dec 2002 B1
6505050 Brudos et al. Jan 2003 B1
6515997 Feltner et al. Feb 2003 B1
6516197 Havinis et al. Feb 2003 B2
6553336 Johnson et al. Apr 2003 B1
6560456 Lohtia et al. May 2003 B1
6567501 Pernu et al. May 2003 B1
6570532 Mise et al. May 2003 B2
6603755 Parker Aug 2003 B1
6608553 Isobe Aug 2003 B2
6611689 Cartigny et al. Aug 2003 B1
6618671 Dooley et al. Sep 2003 B2
6622016 Sladek et al. Sep 2003 B1
6625142 Joffe et al. Sep 2003 B1
6625461 Bertacchi Sep 2003 B1
6643511 Rune et al. Nov 2003 B1
6665532 Boland et al. Dec 2003 B1
6683881 Mijares et al. Jan 2004 B1
6710738 Allen, Jr. Mar 2004 B2
6714793 Carey et al. Mar 2004 B1
6718177 Comer et al. Apr 2004 B1
6718237 Murray et al. Apr 2004 B1
6738647 Link, II May 2004 B1
6741853 Jiang et al. May 2004 B1
6741863 Chiang et al. May 2004 B1
6745041 Allison et al. Jun 2004 B2
6760580 Robinson et al. Jul 2004 B2
6771949 Corliss Aug 2004 B1
6782276 Lam et al. Aug 2004 B1
6826397 Vasa Nov 2004 B1
6856808 Comer et al. Feb 2005 B1
6861947 Albert Mar 2005 B2
6865191 Bengtsson et al. Mar 2005 B1
6882843 Comer Apr 2005 B1
6912230 Salkini et al. Jun 2005 B1
6938087 Abu-Samaha Aug 2005 B1
6959192 Cannon et al. Oct 2005 B1
6961330 Cattan et al. Nov 2005 B1
6980887 Varga et al. Dec 2005 B2
6982656 Coppinger et al. Jan 2006 B1
7005997 Wiewiura Feb 2006 B1
7010306 Tanibayashi et al. Mar 2006 B1
7058076 Jiang Jun 2006 B1
7164936 Heatley Jan 2007 B2
7257122 Keturi Aug 2007 B1
7493381 Garg Feb 2009 B2
20010003093 Lundin Jun 2001 A1
20010016495 Chandnani et al. Aug 2001 A1
20010042121 Defosse et al. Nov 2001 A1
20010047244 Harrison et al. Nov 2001 A1
20010047410 Defosse Nov 2001 A1
20010054083 Defosse Dec 2001 A1
20020016829 Defosse Feb 2002 A1
20020086636 Tracy et al. Jul 2002 A1
20020110230 Leuca et al. Aug 2002 A1
20020120728 Braatz et al. Aug 2002 A1
20020142759 Newell et al. Oct 2002 A1
20020155844 Rankin et al. Oct 2002 A1
20020160771 Massie et al. Oct 2002 A1
20020164988 Vishwanathan et al. Nov 2002 A1
20020193127 Martschitsch Dec 2002 A1
20020194387 Defosse Dec 2002 A1
20020196924 Dahari Dec 2002 A1
20030003930 Allison et al. Jan 2003 A1
20030009313 May et al. Jan 2003 A1
20030021273 Fouquet et al. Jan 2003 A1
20030022656 Hinnant, Jr. et al. Jan 2003 A1
20030054830 Williams et al. Mar 2003 A1
20030097474 Defosse et al. May 2003 A1
20030101257 Godwin May 2003 A1
20030101262 Godwin May 2003 A1
20030119489 Mohammed Jun 2003 A1
20030119498 Haas et al. Jun 2003 A1
20030129969 Rucinski Jul 2003 A1
20030141990 Coon Jul 2003 A1
20030158650 Abe et al. Aug 2003 A1
20030182053 Swope et al. Sep 2003 A1
20030204391 May et al. Oct 2003 A1
20040029598 Guggisberg Feb 2004 A1
20040110493 Alvarez et al. Jun 2004 A1
20040142707 Midkiff et al. Jul 2004 A1
20040180678 Smith et al. Sep 2004 A1
20040199649 Tarnanen et al. Oct 2004 A1
20040203640 Molander et al. Oct 2004 A1
20050037784 Cleary Feb 2005 A1
20050102074 Kolls May 2005 A1
20050197106 Bristow et al. Sep 2005 A1
Foreign Referenced Citations (39)
Number Date Country
0 123 456 Oct 1984 EP
0 123 562 Jul 1990 EP
0 345 818 Dec 1996 EP
0 837 341 Apr 1998 EP
0 855 824 Jul 1998 EP
0 924 918 Jun 1999 EP
0 959 600 Nov 1999 EP
2 363 289 Dec 2001 GB
4-96509 Mar 1992 JP
WO 9214329 Aug 1992 WO
WO 9405095 Mar 1994 WO
WO 9524791 Sep 1995 WO
WO 9525407 Sep 1995 WO
WO 9526088 Sep 1995 WO
WO 9603007 Feb 1996 WO
WO 9610895 Apr 1996 WO
WO 9637079 Nov 1996 WO
WO 9638989 Dec 1996 WO
WO 9736435 Oct 1997 WO
WO 9738540 Oct 1997 WO
WO 9745991 Dec 1997 WO
WO 9806227 Feb 1998 WO
WO 9819438 May 1998 WO
WO 9819447 May 1998 WO
WO 9827780 Jun 1998 WO
WO 9926428 May 1999 WO
WO 9960769 Nov 1999 WO
WO 0003532 Jan 2000 WO
WO 0017021 Mar 2000 WO
WO 0028347 May 2000 WO
WO 0036812 Jun 2000 WO
WO 0163825 Aug 2001 WO
WO 0163960 Aug 2001 WO
WO 0172068 Sep 2001 WO
WO 0180583 Oct 2001 WO
WO 0235866 May 2002 WO
WO 03019925 Mar 2003 WO
WO 2005074430 Aug 2005 WO
WO 2006014419 Feb 2006 WO
Non-Patent Literature Citations (8)
Entry
EIA/TIA 1S-54-B Standard; p. 115 and pp. 215-222.
European Telecommunication Standards Institute; European Digital Cellular Telecommunications System (Phase 2); Technical Realization of the Short Message Service (SMS) Point to Point (PP) (GSM 03.40); European Telecommunication Standard; Oct. 1993; Draft pr ETS 300 536; pp. 1-103.
European Telecommunication Standards Institute; European Digital Cellular Telecommunications System (Phase 2); Technical Realization of Short Message Service Call Broadcast (SMSCB) (GSM 03.41); European Telecommunication Standard; Oct. 1993; Draft pr ETS 300 537; pp. 1-24.
funSMS.net; SMS Tutorial; pp. 1-17; http://www.funsms.net/sms—tutorial.htm.
Isochron Data Corporation; Connect With Your Vending Machines—and Watch Your Profits Soar; www.isochron.com/solutions—VC.htm; (2002); pp. 1-2.
Lee, William C. Y.; Mobile Cellular Telecommunications Systems; ISBN 0-07-037030-3; 1989; pp. 74-80.
Mouly et al.; The GSM System for Mobile Communications; ISBN: 2-9507190-0-7; © 1992; pp. 56-59.
TIA/EIA 1S-41.5-C Standard; pp. 24, 65, 206, 207.
Related Publications (1)
Number Date Country
20120015677 A1 Jan 2012 US
Continuations (3)
Number Date Country
Parent 12704290 Feb 2010 US
Child 13247316 US
Parent 11811855 Jun 2007 US
Child 12704290 US
Parent 10885445 Jul 2004 US
Child 11811855 US
Continuation in Parts (1)
Number Date Country
Parent 09699312 Oct 2000 US
Child 10885445 US