JP3847203B2 - Gateway device - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a gateway device arranged between different mobile communication networks.
[0002]
[Prior art]
As digital mobile communication systems, systems such as PDC (Personal Digital Cellular telecommunication system), GSM (global system for mobile communication), IS-95, and IS-136 are known. The PDC system is implemented in Japan, and the GSM system is prevalent mainly in Europe. In North America, systems such as GSM, IS-95, and IS-136 are used. In these mobile communication networks, a service for delivering a short message from a mobile station to a mobile station is performed.
[0003]
[Problems to be solved by the invention]
SMPP (Short Message Peer to Peer Protocol) is known as a protocol used for transmitting and receiving short messages. It is considered that short messages can be basically exchanged when a carrier supports SMPP together between different mobile communication networks. However, if the versions are different, SMPP may be specialized for the operator, and short messages cannot be exchanged if SMPP is not an upward compatible protocol. Also, different languages are used in different mobile communication networks, the character code used on one side is a 2-byte code and 1-byte code, and the character code used on the other side is only a 1-byte code. If it is, the meaning of the short message cannot be understood because the language is different even if it is garbled or not garbled.
[0004]
Accordingly, a first object of the present invention is to provide a gateway device capable of exchanging short messages capable of communicating as much as possible between mobile communication networks using different languages.
In addition, some operators have a plurality of short message servers for each region. In such a case, broadcasting to all the short message servers from the gateway increases the burden on the short message server. was there.
Accordingly, a second object of the present invention is to provide a gateway device that can reduce the burden on the short message server in a mobile communication network in which a plurality of short message servers are provided for each region.
In addition, when there is a failure in the partner network or in its own network, messages are spooled to the gateway device, and the spooled messages are delivered at one time when the failure is recovered, causing traffic to increase rapidly. It was.
Therefore, a third object of the present invention is to provide a gateway device that can prevent a sudden increase in traffic.
[0005]
[Means for Solving the Problems]
In order to achieve the first object, the gateway device of the present invention is arranged between the mobile communication networks in order to exchange messages between mobile stations belonging to mobile communication networks that can handle different languages. A gateway device, in which a fixed sentence that can be selected as a message body of a message is prepared for each different language, and a database in which a plurality of the fixed sentences are stored in association with number information that specifies the fixed sentence Conversion means for converting the fixed text into a fixed text in a language that can be handled by the mobile communication network of the message destination when the fixed text is included in the message body from the message sender, Determining a mobile communication network to which the message is addressed from a telephone number dialed by a sender of the message; Conversion means But , From the database using the fixed sentence number information contained in the message body Said The message is converted by searching a fixed phrase in a language that can be handled by the mobile communication network of the message destination.
[0006]
In the gateway device of the present invention, the conversion means converts a 2-byte code character included in the message body into a corresponding 1-byte code character in addition to the standard sentence conversion. You may do it.
[0007]
Furthermore, in the gateway device of the present invention described above When a message received from one mobile communication network is distributed to another mobile communication network that is a destination, a message destination of a plurality of short message server groups provided in the other mobile communication network is set. The message is delivered to the short message server of any of the short message server groups corresponding to the telephone number information shown May .
[0008]
Furthermore, in the gateway device of the present invention, When a message received from one mobile communication network or other mobile communication network spooled at the time of failure is distributed to another mobile communication network or one mobile communication network that is the destination at the time of failure recovery, traffic accompanying the distribution Gradually increase to the maximum value along the time axis May .
[0009]
According to the present invention as described above, when a fixed message is included in the message body from the message sender, the fixed message is converted into a fixed message in a language that can be handled by the mobile communication network of the message destination and distributed. Like to do. For this reason, it is possible to understand the delivered message as much as possible in a mobile station in a mobile communication network with a different language. Also, since the 2-byte code characters are converted to the corresponding 1-byte code characters, the message can be delivered without being garbled.
[0010]
Further, the present invention uses the telephone number information indicating the destination of the message to distribute the message only to the short message server of the short message server group provided in the corresponding area. The burden can be reduced.
Furthermore, according to the present invention, the traffic is gradually increased up to the maximum value along the time axis at the time of failure recovery, so that it is possible to prevent a sudden increase in traffic.
[0011]
DETAILED DESCRIPTION OF THE INVENTION
FIG. 1 shows an outline of the configuration of a mobile communication network including a gateway device according to an embodiment of the present invention.
A gateway device (GSMS GATEWAY) 13 according to the present invention is provided between the first mobile communication network 1 and the second mobile communication network 2. For example, it is assumed that the first mobile communication network 1 is a mobile communication network of a communication provider of a PDC system in Japan, and the second mobile communication network 2 is a mobile communication network of a communication provider of a GSM system in North America. As described above, since the distance between the first mobile communication network 1 and the second mobile communication network 2 is greatly separated, the first mobile communication network 1 and the second mobile communication network 2 are connected using the Internet 40. Has been. In this case, since the Internet 40 is a global information network and widely released, security measures are taken. For this purpose, security devices 14 and 41 in which a VPN (Virtual Private Network) is combined with a firewall (FW) are arranged at the entrance and exit of the Internet 40. VPN is a method of using an open network such as the Internet like a private dedicated network.
[0012]
The first mobile communication network 1 is divided into three areas, area A, area B, and area C, and a plurality of SMSCs (Short Message Service Centers) are arranged in each area. The main function of the SMSC is to send and receive short messages. For example, the area A is provided with the SMSC group 12 including SMSCs 12a, 12b,..., The area B is provided with the SMSC group 22 including SMSCs 22a, 22b,. An SMSC group 32 including SMSCs 32a, 32b,... Is provided. The number of SMSCs in each SMSC group is determined according to the traffic volume of message delivery. When the gateway device 13 is activated, the gateway device 13 is connected to all the SMSCs of the SMSC group 12, the SMSC group 22, and the SMSC group 32 by establishing an SMPP binding. The SMSC group 22 and the SMSC group 32 are connected via a wide area network (WAN) 35 that is a wide area network. In area A, area B, and area C, mobile station 11, mobile station 21, and mobile station 31 are located, respectively.
The second mobile communication network 2 includes a gateway device 42 and an SMSC 43, and the mobile station 44 is in the area.
[0013]
The SMSC group 12, the SMSC group 22, and the SMSC group 32 are connected to an SMS gateway (shown as “gateway device 13” in FIG. 1) that is a server connected to the SMSC (SMPP (Short Message Peer to Peer Protocol)). ) As a protocol to send and receive short messages. This SMPP will be described with reference to FIG. FIG. 2 shows a configuration in which a short message is transmitted and received by the SMSP between the SMS gateway 50 and the SMSC 51 which are servers connected to the SMSC. The SMPP is used for communication between the SMSC 51 and the SMS gateway 50 that are used to send and receive short messages. Basically, SMPP adopts a form in which a socket is established by TCP over TCP / IP, and data flows through the socket. In this case, two sessions for transmission and reception are established as data transfer channels.
[0014]
Here, the SMS gateway 50 sends a bind transmitter command to the SMSC 51 and receives a confirmation response resp from the SMSC 51, thereby establishing a transmission channel between the transmitter 51a of the SMSC 51 and the transmission port 50a of the SMS gateway 50. Also, the SMS gateway 50 sends a bind receiver command to the SMSC 51 and receives an acknowledgment response resp from the SMSC 51, whereby a reception channel is established between the reception port 50b of the SMS gateway 50 and the receiver 51b of the SMSC 51. In SMPP, it is defined as a specification that a confirmation response resp is always returned when data is received. The SMPP is composed of a header and a body. The header has a fixed length of 20 bytes, and the body has a variable length.
[0015]
The SMPP command will be described with reference to the sequence diagram between the SMS gateway 50 and the SMSC 51 shown in FIG.
The bind_receiver command is a command for securing a channel (path) for communication between the SMSC 51 and the SMS gateway 50 as described above. This channel is used for data transfer from the SMSC 51 to the SMS gateway 50. The bind_transmitter command is a command for securing a channel (path) for communication between the SMSC 51 and the SMS gateway 50 as described above. This channel is used for data transfer from the SMS gateway 50 to the SMSC 51. Further, the unbind command is a command for disconnecting the established channel, and the submit_sm command is a command used for delivering a message from the SMS gateway 50 to the SMSC 51.
[0016]
Furthermore, the deliver_sm command is a command used for delivering a message from the SMSC 51 to the SMS gateway 50, contrary to the submit_sm command. Furthermore, the delivery_receipt command is a command for requesting message delivery confirmation, and the query_sm command is a command for confirming the message delivery status. Furthermore, the cancel_sm command is a command for canceling the message delivery, and the replace_sm command is a command for replacing the delivery content of the message. Furthermore, the require_link command is a command for verifying the normality of the SMPP binding.
[0017]
Version 3 used in the international standard for SMPP. x and version 4, which is an original specification expanded for Japan. x exists. SMPP is an upper protocol located in the application layer on TCP / IP, and there is no compatibility between major versions. In order to communicate via different versions of SMPP, it is necessary to perform version conversion between them. It becomes. For example, the SMPP version in the mobile communication network 1 is 4.0, and the SMPP version in the second mobile communication network 2 is 3.4. For this purpose, the SMPP version conversion is performed in the gateway device 13 that relays both protocols. Next, the session shown in FIG. 4 and FIG. 5 to be converted will be described. x and version4. x is basically the same specification.
[0018]
FIG. 4 shows a receiver data command sequence. In this sequence, a command indicated by white characters is a command to be converted. That is, the bind_receiver command, bind_receiver_resp command, deliver_sm command, delivery_receipt command, and delivery_receipt_resp command are the conversion target commands. FIG. 5 shows a transmitter data command sequence. In this sequence, a command indicated by white characters is a command to be converted. That is, the bind_transmitter command, submit_sm command, submit_sm_resp command, query_sm command, and replace_sm command are the conversion target commands. For these commands to be converted, the data structure of the header or body is different for different versions.
[0019]
Next, a message transmission process shown in FIG. 6 will be described by taking as an example a case where a message is sent from the mobile station 11 belonging to area A in the first mobile communication network 1 shown in FIG. 1 to the mobile station 44 in the second mobile communication network 2. This will be described with reference to the flowchart.
When the mobile station 11 transmits a message by dialing an address of AAAA (Prefix: identification information) + BB (country code) + XXXXYYYY (phone number of the mobile station 44), the SMSC 12 sets the second prefix in step S10. It is determined whether the value is for GSMS (global SMS) for delivering a message to the mobile communication network 2. If the Prefix value AAAA is a value for GSMS, the process proceeds to step S12. If it is determined that the value is not for GSMS, the process branches to step S11 to perform normal SMS processing, and the message transmission processing ends. The processes in step S10 and step S11 are executed in the SMSC 12.
[0020]
In step S12, it is determined whether or not SMS transmission for delivering a message to the gateway device 13 is accepted. When the SMSC 12 receives the confirmation response resp that the message data has been received from the gateway device 13, it is determined that the SMS transmission has been accepted. Here, when it is determined that the SMS transmission is accepted by the gateway device 13, the process proceeds to step S14. If it is determined that the gateway apparatus 13 has not accepted the SMS transmission, the process branches to step S13 to perform a retransmission process for retransmitting message data from the SMSC 12, and the process returns to step S12. In this way, the retransmission process in step S13 is performed until the SMS transmission is accepted by the gateway device 13. In step S14, it is determined whether or not the value of PDC_MessageClass in the deliver_sm command for delivering a message from the SMSC 12 to the gateway device 13 is “0x2000 (0x indicates hexadecimal)”. When this Value is determined to be “0x2000”, this is a case where standard SMS transmission is performed in which a message is sent from one sender to one recipient. When Value is determined to be “0x2000”. The process proceeds to step S16.
[0021]
On the other hand, if it is determined that Value is not “0x2000”, the process branches to step S15 to perform analysis processing of SMS transmission. In the analysis processing in step S15, when Value is “0x1001”, it is analyzed as an SMS transmission service that can send a message from one sender to two or more recipients. When Value is “0x1002” Is analyzed as an SMS transmission of a chat service between two subscribers. Further, when Value is “0x1003”, it is analyzed as SMS transmission of a relay mail service that sends a chained mail, and when Value is “0x1004”, the sender can specify the message transmission date and time. It is analyzed as the SMS transmission of the timer transmission service. If a service whose Value is other than “0x2000” is not supported in the second mobile communication network 2, delivery of a message accompanied by these services is rejected when performing transmission restriction processing described later. . When the analysis process in step S15 ends, the process proceeds to step S16.
[0022]
In step S16, it is determined whether PDC_PredefiendMsg is defined in the deliver_sm command. Here, when PDC_PredefiendMsg is not defined, it is a case where a fixed phrase is not included in the message. When it is determined that PDC_PredefiendMsg is not defined, the process proceeds to step S18. On the other hand, if it is determined that PDC_PredefiendMsg is defined, the process branches to step S17 to perform a fixed sentence conversion process. Although this conversion process will be described later, it is converted into a language used in the second mobile communication network 2 to which the fixed sentence corresponds, for example, a fixed sentence in English notation, as described later. When the process of step S17 ends, the process proceeds to step S18. In step S18, it is determined whether or not the message includes a kanji-like 2-byte code. Here, if it is determined that a kanji-like 2-byte code is included, the process branches to step S19, and the kanji-like 2-byte code character is converted into a corresponding 1-byte Roman character. Then, the process proceeds to step S20 as in the case where it is determined in step S18 that the kanji-like 2-byte code is not included.
[0023]
In step S20, it is determined whether or not a pictograph is included in the message. If it is determined that a pictograph is included in the message, the process branches to step S21 to move an error message indicating that the pictograph cannot be delivered because the pictograph is hardly supported except for the first mobile communication network 1. It returns to the station 11 and the message transmission process is completed. If it is determined that the message does not include a pictograph, the message is transmitted to the gateway device 42 of the second mobile communication network 2. Next, in step S23, it is determined whether or not SMS transmission for delivering a message to the gateway device 42 has been accepted. When the gateway device 13 receives the bind confirmation response resp from the gateway device 42, it is determined that the SMS transmission has been accepted. If it is determined that the gateway device 42 has accepted the SMS transmission, the process proceeds to step S25. If it is determined that the SMS transmission is not accepted by the gateway device 42, the process branches to step S24, performs a retransmission process, and returns to step S23. In this way, the retransmission processing in step S24 is performed until the SMS transmission is accepted by the gateway device 42.
[0024]
In step S25, it is determined whether or not SMS transmission restriction is applied. Here, if there is a message service that is not supported in the second mobile communication network 2 (various SMS transmission services described in relation to step S15), it is determined that SMS transmission is restricted, and the process branches to step S26. To do. If the message delivered in step S26 is a message accompanied by an unsupported message service in the second mobile communication network 2, the delivery is rejected, and the message service supported by the delivered message is If it is a accompanying message, it will be distributed. And it progresses to step S27 similarly to the case where it is judged in step S25 that the SMS transmission restriction is not applied. In step S27, SMPP version 4.0 is converted to version 3.4, and the message including the fixed text converted into English and the message body converted into Romaji in step S28 is transferred from gateway apparatus 13 to gateway apparatus 42. Send. Next, in step S29, the transmission result is recorded in the log, and the message transmission process ends. In addition, the traffic condition in the gateway apparatus 13 can be monitored periodically by recording in the log.
[0025]
Next, taking the case where the mobile station 11 belonging to area A in the first mobile communication network 1 shown in FIG. 1 receives a message from the mobile station 44 in the second mobile communication network 2 as an example, the message reception shown in FIG. This will be described with reference to a flowchart of the process.
When the mobile station 44 in the second mobile communication network 2 transmits a message to the mobile station 11 belonging to the area A in the first mobile communication network 1, the gateway device 13 in the first mobile communication network 1 that has received this message Then, it is determined whether or not the country code in the message address is “81” indicating Japan (step S30). If it is determined that the country code is “81”, the process proceeds to step S32. If it is determined that the country code is not “81”, the process branches to step S31. In step S31, since the message is not addressed to Japan, the message reception process ends without accepting the message. The gateway device 13 is adapted to receive a message from a communication network of another domestic telecommunications carrier, and the message processing is performed in step S31. In step S32, it is determined whether or not a character other than the ASCII code is included in the message. If it is determined that a character other than the ASCII code is included, the process branches to step S39 and the message cannot be delivered. An error message to that effect is sent back to the sender, and the message reception process ends.
[0026]
Furthermore, if it is determined in step S32 that the message contains no characters other than the ASCII code, the process proceeds to step S33 to determine whether the message size is 128 bytes or more. This is because the second mobile communication network 2 supports a size in which the maximum length of a short message exceeds 128 bytes, but the maximum message length per message of the mobile station 11 in the first mobile communication network 1 is 128 bytes. It is because it is said. That is, when a message exceeding 128 bytes is transmitted as it is, a situation in which the mobile station 11 cannot receive normally occurs. In order to prevent this, when a short message having a size exceeding 128 bytes arrives at the gateway device 13, the gateway device 13 automatically senses it and divides the message into an appropriate size to the mobile station 11. I am trying to send it. Such processing is performed in steps S33 to S35.
[0027]
That is, if it is determined in step S33 that the message size exceeds 128 bytes, the process branches to step S34 to determine whether the message is within 384 bytes. This is because the first mobile communication network 1 supports messages of up to 3 divisions and can only be distributed within 128 × 3 = 384 bytes. Therefore, if it is determined in step S34 that the message exceeds 384 bytes, the process branches to step S39 and an error message indicating that the message cannot be delivered is returned to the transmission source, and the message reception process ends. If it is determined in step S34 that the message is within 384 bytes, it is divided into messages of up to 128 bytes in step S35. Then, the process proceeds to step S36 as in the case where it is determined in step S33 that the message size does not exceed 128 bytes. In step S36, conversion from SMPP version 3.4 to version 4.0 is performed, and the transmission result is recorded in a log in step S37. Next, in step S38, the message is transmitted from the gateway device 13 to the SMSC 12. As a result, the message is delivered from the SMSC 12 to the mobile station 11, and the message reception process is terminated.
[0028]
Next, a fixed sentence conversion process executed in the gateway device according to the present invention will be described with reference to FIGS.
FIG. 8 is a diagram showing an outline of a configuration for sending a message from the mobile station 100 to the mobile station 105. In this case, Japanese is used in the mobile communication network in which the mobile station 100 is located, and the mobile station 105 It is assumed that English is used in the mobile communication network in the area. The SMS message is received by the SMSC 101 and the message sent from the mobile station 100 is sent to the gateway device 102 according to the present invention using the SMPP. The gateway device 102 includes a fixed sentence database 103. In the fixed sentence database 103, as shown in FIG. 9, a document number for specifying a fixed sentence, a Japanese fixed sentence corresponding to the document number, and an English fixed sentence are stored as a set. For example, the standard text of document number 12 is “Good morning” in Japanese and “Good morning” in English, and the standard text of document number 22 is “(1) Congratulations (2)!” “Congratulation on (2) (1)”. For example, “Birthday”, “Pass”, “Win”, etc. can be entered in (1) in the document number 22, and a name or the like can be entered in (2). In this case, for example, if “birthday” is inserted in (1) and (2), it is converted to “birthday”, so a translation database for the translation is prepared in the database 103.
[0029]
Here, if the mobile station 100 selects and sends a fixed phrase “Good morning” as a message, the gateway apparatus 102 analyzes the PDC_PredefiendMsg field of the deliver_sm command in SMPP, and if PDC_PredefiendMsg is defined, the message Is searched for the document number of the fixed sentence. In this case, the document number 12 is retrieved, and the English fixed phrase “Good morning” in the retrieved document number 12 is read out to convert it into an English message. The English message converted in this way is sent from the gateway apparatus 102 to the SMSC 104 using the SMPP, and delivered from the SMSC 104 to the mobile station 105. As a result, the Japanese message “Good morning” transmitted by the mobile station 100 is delivered to the mobile station 105 as an English message “Good morning”. Also, if the mobile station 100 selects and sends a fixed phrase “(Birthday) Congratulations (Tom)!” As a message, the gateway station 102 similarly converts it into an English fixed phrase and sends a message to the mobile station 105. It will be distributed as "Congratulation on your birthday Tom!"
[0030]
Incidentally, the SMSC arrangement in the first mobile communication network 1 is divided into area A, area B, and area C, and a plurality of units according to the current load are arranged. However, an increase in message delivery traffic and message delivery traffic for GSMS may cause a high load on the SMSC and cause a failure. Therefore, the gateway device 13 has a message distribution function. In the message distribution function, the number system function of the first mobile communication network 1 is used. That is, the first mobile communication network 1 adopts a format of “0A0CDE XXXX” as the numbering system, and can identify the communication carrier by ACDE. In addition, by using these four digits, it is possible to determine to which SMSC in any one of area A, area B, and area C the short message is routed. Therefore, the gateway device 13 is provided with a database that holds information on the numbering system and the areas A, B, and C, and the SMSC in any of the corresponding areas A, B, and C based on the address of the incoming message. It has a function to route to.
[0031]
When a failure occurs in the mobile communication network such as the first mobile communication network 1 or the second mobile communication network 2 connected thereto, the message is spooled in the gateway device 13. Spooled messages are automatically sent when a failure is restored and the session is reestablished. However, in this case, since a large number of messages are transmitted, there is a possibility that troubles occur due to bursty traffic. Therefore, in order to prevent this, the traffic is narrowed down at the initial stage when the failure is recovered, and processing for gradually increasing traffic is performed after the stability of communication is confirmed.
[0032]
FIG. 9 shows a flowchart of system trouble processing executed by such a gateway device 13.
In the flowchart shown in FIG. 9, when a system trouble occurs, a message is spooled (step S40). Next, in step S41, it is determined whether or not the system has been restored. If the system has not been restored, the process returns to step S40 and message spooling continues. If it is determined in step S41 that the system has been restored, the process proceeds to step S42 to perform SMS transmission restart processing for establishing a transfer channel. Subsequently, in step S44, the spooled message is transmitted so that the traffic gradually increases along the time axis. This traffic state is determined in step S44, and traffic is gradually increased in step S43 until the maximum traffic is reached. If it is determined in step S44 that the maximum traffic has been reached, the process proceeds to step S45, where the transmission amount restriction is released, and the system trouble processing ends.
[0033]
In the above description, when a pictograph is included in the message, an error message indicating that the message cannot be delivered is returned to the mobile station 11. Instead, the pictograph is replaced with another symbol such as “?”. Or the message may be delivered by deleting the pictograph.
[0034]
【The invention's effect】
As described above, in the present invention, when a fixed message is included in the message body from the message sender, the fixed message is converted into a fixed message in a language that can be handled by the mobile communication network of the message destination and distributed. Like to do. For this reason, it is possible to understand the delivered message as much as possible in a mobile station in a mobile communication network with a different language. Also, since the 2-byte code characters are converted to the corresponding 1-byte code characters, the message can be delivered without being garbled.
[0035]
Furthermore, since the present invention uses the telephone number information indicating the message destination to distribute the message only to a specific short message server provided in the corresponding area, the burden on each short message server is reduced. can do.
Furthermore, according to the present invention, the traffic is gradually increased up to the maximum value along the time axis at the time of failure recovery, so that a sudden increase in traffic can be prevented and trouble can be prevented.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating an outline of a configuration of a mobile communication network including a gateway device according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating a configuration in which a short message is transmitted / received between an SMS gateway and an SMSC by SMPP.
FIG. 3 is a sequence diagram of SMPP between the SMS gateway and the SMSC.
FIG. 4 is a sequence diagram of a receiver data command in the SMPP between the SMS gateway and the SMSC.
FIG. 5 is a sequence diagram of a transmitter data command in the SMPP between the SMS gateway and the SMSC.
FIG. 6 is a flowchart of message transmission processing executed by the gateway device according to the embodiment of the present invention.
FIG. 7 is a flowchart of message reception processing executed by the gateway device according to the embodiment of the present invention.
FIG. 8 is a diagram showing an outline of a configuration that includes a gateway device according to an embodiment of the present invention and sends a message from a mobile station 100 to a mobile station 105;
FIG. 9 is a diagram showing data held in a database included in the gateway device according to the embodiment of the present invention.
FIG. 10 is a flowchart of system trouble processing executed by the gateway device according to the embodiment of the present invention.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 1 1st mobile communication network, 2 2nd mobile communication network, 11 Mobile station, 12 SMSC group, 12a, 12b SMSC, 13 Gateway apparatus, 14,41 Security apparatus, 21 Mobile station, 22 SMSC group, 22a, 22b SMSC, 31 mobile station, 32 SMSC group, 32a, 32b SMSC, 40 Internet, 42 gateway device, 43 SMSC, 44 mobile station, 50 SMS gateway, 50a transmit port, 50b receive port, 51 SMSC, 51a transmitter, 51b receiver, 100 move Station, 101 SMSC, 102 gateway device, 103 database, 104 SMSC, 105 mobile station

