Distribution system, server device, distribution method, and program

Abstract

To provide a distribution system, a server apparatus, a distribution method, and a program which prompts a mobile phone of a customer to correspond to RCS.SOLUTION: An information management server comprises: a storage unit for storing a distribution DB at least having notification contents indicating a message to be noticed to a user, information set with, as a notification method for notifying a user of the notification contents, an RCS notice using an RCS, an SMS notice using an SMS, and a delivery notice for use in delivering a printed matter, and destination information indicating a portable phone number used as a destination of the RCS notification; a confirmation request unit for requesting a portable phone carrier server to determine whether or not a user terminal can use the RCS by using the destination information of the distribution DB; an RCS distribution unit for transmitting, based on the determination result of the portable phone carrier server, the notification contents presented to the distribution DB to the user terminal through the RCS notification; and a control unit for setting a delivery notice to the notification method of the distribution DB if the RCS notification is not normally completed.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a distribution system, a server device, a distribution method, and a program. [Background technology]

[0002] Electronic notification services that notify information online have become available. Such electronic notification services are used by various companies as a means of notifying customers of information introducing new products, for example. Patent Document 1 discloses a technology for sending information to an address that is likely to be seen by the customer immediately when notifying the customer.

[0003] Among such electronic notification services, message services that use mobile phone numbers as the destination are the most popular because they are highly convenient, since they allow you to send messages to the recipient even if you do not know their email address.

[0004] There are several communication protocols for messaging services addressed to mobile phone numbers. For example, there are RCS (Rich Communication Services) and SMS (Short Message Service). RCS is a standard for implementing instant messengers for mobile phones at the terminal level. RCS is designed with consideration for interconnection between communication carriers, and messages can be exchanged even between different communication carriers. In addition, the upper limit of the amount of information that can be sent in RCS is set to be larger than that of SMS. Therefore, while SMS can only send and receive small amounts of information such as text with a limited number of characters, RCS can send and receive large amounts of information such as images. For this reason, companies that want to notify their customers of various information want to distribute information using RCS.

[0005] However, while most mobile phones come with SMS pre-installed, RCS is not always pre-installed. Even if it is installed, it may not be enabled. This means that there are a mixture of mobile phones that support RCS and those that do not, making it difficult to determine whether to send information to customers via RCS or SMS.

[0006] As a countermeasure to this, there is an alternative delivery function (also called a fallback function). The alternative delivery function notifies mobile phones that support RCS of information via RCS, and notifies mobile phones that do not support RCS by SMS. This alternative delivery function is owned by, for example, mobile carriers (mobile phone operators). By using this function, SMS can be automatically sent to mobile phones that do not support RCS. [Prior art documents] [Patent documents]

[0007] [Patent Document 1] JP 2007-241732 A Summary of the Invention [Problem to be solved by the invention]

[0008] However, even if the alternative delivery function could be used to send information via SMS to mobile phones that do not support RCS, it did not encourage customers to make their mobile phones compatible with RCS.

[0009] In view of the above-mentioned problems, an object of the present invention is to provide a distribution system, a server device, a distribution method, and a program that can prompt a customer to make his / her mobile phone compatible with RCS. [Means for solving the problem]

[0010] In order to solve the above-mentioned problems, a delivery system according to one embodiment of the present invention includes a storage unit that stores a delivery DB including at least notification content indicating a message to be notified to a user, information in which one of an RCS notification using RCS, an SMS notification using SMS, or a delivery notification for delivering a printed matter is set as a notification method for notifying the notification content, and destination information indicating a mobile phone number to which the RCS notification and the SMS notification are to be sent, a determination unit that uses the destination information in the delivery DB to determine whether or not the user's terminal supports RCS without sending an actual message indicating the actual state of the notification content to the user's terminal, and a transmission unit that, based on a determination result by the determination unit, transmits the notification content to the user's terminal by the RCS notification if the user's terminal supports RCS, and transmits the notification content to the user's terminal by the SMS notification if the user's terminal does not support RCS, and a determination unit that determines whether or not the RCS notification or the SMS notification by the transmission unit has been completed normally, and if the RCS notification has not been completed normally, transmits the notification content as follows: The same mobile phone number was used as the destination of the RCS notification. and a control unit that sets the delivery notification as the notification method in the distribution DB without sending the SMS notification to the user's terminal, and if the SMS notification is not completed successfully, sets the delivery notification as the notification method in the distribution DB.

[0011] Furthermore, in the above-mentioned distribution system, when the RCS notification or the SMS notification by the transmitting unit is successfully completed, the control unit sends a confirmation notification to the user's terminal inquiring as to whether the next and subsequent notifications should be the RCS notification, the SMS notification, or the delivery notification, and sets the notification method in the distribution DB depending on the response to the confirmation notification.

[0012] Moreover, in the above-mentioned distribution system according to the present invention, the control unit sets an initial setting of the notification method in the distribution DB to the RCS notification.

[0013] Furthermore, a server device according to one embodiment of the present invention includes a storage unit that stores a distribution DB including at least notification content indicating a message to be notified to a user, information in which one of an RCS notification using RCS, an SMS notification using SMS, or a delivery notification for delivering a printed matter is set as a notification method for notifying the notification content, and destination information indicating a mobile phone number to which the RCS notification and the SMS notification are to be sent, a confirmation request unit that requests a mobile carrier server to determine whether or not the user's terminal supports RCS using the destination information in the distribution DB without sending an actual message indicating the actual state of the notification content to the user's terminal, and a confirmation request unit that transmits the notification content to the user's terminal by the RCS notification if the user's terminal supports RCS based on a determination result determined by the mobile carrier server in response to the request by the confirmation request unit, and transmits the notification content to the user's terminal by the SMS notification if the user's terminal does not support RCS. The above A transmission request unit that requests a mobile carrier server, and a transmission request unit that determines whether the RCS notification or the SMS notification by the mobile carrier server is normally completed, and if the RCS notification is not normally completed, the notification content is The same mobile phone number was used as the destination of the RCS notification. and a control unit that sets the delivery notification as the notification method in the distribution DB without sending the SMS notification to the user's terminal, and if the SMS notification is not completed successfully, sets the delivery notification as the notification method in the distribution DB.

