Interconnect system and method for multiple protocol short message services

Information

  • Patent Grant
  • 7233802
  • Patent Number
    7,233,802
  • Date Filed
    Wednesday, September 29, 2004
    21 years ago
  • Date Issued
    Tuesday, June 19, 2007
    18 years ago
Abstract
A customer central location (CCL) communicates with multiple remote wireless devices employing mutually incompatible data formats or short message service (SMS) protocols. A communication, from the CCL to a remote device or from a remote device to the CCL, passes through a short message arbitrator (SMA), which determines the identifying characteristic(s) of the device receiving the communication. From the identifying characteristic(s), the short message arbitrator determines the expected data format and the transmission path to the device. The SMA converts the communication into the expected data format and transmits the communication over the appropriate transmission path.
Description
FIELD OF THE INVENTION

The present invention relates to the exchange of short messages between a central location and a remote location, and more particularly to identifying the recipient of each short message, identifying the data format expected by the recipient of the short message and converting the received short message to the identified data format.


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 system's 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 IS41 industry standard that is currently carried 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 IS41 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.


Thus, there is a need for a system in which a central location can communicate with several remote stations, which use different digital cellular or personal communications system (PCS) formats. The systems and methods discussed above only teach conversion between two specific formats.


SUMMARY OF THE INVENTION

The present invention meets the needs described above by providing a system and method for interconnecting digital cellular systems of multiple formats so that a customer central location (CCL) can send short messages to, or receive short messages from, multiple remote locations using different digital cellular or PCS standards. A short message arbitrator (SMA) intercepts a communication from the CCL to a remote location. The SMA retrieves information sent with the communication, such as the mobile identification number (MIN) or other identifying characteristic. The SMA uses the identifying characteristic to determine the mobile switching center (MSC) serving the remote location, the wireless access method used in the MSC's market, the CCL's class of service and the type of transport to be used between the SMA and the MSC. Based on the information retrieved from the database, the SMA determines whether the communication needs to be converted. If the communication needs to be converted, then the SMA converts the communication to the format expected by the remote device and sends the communication over the appropriate transmission path.


The SMA also intercepts a communication from a remote location to the CCL. The SMA retrieves information sent with the communication, such as the MIN and MSC identifier, or other identifying characteristic. The SMA uses the identifying characteristic to determine the recipient of the communication, in this case the CCL, and the class of service expected by the recipient. The SMA also uses the information stored in the database to determine whether the communication should be converted. If the communication should be converted, then the SMA performs the conversion and sends the communication to the CCL.


Therefore, it is an object of the present invention to provide a system and method for interconnecting multiple remote locations over multiple wireless (e.g., digital cellular and PCS) systems using multiple, otherwise incompatible protocols.


It is another object of the invention to provide a system and method for allowing a CCL to exchange short messages with such remote locations.


It is a further object of the invention to provide such a system and method using a single SMA which can determine the data format or short message system (SMS) protocol expected by the recipient (CCL or remote location), thereby avoiding the need for a separate bi-directional translator for every possible communication path.


It is still a further object of this invention to provide a method for integrating with and supporting all of the currently popular digital cellular systems, simultaneously, thus reducing deployment costs for cellular carriers.


It is yet another object of this invention to permit sending SMS messages originated in one type of cellular system to another dissimilar cellular system in a transparent manner.





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 of 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.





DETAILED DESCRIPTION

The present invention is directed to a system and method for interconnecting digital cellular systems of multiple formats so that a customer central location (CCL) can send short messages to, or receive short messages from, multiple remote locations using different digital cellular or PCS standards. Briefly described, a short message arbitrator (SMA) intercepts a communication between the CCL and the remote locations. The SMA retrieves information sent with the communication, such as the mobile identification number (MIN) or other identifying characteristic. The information is used to search a database to determine the data format used by the sender and expected by the recipient. Based upon the information retrieved from the database, the SMA determines whether the communication should be converted. If the communication should be converted, then the SMA converts the communication and transmits the communication to the intended recipient over the appropriate transmission path.


Exemplary System Architecture



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 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 Communications Methods



FIG. 3 and FIG. 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 FIG. 3 and FIG. 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


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. Therefore, the present invention should be construed as limited only by the present claims.

