Distribution system, server device, distribution method, and program

Abstract

To set a sender display number for a customer who receives information through SMS, the number being the same as a number used in conventional SMS information distribution, in the case that information is transmitted through RCS to a cellphone which is compatible with RCS and information is transmitted through SMS to a cellphone which is incompatible with RCS.SOLUTION: A distribution system includes: an RCS distribution request unit which issues a request to transmit an RCS message through RCS to a user terminal; and an SMS distribution request unit which issues a request to transmit an SMS message through SMS to the user terminal. The RCS distribution request unit controls the RCS message to be transmitted in units of at least one account set for each client which is a sender of the RCS message. The SMS distribution request unit controls the SMS message to be transmitted in units of distribution source number that specifies a sender for each service provided by the client.SELECTED DRAWING: Figure 1

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 immediately accessible by the customer when notifying the customer.

[0003] Among these electronic notification services, messaging services that use mobile phone numbers as destinations are the most popular because they are highly convenient and allow you to send messages even if you do not know the recipient's email address.

[0004] There are several communication protocols for messaging services addressed to mobile phone numbers. Examples include RCS (Rich Communication Services) and SMS (Short Message Service). RCS is a standard for implementing instant messaging for mobile phones at the device level. RCS was designed with interoperability between telecommunications carriers in mind, allowing messages to be exchanged even between different telecommunications carriers. RCS also has a higher upper limit on the amount of information that can be sent than 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 prefer to distribute that information via RCS.

[0005] However, while most mobile phones come with SMS pre-installed, some do not have RCS pre-installed. Even if they are installed, RCS may not be enabled. This resulted in a mix of RCS-compatible and non-RCS-compatible mobile phones, making it difficult to determine whether to send information to customers via RCS or SMS.

[0006] To address this issue, there is an alternative delivery function (also known as a fallback function). The alternative delivery function notifies mobile phones that support RCS via RCS, and notifies mobile phones that do not support RCS via 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] Japanese Patent Application Laid-Open No. 2007-241732 Summary of the Invention [Problem to be solved by the invention]

[0008] However, SMS sent using the alternative delivery function use a sender display number (hereinafter referred to as the primary number), which is set only once for each official account. The official account here refers to the official RCS account of the company that is sending the notification. The sender display number is the phone number displayed on the recipient's mobile phone as the phone number of the SMS notification sender.

[0009] On the other hand, in conventional SMS delivery, different sender display numbers are often used depending on the responsible department or the target business within a company. For example, when sending an advertisement introducing a new product to a customer via SMS, the information is sent via the sender display number of the department in charge of advertising (hereinafter referred to as the second number), and when sending an SMS to inform a customer that their contract is about to expire, the information is sent via the sender display number of the department in charge of customer care (hereinafter referred to as the third number).

[0010] In other words, even if the notification is from the same company, while with conventional SMS delivery the notification is sent to a second or third number, when the alternative delivery function is used the notification is sent to a first number that is different from the second or third number. Therefore, when the alternative delivery function is used, customers who have been receiving information by SMS will receive the information from a different, unknown number. As a result, there is a possibility that the information sent by SMS using the alternative delivery function will be mistakenly perceived as information from a different company than the one they have been receiving notifications from until now.

[0011] In view of the above-mentioned problems, an object of the present invention is to provide a distribution system, server device, distribution method, and program that, when notifying information to mobile phones that support RCS via RCS and notifying information to mobile phones that do not support RCS via SMS, can set a sender display number similar to that used in conventional SMS distribution for customers to whom information is notified via SMS. [Means for solving the problem]

[0012] In order to solve the above-described problems, a delivery system according to one aspect of the present invention is a delivery system including a delivery request unit, a distribution unit, a delivery unit, and a user terminal, wherein the delivery request unit has an RCS delivery request unit that requests an RCS notification using RCS to be sent to the user terminal, an SMS delivery request unit that requests an SMS notification using SMS to be sent to the user terminal, and an RCS transmission availability determination request unit that requests a determination as to whether or not the user terminal is compatible with RCS based on information related to the RCS notification, and the distribution unit is an RCS delivery request relay unit that outputs information related to the SMS notification to the delivery unit based on information acquired from the SMS delivery request unit; an RCS transmission feasibility determination request receiving unit that outputs information acquired from the RCS transmission feasibility determination request unit to the delivery unit, wherein the delivery unit includes an RCS delivery unit that transmits the RCS notification to the user terminal, an SMS delivery unit that transmits the SMS notification to the user terminal, and a and an RCS transmission availability determination unit that determines whether the user terminal is compatible with RCS, and the user terminal has at least one of an RCS processing unit that receives and displays the RCS notification and an SMS processing unit that receives and displays the SMS notification, and the RCS delivery request unit transmits information related to the RCS notification to the RCS delivery unit via the RCS delivery request relay unit or without the RCS delivery request relay unit, and the SMS delivery request unit transmits information related to the SMS notification to the RCS delivery unit via the SMS delivery request relay unit or without the SMS delivery request relay unit. the RCS delivery unit transmits the RCS notification to the user terminal in response to a request from the RCS delivery request unit, the SMS delivery unit transmits the SMS notification to the user terminal in response to a request from the SMS delivery request unit, the RCS delivery request unit controls so that the RCS notification is transmitted in units of at least one account set for each customer that is the source of the RCS notification, and when the SMS delivery request unit receives a response to the request from the RCS transmission feasibility determination request unit indicating that the user terminal does not support RCS,For the user terminal that does not support RCS, The SMS notification is sent with the same sender number as when the SMS notification is sent without using the alternative delivery function. The SMS notification is controlled so that it is sent in units of a delivery source number that identifies the notification source for each service provided by the customer.

