Storage medium, transmission support device, and transmission support method

Abstract

Disclosed is a non-transitory computer-readable storage medium storing a transmission support program, a transmission support apparatus, and a transmission support method. The transmission support program causes at least one computer to execute processing including: generating a management identifier of a message in response to reception of the message; returning the management identifier to a transmission source of the message; when receiving, from each of a plurality of companies holding information on attributes of individuals, a list of personal identifiers of individuals having the attributes in accordance with a condition related to the attributes and the management identifier, specifying, based on reception of the condition from the transmission source and the management identifier, a personal identifier that is repeated between the lists having the common management identifier; and transmitting the specified personal identifier and the received message.

Description

Technical Field

[0001] The implementation methods discussed in this article relate to storage media, transmission support devices, and transmission support methods. Background Technology

[0002] Techniques for extracting users who meet conditions consisting of multiple user attributes, such as "(age = 30 years old) and (gender = male) and (current location = Akihabara)," are known. Furthermore, techniques for distributing advertisements based on user attributes while protecting personal information are also known.

[0003] International Patent No. WO 2011 / 105008 and Japanese Patent No. 2003-115011 are disclosed as related technologies. Summary of the Invention

[0004] [Technical Issues]

[0005] However, it is rare for a single company to hold all user attributes involved in distributing messages containing advertisements. For example, some companies hold date of birth and place of residence as user attributes but not gender, while others hold gender but not date of birth and place of residence. In such cases, it is difficult to distribute messages based on user attributes held by one company, according to user attributes that meet the three specified conditions of date of birth, place of residence, and gender.

[0006] For example, it's conceivable to provide user attributes held by different companies to another company, and to distribute messages based on those user attributes. However, in this scenario, the other company would hold a large number of user attributes, which is undesirable from a personal information protection perspective.

[0007] Therefore, in one aspect, the aim is to provide sending support programs and sending support devices that support sending messages to individuals with attributes according to specified conditions without providing information about the attributes of the individuals held by different companies to another company.

[0008] [Problem Solution]

[0009] According to one aspect of the embodiments, a non-transitory computer-readable storage medium is provided for storing a transmission support program that causes at least one computer to perform processing, the processing including: generating a management identifier for a message in response to receiving a message; returning the management identifier to the sender of the message; when receiving a list of personal identifiers and management identifiers of individuals having the attribute according to conditions associated with the attribute from each of a plurality of companies holding information about individual attributes, specifying a personal identifier that is repeated among the list of common management identifiers based on the conditions and management identifiers received from the sender; and transmitting the specified personal identifier and the received message.

[0010] [Beneficial effects of the invention]

[0011] It can support sending messages to individuals with attributes according to specified conditions without providing information about the individual's attributes held by different companies to another company. Attached Figure Description

[0012] Figure 1 This is an example of sending support systems;

[0013] Figure 2 This is an example of the hardware configuration for controlling the device;

[0014] Figure 3 This is an example of the functional configuration of the control device;

[0015] Figure 4 This is an example of the configuration for sending proxy server functions;

[0016] Figure 5 This is an example of a table storage unit;

[0017] Figure 6 This is an example of the functional configuration of the first database (DB) server and the second DB server;

[0018] Figure 7A This is an example of the DB attribute of the first DB server; Figure 7B This is an example of a list of attribute names stored in the first DB server;

[0019] Figure 8A This is an example of the DB attribute of the second DB server; Figure 8B This is an example of a list of attribute names stored in the second DB server;

[0020] Figure 9 This is an example of the functional configuration of the destination resolution server;

[0021] Figure 10 This is an example of a destination database;

[0022] Figure 11 This is a flowchart illustrating an example of the first transmission support process performed by the first transmission support procedure;

[0023] Figure 12 This is a flowchart illustrating an example of the second transmission support processing performed by the second transmission support procedure;

[0024] Figure 13 This is a flowchart illustrating an example of the destination determination process performed by the destination determination procedure;

[0025] Figure 14 This is a flowchart illustrating an example of destination resolution processing performed by the destination resolver; and

[0026] Figure 15 This is a diagram illustrating an example of sending a support system ST. Detailed Implementation

[0027] In the following description, the mode for performing this embodiment will be described with reference to the accompanying drawings.

[0028] (First Implementation)

[0029] First, refer to Figure 1 The transmission support system ST is described. The transmission support system ST includes a message sending terminal 10 and a transmission proxy server 200, a first database (DB) server 300, a second DB server 400, and a destination resolution server 500, which act as server devices. The mobile information terminal 20 may or may not be included in the transmission support system ST. Although in Figure 1 The illustration shows a smartphone as an example of mobile information terminal 20, but mobile information terminal 20 is not limited to smartphones, and may also be a mobile phone, tablet terminal, laptop personal computer (PC), etc.

[0030] The message sending terminal 10 includes an input device 18, a display device 19, and a control device 100. The input device 18 and the display device 19 are connected to the control device 100. Additionally, a sending proxy server 200, a first database server 300, a second database server 400, a destination resolution server 500, and a mobile base station BS are connected to the control device 100 via a communication network NW. The communication network NW includes at least one of a local area network (LAN) and the Internet. Note that the LAN and the Internet only need to include at least one of wired and wireless communication.

[0031] When a message requester X1 operates on input device 18 to input a message and specified conditions related to the attributes of the individual (hereinafter referred to as user) X2 to whom the message is to be sent, control device 100 receives the message and specified conditions. Upon receiving the message and specified conditions, control device 100 either sends the message to sending proxy server 200 or stops sending the message based on the execution result of various processes described later. When message sending is stopped, control device 100 notifies display device 19 of a sending error. In this way, control device 100 is associated with a sending support device that supports message sending.

