JP2020191071A - Message management server, message management method, message management program, and message management system - Google Patents

Abstract

To provide the versatile data transmission/reception desired by a transmission side without causing a troublesome labor or economic burden to a user on the receiving side, even when data cannot be received at a portable telephone terminal on the receiving side.SOLUTION: The present invention comprises: a delivery unit for delivering a first message in which a first protocol is used to a portable telephone terminal; an error reception unit for receiving the transmission error of first message by the delivery unit; a determination unit for determining, on the basis of a prescribed condition, whether or not to resend the data included in the first message to the portable telephone terminal using a second message in which a second protocol different from the first protocol and having compatibility with the first protocol is used or a message tool which is either an electronic mail or a chat system; and a conversion unit for converting to the data format of the message tool, the converted data being delivered to the portable telephone terminal.SELECTED DRAWING: Figure 2

Description

The present invention relates to a message management server, a message management method, a message management program and a message management system.

In recent years, short message services (SMS (Short Message Service)) provided by each telecommunications carrier that provides mobile phone services for sending messages between users of mobile phone terminals and delivering advertisements from companies to users have been utilized. Has been done. The short message service is a service that does not use the traffic channel used for e-mail, but uses a signaling channel to specify the telephone number of the mobile phone terminal as the destination to send a message. By using the telephone number of the mobile phone terminal as the destination, the user can send the message only by the telephone number of the user to whom the message is sent. In addition, since the signaling channel uses a communication protocol that is lighter and simpler than the communication protocol used for the traffic channel, the message transmitted by the short message service (hereinafter referred to as short message) has an advantage of excellent real-time performance. is there. On the other hand, in the case of short message, since a lightweight communication protocol using a telephone line is used, there is a demerit that the communication capacity per communication is limited. For example, the number of characters in a short message that can be sent at one time is about 60 to 80 characters, so if the number of characters exceeds this, it is necessary to send it in multiple times, and images cannot be sent. There were restrictions such as.

Therefore, as with short messages, a rich communication service (RCS (Rich Communication Services)) has been developed that enables transmission and reception of a larger communication capacity at one time while using the telephone number of a mobile phone terminal as a destination (RCS (Rich Communication Services)). For example, see Patent Document 1.). Rich Communication Services is a comprehensive communication service that includes texts consisting of more characters than can be sent in short messages, sending and receiving high-resolution images, file sharing, group chats, IP phones, video calls, image sharing, etc. -It is a service specification.

However, there is a problem that a message transmitted by using the rich communication service (hereinafter referred to as a rich communication message) can be received only by a mobile phone terminal in which the application of the rich communication service is installed. On the other hand, rich communication messages are compatible with short messages, so if the rich communication service application is not installed on the receiving mobile phone terminal, a transmission error will fall back to the delivery server that delivered the message. .. In this case, the distribution server converts the rich communication message into the protocol used for the short message, divides the rich communication message into the capacity that can be transmitted at one time by the short message, and divides the short message into multiple times on the receiving side. Send to your mobile phone terminal.

Special Table 2018-506793

However, in a rich communication message, the number of characters that can be sent at one time is more than 600 characters, so if this is divided into short messages and sent multiple times, about 10 messages will be sent in many cases. This makes it complicated for the receiving user to open and read the message. Since a charge is incurred for each reception of a short message, there is a request as a receiving user to reject the reception of a plurality of messages. In particular, there is a desire for a B to C (Business to Consumer) company to avoid imposing a burden on the customer side when delivering a message to the customer.

Therefore, according to the present invention, even when data cannot be received by the mobile phone terminal on the receiving side, various data requested by the transmitting side can be transmitted and received without incurring complicated labor and financial burden on the user on the receiving side. It is an object of the present invention to provide a message management server, a message management method, a message management program, and a message management system that can provide.

In order to solve the above problems, the message management server according to the present invention is a message management server that provides a message service using the telephone number of the mobile phone terminal, and the telephone number of the mobile phone terminal and the user of the mobile phone terminal. A storage unit that stores at least one of the e-mail address and the chat ID associated with the telephone number in association with each other, and a distribution unit that delivers the first message using the first protocol to the mobile phone terminal. , The error receiving unit that receives the transmission error of the first message by the distribution unit, and when the transmission error is received by the error receiving unit, it is different from the first protocol and is the first based on predetermined conditions. The data contained in the first message is resent to the mobile phone terminal using at least one message tool of the second message or the e-mail or chat system that uses the second protocol compatible with the protocol of. The message tool determined by the decision unit is provided with a determination unit that determines the data, and a conversion unit that converts the data contained in the first message into the data format of the message tool. The distribution unit is converted by the conversion unit. It is characterized by delivering the generated data to a mobile phone terminal.

According to the present invention, when the rich communication message cannot be received by the receiving mobile phone terminal, the rich communication message is converted into an e-mail and transmitted, so that the data cannot be received by the receiving mobile phone terminal. Even if there is, it is possible to provide a variety of data transmission / reception requested by the transmitting side without causing complicated troubles and financial burden on the receiving side user.

It is a system diagram which shows the structure of the message management system which concerns on Embodiments 1 to 4 of this invention. It is a block diagram which shows the functional structure example of the message management server in Embodiment 1 of this invention. It is a figure which shows an example of the user information in this Embodiment 1. It is a figure which shows an example of the short message in Embodiment 1. FIG. It is a figure which shows an example of the rich communication message in Embodiment 1. FIG. It is a sequence diagram which shows the flow of the transmission processing of a rich communication message by a user terminal, a message management server, and a user terminal in Embodiment 1. FIG. It is a block diagram which shows the functional structure example of the message management server in Embodiment 2. FIG. 8A is a diagram showing an example of model information in the first embodiment, and FIG. 8B is a diagram showing an example of installation information in the second embodiment. It is a sequence diagram which shows the flow of the transmission processing of a rich communication message by a user terminal, a message management server, and a user terminal in Embodiment 2. FIG. It is a sequence diagram which shows another example of the transmission processing of a rich communication message by a user terminal, a message management server, and a user terminal in Embodiment 2. FIG. It is a block diagram which shows the functional structure example of the message management server in Embodiment 3. FIG. 12A is a diagram showing an example of attribute information in the third embodiment. 12 (b) and 12 (c) are diagrams showing an example of the message tool information in the second embodiment. FIG. 12D is a diagram showing an example of response information in the third embodiment. It is a sequence diagram which shows the flow of the message delivery processing by a message delivery request server, a message management server, and a user terminal in Embodiment 3. It is a sequence diagram which shows the flow of the message delivery processing by a message delivery request server, a message management server, and a user terminal in Embodiment 3. It is a block diagram which shows the functional structure example of the message management server in Embodiment 4. It is a sequence diagram which shows the flow of the message delivery processing by a message delivery request server, a message management server, and a user terminal in Embodiment 4. It is a sequence diagram which shows the flow of the message delivery processing by a message delivery request server, a message management server, and a user terminal in Embodiment 4. It is a figure which shows an example of the chat screen in Embodiment 4. It is a hardware block diagram which shows an example of the computer which can realize the message management server in Embodiments 1-4.

(Embodiment 1)
FIG. 1 is a system diagram showing an overall configuration of a message management system according to an embodiment of the present invention. As shown in FIG. 1, in the message management system 1, the message delivery request server 300 is connected to the message management server 100 via the network 10 so as to be able to communicate with each other, and the message management server 100 is connected to the message management server 100 via the mobile network 11. It is connected to the user terminal 200 so as to be able to communicate with each other. Message delivery request server Message delivery request server For example, the network 10 and the mobile network 11 may be a wired network or a wireless network. In FIG. 1, three user terminals 200a to 200c are shown, but there may be more than one (hereinafter, unless otherwise specified, they are collectively referred to as user terminals 200).