[0013] Furthermore, in the above-mentioned delivery system, the present invention is characterized in that the SMS processing unit of the user terminal displays the delivery source number.

[0015] Furthermore, a server device according to one aspect of the present invention includes an RCS delivery request unit that requests an RCS notification using RCS to be sent to a user terminal, an SMS delivery request unit that requests an SMS notification using SMS to be sent to the user terminal, and an RCS transmission availability determination request unit that requests a determination as to whether or not the user terminal supports RCS based on information related to the RCS notification, wherein the RCS delivery request unit controls the RCS notification to be sent for at least one account set for each customer that is the source of the RCS notification, and when a response is received in response to the request by the RCS transmission availability determination request unit that the user terminal does not support RCS, the SMS delivery request unit sends the following to the user terminal that does not support RCS: The SMS notification is sent with the same sender number as when the SMS notification is sent without using the alternative delivery function. The SMS notification is controlled so that it is sent in units of a delivery source number that identifies the notification source for each service provided by the customer.

[0016] Furthermore, a distribution method according to one aspect of the present invention is a distribution method executed by a computer, in which an RCS distribution request unit requests that an RCS notification using RCS be sent to a user terminal, an SMS distribution request unit requests that an SMS notification using SMS be sent to the user terminal, an RCS transmission availability determination request unit requests that a determination be made as to whether or not the user terminal supports RCS based on information related to the RCS notification, the RCS distribution request unit controls the RCS notification to be sent in units of at least one account set for each customer that is the source of the RCS notification, and when a response is received in response to the request by the RCS transmission availability determination request unit that the user terminal does not support RCS, the SMS delivery request unit sends to the user terminal that does not support RCS: The SMS notification is sent with the same sender number as when the SMS notification is sent without using the alternative delivery function. The SMS notification is controlled so that it is sent in units of a delivery source number that identifies the notification source for each service provided by the customer.

[0017] 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 included in the server device. [Effects of the Invention]

[0018] According to the present invention, when information is notified to mobile phones that support RCS via RCS and to mobile phones that do not support RCS via SMS, it is possible to set a sender display number for customers to whom information is notified via SMS, similar to that used for conventional SMS delivery. [Brief explanation of the drawings]

[0019] [Figure 1] 1 is a block diagram showing an example of the configuration of a distribution system 1 according to an embodiment. [Figure 2] 2 is a block diagram showing an example of the configuration of an information management server 20 according to the embodiment. FIG. [Figure 3]2 is a block diagram showing an example of the configuration of a mobile carrier server 30 according to the embodiment. FIG. [Figure 4] FIG. 2 is a diagram showing an example of the configuration of distribution request information 120 according to the embodiment. [Figure 5] FIG. 2 is a diagram showing an example of the configuration of setting information 220 according to the embodiment. [Figure 6] FIG. 2 is a diagram showing an example of the configuration of setting information 220 according to the embodiment. [Figure 7] FIG. 3 is a diagram showing an example of the configuration of RCS transmission availability confirmation result information 320 according to the embodiment. [Figure 8] FIG. 2 is a diagram showing a display example of a resident terminal 40 according to the embodiment. [Figure 9] FIG. 2 is a diagram showing a display example of a resident terminal 40 according to the embodiment. [Figure 10] 3 is a sequence diagram showing a processing flow in the distribution system 1 according to the embodiment. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0020] 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 company 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 company server 10, the information management server 20, the mobile carrier server 30, and the consumer terminal 40) are communicatively connected via a communication network.

[0021] The company server 10 is a terminal device of a company that distributes information to customers 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 company server 10 and one consumer terminal 40 are provided in the distribution system 1, but this is not limiting. The distribution system 1 may be configured to have multiple company servers 10 and multiple consumer terminals 40.

[0022] Furthermore, the mobile carrier server 30 is an information processing device of a mobile carrier (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 limiting. A configuration in which mobile carrier servers 30 of multiple mobile carriers are provided in the distribution system 1 may also be used.

[0023] 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.

[0024] The storage unit 12 is configured by a storage medium such as an HDD (Hard Disk Drive), flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), RAM (Random Access Read / Write Memory), ROM (Read Only Memory), 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 performing various processes. The storage unit 12 stores, for example, distribution request information 120.