[0032] The sending proxy server 200 is managed by a proxy company that acts as an agent for sending messages. The proxy company is an example of a first company. When a message is received, the sending proxy server 200 generates a management identifier (ID) for the message and returns the generated management ID to the control device 100. The management ID is an identifier used to manage messages. The sending proxy server 200 manages the associated management IDs, messages, and information related to the message sender.

[0033] Although details will be described later, the sending proxy server 200 receives a management ID and a list of user IDs (hereinafter referred to as the user list) with attributes of user X2 according to specified conditions from the first DB server 300. Similarly, the sending proxy server 200 also receives a management ID and the user list from the second DB server 400. Upon receiving the user list and management ID, the sending proxy server 200 specifies the user IDs that are repeated among the user IDs in the user list with a common management ID. Once the user IDs have been specified, the sending proxy server 200 sends the specified user IDs and the received message to the telecommunications company. More specifically, the sending proxy server 200 sends a destination list including the specified user IDs and the received message to the destination resolution server 500. In this way, the sending proxy server 200 is also associated with the sending support equipment that supports message sending.

[0034] The first database server 300 is managed by, for example, a broadcasting company that provides broadcasting services to user X2. The broadcasting company is an example of a second company. Note that the first database server 300 is not limited to a broadcasting company, and could also be, for example, an electricity company, etc. The first database server 300 stores information about the user's attributes. For example, the first database server 300 stores information about the user's residential address and date of birth as attributes of user X2. Because the first database server 300 stores this information, it can determine the user X2's place of residence and age.

[0035] Upon receiving specified conditions and a management ID from control device 100, the first DB server 300 sends the management ID and a list of users with user IDs of user X2 according to the specified conditions to the agent company. More specifically, the first DB server 300 sends the user list and management ID to the sending agent server 200. This allows the sending agent server 200 to receive the user list and management ID from the first DB server 300.

[0036] The second DB server 400 is managed by, for example, a water company that provides water service to user X2. The water company is also an example of a second company. Note that the second DB server 400 is not limited to a water company; it could also be an electricity company, etc., as long as the second DB server 400 is different from the broadcasting company. That is, the first DB server 300 and the second DB server 400 only need to be managed by different companies. The second DB server 400 also stores information about the user's attributes. For example, the second DB server 400 stores information about the user's gender and hobbies / preferences as attributes of user X2. Because the second DB server 400 stores this information, it can determine the gender and hobbies / preferences of user X2.

[0037] Upon receiving the specified conditions and management ID from the control device 100, the second DB server 400 sends the management ID and a list of users with user IDs of user X2 according to the specified conditions to the agent. More specifically, the second DB server 400 sends the user list and management ID to the sending agent server 200. This causes the sending agent server 200 to receive the user list and management ID from the second DB server 400. That is, the sending agent server 200 receives the user list and management ID from each of the first DB server 300 and the second DB server 400.

[0038] Destination resolution server 500 is managed by the telecommunications company. Destination resolution server 500 stores destination information corresponding to user IDs. Destination information can also be Internet Protocol (IP) addresses, email addresses, residential addresses, etc. When it receives a destination list and message from sending proxy server 200, destination resolution server 500 specifies the destination information corresponding to the user ID included in the destination list. If destination information has been specified, destination resolution server 500 sends the message to the specified destination information.

[0039] The message sent from the destination resolution server 500 wirelessly reaches the mobile information terminal 20 owned by user X2 via the communication network NW and the mobile base station BS. Since the user IDs included in the destination list are restricted to user IDs of user X2 with attributes according to specified conditions, the message reaches the mobile information terminal 20 owned by user X2 with attributes according to specified conditions. Therefore, when costs such as advertising fees are proportional to the number of destinations to which the message is sent, costs can be reduced compared to sending messages with or without attributes according to specified conditions.

[0040] Next, we will refer to Figure 2 Describe the hardware configuration of control device 100. Note that since the hardware configurations of sending proxy server 200, first DB server 300, second DB server 400 and destination resolution server 500 are basically similar to those of control device 100, their detailed descriptions will be omitted.

[0041] like Figure 2 As shown, the control device 100 includes a central processing unit (CPU) 100A as a processor and random access memory (RAM) 100B and read-only memory (ROM) 100C as storage. The control device 100 includes a network interface (I / F) 100D and a hard disk drive (HDD) 100E. Alternatively, a solid-state drive (SSD) can be used instead of the hard disk drive (HDD) 100E.

[0042] If needed, the control device 100 may further include at least one of an input I / F 100F, an output I / F 100G, an input / output I / F 100H, and a drive device 100I. The CPU 100A and the drive device 100I are interconnected via an internal bus 100J. For example, the control device 100 may be implemented by a computer.

[0043] Input device 18 is connected to input I / F 100F. Examples of input device 18 include a keyboard, mouse, touch panel, etc. Display device 19 is connected to output I / F 100G. Examples of display device 19 include liquid crystal display, etc. Semiconductor memory 13 is connected to input / output I / F 100H. Examples of semiconductor memory 13 include Universal Serial Bus (USB) memory, flash memory, etc. Input / output I / F 100H reads the transmission support program stored in semiconductor memory 13. Input I / F 100F and input / output I / F 100H include, for example, USB ports. Output I / F 100G includes, for example, a display port.

[0044] Portable recording medium 14 is inserted into drive device 100I. Examples of portable recording medium 14 include removable discs such as CD-ROMs and DVDs. Drive device 100I reads the transmission support program recorded on portable recording medium 14. For example, network I / F 100D includes a local area network (LAN) port, communication circuitry, etc.