[0014] Furthermore, a delivery method according to one aspect of the present invention is a delivery method executed by a computer having a storage unit that stores a delivery DB including at least notification content indicating a message to be notified to a user, information in which one of an RCS notification using RCS, an SMS notification using SMS, or a delivery notification for delivering a printed matter is set as a notification method for notifying the notification content, and destination information indicating a mobile phone number to which the RCS notification and the SMS notification are to be sent, wherein a confirmation request unit requests a mobile carrier server to determine whether or not the user's terminal supports RCS using the destination information in the delivery DB without sending an actual message indicating the actual state of the notification content to the user's terminal, and a transmission request unit transmits the notification content to the user's terminal by the RCS notification if the user's terminal supports RCS, and transmits the notification content to the user's terminal by the SMS notification if the user's terminal does not support RCS, based on a determination result determined by the mobile carrier server in response to the request by the confirmation request unit. The above A control unit determines whether the RCS notification or the SMS notification by the mobile carrier server is normally completed, and if the RCS notification is not normally completed, the notification content is: The same mobile phone number was used as the destination of the RCS notification. The delivery notification is set as the notification method in the distribution DB without sending the SMS notification to the user's terminal, and if the SMS notification is not completed normally, the delivery notification is set as the notification method in the distribution DB.

[0015] A program according to one aspect of the present invention is a program for causing a computer to operate as the server device described above, and for causing the computer to function as each unit of the server device. Effect of the Invention

[0016] According to the present invention, customers can be prompted to enable RCS on their mobile phones. [Brief description of the drawings]

[0017] [Figure 1] 1 is a block diagram showing an example of the configuration of a distribution system 1 according to an embodiment. [Diagram 2] 2 is a block diagram showing an example of the configuration of an information management server 20 according to the embodiment. FIG. [Diagram 3] 2 is a block diagram showing a configuration example of a mobile carrier server 30 according to the embodiment. FIG. [Figure 4] 2 is a diagram showing an example of the configuration of distribution target data 120 according to the embodiment. FIG. [Diagram 5] 2 is a diagram showing an example of the configuration of a distribution DB 220 according to the embodiment; FIG. [Figure 6] 4 is a flowchart showing a flow of processing in the distribution system 1 according to the embodiment. [Figure 7] 4 is a flowchart showing a flow of processing in the distribution system 1 according to the embodiment. [Figure 8] 4 is a flowchart showing a flow of processing in the distribution system 1 according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] Fig. 1 is a block diagram showing an example of the configuration of a distribution system 1 according to an embodiment. As shown in Fig. 1, the distribution system 1 includes, for example, a corporate server 10, an information management server 20, a mobile carrier server 30, and a consumer terminal 40. The components of the distribution system 1 (the corporate server 10, the information management server 20, the mobile carrier server 30, and the consumer terminal 40) are communicatively connected via a communication network.

[0019] The corporate server 10 is a terminal device of a company that distributes information to customers (users) via the information management server 20. The consumer terminal 40 is a terminal device of a customer that receives information distributed from a company. In the example of FIG. 1, a case is illustrated in which one corporate server 10 and one consumer terminal 40 are provided in the distribution system 1, but this is not limited thereto. The distribution system 1 may be configured to have multiple corporate servers 10 and multiple consumer terminals 40.

[0020] The mobile carrier server 30 is an information processing device of a mobile carrier (a mobile phone operator). In the example of Fig. 1, a case where one mobile carrier server 30 is provided in the distribution system 1 is illustrated, but this is not limited thereto. A configuration in which each mobile carrier server 30 of a plurality of mobile carriers is provided in the distribution system 1 may be used.

[0021] The enterprise server 10 is realized by a computer device such as a server device, a cloud device, or a PC (Personal Computer). The enterprise server 10 includes, for example, a communication unit 11, a storage unit 12, and a control unit 13. The communication unit 11 communicates with external devices. The external devices here are the information management server 20, the mobile carrier server 30, and the consumer terminal 40. In this embodiment, the enterprise server 10 communicates only with the information management server 20.

[0022] The storage unit 12 is configured by a storage medium such as a hard disk drive (HDD), a flash memory, an electrically erasable programmable read only memory (EEPROM), a random access read / write memory (RAM), a read only memory (ROM), or a combination of these. The storage unit 12 stores programs for executing various processes of the company server 10, and temporary data used when executing various processes. The storage unit 12 stores, for example, data 120 to be distributed.

[0023] Here, the distribution target data 120 will be described with reference to FIG. 4. FIG. 4 is a diagram showing an example of the configuration of the distribution target data 120 according to the embodiment. The distribution target data 120 is information indicating the contents of distribution requested to the information management server 20. As shown in FIG. 4, the distribution target data 120 includes items such as a customer ID, a mobile phone number, a mailing address, and notification contents. The customer ID is identification information that uniquely identifies a customer. The mobile phone number is the telephone number of a mobile phone of a customer identified by the customer ID. The mailing address is information indicating an address to which mail is to be sent when mailing to a customer identified by the customer ID. The notification contents are information indicating the specific contents of a message to be notified to a customer. FIG. 4 shows an example in which a message beginning with "Message from TF Bank..." is set to be delivered to a customer whose mobile phone number is "090-1111-1111" and whose mailing address is "Chuo-ku, Tokyo...".

[0024] Returning to the explanation of Fig. 1, the control unit 13 is realized by causing a CPU (Central Processing Unit) provided as hardware in the enterprise server 10 to execute a program. The control unit 13 comprehensively controls the enterprise server 10. The control unit 13 transmits, for example, data to be distributed 120 to the information management server 20 via the communication unit 11.

[0025] The information management server 20 is a computer device that controls the delivery of information to a notification destination consumer terminal 40 in response to a request from the corporate server 10. The information management server 20 is realized by, for example, a cloud device, a server device, a PC, or the like.

[0026] In response to a request from the enterprise server 10, the information management server 20 requests the mobile carrier server 30 to send a notification using RCS (RCS notification) or a notification using SMS (SMS notification) to the consumer terminal 40 of the notification destination. Specifically, if the consumer terminal 40 of the notification destination supports RCS, the information management server 20 requests the mobile carrier server 30 to send an RCS notification to that consumer terminal 40. In addition, if the consumer terminal 40 of the notification destination does not support RCS, the information management server 20 requests the mobile carrier server 30 to send an SMS notification to that consumer terminal 40.