[0025] Here, the delivery request information 120 will be described with reference to FIG. 4. FIG. 4 is a diagram showing an example of the configuration of the delivery request information 120 according to the embodiment. The delivery request information 120 is information used when requesting delivery from the information management server 20. As shown in FIG. 4, the delivery request information 120 includes items such as delivery conditions, delivery content, and multiple delivery recipients (delivery recipient 1, delivery recipient 2, ...). The delivery conditions are conditions for delivering information. The delivery content is specific content of the information to be delivered. The delivery recipient is information about customers to whom information is to be delivered, and is information that includes at least a mobile phone number that is the destination for RCS notifications or SMS notifications.

[0026] Figure 4 shows an example where the delivery condition is set to "send an RCS message to RCS users and an SMS message to non-RCS users," and the delivery content is set to a sentence beginning with "A message from TF Bank..."

[0027] 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 company server 10 to execute a program. The control unit 13 comprehensively controls the company server 10. The control unit 13 transmits, for example, distribution request information 120 to the information management server 20 via the communication unit 11.

[0028] The information management server 20 is a computer device that controls the distribution of information to the consumer terminal 40 of the notification destination in response to a request from the enterprise server 10. The information management server 20 is realized by, for example, a cloud device, a server device, a PC, etc. The information management server 20 is an example of a "server device."

[0029] 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 destination consumer terminal 40.

[0030] Specifically, if the notification destination resident terminal 40 supports RCS, the information management server 20 requests the mobile carrier server 30 to send an RCS notification to the resident terminal 40 .

[0031] Furthermore, if the consumer terminal 40 to be notified 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 .

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

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

[0034] When sending an RCS notification to the consumer terminal 40, the information management server 20 ensures that the RCS notification is sent to the consumer terminal 40 in units of at least one official account (account) set for each company (client) that is the source of the notification. An official account is an RCS account set by a communications carrier (mobile phone operator) that provides an RCS message service. When an RCS notification is sent, the official account is displayed on the consumer terminal 40 that is the notification destination as information identifying the source of the notification (see reference numeral 440 in FIG. 8 ).

[0035] Here, when sending an SMS notification to the consumer terminal 40, the information management server 20 does not use the alternative delivery function. The alternative delivery function is a function possessed by the mobile carrier server 30, and is a function that notifies information to mobile phones that support RCS via RCS and notifies information to mobile phones that do not support RCS via SMS. SMS notifications sent using the alternative delivery function use a sender number set in correspondence with the official account. For this reason, when an SMS notification uses the alternative delivery function, a sender number different from the number displayed when the alternative delivery function is not used is displayed on the consumer terminal 40 that is the notification destination.

[0036] Specifically, when sending an SMS notification to the consumer terminal 40, the information management server 20 sends the SMS notification to the consumer terminal 40 in units of different numbers (distributor numbers) set for each of multiple services provided by a company (client). When an SMS notification is sent, the distributor number is displayed on the consumer terminal 40 that is the notification destination as a number identifying the sender of the notification (see reference numeral 440 in FIG. 9). The distributor number is, for example, a telephone number.

[0037] The mobile carrier server 30 is a computer device that provides RCS notifications and SMS notifications to the consumer terminal 40. The mobile carrier server 30 is realized, for example, by 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.

[0038] 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 this case, the mobile carrier server 30 sends an RCS notification to the consumer terminal 40, with the official account specified by the request from the information management server 20 as the notification source.

[0039] Furthermore, 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, it sends the SMS notification to the consumer terminal 40. In this case, the mobile carrier server 30 sends an SMS notification to the consumer terminal 40, with the number (distribution source number) specified by the request from the information management server 20 as the notification source.

[0040] 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 determination result as to whether or not the consumer terminal 40 supports RCS.

[0041] 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. Here, the external devices 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.

[0042] The storage unit 42 is configured by a storage medium such as a HDD, flash memory, EEPROM, RAM, or 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 performing the 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.

[0043] The control unit 43 is realized by causing a CPU provided as hardware in the consumer terminal 40 to execute a program. The control unit 43 performs overall control of the consumer terminal 40. For example, the control unit 43 realizes a function related to RCS by causing the CPU to execute an RCS app stored in the storage unit 42. The RCS function here is, for example, a function to receive an RCS notification and display a message notified by the RCS notification based on the received information. In this case, the control unit 43 is an example of an "RCS processing unit."

[0044] Furthermore, the control unit 43 realizes SMS-related functions by causing the CPU to execute an SMS application stored in the storage unit 42. The SMS-related functions here are, for example, functions to receive an SMS notification and display a message notified by the SMS notification based on the received information. In this case, the control unit 43 is an example of an "SMS processing unit."

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

[0046] 2 is a block diagram showing an example of the configuration 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 company server 10, the mobile carrier server 30, and the consumer terminal 40.

[0047] The storage unit 22 is configured by a storage medium such as a HDD, flash memory, EEPROM, RAM, 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, setting information 220.

