JP7651969B2 - Distribution system, server device, distribution method, and program - Google Patents

Description

The present invention relates to a distribution system, a server device, a distribution method, and a program.

Electronic notification services that notify information online are now 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.

Among these electronic notification services, messaging services that use mobile phone numbers as the destination are the most popular. This is because using a mobile phone number as the destination makes it possible to send a message even if the recipient's email address is unknown, making it highly convenient.

An example of a messaging service that uses a mobile phone number as the destination is RCS (Rich Communication Services). 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, making it possible to exchange messages even between different communication carriers.

RCS also allows companies to create official accounts. If users want to receive information distributed by a company, they follow that company's official account. A list of user devices that follow a company's official account is registered in the mobile carrier's (cell phone operator's) registrant list (also called a subscriber list). Companies can obtain the registrant list from the mobile carrier and use it to distribute information introducing new products, etc.

JP 2007-241732 A

However, the subscriber list only contains mobile phone numbers to which information is to be distributed. The subscriber list does not contain any other information than mobile phone numbers. For this reason, it is not possible to know whether a person on the subscriber list is already registered as a customer of the company or is a new customer. For this reason, although companies can use the subscriber list to distribute uniform information, it is difficult to distribute information tailored to individual users.

In view of the above-mentioned problems, the object of the present invention is to provide a distribution system, a server device, a distribution method, and a program that can distribute information tailored to individual users based on a list of registered users.

In order to solve the above-mentioned problems, a distribution system according to one aspect of the present invention includes a registration list acquisition unit that acquires a registration list provided by a mobile carrier server, which is a list of mobile phone numbers registered as recipients of information sent from a company; a distribution unit that transmits a request message to the mobile phone numbers shown in the registration list, requesting that personal information of a user corresponding to the mobile phone number, which is personal information related to the company, and personal identification information that can identify the user, be notified; and a confirmation unit that generates customer information based on a response to the request message, in which the personal information and personal identification information of the user included in the response are associated with the mobile phone number, and confirms the customer information by matching the generated customer information with the customer master information of the company.

The server device according to one aspect of the present invention includes a registration list acquisition unit that acquires a registration list provided by a mobile carrier server, the registration list indicating a list of mobile phone numbers registered as recipients of information sent from a company; a delivery request unit that requests the mobile carrier server to transmit a request message to a mobile phone number indicated in the registration list, the request message requesting notification of personal information of a user corresponding to the mobile phone number, the personal information being related to the company, and personal identification information that can identify the user; and a confirmation unit that generates customer information based on a response to the request message, in which the personal information and personal identification information of the user included in the response are associated with the mobile phone number, and confirms the customer information by matching the generated customer information with customer master information of the company.

In addition, a distribution method according to one aspect of the present invention is a distribution method executed by a computer, in which a registrant list acquisition unit acquires a registrant list provided by a mobile carrier server, which is indicative of a list of mobile phone numbers registered as recipients of information sent from a company, a distribution unit transmits a request message to the mobile phone numbers indicated in the registrant list, requesting that the mobile phone numbers be notified of personal information of a user corresponding to the mobile phone number, which is personal information related to the company, and personal identification information by which the user can be identified, and a confirmation unit generates customer information in which the personal information and personal identification information of the user included in the response are associated with the mobile phone number based on a response to the request message, and confirms the customer information by matching the generated customer information with the customer master information of the company.

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.

According to the present invention, it is possible to deliver information tailored to individual users using a subscriber list.

1 is a block diagram showing an example of a configuration of a distribution system 1 according to an embodiment. FIG. 2 is a block diagram showing an example of the configuration of an information management server 20 according to the embodiment. FIG. 2 is a block diagram showing a configuration example of a mobile carrier server 30 according to the embodiment. FIG. 2 is a diagram illustrating an example of a configuration of customer master information 120 according to the embodiment. FIG. 2 is a diagram showing an example of the configuration of registrant list information 220 (320) according to the embodiment. FIG. 2 is a diagram showing an example of the configuration of customer information 221 according to the embodiment. FIG. 2 is a diagram illustrating a display example of a resident terminal 40 according to an embodiment. FIG. 2 is a diagram illustrating a display example of a resident terminal 40 according to an embodiment. FIG. 2 is a diagram illustrating a display example of a resident terminal 40 according to an embodiment. 2 is a sequence diagram showing a processing flow in the distribution system 1 according to the embodiment. FIG.

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