The message management server 100 manages the delivery of messages such as short messages, rich communication messages, and e-mails delivered from the message delivery request server 300 to the user terminal 200. For example, the message management server 100 has user information related to personal information of the user of the user terminal 200, an error in sending / receiving a message, a response to a message in the user terminal 200 (for example, access to a URL link included in the message), and the like. Communication information related to is managed. Further, the user terminal 200 is a mobile phone terminal such as a smartphone, and corresponds to the mobile phone terminal in the present invention. The message delivery request server is a B to C company or the like, which is a business transaction between a company and an individual (consumer), or a company that conducts a business for an individual. The rich communication message corresponds to the first message in the present invention, and the short message corresponds to the second message in the present invention.

FIG. 2 is a block diagram showing a functional configuration example of the message management server 100 according to the first embodiment of the present invention. As shown in FIG. 2, the message management server 100 includes a control unit 110, a communication control unit 120, and a storage unit 130.

The communication control unit 120 is an interface connected to a communication device (not shown) such as an antenna or a router connected to a communication line, a telephone line, or the like. That is, the communication control unit 120 has a function of communicating data with an external device such as a user terminal 200 or a message delivery request server 300 via a communication line.

The storage unit 130 stores the user information database 131 and the message information database 132. User information is stored in the user information database 131. Here, the user information is personal information of the user and information about the terminal of the user terminal 200 used by the user. The personal information of the user includes at least the name, date of birth, and gender of the user, and the information about the terminal includes at least the telephone number of the user terminal 200 and the terminal identification information of the user terminal 200. The user's personal information may include identification information (account ID) related to the communication service available to the user, and may include information for each communication service as long as it is the same type but different communication service. .. FIG. 3 is a diagram showing an example of user information in the first embodiment. In FIG. 3, the user's name "Yamada 〇〇" is indicated by "19780101" indicating the user's date of birth, January 1, 1978, the user's address "Minato-ku, Tokyo 〇〇", and the user's telephone number " 090-0000-0000 ", terminal ID" XDR123456 "indicating identification information of the user terminal 200 used by the user, model ID" XYZ001 "indicating identification information of the model of the user terminal 200, Email" "Yamada @ ...", the chat A_ID "yama0101" used by the user, and the chat B_ID "yama016" are associated with each other. The terminal ID is terminal-specific identification information given to each user terminal 200, and the model ID is not terminal-specific because it is the model identification information of the user terminal 200. In addition, message information is stored in the message information database 132. Here, the message information is a short message in which the data included in the rich communication message corresponding to the rich communication message is summarized. For example, when the short message is uploaded to the cloud, it is stored in the message information database 132. The URL that can access the short message may be stored. The short message, which is the message information stored in the message information database 132, is a message used for transmission instead of the rich communication message when the user terminal 200 as the transmission destination cannot receive the rich communication message. Further, chat A_ID and chat B_ID are user identification information in the chat system used by the user, the chat system is a kind of communication tool that can be used by the user, and the user terminal 200 receives a rich communication message. It can be used as an alternative communication tool when it is not possible.

The control unit 110 includes a reception unit 111, a determination unit 112, a conversion unit 113, an acquisition unit 114, and a transmission / reception unit 115. The transmission / reception unit 115 corresponds to the error reception unit and the distribution unit in the present invention.

The transmission / reception unit 115 transmits / receives various information to / from an external terminal such as a user terminal 200 or a message distribution request server 300 or an external device. For example, the transmission / reception unit 115 receives a message delivery request from the message delivery request server 300 to the user terminal 200 and transmits the message delivery request to the user terminal 200 to which the message is delivered. Here, the message delivery request means to send a message such as a short message, a rich communication message, or an e-mail, and a message including a destination mobile phone number or an e-mail address to a destination user terminal 200. It is a request. Further, both the short message and the rich communication message are compatible with each other because the mobile phone number of the user terminal 200 is used as the destination. The data capacity of a short message is limited to text within a predetermined number of characters (for example, 70 to 100 characters), but a rich communication message is larger than the data capacity of a short message and is not limited to text. Therefore, according to the rich communication message, it is possible to attach a moving image, a sound source, or the like.

FIG. 4 is a diagram showing an example of a short message according to the first embodiment. In FIG. 4, a message indicating advance boarding guidance from the airline company is displayed on the screen 210 of the user terminal 200. The short message displayed on the screen 210 is composed only of text, and the number of characters in the text is limited to 100 characters or less. For this reason, the text is as short-cultivated as possible, and as the minimum necessary information carefully selected, only the airline name, the message "This is advance information about the reserved May 5 JA078 flight", and the reservation number. Is displayed. On the other hand, FIG. 5 is a diagram showing an example of a rich communication message according to the first embodiment. Also in FIG. 5, a message indicating advance boarding guidance from the airline company is displayed on the screen 210 of the user terminal 200. The rich communication message displayed on the screen 210 is in a display format that is as easy for the user to read as possible, and more detailed information than the short message shown in FIG. 4 is "departure time: 12:00" and "boarding gate". : 25 ”,“ Seat number: A88 ”, Precautions for boarding“ Please check in at least 20 minutes before departure time ”, and an E-ticket is displayed. The E-ticket may be a two-dimensional code such as a barcode or a QR code.

Further, the transmission / reception unit 115 receives a message delivery request from the message delivery request server 300 to the customer's user terminal 200. Here, the message delivery request is a request for simultaneous delivery or individual delivery of the same or individual messages to the customer's user terminal 200, and the message delivery request includes the destination and the message of the delivery destination. Further, when the transmission / reception unit 115 receives the message delivery request from the message delivery request server 300, the transmission / reception unit 115 transmits the message to the destination included in the message delivery request. For example, the destination included in the message delivery request is a mobile phone number, and when the rich communication message is included, the distribution unit delivers the rich communication to the mobile phone number as the destination.

Further, the transmission / reception unit 115 receives a transmission error ACK (Acknowledgement) response indicating that the transmission has failed when the rich communication message cannot be received at the user terminal 200 as the transmission destination. Further, when the transmission / reception unit 115 receives the transmission error ACK response, the transmission / reception unit 115 sends the e-mail converted by the conversion unit 113 or the short message acquired from the message information database 132 by the acquisition unit 114 to the user terminal 200. Send to.

The reception unit 111 receives various requests from an external terminal such as a user terminal 200 or a message delivery request server or an external device via the transmission / reception unit 115. For example, the reception unit 111 receives a message transmission request from the user terminal 200 and a delivery request from the message delivery request server 300.

When the transmission / reception unit 115 receives the transmission error ACK, the determination unit 112 uses either a short message or an e-mail message tool to use the data contained in the rich communication message or the rich communication based on a predetermined condition. It is determined whether to retransmit the short message corresponding to the case where the message cannot be transmitted to the user terminal 200 as the transmission destination to the user terminal 200. For example, when the message delivery request server 300 or the user terminal 200 specifies in advance, the determination unit 112 determines whether to use a short message or an e-mail as a message tool according to the designation. If the rich communication message cannot be transmitted to the user terminal 200 as the transmission destination, the determination unit 112 refers to the message information database 132 and retransmits the short message corresponding to the rich communication message to the user terminal 200. It will be. If the rich communication message cannot be delivered due to a request from the user terminal 200 or the message delivery request server 300, and it is specified that neither the short message nor the e-mail is resent, the determination unit 112 Determines not to resend any of the messages.