[0048] The setting information 220 will now be described with reference to Fig. 5 and Fig. 6. Fig. 5 and Fig. 6 are diagrams showing an example of the configuration of the setting information 220 according to the embodiment. The setting information 220 is information that is set when performing an RCS notification or an SMS notification. Fig. 5 shows an example of information (setting information 220A) that is set when performing an RCS notification. Fig. 6 shows an example of information (setting information 220B) that is set when performing an SMS notification.

[0049] As shown in FIG. 5, the setting information 220A includes items such as an account ID, a protocol, an alternative delivery, a source number, and a plurality of delivery recipients (delivery recipient 1, delivery recipient 2, . . . ).

[0050] The account ID is information indicating an official account corresponding to the corporate server 10 that is the notification source, and is information indicating the account that is displayed as the notification source on the consumer terminal 40 that is the notification destination when an RCS notification is sent. The protocol is information indicating the notification method, and in this case, is information indicating whether to send an RCS notification or an SMS notification.

[0051] The alternative delivery is information indicating whether to notify a consumer terminal 40 that does not support the notification method specified in the protocol item using a method other than the notification method specified in the protocol item. In this case, the alternative delivery is used as information indicating whether to notify an SMS notification when RCS is specified in the protocol item and the consumer terminal 40 does not support RCS.

[0052] In this embodiment, to avoid a situation where the alternative delivery function results in a fixed sender number associated with the official account, the alternative delivery item is set to "Do not use alternative delivery." For mobile phones that do not support RCS, SMS notifications are sent without using the alternative delivery function. This allows the sender number displayed on the consumer terminal 40 of the notification destination to be the same as the number that would be displayed if the alternative delivery function were not used.

[0053] Specifically, the information management server 20 requests the mobile carrier server 30 to confirm whether RCS transmission is possible, and identifies mobile phones that do not support RCS based on the result. The information management server 20 requests the mobile carrier server 30 to send an SMS notification to the mobile phones that do not support RCS, with the same sender number set as when an SMS notification is sent without using the alternative delivery function. As a result, a sender number equivalent to the number that would be displayed when the alternative delivery function is not used is displayed on the consumer terminal 40 that is the notification destination.

[0054] The sender number is information indicating the number (sender number) that is displayed on the consumer terminal 40 of the notification destination as the notification source when an SMS notification is sent. The recipient is information regarding the notification destination to which information is sent, and is information that includes at least the mobile phone number that is the destination of the RCS notification or SMS notification. Although omitted in FIGS. 5 and 6, the setting information 220 includes a message. The message here refers to the specific delivery content to be delivered to the consumer terminal 40, and is, for example, the information indicated in the delivery content of the delivery request information 120. The message may also be stored in the mobile carrier server 30.

[0055] 5 shows an example in which "A" is set as the account ID. It also shows that an RCS notification is sent to the destination consumer terminal 40, and that if the destination consumer terminal 40 does not support RCS, an SMS notification is not sent.

[0056] 6, the setting information 220B includes items such as an account ID, a protocol, an alternative delivery, a sender number, and a plurality of delivery recipients (delivery recipient 1, delivery recipient 2, ...). These items shown in Fig. 6 are the same as those shown in Fig. 5, and therefore a description thereof will be omitted.

[0057] 6 shows an example in which the account ID is set to "B." It also shows that an SMS notification is sent to the consumer terminal 40 that is the notification destination, and that "0120-XXXX-XXXX" is set as the sender number when sending the SMS notification.

[0058] 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 feasibility confirmation request unit 230, an RCS distribution request unit 231, and a device control unit 233. The RCS transmission feasibility confirmation request unit 230 is an example of an "RCS transmission feasibility determination request unit."

[0059] The RCS transmission availability confirmation requesting unit 230 requests the mobile carrier server 30 to determine whether the consumer terminal 40 supports RCS. The RCS transmission availability confirmation requesting unit 230 requests the mobile carrier server 30 to determine whether the consumer terminal 40 supports RCS, for example, by transmitting all or part of the setting information 220 (for example, a mobile phone number) to the mobile carrier server 30. The RCS transmission availability confirmation requesting unit 230 acquires the determination result, made by the mobile carrier server 30, as to whether the consumer terminal 40 supports RCS.

[0060] The RCS distribution request unit 231 requests the mobile carrier server 30 to send an RCS notification to the notification destination user terminal 40. The RCS distribution request unit 231 requests the mobile carrier server 30 to send an RCS notification to the user terminal 40, for example, by sending setting information 220 for RCS notification (setting information 220A) to the mobile carrier server 30.

[0061] The SMS delivery request unit 232 requests the mobile carrier server 30 to send an SMS notification to the notification destination user terminal 40. The SMS delivery request unit 232 requests the mobile carrier server 30 to send an SMS notification to the user terminal 40, for example, by sending setting information 220 for SMS notification (setting information 220B) to the mobile carrier server 30.