The corporate server 10 is a terminal device of a company that requests information distribution from the information management server 20. The corporate server 10 is realized by a computer device such as a server device, a cloud device, or a PC (Personal Computer).

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

The mobile carrier server 30 is a computer device that distributes information in response to a request from the information management server 20. The mobile carrier server 30 is realized, for example, by a cloud device, a server device, a PC, etc. The mobile carrier server 30 is a server device of a communication carrier (mobile phone operator) that provides an RCS message service, and sends notifications using the RCS message service (hereinafter referred to as RCS notifications) to the consumer terminal 40.

The consumer terminal 40 is a computer device that receives information delivered from companies. The consumer terminal 40 is realized, for example, by a smartphone, a tablet terminal, a mobile phone, etc.

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 or multiple consumer terminals 40.

In the example of FIG. 1, a single mobile carrier server 30 is provided in the distribution system 1, but this is not limiting. The distribution system 1 may be configured such that a mobile carrier server 30 for each of multiple mobile carriers is provided.

In this embodiment, information is distributed to the consumer terminal 40 using the company's official RCS account. The official RCS account is an official RCS account set up by a communications carrier (mobile phone operator) that provides the RCS message service.

For example, a company that wants to disseminate information publishes an official RCS account on the RCS message service. Users of the RCS message service (hereinafter simply referred to as "users") follow the desired official RCS account using their consumer terminal 40.

When a user follows the RCS official account using their consumer terminal 40, the mobile phone number of the consumer terminal 40 is notified to the mobile carrier server 30. The mobile carrier server 30 uses the notified mobile phone number to create a registrant list. The information management server 20 obtains the registrant list from the mobile carrier server 30, for example, periodically. The information management server 20 ensures that information from companies is delivered to the mobile phone numbers listed on the registrant list.

As mentioned above, the registration list contains only mobile phone numbers. For this reason, it is not possible to identify individuals from the registration list. While some users only want to receive information that is uniformly notified from companies, there are also users who want to receive individual information. If individual information could be notified to users who want to receive it, it would be more convenient for users and would also be advantageous for companies.

From this perspective, in this embodiment, the company is able to send individual information to users who wish to do so. Specifically, the information management server 20 acquires personal information (such as company account information) from the user who wishes to do so, and is able to identify the individual based on the acquired personal information. In this case, the information management server 20 may acquire identity verification information from the user along with the personal information, and be able to perform identity verification on the acquired personal information. This can increase the reliability of the personal information acquired from the user.

The information management server 20 then confirms the personal information acquired from the user by matching it with the company's customer master information. In this case, the information management server 20 may send the user's personal information to the company server 10, which may then match it with the customer master information. This allows the company to send individual information to the user. The specific process by which the information management server 20 confirms the personal information acquired from the user will be explained in detail later.

As shown in FIG. 1, the enterprise server 10 includes, for example, a communication unit 11, a memory 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 communication unit 11 communicates only with the information management server 20.

The memory unit 12 is configured with a storage medium such as a hard disk drive (HDD), flash memory, electrically erasable programmable read only memory (EEPROM), random access read/write memory (RAM), read only memory (ROM), or a combination of these. The memory unit 12 stores programs for executing various processes of the corporate server 10, and temporary data used when performing various processes. The memory unit 12 stores, for example, customer master information 120. The customer master information 120 is information related to customers in the company.

The customer master information 120 will now be described with reference to FIG. 4. FIG. 4 is a diagram showing an example of the configuration of the customer master information 120 according to an embodiment. As shown in FIG. 4, the customer master information 120 includes items such as a customer ID, name, address, account number, and personal identification information. The customer ID is identification information such as a number that uniquely identifies a customer. The name and address are the name and address of the customer identified by the customer ID.

The account number is the account number of the customer identified by the customer ID. Here, we assume that a company issues account numbers in response to requests from customers, and show an example in which the customer's account number is stored in the customer master information 120. The personal identification information is information used to verify the customer's identity when creating an account number, for example, such as a copy of a driver's license.

Returning to the explanation of FIG. 1, the control unit 13 is realized by having a CPU (Central Processing Unit) that the enterprise server 10 has as hardware execute a program. The control unit 13 comprehensively controls the enterprise server 10. The control unit 13 transmits, for example, customer master information 120 to the information management server 20 via the communication unit 11.

The consumer terminal 40 also includes, for example, a communication unit 41, a memory 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.

The storage unit 42 is configured with a storage medium such as a HDD, flash memory, EEPROM, RAM, 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 various processes. The storage unit 42 stores, for example, an application program related to the RCS (RCS app).

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 memory unit 42. The RCS-related 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.