When the transmission / reception unit 115 receives the transmission error ACK response, the conversion unit 113 converts the message data included in the rich communication message into a short message or e-mail data format which is a message tool determined by the determination unit 112. Convert. Specifically, the conversion unit 113 is generated by using a protocol that enables transmission / reception of a rich communication message received from the user terminal 200 that is the transmission source when the transmission / reception unit 115 receives the transmission error ACK response. Generate rich communication messages, short messages or email messages using the short message or email protocol. For example, the conversion unit 113 acquires an e-mail address corresponding to the mobile phone number to which the rich communication message is sent from the user information database 131, and includes the acquired e-mail address in the generated e-mail message. When the transmission / reception unit 115 receives the transmission error ACK response and converts the message data included in the rich communication message into short message data, the conversion unit 113 includes the conversion unit 113 in the rich communication message. Not only is all the data to be transmitted divided into data capacities that can be transmitted at one time by short messages, but also a message for short messages prepared in advance is transmitted to the user terminal 200 as the destination via the transmission / reception unit 115. May be good. For example, the transmission / reception unit 115 may transmit a short message corresponding to the rich communication message stored in the message information database 132 acquired by the acquisition unit 114 described later. The short message corresponding to the rich communication message is that the rich communication message shown in FIG. 5 can be transmitted as a message for the short message prepared in advance by a short message like the short message shown in FIG. It is possible to send a message that contains the minimum required content as a message of a large capacity. If the rich communication message cannot be received by the user terminal 200 as the transmission destination, and the short message corresponding to the rich communication message is acquired from the message information database 132 by the acquisition unit 114 described later, the conversion unit 113 uses the conversion unit 113. No processing is done.

When the transmission / reception unit 115 fails to receive the rich communication message at the transmission destination user terminal 200, the acquisition unit 114 acquires a short message corresponding to the rich communication message from the message information database 132. Here, the acquisition unit 114 may acquire the short message from the message information database 132, or may acquire the short message from the URL indicating the location of the short message.

Next, a process of transmitting a rich communication message by the message delivery request server 300, the message management server 100, and the user terminal 200 will be described with reference to an example of transmitting a message from the message delivery request server 300a to the user terminal 200. FIG. 6 is a sequence diagram showing a flow of a rich communication message transmission process by the message delivery request server 300, the message management server 100, and the user terminal 200 according to the first embodiment.

The message delivery request server 300 transmits a rich communication message to the message management server 100 (step S1). The message management server 100 transmits the rich communication message received in step S1 to the user terminal 200 to the user terminal 200 as the transmission destination (step S2). Here, if the user terminal 200 cannot receive the rich communication message transmitted in step S2, the user terminal 200b transmits a transmission error ACK to the message management server 100 (step S3). The message management server 100 receives the transmission error ACK response (step S4). The message management server 100 converts the rich communication message received from the message delivery request server 300 in step S1 into an email format message (step S5). The message management server 100 transmits the Email converted in step S5 to the user terminal 200 (step S6).

As described above, according to the message management server 100 in the first embodiment, when the transmission of the rich communication message to the user terminal 200 as the destination becomes an error, it is converted into an e-mail and retransmitted. It is possible to transmit a variety of data requested by the transmitting side without incurring complicated labor and financial burden on the user of the user terminal 200. For example, if an error occurs in sending a rich communication message and a plurality of short messages are sent to the user terminal 200 as the destination multiple times, it is possible to confirm one message. Where it can be read and managed, it will be troublesome for the user to check multiple messages. In addition, since a communication cost is incurred for each reception of a short message, the communication cost increases when a plurality of messages are received.

(Embodiment 2)
In the first embodiment, the message management server 100 is configured to convert the rich communication message into an e-mail and transmit the rich communication message when receiving the transmission error ACK response of the rich communication message. In the second embodiment, a configuration that does not require a transmission error ACK response of a rich communication message will be described in order to further improve communication efficiency. The overall configuration in the second embodiment is the same as the overall configuration described with reference to FIG. 1 in the first embodiment.

FIG. 7 is a block diagram showing a functional configuration example of the message management server 400 according to the second embodiment. As shown in FIG. 7, the message management server 400 includes a control unit 410, a communication control unit 120, and a storage unit 430. The same configurations and functions as those in the first embodiment are designated by the same reference numerals, and the description thereof will be omitted.

The storage unit 430 stores the user information database 131, the model information database 431, and the installation information database 433. Model information is stored in the model information database 432. Here, the model information is information indicating whether or not the model of the user terminal 200 can receive the rich communication message. For example, the model ID indicating the model identification information receives the rich communication message. Is associated with the availability of. FIG. 8A is a diagram showing an example of model information in the first embodiment. As shown in FIG. 8A, the model ID "XYZ001" that identifies the model of the user terminal 200 includes "OK" for RCS reception, which indicates whether or not the model can receive the rich communication service. , The model ID "XYZ003" is associated with "RCS reception enable / disable". Further, the model ID "XYZ001" has a chat reception enable / disable "impossible" indicating whether or not the model can receive the chat service, and the model ID "XYZ002" has a chat reception enable / fail "possible". It is associated. In the present embodiment, whether or not the user terminal can receive the message transmitted by the rich communication message is determined before the transmission by using the model information shown in FIG. 8, and if it is "OK", the message is transmitted as it is. An example of not sending when "impossible" or converting to another communication service and sending will be described, but this is the same even when a message is sent by the chat system.

Further, the installation information is stored in the installation information database 133. Here, the installation information is information indicating whether or not the rich communication service application is installed on the user terminal 200. For example, whether or not the rich communication service application is installed on the mobile phone number of the user terminal 200. Are associated with each other. As another example, the presence / absence of installation of an application related to the chat system may be associated. FIG. 8B is a diagram showing an example of installation information in the second embodiment. As shown in FIG. 8B, the mobile phone number "090-000-0000" of the user terminal 200 is associated with "None" of RCS installation indicating whether or not the application of the rich communication service is installed. Whether or not the application related to the chat system A is installed "Yes" is associated with it. Information on whether or not an application related to the chat system is installed can be used when a chat message is sent from the message delivery request server.

The control unit 410 includes a reception unit 111, a determination unit 411, an acquisition unit 413, a conversion unit 113, a determination unit 412, an acquisition unit 114, and a transmission / reception unit 115.

When the message transmission request is received by the reception unit 111, the acquisition unit 413 refers to the model information database 432 or the installation information database 433 and acquires the model information or the installation information. Specifically, the acquisition unit 413 acquires the model ID corresponding to the destination mobile phone number included in the message transmission request from the user information database 131, and from the model information database 432 the rich communication message corresponding to the model ID. Acquires information indicating whether or not reception is possible. Alternatively, the acquisition unit 413 acquires information indicating whether or not the application of the rich communication service corresponding to the destination mobile phone number included in the message transmission request is installed from the installation information database 433.

When the transmission / reception unit 115 receives the message transmission request, the determination unit 412 determines whether or not the user terminal 200 as the transmission destination can receive the rich communication message. Specifically, the determination unit 412 determines whether or not the information indicating whether or not the rich communication message corresponding to the model ID acquired by the acquisition unit 413 can be received indicates whether or not the information can be received. Alternatively, when the transmission / reception unit 115 receives the message transmission request, the determination unit 412 determines whether or not the application is installed in the user terminal 200 as the transmission destination. Specifically, the determination unit 412 determines whether or not the installation information corresponding to the user terminal 200 mobile phone number to be the transmission destination acquired by the acquisition unit 413 indicates no installation.

When the determination unit 412 determines that the model ID of the user terminal 200 is a terminal that cannot send and receive rich communication messages, the determination unit 411 is a message tool for either short message or e-mail based on a predetermined condition. Is used to determine whether to resend the data contained in the rich communication message to the user terminal 200. For example, when the message delivery request server 300 or the user terminal 200 specifies in advance, the determination unit 411 determines whether to use a short message or an e-mail as a message tool according to the designation. If the rich communication message cannot be delivered due to a request from the user terminal 200 or the message delivery request server 300, and it is specified that neither the short message nor the e-mail is resent, the determination unit 411 Determines not to resend any of the messages.