[0027] The information management server 20 may determine whether the notification destination resident terminal 40 supports RCS by any method. For example, the information management server 20 may determine whether the resident terminal 40 supports RCS based on information reported by the resident terminal 40.

[0028] Furthermore, the information management server 20 may request the mobile carrier server 30 to determine whether or not the resident terminal 40 supports RCS. In this case, the mobile carrier server 30 uses a function of the mobile carrier server 30 (a function of an RCS transmission availability confirmation unit 333 described later) to determine whether or not the resident terminal 40 supports RCS, and notifies the information management server 20 of the determination result. Based on the determination result notified from the mobile carrier server 30, the information management server 20 determines whether or not the resident terminal 40 supports RCS.

[0029] Furthermore, if an RCS notification or an SMS notification sent to the consumer terminal 40 of a customer fails, the information management server 20 causes mail to be delivered to the customer. The process by which the information management server 20 causes mail to be delivered to a customer will be described in detail later.

[0030] The mobile carrier server 30 is a computer device that sends RCS notifications and SMS notifications to the consumer terminal 40. The mobile carrier server 30 is realized by, for example, a cloud device, a server device, a PC, etc. In response to a request from the information management server 20, the mobile carrier server 30 sends an RCS notification or an SMS notification to the consumer terminal 40 that is the notification destination. Specifically, when the mobile carrier server 30 receives a request from the information management server 20 to send an RCS notification to the consumer terminal 40, the mobile carrier server 30 sends an RCS notification to the consumer terminal 40. In addition, when the mobile carrier server 30 receives a request from the information management server 20 to send an SMS notification to the consumer terminal 40, the mobile carrier server 30 sends an SMS notification to the consumer terminal 40.

[0031] Furthermore, when the mobile carrier server 30 receives a request from the information management server 20 to determine whether or not the consumer terminal 40 supports RCS, the mobile carrier server 30 determines whether or not the consumer terminal 40 supports RCS. The mobile carrier server 30 notifies the information management server 20 of the result of determining whether or not the consumer terminal 40 supports RCS.

[0032] The consumer terminal 40 is, for example, a computer device such as a smartphone, a tablet terminal, or a mobile phone. The consumer terminal 40 includes, for example, a communication unit 41, a storage unit 42, a control unit 43, and a display unit 44. The communication unit 41 communicates with external devices. The external devices here are the enterprise server 10, the information management server 20, and the mobile carrier server 30. In this embodiment, the consumer terminal 40 communicates only with the mobile carrier server 30.

[0033] The storage unit 42 is configured by a storage medium such as a HDD, a flash memory, an EEPROM, a RAM, a ROM, or a combination of these. The storage unit 42 stores programs for executing various processes of the consumer terminal 40, and temporary data used when executing various processes. The storage unit 42 stores, for example, an application program related to RCS (RCS app) and an application program related to SMS (SMS app). Note that the RCS app and the SMS app may be configured by the same application program.

[0034] The control unit 43 is realized by making the CPU, which the consumer terminal 40 has as hardware, execute a program. The control unit 43 comprehensively controls the consumer terminal 40. For example, the control unit 43 makes the CPU execute an RCS app stored in the storage unit 42, thereby realizing a function related to RCS. The RCS-related function here is, for example, a function of receiving an RCS notification and displaying a message notified by the RCS notification based on the received information. The control unit 43 also makes the CPU execute an SMS app stored in the storage unit 42, thereby realizing a function related to SMS. The SMS-related function here is, for example, a function of receiving an SMS notification and displaying a message notified by the SMS notification based on the received information.

[0035] The display unit 44 includes a display device such as a liquid crystal display, and under the control of the control unit 43, displays an image of a message notified by RCS notification or a message notified by SMS notification.

[0036] 2 is a block diagram showing a configuration example of the information management server 20 according to the embodiment. The information management server 20 includes, for example, a communication unit 21, a storage unit 22, and a control unit 23. The communication unit 21 communicates with external devices. The external devices here are the enterprise server 10 and the mobile carrier server 30.

[0037] The storage unit 22 is configured by a storage medium such as a HDD, a flash memory, an EEPROM, a RAM, a ROM, or a combination of these. The storage unit 22 stores programs for executing various processes of the information management server 20 and temporary data used when performing various processes. The storage unit 22 stores, for example, a distribution DB 220.

[0038] Here, the distribution DB 220 will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of the configuration of the distribution DB 220 according to the embodiment. The distribution DB 220 is a database in which information related to distribution is stored. The distribution DB 220 is generated according to the distribution target data 120 received from the company server 10, for example.

[0039] As shown in FIG. 5, the distribution DB 220 includes items such as a customer ID, a mobile phone number, a mailing address, a notification content, a notification method, a notification completion flag, and a notification date and time. The contents shown in each of the items of the customer ID, the mobile phone number, the mailing address, and the notification content are the same as those of the distribution target data 120, and therefore the description thereof will be omitted. These items are set, for example, based on the distribution target data 120 notified from the enterprise server 10. Note that the notification content may be held by the carrier side and not held by the information management server 20. The carrier side here is the mobile carrier server 30. In this case, the notification content of the distribution target data 120 is transmitted from the information management server 20 to the mobile carrier server 30, and the transmitted notification content is stored in the storage unit 32. The notification content is not stored in the information management server 20.

[0040] The notification method is an item in which the notification method is set when notifying a customer of information. The notification method has items of an RCS flag, an SMS flag, and a mail flag. The RCS flag is binary information indicating whether or not to perform an RCS notification. The SMS flag is binary information indicating whether or not to perform an SMS notification. The mail flag is binary information indicating whether or not to perform notification by mailing a piece of mail (an example of a "delivery notification").

[0041] For example, when the RCS flag is set to "1", an RCS notification is sent. On the other hand, when the RCS flag is set to "0", an RCS notification is not sent. For example, when the SMS flag is set to "1", an SMS notification is sent. On the other hand, when the SMS flag is set to "0", an SMS notification is not sent. For example, when the mail flag is set to "1", a mail notification is sent. On the other hand, when the mail flag is set to "0", a mail notification is not sent. In terms of the notification method, one of the RCS flag, SMS flag, and mail flag is set to "1", and the remaining flags are set to "0".