Claims (4)

A gateway device arranged between the mobile communication networks for exchanging messages between mobile stations belonging to mobile communication networks capable of handling different languages,
A standard sentence that can be selected as a message body of a message is prepared for each different language, and a database in which a plurality of the standard sentences are stored in association with number information that specifies the standard sentence;
A conversion means for converting the standard text into a standard text in a language that can be handled by the mobile communication network of the message destination when the standard text is included in the message body from the message sender;
Determining mobile communication network of the destination of the message from the telephone number that sender dials the message, the converting means, by using the number information of the fixed phrase is included in the message body, the message from the database A gateway apparatus characterized in that it is converted by searching a fixed phrase in a language that can be handled by a mobile communication network of the destination.   The conversion means is characterized in that, in addition to the conversion of the fixed sentence, the 2-byte code character included in the message body is converted into a corresponding 1-byte code character. The gateway device according to 1. In the gateway device,
When a message received from one mobile communication network is distributed to another mobile communication network that is a destination, the message destination of a plurality of short message server groups provided in the other mobile communication network is indicated. 2. The gateway device according to claim 1 , wherein the message is distributed to a short message server of any of the short message server groups corresponding to the telephone number information. In the gateway device,
When a message received from one mobile communication network or another mobile communication network spooled at the time of failure is distributed to another mobile communication network or one mobile communication network that is the destination at the time of failure recovery, 2. The gateway device according to claim 1, wherein the gateway device gradually increases up to a maximum value along a time axis.

Images