The display unit 44 includes a display device such as a liquid crystal display, and displays images of messages and other information notified by RCS notification in accordance with the control of the control unit 43.

FIG. 2 is a block diagram showing an example of the configuration of the information management server 20 according to an 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, the mobile carrier server 30, and the consumer terminal 40.

The storage unit 22 is configured with 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, registrant list information 220 and customer information 221.

FIG. 5 is a diagram showing an example of the configuration of registrant list information 220 according to an embodiment. Registrant list information 220 is information showing a list of registrants. Registrant list information 220 includes items such as an official account and multiple registrants (registrant 1, registrant 2, ...). An official account is information showing which company's official RCS account it is. For a registrant, the mobile phone number of a consumer terminal 40 that follows the official account is shown.

FIG. 6 is a diagram showing an example of the configuration of customer information 221 according to an embodiment. It is personal information of a user who wishes to receive individual information, not uniform, from a company. The customer information 221 includes items such as an official account and multiple registrants (registrant 1, registrant 2, etc.). The official account is information indicating which company's official RCS account it is. The registrants show personal information of users who follow the official account.

The registrant column of customer information 221 shown in FIG. 6 includes, for example, items of registrant list information and confirmed information. The registrant list information indicates the mobile phone number of the user listed on the registrant list and the date of registration. The date of registration is the date on which the user was registered on the registrant list, or the date on which the information management server 20 obtained the registrant list. The confirmed information includes items such as the user's name, mobile phone number, address, account number, and identity verification information. This confirmed information is personal information of the user that is notified by the user and then confirmed by matching it with the company's customer master information 120.

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, a registrant list acquisition unit 230, a distribution request unit 231, a determination unit 232, and a device control unit 233.

The registrant list acquisition unit 230 acquires the registrant list from the mobile carrier server 30. The registrant list acquisition unit 230 may acquire the registrant list periodically, or if the timing when a mobile phone number was added to the registrant list is known, may acquire the registrant list at that timing. The registrant list acquisition unit 230 stores the acquired registrant list in the memory unit 12 as registrant list information 220.

In this case, the registrant list acquisition unit 230 may not store a mobile phone number that has already been acquired in the past in the registrant list information 220. Specifically, if a specific condition is satisfied for a user of a mobile phone number previously acquired from the registrant list, the registrant list acquisition unit 230 may not store the mobile phone number in the registrant list information 220. The specific condition may be, for example, when the registrant list information 220 or customer information 221 for that user has already been generated.

The delivery request unit 231 transmits a request message to the consumer terminal 40 based on the registrant list information 220. The request message is a message that requests notification of the user's personal information when the user wishes to receive individual information, rather than uniform information, from the company.

Figures 7 to 9 are diagrams showing examples of request messages displayed on the consumer terminal 40. The request message is posted to the chat room of the official RCS account, for example.

Figure 7 shows an example of a question message. The question message is a message that asks the user whether or not they wish to receive individual, rather than uniform, information from the company. The question message is an example of a "request message." In the question message, for example, selection buttons B1 to B3 are displayed along with a notification text. The notification text is a sentence such as "Please follow TF Bank...so we can verify your account."

The notification states that if the user wishes to receive individual, non-uniform information from the company, they should confirm their account. In this case, the account refers to personal information about the user that is related to the company. For example, if the company issues account numbers to customers, the account is the user's account number.

Selection buttons B1 to B3 are buttons that are selected according to the user's wishes. If the user wishes to receive individual information, rather than uniform information, from companies, the user selects selection button B1. When selection button B1 is selected, a message is sent to the information management server 20 via the mobile carrier server 30 requesting that the account be confirmed. This allows the information management server 20 to understand that the user wishes to receive individual information from companies.

If the user does not have an account (e.g., an account number), the user selects selection button B2. When selection button B2 is selected, the site for creating an account transitions to, for example, an account opening site provided by a company.

If the user does not wish to confirm the account, the user selects selection button B3. When selection button B3 is selected, the information management server 20 is notified that the account will not be confirmed. This allows the information management server 20 to understand that the user does not wish to receive individual information from companies.

When the selection button B1 is selected in response to the question message and a response is made to confirm the account, the delivery request unit 231 notifies the account confirmation message. The account confirmation message is a message for confirming the account and is an example of a "request message."

Figure 8 shows an example of an account confirmation message. The account confirmation message includes a notification message requesting the user to provide personal information, such as "Confirm your account...please confirm your account number."