[0042] In this embodiment, as shown in the example of this figure, the initial setting values ​​of the notification method are set to "1" for the RCS flag, "0" for the SMS flag, and "0" for the mailing flag. However, this is not limited to this. The initial setting values ​​of the notification method may be set arbitrarily. Alternatively, the carrier side may have the RCS flag and the SMS flag for the notification method, and the information management server 20 may not hold them. The carrier side here is the mobile carrier server 30. In this case, the mobile carrier server 30 stores the RCS flag and the SMS flag for each of the consumer terminals 40 in the storage unit 32. For example, the mobile carrier server 30 sets the RCS flag and the SMS flag based on the result of determining whether or not the consumer terminal 40 supports RCS. Specifically, the mobile carrier server 30 sets the consumer terminals 40 to perform RCS notification for those consumer terminals 40 that support RCS, and to perform SMS notification for those consumer terminals 40 that do not support RCS. Also, each of the RCS flag, the SMS flag, and the mailing flag may be set as one flag (hereinafter, referred to as the notification method flag). For example, when the notification method flag is set to "0", an RCS notification may be performed, when the notification method flag is set to "1", an SMS notification may be performed, and when the notification method flag is set to "9", a mailing notification may be performed.

[0043] The notification completion flag is binary information that indicates whether or not notification to the customer has been completed. For example, when the notification completion flag is set to "1", it indicates that notification to the customer has been completed. On the other hand, when the notification completion flag is set to "0", it indicates that notification to the customer has not been completed. In this case, the initial setting of the notification completion flag is set to "0".

[0044] The notification date and time indicates information indicating the date and time when the notification is to be sent to the customer.

[0045] Returning to the explanation of Fig. 2, the control unit 23 is realized by causing a CPU provided as hardware in the information management server 20 to execute a program. The control unit 23 comprehensively controls the information management server 20. The control unit 23 includes, for example, an RCS transmission availability confirmation request unit 230, an RCS distribution request unit 231, and a device control unit 233.

[0046] The RCS transmission availability confirmation request unit 230 requests the mobile carrier server 30 to determine whether or not the consumer terminal 40 supports RCS, without transmitting an actual message (notification content in the distribution DB 220).

[0047] Specifically, the RCS transmission permission confirmation requesting unit 230 acquires the customer's mobile phone number by referring to the distribution DB 220. The RCS transmission permission confirmation requesting unit 230 transmits the acquired mobile phone number to the mobile carrier server 30, thereby requesting the mobile carrier server 30 to determine whether the consumer terminal 40 corresponding to the mobile phone number supports RCS. The RCS transmission permission confirmation requesting unit 230 acquires from the mobile carrier server 30 the determination result as to whether the consumer terminal 40 supports RCS.

[0048] In this way, the RCS transmission availability confirmation request unit 230 sends the mobile number and other associated management information to the mobile carrier server 30 to confirm whether the consumer terminal 40 corresponding to the mobile number supports RCS or not, without sending an actual message (the actual notification content in the distribution DB 220, i.e., the "Message from TF Bank..." portion). This eliminates the need to send an actual message to the customer's consumer terminal 40 and then perform trial and error such as sending an RRCS notification and an SMS notification in sequence until the transmission is successful.

[0049] The RCS delivery request unit 231 requests the mobile carrier server 30 to send an RCS notification to the notification destination consumer terminal 40 in accordance with instructions from the device control unit 233. The RCS delivery request unit 231 transmits, for example, a mobile phone number (mobile phone number in the delivery DB 220) that is the destination of the RCS notification and an actual message (notification content in the delivery DB 220) to the mobile carrier server 30. In this way, the RCS delivery request unit 231 requests the mobile carrier server 30 to send an RCS notification to the consumer terminal 40 of the customer.

[0050] The SMS delivery request unit 232 requests the mobile carrier server 30 to send an SMS notification to the consumer terminal 40 of the notification destination according to instructions from the device control unit 233. The SMS delivery request unit 232 transmits, for example, a mobile phone number (mobile phone number in the delivery DB 220) that is the destination of the SMS notification and an actual message (notification content in the delivery DB 220) to the mobile carrier server 30. In this way, the SMS delivery request unit 232 requests the mobile carrier server 30 to send an SMS notification to the consumer terminal 40 of the customer.

[0051] The device control unit 233 comprehensively controls the information management server 20. For example, the device control unit 233 transmits a request from the RCS transmission availability confirmation request unit 230 to the mobile carrier server 30 via the communication unit 21. Here, the request from the RCS transmission availability confirmation request unit 230 is a request to determine whether or not the consumer terminal 40 of the customer supports RCS.

[0052] The device control unit 233 acquires the determination result in response to the request from the RCS transmission availability confirmation request unit 230, which the communication unit 21 receives from the mobile carrier server 30. The determination result in response to the request from the RCS transmission availability confirmation request unit 230 is a determination result indicating whether or not the customer's consumer terminal 40 supports RCS.

[0053] The device control unit 233 delivers the real message to the customer based on the determination result in response to the request from the RCS transmission availability confirmation request unit 230. For the consumer terminal 40 determined by the mobile carrier server 30 to be compatible with RCS, the device control unit 233 outputs the mobile phone number (mobile phone number in the delivery DB 220) and the real message (notification content in the delivery DB 220) to the RCS delivery request unit 231. As a result, the device control unit 233 issues an RCS notification to the customer via the RCS delivery request unit 231. Also, for the consumer terminal 40 determined by the mobile carrier server 30 to be incompatible with RCS, the device control unit 233 outputs the mobile phone number (mobile phone number in the delivery DB 220) and the real message (notification content in the delivery DB 220) to the SMS delivery request unit 232. As a result, the device control unit 233 issues an SMS notification to the customer via the SMS delivery request unit 232.