Next, a process of transmitting a rich communication message by the message delivery request server 300, the message management server 100, and the user terminal 200 will be described with reference to an example of transmitting a message from the message delivery request server 300 to the user terminal 200. FIG. 9 is a sequence diagram showing a process of transmitting a rich communication message by the message delivery request server 300, the message management server 100, and the user terminal 200 according to the second embodiment.

The message delivery request server 300 transmits a rich communication message to the message management server 400 (step S11). When the message management server 400 receives the rich communication message in step S11, the message management server 400 determines whether or not the user terminal 200 is a terminal capable of receiving the rich communication message (step S12). Specifically, the determination unit 412 of the message management server 400 refers to the model information database 432 stored in the storage unit 130 of the message management server 400, and the user terminal 200 is a model capable of transmitting and receiving rich communication services. Judge whether or not. When the message management server 400 determines in step S14 that the user terminal 200 is a model capable of transmitting and receiving rich communication services, the message management server 400 sends the user terminal 200 the rich communication message received from the message delivery request server 300 in step S11. It is transmitted to the user terminal 200 (step S13). If the message management server 400 determines in step S12 that the user terminal 200 cannot send and receive rich communication services, the message management server 400 sends the user terminal 200 to the user terminal 200 from the message delivery request server 300 in step S11. The received rich communication message is not transmitted to the user terminal 200. Alternatively, even if the message management server 400 determines in step S12 that the user terminal 200 is a model that cannot send and receive rich communication services, the data capacity of the rich communication message received in step S11 is the short message. When the capacity is such that it can be transmitted at one time, the message management server 400 may convert the rich communication message received from the message delivery request server 300 into a short message and send the converted short message to the user terminal 200. Good.

Further, the process of transmitting a rich communication message by the message delivery request server 300, the message management server 400, and the user terminal 200 will be described with reference to another example of transmitting a message from the message delivery request server 300 to the user terminal 200. .. FIG. 10 is a sequence diagram showing another example of the transmission processing of the rich communication message by the message delivery request server 300, the message management server 400, and the user terminal 200 according to the second embodiment.

The message delivery request server 300 transmits a rich communication message to the message management server 400 (step S21). When the message management server 400 receives the rich communication message in step S21, the message management server 400 determines whether or not the user terminal 200 is a terminal capable of receiving the rich communication message (step S22). Specifically, the determination unit 412 of the message management server 400 refers to the installation information database 133 stored in the storage unit 130 of the message management server 400, and whether the user terminal 200 has the rich communication service application installed. Judge whether or not. When it is determined in step S14 that the application of the rich communication service is installed in the user terminal 200, the message management server 400 transmits the rich communication message received from the message delivery request server 300 to the user terminal 200 in step S11. It is transmitted to the user terminal 200 (step S23). If the message management server 400 determines in step S12 that the rich communication service application is not installed on the user terminal 200, the message management server 400 sends the user terminal 200 the message delivery request server 300 in step S11. The rich communication message received from is not transmitted to the user terminal 200. Alternatively, even if the message management server 400 determines in step S22 that the rich communication service application is not installed on the user terminal 200, the data capacity of the rich communication message received in step S21 is a short message. In the case of the capacity that can be transmitted at one time, the message management server 400 converts the rich communication message received from the message delivery request server 300 into a short message, and transmits the converted short message to the user terminal 200. May be good.

As described above, according to the message management server 400 in the second embodiment, before transmitting the message to the user terminal 200 as the transmission destination, the user terminal 200 determines whether or not the rich communication message can be received and receives the message. If this is not possible, the rich communication message is not sent, so communication efficiency can be improved.

(Embodiment 3)
In the first and second embodiments, the basic configuration of the transmission processing of the rich communication message is shown. However, in particular, whether or not a customer reads a message delivered from a B to C company to a customer depends on the type of message tool. Therefore, in the third embodiment, when the message is delivered from the message delivery request server 300 to the customer, the process of delivering the message by a method that the customer can easily read the information on the company side will be described. The overall configuration in the third embodiment is the same as the overall configuration described with reference to FIG. 1 in the first embodiment.

FIG. 11 is a block diagram showing a functional configuration example of the message management server 500 according to the third embodiment. As shown in FIG. 11, the message management server 500 includes a control unit 510, a communication control unit 120, and a storage unit 530. The same configurations and functions as those of the first embodiment or the second embodiment are designated by the same reference numerals, and the description thereof will be omitted.

The storage unit 530 stores the user information database 131, the attribute information database 532, and the response information database 533. Attribute information and message tool information are stored in the attribute information database 532. Here, the attribute information is information indicating the attributes of the user of the user terminal 200, and at least one of the gender or age of the user of the user terminal 200 is associated with the telephone number of the user terminal 200. There is. Further, for example, in addition to the gender and age of the user, any information indicating the user's preference such as the user's living area, hobbies, preferences, and purchase history may be associated with the telephone number of the user terminal 200. FIG. 12A is a diagram showing an example of attribute information in the third embodiment. In FIG. 12A, the telephone number “090-0000-0000” indicating the mobile phone number of the user terminal 200, the age “40 years old” indicating the age of the user, and the gender “male” indicating the gender of the user are added. It is associated with a meal preference "Japanese food" indicating a meal preferred by the user. Further, the message tool information is information indicating the type of the message tool determined according to the attribute information, and the message tool is associated with the attribute of the user. The message tool associated with the user's attribute is a message tool that is frequently or likely to be used depending on the user's attribute. 12 (b) and 12 (c) are diagrams showing an example of the message tool information in the second embodiment. In FIG. 12B, a message tool is associated with each user's gender, the message tool “Email” indicating e-mail is associated with the gender “male”, and rich communication is associated with the gender “female”. A message tool "RCS" that indicates a message is associated with each other. Further, in FIG. 12C, a message tool is associated with each meal preference. The message tool “Email” indicating an e-mail is associated with the meal preference “Japanese food”, and the meal preference “Western food” is rich. A message tool "RCS" indicating a communication message, a message tool "SMS" indicating a short message are associated with a meal preference "Chinese", and a chat service "chat" is associated with a meal preference "ethnic". ..

Further, the response information is stored in the response information database 533. Here, the response information is information indicating the number of times a response has been received from the user terminal 200 for each of a plurality of message tools, and at least the number of responses for each message tool is associated with the mobile phone number of the user terminal 200. ing. The response indicates an operation of opening a message, an operation of displaying the content of the message, and the like. The message tool is a tool such as an application for sending and receiving a message, such as a short message, a rich communication message, and an e-mail. FIG. 12D is a diagram showing an example of response information in the third embodiment. In FIG. 12D, the telephone number “090-0000-0000” indicating the mobile phone number of the user terminal 200 is the number of responses to the e-mail of the user terminal 200 as Email “20/30”, and the number of responses to the rich communication message. RCS "30/30", SMS "0/20" as the number of responses to short messages, and chat "10/20" as the number of responses to chat messages. The reception period "20180101-20181231" corresponds to the period when the number of responses was counted. It is attached. Here, it is shown that the number of email responses during the reception period from January 1, 2018 to December 31, 2018 is 20 out of the total number of 30 emails sent and received by the user terminal 200. Further, the number of responses of the rich communication service during the reception period indicates that the number of responses is 30 out of a total of 30 rich communication messages sent and received by the user terminal 200. Further, the number of short message responses during the reception period indicates that the total number of short messages sent / received by the user terminal 200 is 0 out of 30. Further, the number of responses of the chat system at the receiving organization indicates that the number of responses is 10 out of the total number of 20 chat messages sent and received by the user terminal 200. In FIG. 12D, the rich communication message has the highest number of responses, and the ratio of the response by the rich communication message is the highest even when the ratio of the number of responses to the number of receptions is compared. In the present embodiment, an example of counting the response information for each mobile phone number of each user terminal 200 has been shown, but the present invention is not limited to this, and for example, for each message tool for each predetermined age group and gender. The number of responses may be counted, and the message tool may be determined according to the statistics of the counted number of responses. Further, the statistics may be statistics for each individual or for each predetermined group (for example, a group created in the talk room of the message application). Further, in the case of a group, the display mode of the application may differ depending on the model, and the easiness of the click operation may differ. Therefore, it is possible to obtain statistics for each model.