The user responds to the account confirmation message. Specifically, the user enters the account number into the message input field in the chat room and sends the message. This causes the user's account number to be notified to the information management server 20 via the mobile carrier server 30.

When the user's account number is notified in response to the account confirmation message, the delivery request unit 231 notifies an identity confirmation message. The identity confirmation message is a message for verifying the identity of the user who notified the account number, and is an example of a "request message."

Figure 9 shows an example of an identity verification message. In the identity verification message, for example, a notification text is displayed along with selection buttons B1 to B3. The notification text conveys that identity verification will be performed, such as "We will be conducting identity verification...please select an option."

Selection buttons B1 to B3 are buttons that are selected according to the method of identity verification desired by the user. If the user desires official personal authentication, the user selects selection button B1. When selection button B1 is selected, official personal authentication is performed. In this case, the user can verify their identity by, for example, touching their My Number card to the screen, following the instructions on the screen. The results of the identity verification are then notified to the information management server 20. This allows the information management server 20 to obtain the user's identity verification information.

If the user wishes to be authenticated by the mobile carrier, the user selects selection button B2. When selection button B2 is selected, the user is redirected to a site for mobile carrier authentication, for example, a site for mobile carrier authentication provided by a mobile phone operator. In this case, the user can verify their identity by following the instructions on the screen and entering the PIN number registered when signing up for the mobile phone. The result of the identity verification is then notified to information management server 20. This allows information management server 20 to obtain the user's identity verification information.

If the user desires other authentication (in this example, it is written as "XX authentication"), the user selects the selection button B3. The other authentication may be any method. The other authentication is, for example, a method of performing online identity verification by notifying an image of the user's face or an image of the user's driver's license. When the selection button B3 is selected, other authentication is performed. In this case, the user can perform identity verification by taking an image and sending the captured image following the instructions on the screen. The result of the identity verification is then notified to the information management server 20. This allows the information management server 20 to obtain the user's identity verification information.

The delivery request unit 231 outputs the personal information (account number) and identity verification information notified by the user to the confirmation unit 232.

Returning to the explanation of FIG. 2, the confirmation unit 232 confirms the personal information (account number) and identity verification information of the user acquired from the distribution request unit 231. For example, the confirmation unit 232 notifies the enterprise server 10 of the acquired information and inquires whether it matches the customer master information 120 of the enterprise server 10. The enterprise server 10, for example, determines whether the notified information matches the customer master information 120 by comparing the notified information with the customer master information 120. The enterprise server 10 notifies the information management server 20 of the determination result. When the confirmation unit 232 receives a response from the enterprise server 10 indicating that the information matches the customer master information 120, it confirms the personal information (account number) and identity verification information of the user. The confirmation unit 232 stores the confirmed information as confirmed information of the customer information 221.

On the other hand, if the confirmation unit 232 receives a response from the enterprise server 10 indicating that the information does not match the customer master information 120, the confirmation unit 232 does not confirm the user's personal information (account number) and identity verification information. Specifically, the confirmation unit 232 does not store the user's personal information (account number) and identity verification information as confirmed information in the customer information 221. In this case, the confirmation unit 232 may notify the consumer terminal 40 of the user that the user's personal information (account number) and identity verification information could not be confirmed.

The method of making an inquiry to the enterprise server 10 may be arbitrary. For example, the information management server 20 may temporarily receive the customer master information 120 from the enterprise server 10 and perform a comparison at the information management server 20.

The device control unit 233 performs overall control of the information management server 20. For example, the device control unit 233 outputs the registrant list received by the communication unit 21 to the registrant list acquisition unit 230. The device control unit 233 outputs a response to the request message received by the communication unit 21 to the delivery request unit 231.

FIG. 3 is a block diagram showing an example of the configuration of the mobile carrier server 30 according to an 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.

The memory unit 32 is configured with a storage medium such as a HDD, flash memory, EEPROM, RAM, ROM, or a combination of these. The memory unit 32 stores programs for executing various processes of the mobile carrier server 30, and temporary data used when performing various processes. The memory unit 32 stores, for example, registrant list information 320. The registrant list information 320 is similar to the registrant list information 220, so a description thereof will be omitted.

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 acquisition unit 330, a registrant list generation unit 331, a distribution unit 332, and a device control unit 333.

The acquisition unit 330 acquires notifications from the consumer terminals 40 of users who follow the official account. The acquisition unit 330 outputs the acquired mobile phone numbers of the consumer terminals 40 to the registered user list generation unit 331.