[0054] The device control unit 233 judges whether the electronic notification (RCS notification or SMS notification) sent to the customer has been completed normally. As described above, the device control unit 233 performs the electronic notification based on the judgment result judged by the mobile carrier server 30. For this reason, it is considered that most of the electronic notifications sent to the customer are completed normally. However, after the judgment of the mobile carrier server 30, there may be cases where the customer cancels the mobile phone contract, changes the mobile carrier (mobile phone carrier), or uninstalls the RCS app or SMS app. In such cases, it is considered that the electronic notification is not completed normally and fails. Also, if the mobile phone is not turned on when the electronic notification is sent, the electronic notification is not completed normally and fails.

[0055] If an electronic notification to a customer fails, the device control unit 233 sets the notification method in the delivery DB 220 corresponding to that customer to "mail notification." Specifically, the device control unit 233 sets the mail flag in the notification method in the delivery DB 220 to "1," and sets the other RCS flags and SMS flags to "0."

[0056] In this manner, in the present embodiment, if the RCS notification fails, the notification is set to be sent by post instead of the SMS notification, thereby prompting the customer to make the consumer terminal 40 compatible with RCS.

[0057] When SMS notification is made to a consumer terminal 40 that does not support RCS, the customer can receive the message by SMS. Therefore, a customer who thinks that it is sufficient to be able to receive information on the consumer terminal 40 is likely to continue receiving information by SMS out of habit. In this case, it is not possible to urge the customer to make the consumer terminal 40 compatible with RCS. On the other hand, if a message is sent by mail to the consumer terminal 40 when it is not compatible with RCS, the customer will understand that unless the consumer terminal 40 is made compatible with RCS, the customer will not be able to receive information on the consumer terminal 40. Therefore, it is considered that a customer who wants to receive information on the consumer terminal 40 will make the consumer terminal 40 compatible with RCS. Therefore, it is possible to urge the customer to make the consumer terminal 40 compatible with RCS.

[0058] On the other hand, when the electronic notification to the customer is completed normally, the device control unit 233 performs a next preference confirmation with the customer. The next preference confirmation is to confirm the notification method the customer desires for the next notification onwards. For example, the device control unit 233 sends a confirmation notification to the mobile phone number to which the electronic notification was successful.

[0059] The confirmation notification is a notification for confirming the notification method from the next time onwards. For example, a confirmation notification sent to the consumer terminal 40 for which the RCS notification was successful is a notification in which three selection buttons, "Notification by RCS," "Notification by SMS," and "Notification by mail," are displayed together with a message such as "Please select your desired notification method for the next notification onwards."

[0060] In this case, the customer visually checks the confirmation notice displayed on the consumer terminal 40 and selects, by touch operation or the like, a selection button corresponding to the notification method desired by the customer. As a result, the notification method desired by the customer is notified to the information management server 20. The device control unit 233 acquires the information notified to the information management server 20 via the communication unit 21. The device control unit 233 sets the acquired notification method as the notification method of the delivery DB 220 corresponding to that customer.

[0061] Specifically, if the customer desires RCS notification for the next or subsequent notification, the device control unit 233 does not change the notification method in the delivery DB 220. This is because the RCS notification flag is set to "1" as the initial setting. Also, if the customer desires SMS notification for the next or subsequent notification, the device control unit 233 sets the SMS notification flag in the notification method in the delivery DB 220 to "1" and sets other RCS flags and mail flags to "0." Also, if the customer desires mail notification for the next or subsequent notification, the device control unit 233 sets the mail flag in the notification method in the delivery DB 220 to "1" and sets other RCS flags and SMS flags to "0."

[0062] 3 is a block diagram showing an example of a configuration of the mobile carrier server 30 according to the embodiment. The mobile carrier server 30 includes, for example, a communication unit 31, a storage unit 32, and a control unit 33. The communication unit 31 communicates with external devices. The external devices here are the information management server 20 and the resident terminal 40.

[0063] The storage unit 32 is configured with a storage medium such as a HDD, a flash memory, an EEPROM, a RAM, a ROM, or a combination of these. The storage unit 32 stores programs for executing various processes of the mobile carrier server 30, and temporary data used when performing various processes. The storage unit 32 stores, for example, RCS transmission feasibility check result information 320. The RCS transmission feasibility check result information 320 is information indicating whether or not a mobile phone supports RCS. The RCS transmission feasibility check result information 320 is, for example, information in which the telephone number of a mobile phone is associated with information indicating whether or not the mobile phone supports RCS.

[0064] The control unit 33 is realized by causing a CPU provided as hardware in the mobile carrier server 30 to execute a program. The control unit 33 comprehensively controls the mobile carrier server 30. The control unit 33 includes, for example, an RCS transmission availability confirmation request receiving unit 330, an RCS delivery request relay unit 331, an SMS delivery request relay unit 332, an RCS transmission availability confirmation unit 333, an RCS delivery unit 334, an SMS delivery unit 335, and a device control unit 336.

[0065] Here, a configuration including the RCS transmission availability confirmation request receiving unit 330, the RCS delivery request relay unit 331, and the SMS delivery request relay unit 332 is referred to as a distribution unit 33A. Also, a configuration including the RCS transmission availability confirmation unit 333, the RCS delivery unit 334, and the SMS delivery unit 335 is referred to as a delivery unit 33B.

[0066] 3, the case where the sorting unit 33A and the delivery unit 33B are provided in the mobile carrier server 30 is illustrated, but the present invention is not limited thereto. For example, one of the multiple mobile carriers may be configured to have the sorting unit 33A and the delivery unit 33B, and the remaining mobile carriers may be configured to have only the delivery unit 33B. Also, the information management server 20 may be configured to have the sorting unit 33A, and to perform delivery using the delivery units 33B provided in each of the multiple mobile carriers.

[0067] The RCS transmission permission confirmation request reception unit 330 acquires the request from the RCS transmission permission confirmation request unit 230 via the communication unit 31 , and outputs the acquired information to the RCS transmission permission confirmation unit 333 .

[0068] The RCS distribution request relay unit 331 acquires the request from the RCS distribution request unit 231 via the communication unit 31 , and outputs the acquired information to the RCS distribution unit 334 .

[0069] The SMS delivery request relay unit 332 acquires the request from the SMS delivery request unit 232 via the communication unit 31 , and outputs the acquired information to the SMS delivery unit 335 .