The control unit 510 includes a reception unit 511, an acquisition unit 512, a conversion unit 513, a determination unit 414, a determination unit 514, and a transmission / reception unit 115.

The reception unit 511 receives a message delivery request including the message content type from the message delivery request server 300. Here, the content type of the message is a type classified according to the content and purpose of delivery of the message, and includes, for example, corporate advertisement, authentication of application and payment, disaster notification, and the like.

The acquisition unit 512 acquires the attribute information from the attribute information database 532 when the message delivery request is received by the reception unit 111. Specifically, the acquisition unit 512 acquires at least one or more of age, gender, user's hobbies, tastes, and purchase history as attributes corresponding to the destination mobile phone number included in the message delivery request. To do. For example, when the message delivery request includes the gender designation as the attribute information for determining the message tool, the acquisition unit 512 acquires the message tool corresponding to the gender. Alternatively, the acquisition unit 512 acquires the response information from the response information database 533 when the message delivery request is received by the reception unit 111. Specifically, the acquisition unit 512 acquires the number of responses of each of the plurality of message tools corresponding to the destination mobile phone numbers included in the message delivery request.

The determination unit 514 is used to transmit a message according to at least one of the attributes acquired by the acquisition unit 512, the user's age, gender, user's living area, hobbies, tastes, and purchase history. A message tool is determined, and a message is delivered via the transmission / reception unit 116 using the determined message tool. Alternatively, the determination unit 514 determines as a message tool that uses the message tool that has the largest number of responses among the response times acquired by the acquisition unit 512, and uses the determined message tool to send a message via the transmission / reception unit 116. It may be delivered. Even if the determination unit 514 determines as a message tool that uses the rich communication message, if the determination unit 412 determines that the rich communication message is not installed on the user terminal 200 that is the delivery destination. You may use other message tools for this. Further, when the message delivery request received by the reception unit 511 includes the content type of the message, the determination unit 514 may determine the message tool according to the content type. For example, the message tool is determined in advance according to the order of rich communication message, e-mail, short message in the case of corporate advertisement, short message only in the case of authentication, and short message in the case of disaster notification. To do. In this way, if it is a message indicating the type of corporate advertisement, it is requested that a message indicating the details of the advertisement content of the product or service be delivered to the user terminal 200, and if it is a message indicating the type of authentication, one In many cases, it is short character information such as a time password in which numbers or Roman characters are listed, and if it is a message indicating the type of disaster notification, it is required to notify the user of the disaster information more reliably. In this way, by making the message tool used for delivery different depending on the type of message, it is possible to perform efficient and effective message delivery according to the actual situation for the user or the message delivery requester.

The conversion unit 513 converts the message included in the delivery request of the message received by the reception unit 111 by using the protocol of the message tool determined by the distribution unit 515. When the reception unit 111 receives the message generated by one type of message tool in the message distribution request from the message distribution request server 300, the conversion unit 513 performs the above conversion process. On the other hand, when the reception unit 111 includes a plurality of messages generated by a plurality of message tools in the message distribution request from the message distribution request server 300, the conversion unit 513 does not perform the above conversion process, and the distribution unit 515 does not perform the above conversion process. Will use the messages generated by the various message tools included in the message delivery request.

Next, the message delivery process by the message delivery request server 300, the message management server 500, and the user terminal 200 will be described. FIG. 13 is a sequence diagram showing a flow of message delivery processing by the message delivery request server 300, the message management server 500, and the user terminal 200.

The message delivery request server 300 transmits a message delivery request to the message management server 500 (step S31). The message management server 500 acquires the attribute information from the attribute information database 532 (step S32). The message management server 500 determines the message tool according to the attribute information acquired in step S32 (step S33). Specifically, the message management server 500 refers to the message tool information stored in the attribute information database 532, and uses the message tool associated with the attribute information acquired in step S32 to deliver the message. Decide on a tool. The message management server 500 transmits a message to the user terminal 200 using the message tool determined in step S33 (step S34).

Next, another example of the message delivery process by the message delivery request server 300, the message management server 500, and the user terminal 200 will be described. FIG. 14 is a sequence diagram showing a flow of message delivery processing by the message delivery request server 300, the message management server 500, and the user terminal 200.

The message delivery request server 300 transmits a message delivery request to the message management server 500 (step S41). The message management server 500 acquires the response information from the response information database 533 (step S42). The message management server 500 determines the message tool according to the response information acquired in step S42 (step S43). Specifically, the message management server 500 refers to the message tool information stored in the response information database 533, and the message tool having the largest number of responses associated with the mobile phone number of the user terminal 200 as the destination. Is the message tool used to deliver the message. The message management server 500 transmits a message to the user terminal 200 using the message tool determined in step S43 (step S44).

As described above, according to the message management server 500 in the third embodiment, the message tool is determined according to the attributes such as the gender and age of the user, and the number of responses to the message by the user terminal 200. It can increase the possibility that users will read messages from companies.

(Embodiment 4)
In the above embodiment, the basic configuration of the transmission processing of the rich communication message is shown. That is, although the mode of switching the rich communication message to the transmission by Email or SMS and the switching of the Email to the transmission by the rich communication message is shown, the switching of the message type is not limited to these. In the fourth embodiment, an example of using a chat system as a message transmission tool will be further described.

Chat is generally a tool for real-time communication via a data communication line on a computer network, but message exchange does not have to be real-time, and messages can be confirmed later. There may be. Normally, in chat, messages are exchanged between the user and one or more other users, and the chat user interface is a message sent by oneself on either the left or right side of the screen. And display messages sent by other users to the other.

The overall configuration in the fourth embodiment is the same as the overall configuration described with reference to FIG. 1 in the first embodiment. FIG. 15 is a block diagram showing a functional configuration example of the message management server 600 according to the fourth embodiment. As shown in FIG. 15, the message management server 600 includes a control unit 610, a storage unit 630, and a communication control unit 120. The control unit 610 includes a conversion unit 613 unlike the control unit 510 shown in the third embodiment. Further, the storage unit 630 includes the user information DB 631 unlike the user information DB 531.

Hereinafter, as the function of the message management server 600 according to the fourth embodiment, the contents not described in the first to third embodiments will be described.
In the fourth embodiment, the user information DB 631 of the storage unit 630 of the message management server 600 is basically the same as the data structure shown in FIG. 3, but in addition to the information shown in FIG. 3, for each user. Is associated with information indicating the chat system (service) used by the user and user identification information (user ID) for using the chat system. The information indicating the chat system may be a product name or a service name of the chat system, and may be one that can specify the protocol of the chat system used in the service. The user identification information when using the chat system may be any information that can uniquely identify each user on the chat system, or may be a name given to the user himself or the system side of the chat system. It may be the information to be given. In a chat system, the content of a message exchanged only between users who send and receive a message can be confirmed, and the UI for exchanging messages is sometimes called a chat room. Other users cannot join the chat room without being invited by a user associated with the chat. If the message delivery request server 300 is, for example, a corporate server 300,

The conversion unit 613 has a function of converting a message transmitted to the chat system into any of the formats of Email, rich communication message, and SMS, in addition to the functions provided by the conversion unit 113 and the conversion unit 513, and is a transmission / reception unit. Communicate to 115. Further, the conversion unit 113 also has a function of converting a message received in any of the formats of Email, rich communication message, and SMS into a chat system format and transmitting the message.