[0062] 3 is a block diagram showing an example of the 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 enterprise server 10, the information management server 20, and the consumer terminal 40.

[0063] The storage unit 32 is configured by a storage medium such as a HDD, flash memory, EEPROM, RAM, 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 availability confirmation result information 320.

[0064] Here, the RCS transmission availability check result information 320 will be described with reference to Fig. 7. Fig. 7 is a diagram showing an example of the configuration of the RCS transmission availability check result information 320 according to an embodiment. The RCS transmission availability check result information 320 includes, for example, items such as a plurality of recipients of distribution (recipient 1, recipient 2, ...). The recipient of distribution is information indicating whether or not the consumer terminal 40 to which information is to be distributed supports RCS. The recipient of distribution includes a mobile phone number and information indicating whether or not the consumer terminal 40 corresponding to that number supports RCS.

[0065] Returning to the explanation of FIG. 3 , control unit 33 is realized by causing a CPU provided as hardware in mobile carrier server 30 to execute a program. Control unit 33 comprehensively controls mobile carrier server 30. Control unit 33 includes, for example, an RCS transmission feasibility confirmation request receiving unit 330, an RCS delivery request relay unit 331, an SMS delivery request relay unit 332, an RCS transmission feasibility confirmation unit 333, an RCS delivery unit 334, an SMS delivery unit 335, and a device control unit 336. RCS transmission feasibility confirmation request receiving unit 330 is an example of an "RCS transmission feasibility determination request receiving unit." RCS transmission feasibility confirmation unit 333 is an example of an "RCS transmission feasibility determination unit."

[0066] Here, the RCS transmission availability confirmation request receiving unit 330, the RCS delivery request relay unit 331, and the SMS delivery request relay unit 332 (reference numeral 33A) are each an example of a "sorting unit." Also, the RCS transmission availability confirmation unit 333, the RCS delivery unit 334, and the SMS delivery unit 335 (reference numeral 33B) are each an example of a "delivery unit."

[0067] 3 illustrates a case where the "sorting unit" and the "distribution unit" are provided in the mobile carrier server 30, but the present invention is not limited to this. For example, one of the multiple mobile carriers may be configured to have both the "sorting unit" and the "distribution unit," while the remaining mobile carriers may be configured to have only the "distribution unit." Furthermore, the information management server 20 may be configured to have the "sorting unit," and to perform distribution using the "distribution units" provided in each of the multiple mobile carriers.

[0068] The RCS transmission permission confirmation request receiving unit 330 acquires the request from the RCS transmission permission confirmation requesting unit 230 via the communication unit 31 and outputs the acquired information to the RCS transmission permission confirming unit 333 .

[0069] 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.

[0070] 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.

[0071] The RCS transmission feasibility confirmation unit 333 acquires the request from the RCS transmission feasibility confirmation request unit 230 from the RCS transmission feasibility confirmation request reception unit 330. The RCS transmission feasibility confirmation unit 333 determines whether the user terminal 40 supports RCS in response to the acquired request.

[0072] The method by which the RCS transmission availability confirmation unit 333 determines whether the consumer terminal 40 supports RCS may be determined arbitrarily. For example, the RCS transmission availability confirmation unit 333 notifies the mobile phone number of the consumer 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 RCS notification is available. Upon receiving the control signal related to RCS notification, the consumer terminal 40 returns a response to the mobile carrier server 30 as to whether RCS is available, in response to the received control signal. The RCS transmission availability confirmation unit 333 determines whether the consumer terminal 40 supports RCS based on the response from the consumer terminal 40. The RCS transmission availability confirmation unit 333 notifies the information management server 20 of the determination result.

[0073] The RCS distribution unit 334 acquires the request from the RCS distribution request unit 231 from the RCS distribution request relay unit 331. The RCS distribution unit 334 transmits an RCS notification to the consumer terminal 40 in response to the acquired request.

[0074] 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.

[0075] The "distribution unit" may directly acquire a request (a request for an RCS notification or an SMS notification) from the information management server 20. For example, if the mobile carrier server 30 does not include a "distribution unit," or if the information management server 20 does not use the "distribution unit" 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" without going through the "distribution unit."

[0076] 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 consumer 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 consumer terminal 40 in response to the request received from the information management server 20.

[0077] 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 the setting information 220 that the communication unit 31 receives from the information management server 20, and if the information requests confirmation of RCS transmission feasibility, outputs the information to the RCS transmission feasibility confirmation request receiving unit 330.

[0078] If the setting information 220 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. If the setting information 220 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.

[0079] If the setting information 220 received by the communication unit 31 from the information management server 20 requests an RCS notification without going through the RCS delivery request relay unit 331, the device control unit 336 outputs the information to the RCS delivery unit 334. If the setting information 220 received by the communication unit 31 from the information management server 20 requests an SMS notification without going through the SMS delivery request relay unit 332, the device control unit 336 outputs the information to the SMS delivery unit 335.