[0070] The RCS transmission permission confirmation unit 333 acquires a request from the RCS transmission permission confirmation request unit 230 from the RCS transmission permission confirmation request reception unit 330. In response to the acquired request, the RCS transmission permission confirmation unit 333 determines whether the lifestyle terminal 40 supports RCS.

[0071] The method by which the RCS transmission availability confirmation unit 333 determines whether the resident terminal 40 supports RCS may be determined arbitrarily. For example, the RCS transmission availability confirmation unit 333 notifies the mobile phone number of the resident terminal 40 of a control signal related to RCS notification. This control signal includes, for example, a request signal requesting a response as to whether the resident terminal 40 can use RCS notification. When the resident terminal 40 receives the control signal related to RCS notification, the resident terminal 40 returns a response to the mobile carrier server 30 as to whether RCS can be used or not in response to the received control signal. The RCS transmission availability confirmation unit 333 determines whether the resident terminal 40 supports RCS based on the response from the resident terminal 40. The RCS transmission availability confirmation unit 333 notifies the information management server 20 of the determination result.

[0072] The RCS distribution unit 334 acquires the request from the RCS distribution request unit 231 via the RCS distribution request relay unit 331. The RCS distribution unit 334 performs an RCS notification to the user terminal 40 in response to the acquired request.

[0073] The SMS delivery unit 335 acquires the request from the SMS delivery request unit 232 via the SMS delivery request relay unit 332. The SMS delivery unit 335 sends an SMS notification to the consumer terminal 40 in response to the acquired request.

[0074] The distribution unit 33B may directly acquire a request (a request for an RCS notification or an SMS notification) from the information management server 20. For example, when the mobile carrier server 30 does not include the distribution unit 33A, or when the information management server 20 does not use the distribution unit 33A of the mobile carrier server 30, the information management server 20 transmits a request for an RCS notification or an SMS notification to the distribution unit 33B without going through the distribution unit 33A.

[0075] In this case, the RCS distribution unit 334 directly receives the request from the RCS distribution request unit 231, without going through the RCS distribution request relay unit 331. The RCS distribution unit 334 sends an RCS notification to the resident terminal 40 in response to the request received from the information management server 20. Also, in this case, the SMS distribution unit 335 directly receives the request from the SMS distribution request unit 232, without going through the SMS distribution request relay unit 332. The SMS distribution unit 335 sends an SMS notification to the resident terminal 40 in response to the request received from the information management server 20.

[0076] The device control unit 336 performs overall control of the mobile carrier server 30. For example, the device control unit 336 determines the content of information received by the communication unit 31 from the information management server 20 based on the information, and outputs the information to the RCS transmission permission confirmation request receiving unit 330 if the information requests an RCS transmission permission confirmation.

[0077] When the information received by the communication unit 31 from the information management server 20 requests an RCS notification, the device control unit 336 outputs the information to the RCS delivery request relay unit 331. When the information received by the communication unit 31 from the information management server 20 requests an SMS notification, the device control unit 336 outputs the information to the SMS delivery request relay unit 332.

[0078] If the information received by the communication unit 31 from the information management server 20 is a request for an RCS notification without passing through the RCS delivery request relay unit 331, the device control unit 336 outputs the information to the RCS delivery unit 334. If the information received by the communication unit 31 from the information management server 20 is a request for an SMS notification without passing through the SMS delivery request relay unit 332, the device control unit 336 outputs the information to the SMS delivery unit 335.

[0079] 6 is a flowchart showing a flow of processing performed by the information management server 20 according to the embodiment. First, the information management server 20 acquires the distribution target data 120 transmitted from the company server 10 (step S1). The information management server 20 generates a distribution DB 220 based on the acquired distribution target data 120 (step S2).

[0080] The information management server 20 determines whether the customer's consumer terminal 40 supports RCS (step S3). The information management server 20 refers to the distribution DB 220 to acquire the customer's mobile phone number, transmits the acquired number to the mobile carrier server 30, and requests the mobile carrier server 30 to determine whether the mobile phone with that number supports RCS. In response to the request from the information management server 20, the mobile carrier server 30 determines whether the mobile phone with that number supports RCS by notifying a control signal, for example, and transmits the determination result to the information management server 20. The information management server 20 receives the determination result from the mobile carrier server 30.

[0081] If the customer's consumer terminal 40 supports RCS, the information management server 20 sends an RCS notification to the consumer terminal 40 (step S4). On the other hand, if the customer's consumer terminal 40 does not support RCS, the information management server 20 sends an SMS notification to the consumer terminal 40 (step S5).

[0082] The information management server 20 determines whether the electronic notification (RCS notification or SMS notification) sent to the customer has been completed normally (step S6). If the electronic notification sent to the customer has been completed normally, the information management server 20 performs a next preference confirmation process (step S7). The next preference confirmation process is a process for confirming the notification method desired by the customer for the next and subsequent notifications by sending a confirmation notification. The flow of the next preference confirmation process will be described later.

[0083] On the other hand, if the electronic notification to the customer is not completed normally and fails, the information management server 20 sets the mail flag of the notification method in the delivery DB 220 corresponding to the customer to "1" (step S8). The information management server 20 sets the RCS flag and the SMS flag of the notification method in the delivery DB 220 corresponding to the customer to "0".

[0084] The information management server 20 updates the delivery DB 220 (step S9). For example, for a delivery in which electronic notification has been normally completed, the information management server 20 sets the notification completion flag in the delivery DB 220 to "1". Here, the information management server 20 may report the updated delivery DB 220 to the company server 10 as the delivery result.

[0085] The information management server 20 performs mailing processing for the customer whose mailing flag is set to "1" (step S10). The mailing processing is processing for mailing a mail piece on which the contents of the actual message are printed to the customer. The flow of the mailing processing will be described later.

[0086] Fig. 7 is a flowchart showing the flow of the next preference confirmation process shown in step S7 of Fig. 6. As a premise of this flow, it is assumed that the information management server 20 has already transmitted a confirmation notification to the resident terminal 40 for which the electronic notification has been normally completed.

[0087] The information management server 20 receives a response to the confirmation notice (step S70). The response indicates one of RCS notification, SMS notification, and mail notification as the notification method the customer prefers for the next and subsequent notifications.