That is, the message management server 600 receives the message transmitted to the chat room. The conversion unit 613 identifies the content of the latest message sent to the chat system (chat room). Then, it is converted into one of the formats of Email, rich communication message, and SMS including the content of the specified message, and the destination is converted into a message with another user participating in the chat room.

Further, the conversion unit 613 of the message management server 600 sends a message transmitted by Email, a rich communication message, or an SMS to a chat room including the user and the sender of the message, as a text message, image data, or video data. And so on.

Hereinafter, the message delivery process by the message delivery request server 300, the message management server 600, and the user terminal 200 will be described. FIG. 16 is a sequence diagram showing a flow of message delivery processing by the message delivery request server 300, the message management server 600, and the user terminal 200, and the message is transmitted from the message management server 600 by the chat system. It is a sequence diagram when it is broken.

The message delivery request server 300 transmits a message to the message management server 600 using the chat system (step S51). The message management server 600 transmits the message received in step S51 to the user terminal 200 to the user terminal 200 as the destination using the same chat system (step S52). Here, if the user terminal 200 cannot receive the message in the chat system transmitted in step S52, the user terminal 200 transmits a transmission error ACK to the message management server 600 (step S53). The message management server 600 receives the transmission error ACK response (step S54). The message management server 600 converts the chat message content received from the message delivery request server 300 in step S51 into an email format message (step S55). The message management server 600 transmits the Email converted in step S55 to the user terminal 200 (step S56). In step S55, an example of converting to E-mail is shown, but this is not limited to E-mail if the communication uses a method other than the chat system, and is a rich communication message, SMS, or the like. May be good.

Next, FIG. 17 is a sequence diagram showing a flow of message delivery processing by the message delivery request server 300, the message management server 600, and the user terminal 200, and the transmission of the message from the message management server 600 is Email. It is a sequence diagram when it is performed by (or rich communication message or SMS).

The message delivery request server 300 transmits a format other than the chat system, for example, a rich communication message to the management server 600 (step S61). The message management server 600 transmits the rich communication message received in step S61 to the user terminal 200 to the destination user terminal 200 (step S62). Here, if the user terminal 200 cannot receive the rich communication message transmitted in step S62, the user terminal 200 transmits a transmission error ACK to the message management server 600 (step S63). The message management server 600 receives the transmission error ACK response (step S64). The message management server 600 converts the message content of the rich communication message received from the message delivery request server 300 in step S61 into a message of the chat system (step S65). The message management server 600 transmits the message converted in step S65 to the user terminal 200 using the chat system (step S66). In step S65, an example of converting to a message in the chat system is shown, but this may be conversion to Email or SMS.

As shown in FIGS. 16 and 17, the message management server 600 communicates the contents of the messages exchanged in the chat system using a communication tool other than the chat system (for example, rich communication, Email, SMS, etc.). Can be switched to, and vice versa. Therefore, even if the user refuses to exchange messages by the chat system, the message from the message delivery request server 300 can be transmitted to the user terminal 200.

FIG. 18 shows an example in which a message transmitted by the message delivery request server 300 is displayed on the user terminal 200 by using the chat system. Here, an example is shown in which the content of the message transmitted by the rich communication message shown in FIG. 5 is transmitted by the chat system, and the content corresponds to the content. Therefore, it can be said that FIGS. 5 and 18 show the relationship between before and after conversion by the conversion unit 613.

As shown in FIG. 18, the screen 210 of the user terminal 200 shows an example of a chat room between the airline and the user, and in the chat room, a speaker (in the example shown in FIG. 18, the airline) The message content is shown in the message bubble 211. In the example shown in FIG. 18, it can be understood that the message from the airline company is the advance notice of the reservation in the message bubble 211, the reservation number is "4155-4477", and the boarding date is "May 5". The day, the boarding flight is "JA078", the departure time is "12:00", the boarding gate is "25", and the seat number is "A88". It can be understood. The content shown in FIG. 18 is transmitted from the message delivery request server 300 using a chat message, and if the user terminal 200 does not reject the content, the content shown in FIG. 18 is displayed. On the other hand, when the chat message transmitted by the message delivery request server 300 is rejected by the user terminal 200, it is converted into a rich communication message by the conversion unit 613 as an example, and is displayed in the manner shown in FIG. 5, for example. The Rukoto. The reverse is also true. When the rich communication message shown in FIG. 5 is transmitted by the message delivery request server 300 and rejected by the user terminal 200, the conversion unit 613 converts it into a chat message, and FIG. It is displayed on the user terminal 200 in the manner shown.

Also in the fourth embodiment, as shown in the second embodiment, before sending the message, it is confirmed whether the user can receive the chat message, and when it is determined that the chat message is not possible, the chat message is displayed. Instead of sending, for example, the message may be converted into a rich communication message and transmitted from the beginning, or the message may be delivered according to the attributes of the user as shown in the third embodiment.

In the above embodiments 1 to 4, when the receiving side cannot receive the message in the communication protocol first specified in the message delivery request server 300, the conversion unit 113 of the message management server 100 (400, 500, 600) However, by converting the message from the message delivery request server 300 into the mode of another communication protocol, the transmission of the message by another communication protocol has been realized, but this is not the case. In advance, the storage unit 130 of the message management server 100 (400, 500, 600) stores the data of the message in another communication protocol as an alternative, and when the receiving side cannot receive the data, the data is read out. It may be configured to transmit. As the data of the message in another communication protocol to be substituted in advance in the storage unit 130, the data received from the message delivery request server 300 may be stored first. That is, when the first message delivery request is made, the message delivery request server 300 sends a message corresponding to each communication protocol to the message management server 100 (400, 500, 600), with the content to be transmitted being the same purpose. It may be transmitted to the storage unit 130 and stored in the storage unit 130. With such a configuration, the message management server 100 (400, 500, 600) can transmit a message corresponding to a plurality of communication protocols without the conversion unit 113.

In the above embodiments 1 to 4, when a transmission error ACK is received after the message is transmitted, or when it is known that the message in the specified mode is rejected in advance on the receiving side or cannot be received. In addition, when sending a message using another communication protocol (tool), there may be a plurality of available communication protocols. In such a case, the message management server 100 (400, 500, 600) may transmit (retransmit) a message using a communication protocol randomly selected from the plurality of other available communication protocols. Alternatively, the message may be transmitted using a communication protocol selected according to a predetermined criterion. The predetermined standard referred to here may be a predetermined priority, for example, when the order of RSC, chat, Email, SMS is set in advance, and the first message is chat. If the receiving side rejects the chat when it is sent by, the message management server first challenges the transmission by RSC, then sends by Email, and finally by SMS. Further, this predetermined standard may differ depending on the terminal on the receiving side, and the priority may be set for each user. Furthermore, instead of sending messages in different communication protocols in order, if a transmission error ACK is received after sending the message, or if the message in the specified mode is rejected in advance on the receiving side. It may be configured to send messages at once with a plurality of different communication protocols when it is known that it is present or cannot be received.

Further, in the above-described first and fourth embodiments, when the message management server 100 (600) receives the transmission error ACK, the message management server 100 (600) automatically converts the message into another communication protocol mode and corresponds to the converted message. It is supposed to be transmitted by other communication protocols. At this time, the message management server 100 (600) may be configured to request permission from the receiving side, that is, the user of the user terminal 200, and then retransmit the message before retransmitting the message. That is, when the message management server 100 (600) receives the transmission error ACK, the message management server 100 (600) notifies the user terminal 200 that the message delivery request server 300 wants to deliver the message. When the user of the user terminal 200 sees the notification and decides that the message may be received, the user notifies the message management server 100 (600) of the reception permission. When it is determined that the message is not received, the message management server 100 (600) is notified of the reception permission. Then, the message management server 100 (600) transmits the message by another communication protocol only when the reception permission is received from the user terminal 200. At this time, if the user terminal 200 permits, the message may be retransmitted using the communication protocol first specified by the message delivery request server 300.