The registrant list generation unit 331 acquires the mobile phone numbers of the consumer terminals 40 of the users who follow the official account from the acquisition unit 330, and generates a registrant list that lists the acquired mobile phone numbers. The registrant list generation unit 331 stores the generated registrant list in the memory unit 32 as the registrant list acquisition unit 230.

The acquisition unit 330 also acquires an RCS notification requested from the information management server 20. The acquisition unit 330 outputs the acquired request to the distribution unit 332.

The distribution unit 332 performs RCS notification. In response to a request acquired from the acquisition unit 330, the distribution unit 332 RCS-notifies the consumer terminal 40 of uniform or individual information from the company.

The device control unit 333 performs overall control of the mobile carrier server 30. For example, the device control unit 333 outputs to the acquisition unit 330 a notification that an official account has been followed, which the communication unit 31 receives from the consumer terminal 40. For example, the device control unit 333 outputs to the acquisition unit 330 a request for an RCS notification, which the communication unit 31 receives from the information management server 20.

Figure 10 is a flowchart showing the processing flow in the distribution system 1 according to the embodiment.

The enterprise server 10 stores customer master information 120 in advance (step S10). The consumer terminal 40 follows the official account (step S11). As a result, the consumer terminal 40 notifies the mobile carrier server 30 that the official account has been followed.

The mobile carrier server 30 updates the list of registered users (step S12). The mobile carrier server 30 updates the list of registered users by adding the mobile phone number of the consumer terminal 40 that notified the consumer that it is following the official account to the list of registered users.

The information management server 20 acquires the registrant list (step S13). The information management server 20 acquires the registrant list by requesting the registrant list from the mobile carrier server 30. The information management server 20 may update the registrant list by requesting the registrant list from the mobile carrier server 30 on a regular or irregular basis (step S14). The information management server 20 sends a request message to the mobile phone numbers listed in the registrant list (step S15).

The consumer terminal 40 receives the request message (step S16). The consumer terminal 40 responds according to the user's wishes (step S17). For example, if the user does not wish to confirm the account, the process ends. If the user wishes to confirm the account, the consumer terminal 40 notifies the information management server 20 of the user's account (account number) via the mobile carrier server 30 (step S18). In this case, the consumer terminal 40 may notify the information management server 20 of the user's identity verification information.

The information management server 20 receives the user's account (account number) and the like from the consumer terminal 40 (step S19). The information management server 20 transmits the received information to the enterprise server 10 and compares it with the customer master information 120 (step S20). Alternatively, in step S20, the information management server 20 may receive the customer master information 120 from the enterprise server 10 in advance and compare the received customer master information 120 with the user's account (account number) and the like. The information management server 20 updates the customer information 221 based on the result of the comparison with the customer master information 120 (step S21). Specifically, when the user's account (account number) and the like match the customer master information 120, the information management server 20 stores the user's account (account number) and the like as confirmed information of the customer information 221.

The information management server 20 may also send a response (message) to the consumer terminal 40 (step S22). The response here is, for example, a response indicating whether the user's account (account number) etc. received from the consumer terminal 40 matches the customer master information 120. Alternatively, the response here is a response indicating that the company will notify the user of individual information, not uniform information, in the future. The consumer terminal 40 receives the response (message) from the information management server 20 via the mobile carrier server 30 (step S23).

As described above, the distribution system 1 according to the embodiment includes a registrant list acquisition unit 230, a distribution unit 332, and a confirmation unit 232. The registrant list acquisition unit 230 acquires a registrant list. The registrant list is a list of mobile phone numbers that follow an official account. Following an official account is an example of "being registered as a person who wishes to receive information provided by a mobile carrier server 30 and sent from a company." The distribution unit 332 transmits a request message. The request message is a message addressed to a mobile phone number shown in the registrant list, requesting that the account and identity verification information be notified. The account is an example of "personal information of a user corresponding to a mobile phone number, which is related to a company." The confirmation unit 232 confirms the customer information 221. The customer information 221 is information in which an account included in a response to the request message is associated with a mobile phone number. The confirmation unit 232 confirms the customer information 221 by matching the account with the customer master information 120.

As a result, the distribution system 1 according to the embodiment can use the registrant list to distribute information tailored to individual customers (users). This is because the user's personal information can be acquired as a response to the request message, and if that information matches the customer master information 120, it can be determined whether the user who follows the official account is one of the company's customers. Once the individual can be determined, it is possible to distribute information tailored to the individual customer (user).