[0045] The first transmission support program stored in at least one of ROM 100C, HDD 100E, and semiconductor memory 13 is temporarily stored in RAM 100B by CPU 100A. The first transmission support program recorded on portable recording medium 14 is also temporarily stored in RAM 100B by CPU 100A. When CPU 100A executes the stored first transmission support program, CPU 100A implements various functions described later and additionally performs various processes described later. Note that the first transmission support program only needs to comply with the procedures described later. Figure 11 The flowchart shown.

[0046] Similarly, when implementing the various functions of the sending proxy server 200 and additionally performing its various processes, the CPU only needs to execute the second sending support program. The second sending support program only needs to execute according to the procedures described later. Figure 12 The flowchart shown illustrates this. When implementing the various functions of the first DB server 300 and additionally performing various processes of the first DB server 300, the CPU only needs to execute the destination determination program. The destination determination program only needs to follow the procedures described later. Figure 13 The flowchart shown is provided. Since the second DB server 400 is similar to the first DB server 300, its description will be omitted. When implementing the various functions of the destination resolution server 500 and additionally performing its various processes, the CPU only needs to execute the destination resolution program. The destination resolution program only needs to follow the procedures described later. Figure 14 The flowchart shown.

[0047] Next, we will refer to Figure 3 Describe the functional configuration of the control device 100. Note that... Figure 3 The main functions of the control device 100 are shown.

[0048] like Figure 3As shown, the control device 100 includes a storage unit 110, a processing unit 120, an input unit 130, an output unit 140, and a communication unit 150. The storage unit 110 can be implemented using the aforementioned RAM 100B, HDD 100E, etc. The processing unit 120 can be implemented using the aforementioned CPU 100A. The input unit 130 can be implemented using the aforementioned input I / F 100F. The output unit 140 can be implemented using the aforementioned output I / F 100G. The communication unit 150 can be implemented using the aforementioned network I / F 100D. Therefore, the storage unit 110, processing unit 120, input unit 130, output unit 140, and communication unit 150 are interconnected.

[0049] Here, storage unit 110 includes a transmission target storage unit 111. Meanwhile, processing unit 120 includes a message sending unit 121 as a first sending component and a specified condition sending unit 122 as a second sending component. When an operation is performed on input device 18 to input a message and specified conditions, message sending unit 121 receives the message and specified conditions through input unit 130. Upon receiving the message and specified conditions, message sending unit 121 stores the message and specified conditions in transmission target storage unit 111. This allows transmission target storage unit 111 to store the message and specified conditions.

[0050] When the message and specified conditions have been saved, the message sending unit 121 performs various processes described later. Based on the execution result of these processes, the message sending unit 121 either sends the message to the sending proxy server 200 via the communication unit 150 or stops sending the message. When message sending is stopped, the message sending unit 121 notifies the display device 19 of a sending error via the output unit 140. When a message has been sent or message sending has stopped, the message sending unit 121 can also delete the message stored in the sending target storage unit 111. This can alleviate the strain on remaining memory due to messages.

[0051] Upon receiving a management ID from the sending agent server 200, the specified condition sending unit 122 retrieves the specified condition from the sending target storage unit 111. Once the specified condition has been retrieved, the specified condition sending unit 122 sends the associated retrieved specified condition and the received management ID to the first DB server 300 and the second DB server 400 via the communication unit 150. When the specified condition has been sent, the specified condition sending unit 122 can also delete the specified condition stored in the sending target storage unit 111. This can alleviate the strain on remaining storage space caused by the specified condition.

[0052] Next, we will refer to Figures 4 to 5 Describe the configuration for sending to the proxy server 200. Note that... Figure 4 The main functionalities of the sending proxy server 200 are shown.

[0053] like Figure 4 As shown, the sending proxy server 200 includes a storage unit 210, a processing unit 220, and a communication unit 250. Since the hardware configuration of the storage unit 210, processing unit 220, and communication unit 250 is basically similar to the hardware configuration of the storage unit 110, processing unit 120, and communication unit 150 of the control device 100, a detailed description of them will be omitted. Therefore, the storage unit 210, processing unit 220, and communication unit 250 are interconnected.

[0054] Here, storage unit 210 includes table storage unit 211. Processing unit 220 includes a management ID generation unit 221 as a generation component and a destination list generation unit 222 as a designation component. Management ID generation unit 221 receives messages via communication unit 250. When a message is received, management ID generation unit 221 generates a management ID for managing the message and returns the generated management ID to control device 100, which is the sender of the message, via communication unit 250. Additionally, management ID generation unit 221 stores the associated generated management IDs and received messages in table storage unit 211.

[0055] like Figure 5 As shown, the management ID and messages are registered and managed in the relevant fields of the transmission management table TBL included in the table storage unit 211. In addition to managing the management ID and messages, the transmission management table TBL also manages the aforementioned user list, the first transmission support program ID, the destination determination program ID, and the received ID. The first transmission support program ID is an identifier that identifies the first transmission support program.

[0056] For example, when a message is received from another message sending terminal (not shown) different from message sending terminal 10, a different first sending support program ID is registered in the relevant field of the sending management table TBL. In this embodiment, the first sending support program ID "α" corresponds to the identifier of the first sending support program installed in message sending terminal 10. Additionally, the first sending support program ID "β" corresponds to the identifier of the first sending support program installed in another message sending terminal.

[0057] The destination determination program ID is essentially similar to the first sending support program ID. For example, when user lists are received from each of the first DB server 300 and the second DB server 400, different destination determination program IDs are registered in the relevant fields of the sending management table TBL. In this embodiment, destination determination program ID "A" corresponds to the identifier of the destination determination program installed in the first DB server 300. Similarly, destination determination program ID "B" corresponds to the identifier of the destination determination program installed in the second DB server 400. Note that the received IDs will be described later.