FIG. 19 is a hardware configuration diagram showing an example of a computer 20 capable of realizing the message management servers 100, 400, 500, 600 in the first to fourth embodiments. As shown in FIG. 19, the computer 20 includes a CPU (Central Processing Unit) 21, a RAM (Random Access Memory) 22, a ROM (Read Only Memory) 23, an HDD (Hard Disk Drive) 24, and a communication interface (I / F). 25, an input / output interface (I / F) 26, and a media interface (I / F) 27 are provided.

The CPU 21 operates by a program stored in the ROM 23 or the HDD 24, and controls each part. The ROM 23 stores a boot program executed by the CPU 21 when the computer 20 is started, a program that depends on the hardware of the computer 20, and the like.

The HDD 24 stores a program executed by the CPU 21 and data used by the program. The communication interface 25 sends data received from an external device via a communication line to the CPU 21, and transmits the data generated by the CPU 21 to the external device via the communication line.

The CPU 21 controls an output device such as a display or a printer, and an input device such as a keyboard or a mouse via the input / output interface 26. The CPU 21 acquires data from the input device via the input / output interface 26. Further, the CPU 21 outputs the generated data to the output device via the input / output interface 26.

The media interface 27 reads the program or data stored in the storage medium 28 and provides it to the CPU 21 via the RAM 22. The CPU 21 loads the program from a storage medium (not shown) onto the RAM 22 via the media interface 27, and executes the loaded program. The storage medium is, for example, an optical storage medium such as a DVD (Digital Versatile Disc), a magnetic storage medium, a semiconductor memory, or the like.

When the computer 20 functions as the message management server 100 in the present embodiment, the CPU 21 of the computer 20 executes the program loaded on the RAM 22 to execute the reception unit 111, the determination unit 112, the determination unit 411, and the determination unit 514. , Conversion unit 113, determination unit 412, acquisition unit 114, acquisition unit 413, acquisition unit 512, determination unit 412, and transmission / reception unit 115 are realized. Further, the HDD 24 stores the data in the user information database 131, the model information database 432, the installation information database 433, the attribute information database 532, and the response information database 533.

The message management system is a computer-readable storage medium such as a CD-ROM, CD-R, memory card, DVD (Digital Versatile Disk), or flexible disk (FD) in an installable or executable format. Memorized and provided. The CPU 21 of the computer 20 reads and executes these programs from the above storage medium via the media interface 27, but as another example, even if these programs are acquired from an external device via a communication line. Good.

The message management system uses, for example, script languages such as ActionScript, JavaScript (registered trademark), Python, and Ruby, and compiler languages such as C language, C ++, C #, Objective-C, Swift, and Java (registered trademark). Can be implemented using.

1 Message management system 100 Message management server 110 Control unit 111 Reception unit 112 Decision unit 113 Conversion unit 114 Acquisition unit 115 Transmission / reception unit 120 Communication control unit 130 Storage unit 131 User information database 132 Message information database 200 User terminal 210 Screen 300 Message delivery request server

The message management system uses, for example, script languages such as ActionScript, JavaScript (registered trademark), Python, and Ruby, and compiler languages such as C language, C ++, C #, Objective-C, Swift, and Java (registered trademark). Can be implemented using.
The message management server according to the present invention is a message management server that provides a message service using the telephone number of the mobile phone terminal, and accepts a message delivery request from an external server to a plurality of mobile phone terminals. A first message is used as a message tool used to send a message according to a unit and a predetermined condition. The first message is different from the first protocol and is compatible with the first protocol. A second message using a second protocol, or a decision unit that determines at least one of an email or chat system, and to the mobile phone terminal according to a delivery method determined by the decision unit. It may be characterized by having a delivery unit for delivering a message.
Further, in the message management server, the telephone number of the mobile phone terminal is associated with attribute information indicating at least one of the gender, age, residential area, hobby, and preference of the user of the mobile phone terminal and stored. When a message delivery request is received by the storage unit and the reception unit, the user's gender, age, residential area, hobbies, and preferences associated with the telephone number of the mobile phone are transmitted from the storage unit. Further including an acquisition unit for acquiring at least one of them, the determination unit corresponds to at least one of the user's gender, age, residential area, hobbies, and preferences acquired by the acquisition unit. It may be characterized by determining the message tool used to send the message.
Further, in the message management server, the reception unit may receive a message delivery request including the content type of the message, and the determination unit may determine the message tool according to the content type.
Further, in the message management server, when a message delivery request is received by the mobile phone terminal or the reception unit for a plurality of message tools at the telephone number of the mobile phone terminal, the mobile phone is transmitted from the storage unit. The determination unit further includes an acquisition unit for acquiring the number of responses from the mobile phone terminal associated with the telephone number of the above, and the determination unit responds to the number of responses from the mobile phone terminal acquired by the acquisition unit. , Determining the message tool used to send the message.
Further, when the message management server receives a storage unit for storing the second message corresponding to the first message and a delivery request for a message including the first message, the first message is received. A message acquisition unit that acquires the second message corresponding to the first message from the storage unit when the message cannot be transmitted to the mobile phone terminal is provided, and the distribution unit is provided by the message acquisition unit. It may be characterized in that the acquired second message is transmitted to the mobile phone terminal.

Claims (16)