[0088] The information management server 20 determines whether the reply from the customer indicates a notification method of RCS notification, SMS notification, or mail notification (step S71). If the reply indicates an RCS notification, the information management server 20 ends the processing related to this flow. This is because the RCS flag has already been set to "1" as the initial value of the notification method in the distribution DB 220. Note that, in order to ensure processing, the information management server 20 may refer to the distribution DB 220 and set the RCS flag to "1" and the SMS flag and mail flag to "0".

[0089] If the reply from the customer indicates SMS notification, the information management server 20 sets the SMS flag of the notification method in the corresponding delivery DB 220 to "1" and sets the RCS flag and mail flag to "0" (step S72).

[0090] If the reply from the customer indicates that the notification should be by mail, the information management server 20 sets the mail flag for the notification method in the corresponding delivery DB 220 to "1" and sets the RCS flag and SMS flag to "0" (step S73).

[0091] FIG. 8 is a flowchart showing the flow of the mailing process shown in step S10 of FIG. 6. First, the information management server 20 refers to the distribution DB 220 and extracts items for which the mailing flag is set to "1" (step S100). The information management server 20 generates mailing target data using the extracted distribution DB 220 (step S101). The mailing target data is information used when arranging mailing, and is information indicating, for example, the address, name, and notification content of the destination. The information management server 20 arranges delivery of the mailing using the generated mailing target data (step S102). For example, the information management server 20 transmits the mailing target data to a printing company and instructs them to mail the mailing. For mailings for which the mailing process has been normally completed, the information management server 20 sets the notification completion flag in the distribution DB 220 to "1".

[0092] As described above, the delivery system 1 according to the embodiment includes the storage unit 22, the RCS transmission availability confirmation unit 333, the RCS delivery unit 334, and the device control unit 233. The storage unit 22 stores the delivery DB 220. The delivery DB 220 is information indicating an actual message (notification content) to be notified to a customer, a notification method, and a mobile phone number to be the destination. The notification method is set to be any one of RCS notification, SMS notification, and mail notification. The RCS transmission availability confirmation unit 333 determines whether the consumer terminal 40 of the customer supports RCS using the mobile phone number in the delivery DB 220. The RCS delivery unit 334 transmits the actual message to the consumer terminal 40 by RCS notification if the consumer terminal 40 supports RCS based on the determination result by the RCS transmission availability confirmation unit 333, and transmits the actual message by SMS notification if the consumer terminal 40 does not support RCS. The device control unit 233 determines whether the RCS notification by the RCS distribution unit 334 has been completed normally, and if it has not been completed normally, sets the notification method in the distribution DB 220 to "mail notification."

[0093] As a result, the distribution system 1 according to the embodiment can prompt the customer to make their mobile phone compatible with RCS. If the message is sent by mail instead of by SMS notification, the customer will understand that they will not be able to receive information on the consumer terminal 40 unless they make the consumer terminal 40 compatible with RCS. For this reason, it is considered that a customer who wants to receive information on the consumer terminal 40 will make the consumer terminal 40 compatible with RCS.

[0094] Here, the RCS transmission feasibility confirmation unit 333 is an example of a "determination unit." The RCS distribution unit 334 is an example of a "sending unit." The device control unit 233 is an example of a "control unit." The actual message is an example of "notification content." The customer is an example of a "user." Mailed items are an example of "printed matter." The mobile phone number is an example of "destination information." The mailed notification is an example of a "delivery notification." The consumer terminal 40 is an example of a "user's terminal."

[0095] Furthermore, in the delivery system 1 according to the embodiment, when the RCS notification by the RCS delivery unit 334 is normally completed, the device control unit 233 transmits a confirmation notification to the consumer terminal 40. The confirmation notification is a notification that inquires the customer as to whether the next and subsequent notifications should be RCS notifications, SMS notifications, or mail notifications. The device control unit 233 sets the notification method in the delivery DB 220 according to the response to the confirmation notification. As a result, in the delivery system 1 according to the embodiment, the next and subsequent notifications can be sent by a notification method according to the customer's preference. Furthermore, in the delivery system 1 according to the embodiment, the device control unit 233 may transmit a confirmation notification to the consumer terminal 40 when the SMS notification by the SMS delivery unit 335 is normally completed. The device control unit 233 sets the notification method in the delivery DB 220 according to the response to the confirmation notification. As a result, in the delivery system 1 according to the embodiment, the next and subsequent notifications can be made by the notification method according to the customer's preference.

[0096] Furthermore, in the distribution system 1 according to the embodiment, the device control unit 233 sets the initial setting of the notification method in the distribution DB 220 to RCS notification. As a result, in the distribution system 1 according to the embodiment, when an RCS notification is indicated as a response to a confirmation notification, it is not necessary to change the notification method in the distribution DB 220, and it is possible to reduce the processing load.

[0097] The information management server 20 according to the embodiment includes a storage unit 22, an RCS transmission availability confirmation request unit 230, an RCS distribution request unit 231, and a device control unit 233. The storage unit 22 stores the distribution DB 220. The RCS transmission availability confirmation request unit 230 requests the mobile carrier server 30 to determine whether the customer's resident terminal 40 supports RCS using the mobile phone number in the distribution DB 220. The RCS distribution request unit 231 requests the mobile carrier server 30 to perform an RCS notification to the resident terminal 40 according to the determination result of the mobile carrier server 30 in response to the request by the RCS transmission availability confirmation request unit 230. The device control unit 233 determines whether the RCS notification or SMS notification by the mobile carrier server 30 has been completed normally, and sets the notification method of the distribution DB 220 to a mail notification if it has not been completed normally. In this way, the information management server 20 according to the embodiment can urge the customer to make their mobile phone compatible with RCS, as described above.

[0098] Here, the information management server 20 is an example of a "server device." The RCS transmission permission confirmation request unit 230 is an example of a "confirmation request unit." The RCS distribution request unit 231 is an example of a "transmission request unit."

[0099] In the above embodiment, in the next preference confirmation process shown in step S7, an example has been described in which the customer responds with one of RCS notification, SMS notification, and mail notification as the desired notification method. However, this is not limited to this. The customer may select one desired notification method, or may select multiple notification methods. For example, if the customer selects both RCS notification and mail notification as the notification method from the next time onwards, both RCS notification and mail notification will be implemented for the next notification.