[0058] Upon receiving a user list and a management ID, the destination list generation unit 222 specifies the user IDs that are repeated among users with a common management ID. Once user IDs have been specified, the destination list generation unit 222 generates a destination list including the specified user IDs. After the destination list has been generated, the destination list generation unit 222 sends the generated destination list and the message received from the control device 100 to the destination resolution server 500 via the communication unit 250.

[0059] Next, we will refer to Figures 6 to 8B Describe the functional configuration of the first DB server 300 and the second DB server 400. Note that... Figure 6 The main functional components of the first DB server 300 are shown. Furthermore, since the functional configuration of the second DB server 400 is substantially similar to that of the first DB server 300, its detailed description will be omitted.

[0060] like Figure 6 As shown, the first DB server 300 includes a storage unit 310, a processing unit 320, and a communication unit 350. Since the hardware configuration of the storage unit 310, processing unit 320, and communication unit 350 is basically similar to the hardware configuration of the storage unit 110, processing unit 120, and communication unit 150 of the control device 100, a detailed description of them will be omitted. Therefore, the storage unit 310, processing unit 320, and communication unit 350 are interconnected.

[0061] Here, storage unit 310 includes attribute DB 311 and attribute name list storage unit 312. Processing unit 320 includes a specified condition receiving unit 321, a user list generation unit 322, and a user list sending unit 323. The specified condition receiving unit 321 receives specified conditions and management IDs via communication unit 350. When the specified condition receiving unit 321 receives the specified conditions, the user list generation unit 322 generates a user list with reference to attribute DB 311.

[0062] like Figure 7AAs shown, attribute DB 311 stores the user ID of user X2, as well as the name, residential address, and date of birth related to user X2's attributes. Since the specified conditions include conditions related to the attributes specified by the requester X1, user list generation unit 322 refers to attribute DB 311 to specify the user ID according to these conditions. When a user ID has been specified, user list generation unit 322 generates a user list including the specified user ID. User list sending unit 323 sends the management ID along with the user list generated by user list generation unit 322 to sending proxy server 200 via communication unit 350.

[0063] Note that, as Figure 7B As shown, attribute name list storage unit 312 stores attribute name list file F1. Attribute name list file F1 is an electronic file representing a list of attributes that can be determined by the first DB server 300. In this embodiment, name, residential address, and date of birth are recorded as attributes that can be determined by the first DB server 300 in attribute name list file F1. Unlike the non-public attribute DB 311, attribute name list file F1 is publicly accessible in the transmission support system ST. This allows, for example, the control device 100 of message sending terminal 10 to refer to attribute name list file F1.

[0064] like Figure 8A As shown, the attribute DB 411 of the second DB server 400 stores the user ID of user X2, as well as gender, educational background, and hobbies / preferences related to user X2's attributes. The specified condition receiving unit 421 of the second DB server 400 receives specified conditions and management IDs from the control device 100, similar to the specified condition receiving unit 321. The user list generation unit 422 of the second DB server 400 generates a user list, similar to the user list generation unit 322. The user list sending unit 423 of the second DB server 400 sends the user list along with the management IDs to the sending agent server 200, similar to the user list sending unit 323.

[0065] Note that, as Figure 8B As shown, attribute name list storage unit 412 stores attribute name list file F2. Attribute name list file F2 is an electronic file representing a list of attributes that can be determined by the second DB server 400. In this embodiment, gender, educational background, and hobbies / preferences are recorded as attributes that can be determined by the second DB server 400 in attribute name list file F2. Unlike the non-public attribute DB 411, attribute name list file F2 is publicly accessible in the transmission support system ST. This allows, for example, the control device 100 of message sending terminal 10 to refer to attribute name list file F2.

[0066] Next, we will refer to Figures 9 to 10 Describe the functional configuration of the Destination Resolution Server 500. Note that... Figure 9 This shows the main functionalities of the Destination Resolution Server 500.

[0067] like Figure 9 As shown, the destination resolution server 500 includes a storage unit 510, a processing unit 520, and a communication unit 550. Since the hardware configuration of the storage unit 510, processing unit 520, and communication unit 550 is basically similar to the hardware configuration of the storage unit 110, processing unit 120, and communication unit 150 of the control device 100, a detailed description of them will be omitted. Therefore, the storage unit 510, processing unit 520, and communication unit 550 are interconnected.

[0068] Here, storage unit 510 includes destination database 511. Processing unit 520 includes destination information extraction unit 521 and message sending unit 522. Destination information extraction unit 521 receives a destination list and a message via communication unit 550. When the destination list is received, destination information extraction unit 521 extracts destination information by referring to destination database 511.

[0069] like Figure 10 As shown, destination DB 511 stores destination information for user IDs and user X2 that uniquely correspond to each other. Since the destination list includes user IDs, destination information extraction unit 521 refers to destination DB 511 to extract destination information based on the user IDs included in the destination list. When destination information extraction unit 521 has extracted the destination information, message sending unit 522 sends a message via communication unit 550 to the mobile information terminal 20 associated with the extracted destination information. This ensures the message reaches the mobile information terminal 20 owned by user X2, who possesses attributes according to specified conditions.

[0070] Next, we will refer to Figures 11 to 15 Describe the action of sending the support system ST.

[0071] First, such as Figure 11 As shown, message sending unit 121 waits until it receives a message and specified conditions (step S1: No). When the requester X1 performs an operation to input a message and specified conditions, message sending unit 121 receives the message and specified conditions (step S1: Yes). When the message and specified conditions are received, message sending unit 121 searches for companies that hold the attributes specified by the specified conditions (step S2) and determines whether there are any relevant companies (step S3).