[0080] FIG. 8 is a diagram illustrating an example of a display on the consumer terminal 40 according to the embodiment. FIG. 8 illustrates an example of an image displayed on the display unit 44 when an RCS notification is sent to the consumer terminal 40. As illustrated in the example of FIG. 8, the display unit 44 displays, for example, information indicating the source of the notification (reference numeral 440), a message M1, and the like. In the example of this figure, an example is shown in which the character string "TF Bank," an official account, is displayed as information indicating the source of the notification. Also illustrated is an example in which a character string beginning with "Message from TF Bank..." is displayed as the message notified to the customer.

[0081] FIG. 9 is a diagram illustrating an example of a display on the consumer terminal 40 according to the embodiment. FIG. 9 illustrates an example of an image displayed on the display unit 44 when an SMS notification is sent to the consumer terminal 40. As illustrated in the example of FIG. 9, the display unit 44 displays, for example, information indicating the notification source (reference numeral 440), a message M1, and the like. In the example of this figure, an example is shown in which the character string "0120-XXXX-XXXX", which is the distribution source number, is displayed as information indicating the notification source. Also, an example is shown in which a character string beginning with "Message from TF Bank..." is displayed as the message notified to the customer.

[0082] FIG. 10 is a sequence diagram showing the flow of processing in the distribution system 1 according to the embodiment.

[0083] First, the company server 10 requests the information management server 20 to perform distribution (step S10). The company server 10 requests the information management server 20 to perform distribution by transmitting distribution request information 120 to the information management server 20.

[0084] The information management server 20 assembles a delivery message in response to a request from the enterprise server 10 (step S11). Specifically, when the information management server 20 receives the setting information 220 from the enterprise server 10, it generates setting information 220A using the received information. The setting information 220A is the setting information 220 that is set when an RCS notification is to be sent to the destination consumer terminal 40. The information management server 20 transmits the generated setting information 220A (referred to as setting information A) to the mobile carrier server 30.

[0085] As a result, the information management server 20 makes a request according to the contents set in the setting information 220A. For example, when the setting information 220A shown in the example of FIG. 5 is transmitted, the information management server 20 requests a determination as to whether or not the consumer terminal 40 of the distribution target notified in the setting information 220A supports RCS. The information management server 20 then requests that information based on the setting information 220A be notified via RCS to the consumer terminal 40 that supports RCS. The information management server 20 also requests that alternative distribution not be made to consumer terminals 40 that do not support RCS. The information management server 20 also requests that the result of determining whether or not the consumer terminal 40 supports RCS be notified.

[0086] The mobile carrier server 30 performs processing according to the setting information 220A received from the information management server 20. For example, when receiving the setting information 220A shown in the example of FIG. 5, the mobile carrier server 30 determines whether the consumer terminal 40 of the distribution target supports RCS (step S12). The mobile carrier server 30 transmits a control signal related to the RCS notification to each consumer terminal 40 of the distribution target notified in the setting information 220A, and receives a response to the control signal from each consumer terminal 40. The mobile carrier server 30 determines whether each consumer terminal 40 supports RCS based on the response received from each consumer terminal 40.

[0087] The mobile carrier server 30 sends an RCS notification to the consumer terminal 40 that supports RCS (step S13). On the other hand, the mobile carrier server 30 does not send an SMS notification to the consumer terminal 40 that does not support RCS.

[0088] The mobile carrier server 30 notifies the information management server 20 of the determination result of whether or not RCS is supported (step S14). The determination result here is the result of determining whether or not each of the consumer terminals 40 of the distribution target persons notified in the setting information 220A supports RCS. Alternatively, the determination result may be information notifying only the consumer terminals 40 that do not support RCS among the consumer terminals 40. The determination result may be information notifying only the consumer terminals 40 that support RCS among the consumer terminals 40. Note that in step S14, the determination result may be obtained from the information management server 20. In this case, for example, the information management server 20 queries the mobile carrier server 30 and obtains the determination result of whether or not the consumer terminal 40 supports RCS.

[0089] The information management server 20 collects logs based on the determination result received from the mobile carrier server 30 (step S15). For example, the information management server 20 stores the determination result received from the mobile carrier server 30 in the storage unit 22.

[0090] The information management server 20 assembles a delivery message based on the determination result received from the mobile carrier server 30 (step S16). Specifically, the information management server 20 extracts, based on the determination result, terminals that do not support RCS from the consumer terminals 40 of the delivery recipients indicated in the setting information 220 received from the company server 10 in step S10. The information management server 20 generates setting information 220B using the extracted information. The setting information 220B is the setting information 220 that is set when an SMS notification is to be sent to the consumer terminal 40 that is the notification destination. The information management server 20 transmits the generated setting information 220B (referred to as setting information B) to the mobile carrier server 30.

[0091] As a result, the information management server 20 makes a request according to the content set in the setting information 220B. For example, when the setting information 220B shown in the example of Fig. 6 is transmitted, the information management server 20 requests the consumer terminal 40 of the distribution target notified in the setting information 220B to send an SMS notification from the number set as the distribution source number.