[0100] In the above embodiment, the notification method is described as "RCS notification, SMS notification, or mail notification", but is not limited thereto. The notification method may be email, SNS (Social Networking Service), or the like.

[0101] The notification method determined by the information management server 20 may be notified to the enterprise server 10. In this case, for example, in step S9, the information management server 20 reports the delivery result together with the latest notification method to the enterprise server 10.

[0102] The embodiment of the present invention has been described above. Note that all or part of the functions of the distribution system 1 and the information management server 20 in the above-mentioned embodiment may be realized by a computer. In that case, a program for realizing the functions may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read into a computer system and executed to realize the functions. Note that the term "computer system" here includes hardware such as an OS and peripheral devices. Furthermore, the term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into a computer system. Furthermore, the term "computer-readable recording medium" may include those that dynamically hold a program for a short period of time, such as a communication line when a program is transmitted via a network such as the Internet or a communication line such as a telephone line, and those that hold a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client in that case. Furthermore, the above-mentioned program may be for realizing part of the above-mentioned functions, and may further be capable of realizing the above-mentioned functions in combination with a program already recorded in the computer system, or may be realized using a programmable logic device such as an FPGA (Field Programmable Gate Array).

[0103] Although the embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design changes, etc. are possible within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0104] 1. Distribution System 10 Corporate Server 20 Information management server (server device) 230 RCS transmission permission confirmation request part (confirmation request part) 231 RCS distribution request part (transmission request part) 232 SMS delivery request section 233 Device Control Unit (Control Unit) 30 Mobile Carrier Server 330 RCS transmission availability confirmation request reception unit 331 RCS Delivery Request Relay Unit 332 SMS delivery request relay unit 333 RCS transmission confirmation unit (judgment unit) 334 RCS Distribution Unit (Transmitter) 335 SMS delivery unit (sending unit) 40 Consumer terminals (user terminals)

Claims

1. a storage unit that stores a delivery DB including at least notification contents indicating messages to be notified to a user, information in which any one of RCS notification using RCS, SMS notification using SMS, or delivery notification for delivering a printed matter is set as a notification method for notifying the notification contents, and destination information indicating mobile phone numbers to which the RCS notification and the SMS notification are to be sent; a determination unit that determines whether or not the user's terminal supports RCS by using the destination information in the distribution DB without transmitting an actual message indicating the actual state of the notification content to the user's terminal; a transmission unit that transmits the notification content to the user's terminal by the RCS notification when the user's terminal supports RCS based on a determination result by the determination unit, and transmits the notification content to the user's terminal by the SMS notification when the user's terminal does not support RCS; a control unit which determines whether the RCS notification or the SMS notification by the transmission unit has been normally completed, and if the RCS notification has not been normally completed, sets the delivery notification as the notification method in the distribution DB without transmitting the notification content to the user's terminal by the SMS notification addressed to the same mobile phone number as the destination of the RCS notification, and if the SMS notification has not been normally completed, sets the delivery notification as the notification method in the distribution DB; A distribution system comprising:

2. When the RCS notification or the SMS notification by the transmission unit is normally completed, the control unit transmits a confirmation notification to the user's terminal inquiring whether the next and subsequent notifications should be the RCS notification, the SMS notification, or the delivery notification, and sets the notification method in the delivery DB according to the response to the confirmation notification. The distribution system according to claim 1 .

3. The control unit sets an initial setting of the notification method in the distribution DB to the RCS notification.

3. The distribution system according to claim 1 or 2.

4. a storage unit that stores a delivery DB including at least notification contents indicating messages to be notified to a user, information in which any one of RCS notification using RCS, SMS notification using SMS, or delivery notification for delivering a printed matter is set as a notification method for notifying the notification contents, and destination information indicating mobile phone numbers to which the RCS notification and the SMS notification are to be sent; a confirmation request unit that requests a mobile carrier server to determine whether or not the user's terminal supports RCS by using the destination information in the distribution DB, without transmitting an actual message indicating the actual state of the notification content to the user's terminal; a transmission request unit that requests the mobile carrier server to transmit the notification content to the user's terminal by the RCS notification if the user's terminal supports RCS, and to transmit the notification content to the user's terminal by the SMS notification if the user's terminal does not support RCS, based on a determination result made by the mobile carrier server in response to a request from the confirmation request unit; a control unit that determines whether the RCS notification or the SMS notification by the mobile carrier server has been completed normally, and if the RCS notification has not been completed normally, sets the delivery notification as the notification method in the distribution DB without transmitting the notification content to the user's terminal by the SMS notification addressed to the same mobile phone number as the destination of the RCS notification, and if the SMS notification has not been completed normally, sets the delivery notification as the notification method in the distribution DB; A server device comprising:

5. A delivery method executed by a computer having a storage unit that stores a delivery DB including at least notification content indicating a message to be notified to a user, information in which any one of an RCS notification using an RCS, an SMS notification using an SMS, or a delivery notification for delivering a printed matter is set as a notification method for notifying a user of the notification content, and destination information indicating a mobile phone number to which the RCS notification and the SMS notification are to be sent, A confirmation request unit requests a mobile carrier server to determine whether or not the user's terminal supports RCS by using the destination information in the distribution DB, without transmitting an actual message indicating the actual state of the notification content to the user's terminal; a transmission request unit, based on a determination result made by the mobile carrier server in response to a request from the confirmation request unit, requests the mobile carrier server to transmit the notification content to the user's terminal by the RCS notification if the user's terminal supports RCS, and to transmit the notification content to the user's terminal by the SMS notification if the user's terminal does not support RCS; a control unit determines whether the RCS notification or the SMS notification by the mobile carrier server has been completed normally, and if the RCS notification has not been completed normally, sets the delivery notification as the notification method in the distribution DB without transmitting the notification content to the user's terminal by the SMS notification addressed to the same mobile phone number as the destination of the RCS notification, and if the SMS notification has not been completed normally, sets the delivery notification as the notification method in the distribution DB. Delivery method.

6. 5. A program for causing a computer to operate as the server device according to claim 4, the program causing the computer to function as each unit included in the server device.

Images