[0072] For example, firstly, the message sending unit 121 refers to attribute name list files F1 and F2, which are publicly available in the transmission support system ST. When referring to attribute name list files F1 and F2, the message sending unit 121 determines whether at least a portion of the attributes specified by the specified conditions are included in attribute name list files F1 and F2. For example, when a message is received and three of the conditions are specified as conditions concerning attributes of user X2, the message sending unit 121 refers to attribute name list files F1 and F2. In this embodiment, as... Figure 15 As shown, the three conditions are male, 50 years old, and residing in Tokyo.

[0073] In this scenario, since the residential address and date of birth are recorded in the attribute name list file F1, the place of residence and age can be determined. Because the attribute name list file F1 is managed by the broadcasting company, the message sending unit 121 determines that a relevant company exists. Furthermore, since gender is recorded in the attribute name list file F2, gender can be determined. Because the attribute name list file F2 is managed by the water company, the message sending unit 121 determines that a relevant company exists.

[0074] When a relevant company exists (step S3: Yes), the message sending unit 121 determines whether all attributes included in the specified conditions can be determined (step S4). For example, it determines whether any attribute included in the specified conditions is held by any company. When an attribute included in the specified conditions cannot be determined (step S4: No), or when a relevant company does not exist in the process of step S3 (step S3: No), the message sending unit 121 issues a notification of a sending error on the display device 19 (step S5).

[0075] When it can be determined that all attributes included in the specified conditions are true (step S4: Yes), message sending unit 121 sends a message (step S6). More specifically, as... Figure 15 As shown, message sending unit 121 sends message MSG to sending proxy server 200 (arrow P1). When sending message MSG, message sending unit 121 simultaneously sends the first sending support program ID and the destination determination program ID.

[0076] The first sending support program ID is an identifier that identifies the first sending support program, which represents the sender of message MSG. In this embodiment, the first sending support program ID "α" is assigned to the first sending support program installed in the control device 100 of the message sending terminal 10. Meanwhile, the destination determination program ID is an identifier that identifies the destination determination program. In this embodiment, the destination determination program ID "A" is assigned to the destination determination program installed in the first DB server 300. The destination determination program ID "B" is assigned to the destination determination program installed in the second DB server 400. In the processing of step S3, when a related company exists, the message sending unit 121 can obtain the destination determination program ID corresponding to the related company.

[0077] like Figure 12 As shown, in the sending proxy server 200, the management ID generation unit 221 waits until a message is received (step S11: No). When a message is received (step S11: Yes), the management ID generation unit 221 generates a management ID (step S12). For example, if management ID "1" is already registered in the sending management table TBL (see... Figure 5 In the relevant fields of ), the management ID generation unit 221 generates a management ID "2" that is consecutive to management ID "1".

[0078] When a management ID has been generated, the management ID generation unit 221 registers the management ID and the message (step S13). More specifically, the management ID generation unit 221 registers the management ID, the message, and the first transmission support program ID and destination determination program ID received along with the message in the relevant fields of the transmission management table TBL. In this embodiment, the management ID generation unit 221 registers the interrelated management ID "2", message "[Message 1]", first transmission support program ID "α", and destination determination program IDs "A, B" in the relevant fields of the transmission management table TBL (see reference). Figure 5 ).

[0079] Once the management ID and message have been registered, the management ID generation unit 221 returns the management ID (step S14). More details, such as... Figure 15 As shown, the management ID generation unit 221 returns the management ID to the control device 100 of the message sending terminal 10 (arrow P2). In the control device 100, as... Figure 11 As shown, the specified condition sending unit 122 receives the management ID (step S7). When the management ID is received, the specified condition sending unit 122 sends the specified condition and the management ID (step S8). More detailed, as... Figure 15As shown, the specified condition sending unit 122 sends the specified condition and management ID to the first DB server 300 and the second DB server 400 (arrow P3). When the specified condition and management ID have been sent, the specified condition sending unit 122 waits until it receives a completion notification from the sending agent server 200 regarding the sending (step S9: No).