A message management server that provides a message service using the telephone number of a mobile phone terminal.
A storage unit that stores the telephone number of the mobile phone terminal, the e-mail address of the user of the mobile phone terminal, and at least one of the chat IDs associated with the telephone number in association with each other.
A distribution unit that distributes the first message using the first protocol to the mobile phone terminal, and
An error receiving unit that receives a transmission error of the first message by the distribution unit, and an error receiving unit.
When the transmission error is received by the error receiving unit, a second protocol different from the first protocol and compatible with the first protocol is used based on predetermined conditions. A determination unit that determines whether to resend the data contained in the first message to the mobile phone terminal using the second message or at least one of the message tools of the e-mail or chat system.
A conversion unit that converts the data contained in the first message into the data format of the message tool in the message tool determined by the determination unit, and
With
The distribution unit distributes the data converted by the conversion unit to the mobile phone terminal.
A message management server that features. A message management server that provides a message service using the telephone number of a mobile phone terminal.
A storage unit that stores the telephone number of the mobile phone terminal, the e-mail address of the user of the mobile phone terminal, and at least one of the chat IDs associated with the telephone number in association with each other.
A distribution unit that distributes the first message using the first protocol to the mobile phone terminal, and
An error receiving unit that receives a transmission error of the first message by the distribution unit, and an error receiving unit.
When the transmission error is received by the error receiving unit, a second protocol different from the first protocol and compatible with the first protocol is used based on predetermined conditions. A determination unit that determines whether to resend the data contained in the first message to the mobile phone terminal using at least one of the message tools of the second message, e-mail, or chat system.
At least one message of the second message, e-mail or chat system, which uses a second protocol compatible with the first protocol corresponding to the data contained in the first message, of the message tool. A second storage unit that stores data and
With
The distribution unit distributes the data of the second storage unit to the mobile phone terminal.
A message management server that features. A second message, e-mail, or chat system in which a second protocol compatible with the first protocol is used, if a plurality of the second protocols are available, is based on the predetermined conditions. The message management server according to claim 1 or 2, wherein the message tool is sequentially retransmitted or simultaneously retransmitted based on a predetermined priority of using the message tool. A second message, e-mail, or chat system in which a second protocol compatible with the first protocol is used, if a plurality of the second protocols are available, is based on the predetermined conditions. Retransmission is performed based on the predetermined message tool and the priority of using the message tool, and when the information indicating that the message has been received is received, the retransmission is completed and the message cannot be received. The message management server according to claim 3, wherein when the information is received, the information is resent to the following message tools having different priorities. The storage unit stores the telephone number of the mobile phone terminal, the identification information of the model of the mobile phone terminal, and the identification information of the model of the mobile phone terminal that cannot send and receive the first message in association with each other.
Whether or not the model identification information associated with the telephone number of the mobile phone terminal to be transmitted by referring to the storage unit is the identification information of the model of the mobile phone terminal that cannot send and receive the first message. Judgment unit to judge
When the determination unit determines that the determination information is the identification information of the model of the mobile phone terminal that cannot send and receive the first message, the distribution unit does not transmit the first message.
The message management server according to any one of claims 1 to 4. The storage unit stores the telephone number of the mobile phone terminal, the identification information of the model of the mobile phone terminal, and the identification information of the model of the mobile phone terminal that cannot send and receive the first message in association with each other.
Whether or not the model identification information associated with the telephone number of the mobile phone terminal to be transmitted by referring to the storage unit is the identification information of the model of the mobile phone terminal that cannot send and receive the first message. Judgment unit to judge
When the determination unit determines that the determination information is the identification information of the model of the mobile phone terminal capable of transmitting and receiving the first message, the distribution unit transmits the first message.
The message management server according to any one of claims 1 to 5. A message management server that provides a message service using the telephone number of a mobile phone terminal.
The destination information in which the telephone number of the mobile phone terminal is associated with the e-mail address of the user of the mobile phone terminal and at least one of the chat IDs associated with the telephone number, and the telephone number of the mobile phone terminal. , The user information associated with the identification information of the model of the mobile phone terminal is associated with the identification information indicating the identification information of the model of the mobile phone terminal that cannot send and receive the first message using the first protocol. A storage unit that stores model information and
Whether or not the model identification information associated with the telephone number of the mobile phone terminal to be transmitted by referring to the storage unit is the identification information of the model of the mobile phone terminal that cannot send and receive the first message. Judgment unit to judge
When the determination unit determines that the identification information of the model of the mobile phone terminal is a mobile phone terminal that cannot send and receive the first message, it is different from the first protocol based on a predetermined condition. And included in the first message using a second message that uses a second protocol compatible with the first protocol or at least one of the message tools of an email or chat system. A decision unit that determines whether to resend the data to the mobile phone terminal,
A distribution unit that delivers a message to the mobile phone terminal using a message tool determined by the determination unit, and a distribution unit.
A message management server characterized by being equipped with. A message management server that provides a message service using the telephone number of a mobile phone terminal.
A reception unit that accepts message delivery requests from external servers to multiple mobile phone terminals,
A first message in which a first protocol is used as a message tool used for transmitting a message according to a predetermined condition, a first message different from the first protocol and compatible with the first protocol. A second message in which the two protocols are used, or a decision-making body that determines at least one of the email or chat systems,
A distribution unit that delivers a message to the mobile phone terminal according to a distribution method determined by the determination unit, and a distribution unit.
A message management server characterized by being equipped with. A storage unit that stores attribute information indicating at least one of the gender, age, residential area, hobbies, and preferences of the user of the mobile phone terminal in association with the telephone number of the mobile phone terminal.
When a message delivery request is received by the reception unit, at least one of the user's gender, age, residential area, hobby, and preference associated with the telephone number of the mobile phone from the storage unit. And the acquisition department to acquire
With more
The determination unit determines a message tool to be used for transmitting a message according to at least one of the user's gender, age, residential area, hobbies, and tastes acquired by the acquisition unit.
8. The message management server according to claim 8. The reception unit receives a message delivery request including the content type of the message, and receives the request.
The determination unit determines the message tool according to the content type.
8. The message management server according to claim 8. When a message delivery request is received by the mobile phone terminal or the reception unit for a plurality of message tools, the telephone number of the mobile phone terminal is associated with the telephone number of the mobile phone from the storage unit. An acquisition unit that acquires the number of responses from the mobile phone terminal, and
With more
The determination unit determines a message tool used for transmitting a message according to the number of responses from the mobile phone terminal acquired by the acquisition unit.
9. The message management server according to claim 9. A storage unit that stores the second message corresponding to the first message,
When the delivery request of the message including the first message is received and the first message cannot be transmitted to the mobile phone terminal, the second message corresponding to the first message from the storage unit. Message acquisition part to acquire the message of
With
The distribution unit transmits the second message acquired by the message acquisition unit to the mobile phone terminal.
The message management server according to any one of claims 8 to 11. It is a message management method by a message management server that provides a message service using the telephone number of a mobile phone terminal.
A storage step of associating the telephone number of the mobile phone terminal with at least one of the e-mail address of the user of the mobile phone terminal and the chat ID associated with the telephone number and storing it in the storage unit.
A delivery step of delivering the first message using the first protocol to the mobile phone terminal, and
An error receiving step for receiving the transmission error of the first message by the delivery step, and
When the transmission error is received by the error reception step, a second protocol different from the first protocol and compatible with the first protocol is used based on predetermined conditions. A determination step of deciding whether to resend the data contained in the first message to the mobile phone terminal using the second message or at least one of the message tools of the email or chat system.
A conversion step of converting the data contained in the first message into the data format of the message tool determined by the determination step, and a conversion step.
Including
The distribution step is to distribute the data converted by the conversion step to the mobile phone terminal.
A message management method characterized by. Computer,
A storage function that stores the telephone number of the mobile phone terminal, the e-mail address of the user of the mobile phone terminal, and at least one of the chat IDs associated with the telephone number in the storage unit in association with each other.
A delivery function that delivers the first message using the first protocol to the mobile phone terminal, and
An error receiving function for receiving the transmission error of the first message by the delivery function, and
When the transmission error is received by the error receiving function, a second protocol different from the first protocol and compatible with the first protocol is used based on predetermined conditions. A decision function for deciding whether to resend the data contained in the first message to the mobile phone terminal using the second message or at least one of the message tools of the e-mail or chat system.
A conversion function that converts the data contained in the first message into the data format of the message tool in the message tool determined by the determination function, and
Realized
The distribution function distributes the data converted by the conversion function to the mobile phone terminal.
A message management program featuring. It is a message management method by a message management server that provides a message service using the telephone number of a mobile phone terminal.
A storage step of associating and storing the telephone number of the mobile phone terminal, the e-mail address of the user of the mobile phone terminal, and at least one of the chat IDs associated with the telephone number.
A delivery step of delivering the first message using the first protocol to the mobile phone terminal, and
An error receiving step for receiving the transmission error of the first message by the delivery step, and
When the transmission error is received by the error reception step, a second protocol different from the first protocol and compatible with the first protocol is used based on predetermined conditions. A decision step of deciding whether to resend the data contained in the first message to the mobile phone terminal using at least one of the message tools of the second message, e-mail or chat system.
At least one message of the second message, e-mail or chat system, which uses a second protocol compatible with the first protocol corresponding to the data contained in the first message, of the message tool. The second storage step to store the data and
With
The distribution step is to distribute the data of the second storage step to the mobile phone terminal.
A message management method characterized by. Computer,
A storage function that associates the telephone number of the mobile phone terminal with at least one of the e-mail address of the user of the mobile phone terminal and the chat ID associated with the telephone number and stores it in the storage unit.
A delivery function that delivers the first message using the first protocol to the mobile phone terminal, and
An error receiving function for receiving the transmission error of the first message by the delivery function, and
When the transmission error is received by the error receiving function, a second protocol different from the first protocol and compatible with the first protocol is used based on predetermined conditions. A decision function for deciding whether to resend the data contained in the first message to the mobile phone terminal using at least one message tool of the second message, e-mail or chat system.
At least one message of the second message, e-mail or chat system, which uses a second protocol compatible with the first protocol corresponding to the data contained in the first message, of the message tool. A second storage function that stores data in the storage unit,
Realized
The distribution function distributes the data of the second storage function to the mobile phone terminal.
A message management server that features.

Images