In addition, in the distribution system 1 according to the embodiment, the list of registered users is a list showing the mobile phone numbers of users who follow the official account of the RCS of the company. This allows the distribution system 1 according to the embodiment to easily obtain the phone numbers of the mobile phones that follow the official account by making a request to the mobile carrier server 30.

In addition, in the distribution system 1 according to the embodiment, the request message requests that the account and identity verification information be notified if the customer (user) wishes to receive information sent individually from the company to the customer. In addition, in the distribution system 1 according to the embodiment, to a customer (user) whose customer information 221 has been confirmed by the confirmation unit 232, information sent individually from the company to the customer (user) using the confirmed customer information 221 is sent. On the other hand, to a user whose customer information 221 has not been confirmed by the confirmation unit 232, information sent uniformly from the company to unspecified users (users) using the registrant list information 220 is sent. This makes it possible to meet both the wishes of customers who wish to receive individual information and the wishes of users who do not wish to receive individual information, thereby improving convenience.

The above describes an embodiment of the present invention. The functions of the distribution system 1 and the information management server 20 in the above 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. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. 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. The term "computer-readable recording medium" may also include a medium that dynamically holds a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, and a medium that holds 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. The above program may be a program for realizing a part of the functions described above, or may be a program that can realize the functions described above in combination with a program already recorded in the computer system, or may be a program that is realized using a programmable logic device such as an FPGA (Field Programmable Gate Array).

The above describes in detail the embodiments of the present invention with reference to the drawings, but the specific configuration is not limited to the above, and various design changes can be made without departing from the spirit of the present invention.

1 Distribution system 10 Corporate server 20 Information management server (server device)
230 Registered person list acquisition unit 231 Distribution request unit 232 Confirmation unit 30 Mobile carrier server 330 Acquisition unit 331 Registered person list generation unit 332 Distribution unit 333 Device control unit 40 Consumer terminal (customer terminal)

Claims (7)

a subscriber list acquisition unit that acquires a subscriber list provided by a mobile carrier server, the subscriber list indicating a list of mobile phone numbers registered as recipients of information sent by a company;
a distribution unit that transmits a request message to a mobile phone number shown in the registrant list, requesting that the mobile phone number be notified of personal information of the user corresponding to the mobile phone number, which is related to the company, and personal identification information that can identify the user;
a confirmation unit that generates customer information in which the personal information and identity verification information of the user included in a response to the request message are associated with the mobile phone number, and confirms the customer information by matching the generated customer information with customer master information of the company;
A distribution system comprising: The list of registered users is a list showing mobile phone numbers of users who follow the official account of the RCS of the company.
The distribution system according to claim 1 . the request message is a message requesting the user to notify the company of the personal information and the identity verification information when the user wishes to receive information individually sent to the user from the company;
3. A distribution system according to claim 1 or 2. For a user whose customer information has been confirmed by the confirmation unit, information that is individually sent from the company to the user is transmitted using the confirmed customer information, and for a user whose customer information has not been confirmed by the confirmation unit, information that is uniformly sent from the company to unspecified users is transmitted using the registrant list.
The distribution system according to any one of claims 1 to 3. a subscriber list acquisition unit that acquires a subscriber list provided by a mobile carrier server, the subscriber list indicating a list of mobile phone numbers registered as recipients of information sent by a company;
a delivery request unit that requests the mobile carrier server to transmit a request message to a mobile phone number shown in the registrant list, the request message requesting notification of personal information of a user corresponding to the mobile phone number, which is related to the company, and personal identification information that can identify the user;
a confirmation unit that generates customer information in which the personal information and identity verification information of the user included in a response to the request message are associated with the mobile phone number, and confirms the customer information by matching the generated customer information with customer master information of the company;
A server device comprising: 1. A computer-implemented distribution method, comprising:
A subscriber list acquisition unit acquires a subscriber list provided by a mobile carrier server, the subscriber list indicating a list of mobile phone numbers registered as recipients of information sent by the company,
A distribution unit transmits a request message to a mobile phone number shown in the registrant list, requesting notification of personal information of a user corresponding to the mobile phone number, which is related to the company, and identity verification information that can verify the identity of the user;
a determination unit generates customer information in which the personal information and identity verification information of the user included in the response to the request message are associated with the mobile phone number, and determines the customer information by matching the generated customer information with customer master information of the company;
Delivery method. A program for operating a computer as the server device according to claim 5, the program causing the computer to function as each unit of the server device.

Images