[0080] In the first DB server 300, such as Figure 13 As shown, the specified condition receiving unit 321 waits until it receives the specified condition and management ID (step S31: No). When the specified condition and management ID have been received (step S31: Yes), the user list generation unit 322 generates the user list (step S32). Figure 15 As shown, the first DB server 300 can determine age and place of residence. Therefore, among the three conditions specified in the specified conditions, the user ID of user X2, who is 50 years old and resides in Tokyo, can be specified. The user list generation unit 322 refers to attribute DB 311 ( Figure 7A This specifies a user ID that meets the criteria of age and place of residence. In this implementation, such as... Figure 15 As shown, user IDs "a, b, c, e, g, h" are specified. When user IDs have been specified, the user list generation unit 322 generates a user list that includes the specified user IDs but does not include the attributes possessed by user X2 with the specified user IDs. In this embodiment, as... Figure 15 As shown, the user list generation unit 322 generates a user list "A" that includes user IDs "a, b, c, e, g, h".

[0081] Once the user list has been generated, the user list sending unit 323 sends the management ID and the user list (step S33). More details, such as... Figure 15 As shown, the user list sending unit 323 sends a combination of the user list "[User List A]", management ID "2" (not shown), and destination determination program ID "A" to the sending proxy server 200 (arrow P4). Once the management ID and user list have been sent, the user list sending unit 323 terminates the process.

[0082] Similarly, in the second DB server 400, as in the first DB server 300, the specified condition receiving unit 421 waits until it receives the specified condition and management ID. Once the specified condition and management ID have been received, the user list generation unit 422 generates the user list. Figure 15As shown, the second DB server 400 can determine gender. Therefore, among the three conditions specified in the specified conditions, the user ID of user X2 can be specified based on the condition that the gender is male. The user list generation unit 422 refers to attribute DB 411 ( Figure 8A This specifies the user ID that meets the gender-specific criteria. In this implementation, such as... Figure 15 As shown, user IDs "b, c, d, f, h" are specified. When user IDs have been specified, the user list generation unit 422 generates a user list that includes the specified user IDs but does not include the attributes possessed by user X2 with the specified user IDs. In this embodiment, as... Figure 15 As shown, the user list generation unit 422 generates a user list "B" that includes user IDs "b, c, d, f, h".

[0083] Once the user list has been generated, user list sending unit 423 sends the management ID and the user list. More details, such as... Figure 15 As shown, the user list sending unit 423 sends the combination of user list "[User List B]", management ID "2", and destination determination program ID "B" to the sending proxy server 200 (arrow P4). Once the management ID and user list have been sent, the user list sending unit 423 ends the processing.

[0084] In the sending proxy server 200, such as Figure 12 As shown, the destination list generation unit 222 waits until it receives the user list and management ID (step S15: No). When the user list and management ID are received (step S15: Yes), the destination list generation unit 222 registers the user list (step S16). More specifically, each time a combination of user list, management ID, and destination determination program ID is received, the destination list generation unit 222 accesses the sending management table TBL (see reference). Figure 5 When the Sending Management Table TBL is accessed, the Destination List Generation Unit 222 searches for a Management ID that matches the received Management ID.

[0085] When a matching management ID is found, the destination list generation unit 222 registers the received user list in the user list corresponding to the found management ID. In this embodiment, user list "A" is sent from the first DB server 300, and user list "B" is sent from the second DB server 400. Therefore, the destination list generation unit 222 registers [user list A] and [user list B] in the field of the user list corresponding to management ID "2". Here, the user list includes user IDs, but does not include the attributes possessed by user X2 assigned with the included user IDs. Therefore, as... Figure 15As shown, the agency is not allowed to access the attributes of user X2. This protects user X2's personal information and privacy.

[0086] Furthermore, when a management ID matching the received management ID is found, the destination list generation unit 222 registers the received destination determination program ID in the field of the received ID corresponding to the found management ID. In this embodiment, the destination determination program ID "A" is sent from the first DB server 300, and the destination determination program ID "B" is sent from the second DB server 400. Therefore, the destination list generation unit 222 registers the destination determination program IDs "A" and "B" in the field of the received ID corresponding to the management ID "2".

[0087] When a user list has been registered, the destination list generation unit 222 determines whether the destination determination program ID in the sending management table TBL matches the received ID (step S17). For example, sometimes there is a gap between the time when the user list sent from the first DB server 300 is received and the time when the user list sent from the second DB server 400 is received. In this case, there is a possibility that the destination determination program IDs "A" and "B" are registered in the field of the destination determination program ID, and the received ID "A" is registered in the field of the received ID, but the received ID "B" is not registered in the field of the received ID. When the destination determination program ID and the received ID do not match (step S17: No), the destination list generation unit 222 returns to the processing in step S15. This avoids subsequent processing from starting in the absence of a destination determination program ID.

[0088] When the destination determination program ID matches the received ID (step S17: Yes), the destination list generation unit 222 generates a destination list (step S18). More specifically, the destination list generation unit 222 specifies the user IDs that are repeated in the user list and generates a destination list including the specified user IDs. In this embodiment, as... Figure 15 As shown, user list "A" includes user IDs "a, b, c, e, g, h". User list "B" includes user IDs "b, c, d, f, h". Therefore, as... Figure 15 As shown, the destination list generation unit 222 specifies the user IDs "b, c, h" that are repeated in user list "A" and user list "B", and generates a destination list including these user IDs "b, c, h".

[0089] When a destination list has been generated, the destination list generation unit 222 determines whether the destination list is empty (step S19). If the destination list is empty (step S19: Yes), the destination list generation unit 222 sends an error notification (step S20). More specifically, the destination list generation unit 222 sends the error notification to the control device 100 of the message sending terminal 10. Figure 11 As shown, this causes the message sending unit 121 to issue a notification of a sending error on the display device 19, just as in step S5.

[0090] When the destination list is not empty (step S19: No), the destination list generation unit 222 sends the destination list and a message (step S21). In this embodiment, as described above, since the destination list includes user IDs "b, c, h", the destination list generation unit 222 determines that the destination list is not empty. Therefore, as... Figure 15 As shown, the destination list generation unit 222 sends the destination list and messages to the destination resolution server 500 (arrow P5).

[0091] When the destination list and message have been sent, the destination list generation unit 222 sends a completion notification regarding the sending (step S22). More specifically, the destination list generation unit 222 sends the completion notification to the control device 100 of the message sending terminal 10. Along with sending the completion notification, the destination list generation unit 222 may also send the number of user IDs included in the destination list to the control device 100. Figure 11 As shown, in step S9, the control device 100 waits until a completion notification is received, and when a completion notification has been received (step S9: Yes), the specified condition sending unit 122 ends the process. Note that when the number of user IDs has been received, the specified condition sending unit 122 can also notify the display device 19 of the number of user IDs.

[0092] In the destination resolution server 500, such as Figure 14 As shown, the destination information extraction unit 521 waits until it receives a message and a destination list (step S51: No). When it receives a message and a destination list (step S51: Yes), the destination information extraction unit 521 extracts the destination information corresponding to the user ID (step S52). More specifically, the destination information extraction unit 521 searches the destination DB 511 (see reference) based on the user ID included in the destination list. Figure 10The destination information extraction unit 521 extracts the destination information corresponding to the user ID from the destination DB 511. In this embodiment, the user IDs "b, c, h" are included in the destination list. Therefore, the destination information extraction unit 521 extracts the destination information corresponding to the user IDs "b, c, h" from the destination DB 511.

[0093] Once the destination information has been extracted, the message sending unit 522 sends a message (step S53). More specifically, the message sending unit 522 sends the message to the mobile information terminal 20 associated with the extracted destination information. Figure 15 As shown, this allows the message to reach the mobile information terminal 20 owned by user X2 with user IDs "b, c, h" (arrow P6). Once the message has been sent, the message sending unit 522 terminates processing. In this way, the message reaches user X2 with attributes according to specified conditions, and the message is prevented from reaching user X2 by including or even not meeting the specified conditions. Wasteful costs can be suppressed when the cost is proportional to the number of messages reached (or the number of destinations).

[0094] (Second Implementation)

[0095] The second embodiment of this implementation will then be described. In the first embodiment described above, the broadcasting company and the water company each hold a user ID, but they may also hold the destination information of user X2 instead of the user ID. The destination information may also be an email address or a telephone number assigned to the mobile information terminal 20. For example, user X2's email address or telephone number may also be registered in attribute DB 311 of the first DB server 300 managed by the broadcasting company. Furthermore, user X2's email address or telephone number may also be registered in attribute DB 411 of the second DB server 400 managed by the water company.

[0096] This allows the user list "A" and user list "B" described in the first embodiment to include destination information instead of user IDs. In this case, user list sending unit 323 and user list sending unit 423 send the user list "A" and user list "B" including destination information along with the management ID to the sending proxy server 200, respectively.

[0097] Therefore, in the sending proxy server 200, the destination list generation unit 222 specifies multiple destination information entries that are repeated among the user lists. Subsequently, in the first embodiment, the destination list generation unit 222 generates a destination list including the specified destination information and sends the generated destination list along with the message to the destination resolution server 500. However, in the second embodiment, since the destination information has already been specified, destination resolution is no longer necessary. For example, the process of extracting the destination information corresponding to the user ID from the destination resolution server 500 can be omitted. In the case of the second embodiment, the message can be sent directly from the sending proxy server 200 to the mobile information terminal 20 without including the destination resolution server 500 in the sending support system ST.

[0098] (Third Implementation)

[0099] The third embodiment of this implementation will then be described. In the first embodiment described above, the telecommunications company holds the IP address as destination information; however, a postal company could be used instead of a telecommunications company, thereby holding the residential address and name of user X2 instead of the IP address. For example, the residential address and name of user X2 could also be registered in the destination DB 511 of the destination resolution server 500 managed by the postal company.

[0100] In this scenario, the control device 100 of the message sending terminal 10 sends print data containing the message to the destination resolution server 500, with the control device 100 being the message sender. The print data is data used to print messages, etc., onto mail. Simultaneously, similar to the first embodiment, the sending proxy server 200 sends a destination list containing user IDs that are repeated across user lists to the destination resolution server 500. This allows the destination information extraction unit 521 to extract the residential address and name based on the user IDs included in the destination list. In the third embodiment, since the destination resolution server 500 is managed by the postal company, messages can be printed onto mail based on the print data, and additionally, the extracted residential address and name can be printed onto the mail. The postal company can then send mail containing the message, residential address, and name to user X2. Note that in the third embodiment, sending messages from the sending proxy server 200 to the destination resolution server 500 can also be stopped. In this way, according to the third embodiment, while protecting user X2's personal information, physical mail, rather than electronic messages, can be mailed to user X2 who has attributes according to specified conditions.

[0101] Furthermore, in the first embodiment described above, the telecommunications company holds the IP address as destination information. However, a delivery company could be used instead of a telecommunications company, holding the residential address and name of user X2 instead of the IP address. For example, user X2's residential address and name could also be registered in the destination DB511 of the destination resolution server 500 managed by the delivery company.

[0102] In this scenario, the destination list generation unit 222 generates a destination list including user IDs that are repeated across user lists, and then notifies the control device 100 of the number of user IDs included in the destination list; the control device 100 is the message sender. The requester X1 prepares the notified number of delivery objects and sends the prepared delivery objects to a delivery company using a courier company or similar means. Examples of delivery objects include packages. Simultaneously, similar to the first embodiment, the sending proxy server 200 sends the destination list including user IDs that are repeated across user lists to the destination resolution server 500. This allows the destination information extraction unit 521 to extract residential addresses and names based on the user IDs included in the destination list.

[0103] Since the destination resolution server 500 is managed by the delivery company, when the delivery object has been transferred from the requester X1 to the delivery company, the delivery company will attach a document with the retrieved residential address and name written on it to the delivery object. This allows the delivery object to be sent to user X2. Note that, in the same case, it is also possible to stop sending messages from the sending agent server 200 to the destination resolution server 500. In this way, also when using a delivery company, while protecting user X2's personal information, a physical delivery object, rather than an electronic message, can be mailed to user X2 with attributes according to specified conditions.

[0104] (Fourth Implementation)

[0105] Next, a fourth embodiment of this embodiment will be described. In the first embodiment described above, it was described that the destination list generation unit 222 specifies user IDs that are repeated among the user lists with public management IDs and generates a destination list including the specified user IDs. In the fourth embodiment, the destination list generation unit 222 specifies a first number of identifiers, which is the number of user IDs that are repeated among the user lists with public management IDs. For example, if the user IDs that are repeated among the user lists with public management IDs are user IDs "b, c, h", then the destination list generation unit 222 specifies a first number of identifiers as "3".

[0106] Furthermore, the destination list generation unit 222 specifies a second number of identifiers, which is the number of identifiers in the union of user IDs of user X2 held by the broadcasting company and the water company respectively. For example, suppose user IDs "a, b, c, d, e, f, g, h" are included in attribute DB 311 (refer to...) of the first DB server 300 managed by the broadcasting company. Figure 7A In ), and also assume that user IDs “a, b, c, d, e, f, g, h, i, j” are included in attribute DB 411 (refer to) of the second DB server 400 managed by the water company. Figure 8A In this case, since the union of the two sets of user IDs is user IDs "a, b, c, d, e, f, g, h, i, j", the destination list generation unit 222 specifies the second number of identifiers as "10".

[0107] When a first number and a second number of identifiers have been specified, the destination list generation unit 222 sends the ratio of the first number to the second number of identifiers to the control device 100, which is the sender, of the message sending terminal 10. In this embodiment, the destination list generation unit 222 sends ratios such as "0.3" and "30%" to the control device 100. In the control device 100, since the specified condition sending unit 122 receives the ratio and makes a notification on the display device 19, the sending requester X1 is allowed to confirm the percentage to which the message has been sent.

[0108] Although preferred embodiments have been described in detail so far, this embodiment is not limited to the specific embodiments, and various modifications and changes can be made within the scope of this embodiment described in the claims. For example, the various servers described above can also be implemented using physical servers or virtual servers.

Claims

1. A non-transitory computer-readable storage medium storing a transmission support program, the transmission support program causing at least one computer to perform a process, the process comprising: In response to the receipt of a message, a management identifier for the message is generated; Return the management identifier to the sender of the message; Receive from the sender the management identifier and a set of designated company identifiers for multiple companies holding information about the attributes of an individual. Upon receiving a list of personal identifiers and the management identifier of an individual who has the attribute according to conditions associated with the attribute from each of the plurality of companies holding information about the individual's attribute, based on the conditions from the sender and the receipt of the management identifier, it is determined that a list of personal identifiers has been received from each company corresponding to the set of specified company identifiers. In response to determining that a list has been received from each company, personal identifiers that are repeated among the lists having common management identifiers are specified; and Send the specified personal identifier and the received message.

2. The non-transitory computer-readable storage medium according to claim 1, wherein, The multiple companies hold the individual's destination as the personal identifier and send a list of the destinations and the management identifier, wherein, The designation includes, when a list of destinations and the management identifier are received from each of the plurality of companies, designating destinations that are repeated among the lists of destinations with a common management identifier, and The sending includes sending the received message to the specified destination.

3. The non-transitory computer-readable storage medium according to claim 1, wherein, The sender sends print data, including the message to be printed on the mail, to the postal company, which holds information related to mailing the mail to the individual associated with the personal identifier. The transmission includes stopping the transmission of received messages used to send the designated personal identifier to the postal company.

4. The non-transitory computer-readable storage medium according to claim 1, wherein, The designation includes notifying the sender of a plurality of designated personal identifiers, wherein... The sender sends the number of notified delivery recipients to the delivery company, which holds information related to delivering the delivery recipients to individuals associated with the personal identifier. The transmission includes stopping the transmission of received messages used to send the designated personal identifier to the delivery company.

5. The non-transitory computer-readable storage medium according to claim 1, wherein, The designation includes designating a first quantity and a second quantity, wherein the first quantity is the number of personal identifiers repeated among lists of individuals with common management identifiers, and the second quantity is the number of identifiers in a union of the personal identifiers of individuals held separately by the plurality of companies. The sending includes sending the ratio of the first quantity to the second quantity to the sender.

6. The non-transitory computer-readable storage medium according to claim 1, wherein, The process also includes: Upon receiving a message from the sender requesting the message and conditions related to the individual's attributes, the message is sent to a first company acting as the sender's agent, which then sends the message to the individual; and When a management identifier for a message generated by the first company in response to the receipt of the message is received, the condition and the management identifier are sent to each of a plurality of second companies holding information about the attribute, wherein, The plurality of second companies send the management identifier and a list of individual identifiers of individuals having attributes according to the conditions to the first company, and The first company Specify a personal identifier that is repeated across lists of publicly known administrative identifiers, and Send the specified personal identifier and the received message.

7. A transmission support device, comprising: Generation unit, the generation unit In response to the receipt of a message, a management identifier for the message is generated, and Return the management identifier to the sender of the message; as well as Designated part, the designated part Upon receiving the management identifier and a set of designated company identifiers for a plurality of companies holding information about an individual's attributes from the sender, and upon receiving from each of the plurality of companies holding information about the individual's attributes a list of personal identifiers of the individual who have the attributes according to conditions associated with the attributes, and the management identifier, based on the conditions from the sender and the receipt of the management identifier, it is determined that a list of personal identifiers has been received from each company corresponding to the set of designated company identifiers. In response to determining that a list has been received from each company, personal identifiers that are repeated among the lists having common management identifiers are designated. Send the specified personal identifier and the received message.

8. A method for sending support for computer-executed processing, the method comprising: In response to the receipt of a message, a management identifier for the message is generated; Return the management identifier to the sender of the message; Receive from the sender the management identifier and a set of designated company identifiers for multiple companies holding information about the attributes of an individual. Upon receiving a list of personal identifiers and the management identifier of an individual who has the attribute according to conditions associated with the attribute from each of the plurality of companies holding information about the individual's attribute, based on the conditions from the sender and the receipt of the management identifier, it is determined that a list of personal identifiers has been received from each company corresponding to the set of specified company identifiers. In response to determining that a list has been received from each company, personal identifiers that are repeated among the lists having common management identifiers are specified; and Send the specified personal identifier and the received message.

Images