[0092] The mobile carrier server 30 performs processing according to the setting information 220B received from the information management server 20. For example, when the setting information 220B shown in the example of Fig. 6 is received, the mobile carrier server 30 sends an SMS notification to the consumer terminal 40 of the distribution target person, with the number set as the distribution source number as the sender (step S17).

[0093] As described above, the distribution system 1 according to the embodiment includes the information management server 20, the mobile carrier server 30, and the consumer terminal 40. The information management server 20 is an example of a "distribution request unit." The mobile carrier server 30 is an example of a "distribution unit." The mobile carrier server 30 is an example of a "distribution unit." The consumer terminal 40 is an example of a "user terminal."

[0094] The information management server 20 includes an RCS delivery request unit 231 and an SMS delivery request unit 232. The RCS delivery request unit 231 requests that an RCS notification be sent to the resident terminal 40. The SMS delivery request unit 232 requests that an SMS notification be sent to the resident terminal 40.

[0095] The mobile carrier server 30 includes an RCS delivery request relay unit 331, an SMS delivery request relay unit 332, an RCS delivery unit 334, and an SMS delivery unit 335. The RCS delivery request relay unit 331 outputs information to be transmitted to the consumer terminal 40 based on information acquired from the RCS delivery request unit 231 to the RCS delivery unit 334. The SMS delivery request relay unit 332 outputs information to be transmitted to the consumer terminal 40 based on information acquired from the SMS delivery request unit 232 to the SMS delivery unit 335. The RCS delivery unit 334 transmits an RCS notification to the consumer terminal 40. The SMS delivery unit 335 transmits an SMS notification to the consumer terminal 40.

[0096] The consumer terminal 40 includes a control unit 43. The control unit 43 is an example of an "RCS message processing unit." The control unit 43 is an example of an "SMS processing unit." The control unit 43 receives and displays an RCS notification. The control unit 43 receives and displays an SMS notification.

[0097] The RCS delivery request unit 231 transmits setting information 220A (information related to the request) to the RCS delivery unit 334 via the RCS delivery request relay unit 331, or without the RCS delivery request relay unit 331. The SMS delivery request unit 232 transmits setting information 220B (information related to the request) to the SMS delivery unit 335 via the SMS delivery request relay unit 332, or without the SMS delivery request relay unit 332. The RCS delivery unit 334 transmits an RCS notification to the consumer terminal 40 in response to the setting information 220A (request by the RCS delivery request unit 231). The SMS delivery unit 335 transmits an SMS notification to the consumer terminal 40 in response to the setting information 220B (request by the SMS delivery request unit 232).

[0098] The RCS delivery request unit 231 controls the transmission of RCS notifications for each official company account (at least one account set for each customer who will be the source of the RCS notification). The SMS delivery request unit 232 controls the transmission of SMS notifications for each different delivery source number set for each service provided by the company.

[0099] As a result, in the distribution system 1 of the embodiment, when notifying information to mobile phones that support RCS via RCS and notifying information to mobile phones that do not support RCS via SMS, it is possible to set a sender display number for customers to whom information is to be notified via SMS, similar to that used in conventional SMS distribution.

[0100] Furthermore, in the distribution system 1 according to the embodiment, when an SMS notification is received, the control unit 43 of the consumer terminal 40 displays the sender number. This allows the distribution system 1 according to the embodiment to allow the recipient to recognize the sender number of the SMS notification. Therefore, the recipient can confirm that the received SMS notification is from a specific department of the company from which they usually receive notifications.

[0101] Furthermore, in the distribution system 1 according to the embodiment, the information management server 20 may include an RCS transmission permission confirmation request unit 230, and the mobile carrier server 30 may include an RCS transmission permission confirmation request receiving unit 330 and an RCS transmission permission confirmation unit 333. When it is determined that the consumer terminal 40 does not support RCS, the information management server 20 requests that an SMS notification specifying the distribution source number be sent. This makes it possible in the distribution system 1 according to the embodiment to confirm whether the consumer terminal 40 supports RCS.

[0102] The above describes an embodiment of the present invention. Note that all or part of the functions of the distribution system 1 and the information management server 20 in the above-described embodiment may be implemented by a computer. In this case, a program for implementing these functions may be recorded on a computer-readable recording medium, and the program may be loaded into a computer system and executed. Note that the term "computer system" as used herein includes hardware such as an operating system 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, as well as storage devices such as hard disks built into a computer system. Furthermore, the term "computer-readable recording medium" may also include devices that dynamically store programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or telephone lines, or devices that store programs for a fixed period of time, such as volatile memory within a computer system serving as a server or client. The program may be designed to implement part of the aforementioned functions, or may be capable of implementing the aforementioned functions in combination with a program already stored in the computer system, or may be implemented using a programmable logic device such as an FPGA (Field Programmable Gate Array).