Claims
  • 1. A system for interconnecting a plurality of data communication devices, the system comprising: a first data communication path for receiving a transmission from a first data communication device;an arbitrator operative to automatically: determine, from the transmission, an identity of a second data communication device,determine, from the identity of the second data communication device, a selected data format from a group of at least three data formats, the selected data format being expected by the second data communication device, andconvert the transmission into the selected data format determined from the identity of the second data communication device; anda second data communication path for transmitting the transmission converted by the arbitrator to the second data communication device.
  • 2. The system of claim 1, wherein each of the plurality of data communication devices has an identifying characteristic, and wherein the arbitrator is further operative to: maintain a database that stores the identifying characteristics of each of the plurality of data communication devices;retrieve the identifying characteristic of the first data communication device from the transmission received; andsearch the database with the identifying characteristic of the first data communication device to determine the identity of the second data communication device.
  • 3. The system of claim 2, wherein the database stores a data format expected by each of the plurality of data communication devices, and wherein the arbitrator is further operative to search the database using the identifying characteristic of the first data communication device to determine the data format expected by the second data communication device.
  • 4. The system of claim 1, wherein each of the plurality of data communication devices has an identifying characteristic, and wherein the arbitrator is further operative to: maintain a database that stores the identifying characteristics of each of the plurality of data communication devices;retrieve the identifying characteristic of the second data communication device from the transmission received; andsearch the database with the identifying characteristic of the second data communication device.
  • 5. The system of claim 4, wherein the database stores a method of transport to each of the plurality of data communication devices, and wherein the arbitrator is further operative to: search the database with the identifying characteristic of the second data communication device to determine the method of transport to the second data communication device; andtransmit the transmission that is converted into the data format that is expected by the second communication device using the method of transport determined for the second data communication device.
  • 6. The system of claim 1, wherein at least one of the first and second data communication devices is a wireless device, and wherein at least one of the first and second data communication paths is a data communication path for communicating with the wireless device.
  • 7. The system of claim 1, wherein the first data communication device uses a first data format and the second data communication device uses a second data format which is incompatible with the first data format, and wherein the arbitrator is further operative to convert the transmission from the first data format to the second data format.
  • 8. The system of claim 1, wherein the data format is selected from the group comprising time division multiple access, code division multiple access and global system for mobile telecommunications.
  • 9. A system for managing communication among a plurality of data communication devices, the system comprising: a first data communication device for dispatching a first data transmission using a first wireless access method;a second data communication device for dispatching a second data transmission using a second wireless access method distinct from the first wireless access method;a third data communication device for receiving the second data transmission from the second data communication device; andan arbitrator for: receiving the first data transmission from the first data communication device,determining, from the first data transmission, an identity of the third data communication device to receive the first data transmission,determining a data format from at least three potential data formats, the data format being expected by the third data communication device for the first data transmission,converting the first data transmission to the data format expected by the third data communication device, andtransmitting the converted first data transmission to the third data communication device.
  • 10. The system of claim 9, wherein each of the plurality of data communication devices has an identifying characteristic, further comprising: a database for maintaining information regarding the plurality of data communication devices and the identifying characteristic of each of the plurality of data communication devices, whereby the arbitrator retrieves the identifying characteristic of the first data communication device from the first data transmission and searches the database with the identifying characteristic of the first data communication device to determine the identity of the third data communication device.
  • 11. The system of claim 10, wherein the database stores the data format expected by each of the plurality of data communication devices and the arbitrator searches the database with the identifying characteristics of the first data communication device to determine the data format expected by the third data communication device.
  • 12. The system of claim 10, wherein the arbitrator is further operative to compare the data format expected by the third data communication device with a data format used by the first data communication device.
  • 13. The system of claim 10, wherein at least one of the first and second data communication devices is a wireless device.
  • 14. The system of claim 9, wherein the arbitrator is further operable for, receiving the second data transmission from the second data communication device before it is transmitted to the third data communication device;determining a data format from at least three potential data formats, the data format being expected by the third data communication device for the data transmission;converting the second data transmission to the data format expected by the third data communication device; andtransmitting the converted second data transmission to the third data communication device.
  • 15. A method for communicating among a plurality of data communication devices associated with a plurality of wireless access methods comprising: receiving a converted first transmission from an arbitrator wherein the arbitrator created the converted first transmission from an original first transmission by, receiving the original first transmission from a first data communication device associated with a first wireless access method;retrieving a mobile identification number (MIN) from the original first transmission;using the MN to identify a second data communication device and a data format expected by the second data communication device; andconverting the original first transmission so that it is compatible with the data format expected by the second data communication device.
  • 16. The method of claim 15, wherein the arbitrator is further operable for storing the data format used by the second data communication device.
  • 17. The method of claim 15, wherein the step of converting the original first transmission comprises converting the first wireless access method from one of the group consisting of time division multiple access, code division multiple access, and global system for mobile telecommunications.
  • 18. The method of claim 15, further comprising the steps of retrieving a mobile switching center identification number (MSCID) for a mobile switch associated with the first data communication device from the original first transmission; andusing the MSCID for converting the original first transmission so that it is compatible with the data format expected by the second data communication device.
  • 19. A method for communicating between a first data communication device and a second data communication device comprising: receiving a first transmission from the first data communication device associated with a first communication protocol;retrieving a mobile identification number (MiN) from the first transmission;using the MN to identify the second data communication device and a second communication protocol expected by the second data communication device;converting the first communication protocol of the first transmission so that it is compatible with the second communication protocol; andtransmitting the converted first transmission to the second data communication device.
  • 20. The method of claim 19, further comprising the step of retrieving the second communication protocol from a storage device.
  • 21. The method of claim 19, wherein the step of converting the first transmission comprises converting the first communication protocol from one of the group consisting of time division multiple access, code division multiple access, and global system for mobile communication.
  • 22. The method of claim 19, further comprising the steps of retrieving a mobile switching center identification number (MSCID) for a mobile switch associated with the first data communication device from the first transmission; andusing the MSCID for converting the first transmission so that it is compatible with the data format expected by the second data communication device.
  • 23. A computer-readable storage device storing a set of computer-executable instructions implementing a method for communicating between a first data communication device and a second data communication device comprising: receiving a first transmission from the first data communication device associated with a first communication protocol;retrieving a mobile identification number (MIN) from the first transmission;using the MN to identify the second data communication device and a second communication protocol expected by the second data communication device;converting the first communication protocol of the first transmission so that it is compatible with the second communication protocol; andtransmitting the converted first transmission to the second data communication device.
  • 24. The computer-readable storage device of claim 23 storing a set of computer-executable instructions further comprising the step of retrieving the second communication protocol from a storage device.
  • 25. The computer-readable storage device of claim 23 storing a set of computer-executable instructions wherein the step of converting the first transmission comprises converting the first communication protocol from one of the group consisting of time division multiple access, code division multiple access, and global system for mobile communication.
  • 26. The computer-readable storage device of claim 23 storing a set of computer-executable instructions further comprising the steps of retrieving a mobile switching center identification number (MSCID) for a mobile switch associated with the first data communication device from the first transmission; andusing the MSCID for converting the first transmission so that it is compatible with the data format expected by the second data communication device.
  • 27. An arbitrator for interconnecting a plurality of data communication devices, the arbitrator comprising: means for determining an identity of a receiving data communication device from a transmission received from a sending data communication device;means for determining from the identity of the receiving data communication device, a selected data format from a group of at least three data formats, the selected data format being expected by the receiving data communication device; andmeans for converting the transmission into the selected data format determined from the identity of the receiving data communication device.
  • 28. The arbitrator of claim 27, wherein the arbitrator further comprises: means for maintaining a database that stores identifying characteristics of each of the plurality of data communication devices; andmeans for retrieving the selected data format being expected by the receiving data communication device using the identity of the receiving data communication device.
  • 29. The arbitrator of claim 27, wherein the data format of the sending communication device is different from the data format of the receiving data communication device.
RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patent application Ser. No. 09/699,312, filed Oct. 27, 2000 now U.S. Pat. No. 6,856,808 and entitled “Interconnect System and Method for Multiple Protocol Short Message Services,” which claims priority to U.S. Provisional Patent Application No. 60/162,413, filed Oct. 29, 1999 and having the same title. The content of both of these applications is hereby fully incorporated herein by reference.

US Referenced Citations (310)
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
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
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
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
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
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
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
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
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
5924026 Krishnan Jul 1999 A
5933784 Gallagher et al. Aug 1999 A
5946629 Sawyer et al. Aug 1999 A
5946630 Willars et al. Aug 1999 A
5999808 LaDue Dec 1999 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
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
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
6175732 McDaniel 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
6259781 Crouch et al. Jul 2001 B1
6263212 Ross et al. Jul 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
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
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
6397056 Bugnon et al. May 2002 B1
6405033 Kennedy, III et al. Jun 2002 B1
6424828 Collins et al. Jul 2002 B1
6424841 Gustafsson Jul 2002 B1
6457038 Defosse Sep 2002 B1
6476763 Allen Nov 2002 B2
6484035 Allen Nov 2002 B2
6487602 Thakker Nov 2002 B1
6493556 Stinson Dec 2002 B1
6493558 Bernhart et al. Dec 2002 B1
6515997 Feltner et al. Feb 2003 B1
6560456 Lohtia et al. May 2003 B1
6570532 Mise et al. May 2003 B2
6618671 Dooley et al. Sep 2003 B2
6622016 Sladek et al. Sep 2003 B1
6625461 Bertacchi Sep 2003 B1
6710738 Allen 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
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
6856808 Comer et al. Feb 2005 B1
6865191 Bengtsson et al. Mar 2005 B1
6882843 Comer Apr 2005 B1
20010003093 Lundin Jun 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 Aug 2002 A1
20020155844 Rankin et al. Oct 2002 A1
20020160771 Massie et al. Oct 2002 A1
20020164988 Vishwanathan et al. Nov 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 May 2003 A1
20030101257 Godwin May 2003 A1
20030101262 Godwin May 2003 A1
20030119498 Haas et al. Jun 2003 A1
20030129969 Rucinski Jul 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
20040203640 Molander et al. Oct 2004 A1
20050037784 Cleary Feb 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
WO9819438 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 2006014419 Nov 2002 WO
WO 0319925 Mar 2003 WO
WO 2005074430 Aug 2005 WO
Related Publications (1)
Number Date Country
20050101317 A1 May 2005 US
Provisional Applications (1)
Number Date Country
60162413 Oct 1999 US
Continuations (1)
Number Date Country
Parent 09669312 Oct 2000 US
Child 10952710 US