[0103] The embodiments of the present invention have been described in detail above with reference to the drawings, but the specific configuration is not limited to that described above, and various design changes can be made within the scope of the gist of the present invention. [Explanation of symbols]

[0104] 1. Distribution System 10 Corporate Servers 20 Information management server (server device) 230 RCS transmission availability confirmation request part (distribution request part) 231 RCS distribution request part (distribution request part) 232 SMS delivery request part (delivery request part) 30 Mobile carrier server 330 RCS transmission availability confirmation request reception unit (sorting unit) 331 RCS distribution request relay unit (sorting unit) 332 SMS delivery request relay unit (sorting unit) 333 RCS Transmission Confirmation Unit (Distribution Unit) 334 RCS Distribution Department (Distribution Department) 335 SMS Distribution Department (Distribution Department) 40 Consumer terminals (user terminals) 43 Control unit (RCS processing unit) (SMS processing unit)

Claims

1. A distribution system comprising a distribution request unit, a distribution unit, a distribution unit, and a user terminal, the delivery request unit includes an RCS delivery request unit that requests an RCS notification using RCS to be sent to the user terminal, an SMS delivery request unit that requests an SMS notification using SMS to be sent to the user terminal, and an RCS transmission availability determination request unit that requests a determination as to whether or not the user terminal is compatible with RCS based on information related to the RCS notification; the sorting unit includes an RCS delivery request relay unit that outputs information related to the RCS notification to the delivery unit based on information acquired from the RCS delivery request unit, an SMS delivery request relay unit that outputs information related to the SMS notification to the delivery unit based on information acquired from the SMS delivery request unit, and an RCS transmission permission determination request receiving unit that outputs information acquired from the RCS transmission permission determination request unit to the delivery unit, the distribution unit includes an RCS distribution unit that transmits the RCS notification to the user terminal, an SMS distribution unit that transmits the SMS notification to the user terminal, and an RCS transmission availability determination unit that determines whether the user terminal is RCS-compatible based on information related to the RCS notification; the user terminal has at least one of an RCS processing unit that receives and displays the RCS notification and an SMS processing unit that receives and displays the SMS notification; the RCS distribution request unit transmits information related to the RCS notification to the RCS distribution unit via the RCS distribution request relay unit or without via the RCS distribution request relay unit; the SMS delivery request unit transmits information related to the SMS notification to the SMS delivery unit via the SMS delivery request relay unit or without via the SMS delivery request relay unit; the RCS distribution unit transmits the RCS notification to the user terminal in response to a request from the RCS distribution request unit; the SMS delivery unit transmits the SMS notification to the user terminal in response to a request by the SMS delivery request unit; the RCS distribution request unit controls the RCS notification to be transmitted in units of at least one account set for each customer that is a source of the RCS notification; When a response is received from the RCS transmission determination request unit indicating that the user terminal does not support RCS in response to a request from the RCS transmission determination request unit, the SMS delivery request unit controls the SMS notification to be sent in units of a delivery source number that identifies a notification source for each service provided by the customer, so that the SMS notification is sent to the user terminal that does not support RCS with the same delivery source number set as in the case of sending the SMS notification without using an alternative delivery function. Delivery system.

2. The SMS processing unit of the user terminal displays the sender number. The distribution system according to claim 1 .

3. an RCS distribution request unit that requests that an RCS notification using the RCS be transmitted to a user terminal; an SMS delivery request unit that requests that an SMS notification be sent to the user terminal using SMS; an RCS transmission permission determination request unit that requests a determination as to whether the user terminal supports RCS based on information related to the RCS notification; and the RCS distribution request unit controls the RCS notification to be transmitted in units of at least one account set for each customer that is a source of the RCS notification; When a response is received from the RCS transmission determination request unit indicating that the user terminal does not support RCS in response to a request from the RCS transmission determination request unit, the SMS delivery request unit controls the SMS notification to be sent in units of a delivery source number that identifies a notification source for each service provided by the customer, so that the SMS notification is sent to the user terminal that does not support RCS with the same delivery source number set as in the case of sending the SMS notification without using an alternative delivery function. Server device.

4. 1. A computer-implemented distribution method comprising: The RCS distribution request unit requests the user terminal to transmit an RCS notification using the RCS, an SMS delivery request unit requests that an SMS notification be sent to the user terminal using SMS; an RCS transmission permission determination request unit requests that the user terminal determine whether or not it supports RCS based on information related to the RCS notification; the RCS distribution request unit controls the RCS notification to be transmitted in units of at least one account set for each customer that is a source of the RCS notification; When a response is received from the RCS transmission determination request unit indicating that the user terminal does not support RCS in response to a request from the RCS transmission determination request unit, the SMS delivery request unit controls the SMS notification to be sent in units of a delivery source number that identifies a notification source for each service provided by the customer, so that the SMS notification is sent to the user terminal that does not support RCS with the same delivery source number set as in the case of sending the SMS notification without using an alternative delivery function. Delivery method.

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

Images