Invitation support device, invitation support method, and program

Abstract

To provide an invitation support device, an invitation support method, and a program capable of facilitating processing when making an invitation in various services.SOLUTION: An invitation support device is configure to: acquire request information including information of service to be invited by an inviter user and login information of the inviter user; request authentication of the inviter user based on the login information; and generate a temporary code including information for identifying the inviter user and information on the service when the authentication is successful and the inviter user has been registered in the service to be invited, where the login information can be commonly used in the plurality of services.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present invention relates to an invitation support device, an invitation support method, and a program. [Background technology]

[0002] In recent years, various systems have been proposed for registering members for membership services provided over a network. For example, Patent Document 1 discloses a system that can execute member registration processing without delay, without requiring the inviter to provide the invitee's email address, and without forcing the inviter and invitee to perform redundant operations. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-146452 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the above system has room for improvement in terms of facilitating the process of sending invitations to various services.

[0005] The present invention has been made to solve the above-mentioned problems, and has an object to provide an invitation support device, an invitation support method, and a program that can facilitate the process of making an invitation for various services. [Means for solving the problem]

[0006] An invitation support device according to a first aspect of the present invention comprises: a request information acquisition unit that acquires request information including information on a service to which an inviter user is invited and login information of the inviter user; an authentication request unit that requests authentication of the guest user based on the login information acquired by the request information acquisition unit; a temporary code generating unit that generates a temporary code including information for identifying the inviter user and information about the service when the authentication requested by the authentication requesting unit is successful and the inviter user has already registered for the service to which the invitee is invited; The login information can be used in common across multiple services. It is characterized by:

[0007] In addition, in the invitation support device according to the above aspect, an account information acquiring means for acquiring account information of the guest user corresponding to the login information when the authentication requested by the authentication requesting unit is successful; a determination result acquisition unit that acquires a determination result of whether the inviter user has registered with the service to which the invitee is invited, based on the account information acquired by the account information acquisition unit; the temporary code generation unit generates the temporary code when the determination result acquisition unit determines that the inviter user has already registered with the service to which the invitee is invited. It is characterized by:

[0008] In addition, in the invitation support device according to the above aspect, the determination result acquisition unit acquires a determination result as to whether the inviter user has registered for the service to which the invitee user is invited by inquiring of a service providing server that provides the service to which the invitee user is invited; It is characterized by:

[0009] In addition, in the invitation support device according to the above aspect, the determination result acquisition unit determines whether the inviter user has registered for the service to which the invitee user is invited based on registration information acquired from a service providing server that provides the service to which the invitee user is invited, and acquires the determination result. It is characterized by:

[0010] In addition, in the invitation support device according to the above aspect, a temporary code providing unit that provides the temporary code generated by the temporary code generating unit to the inviter terminal owned by the inviter user; the request information acquisition unit acquires request information including information on the service to which the invitee user is invited and login information of the invitee user, based on the fact that the temporary code provided to the inviter terminal by the temporary code provision unit is acquired by the invitee terminal owned by the invitee user; the authentication request unit requests authentication of the invited user based on the login information of the invited user acquired by the request information acquisition unit; a notification information providing unit that, when the authentication request unit has succeeded in the authentication requested by the invited user and the invited user has already registered for the service to which the invited user has been invited, provides the invited user terminal with usage promotion information that promotes the use of the service, and, when the invited user has not yet registered for the service to which the invited user has been invited, provides the invited user terminal with registration benefit information that can be obtained by the invited user registering; The device is characterized by further comprising:

[0011] In addition, in the invitation support device according to the above aspect, a provision information output unit that outputs provision information that associates information about the inviting user identified from the temporary code, information about the service identified from the temporary code, information about the invited user who obtained the temporary code, and provision information that indicates whether the information provided by the notification information providing unit is the use promotion information or the registration benefit information; The device is characterized by further comprising:

[0012] In addition, in the invitation support device according to the above aspect, an output information transmitting unit that transmits the provided information output by the provided information output unit, output information extracted for each piece of information on the service identified from the temporary code, to a service providing server that provides the corresponding service; The device is characterized by further comprising:

[0013] In addition, in the invitation support device according to the above aspect, a fraud determination unit that determines fraudulent behavior by the inviter user based on an outlier of a two-dimensional distribution for the inviter user, the outlier being based on the ratio of the invitee users who failed the authentication requested by the authentication request unit and the ratio of the invitee users who were not registered with the service to which they were invited, among the inviter users invited by the inviter user; The device is characterized by further comprising:

[0014] In addition, in the invitation support device according to the above aspect, The fraud determination unit determines fraudulent behavior by the inviter user based on an outlier of a four-dimensional distribution for the inviter user, which is based on the ratio of the invitee users who failed the authentication requested by the authentication request unit among the invitee users invited by the inviter user, the ratio of the invitee users who were not registered in the service to which the invitee users were invited, the number of the invitee users who failed the authentication requested by the authentication request unit, and the number of the invitee users who were not registered in the service to which the invitee users were invited. It is characterized by:

[0015] In addition, in the invitation support device according to the above aspect, The notification information providing unit provides different types of registration benefit information according to the ratio of the invited users who failed the authentication requested by the authentication requesting unit, the ratio of the invited users who were not registered with the service to which they were invited, the number of the invited users who failed the authentication requested by the authentication requesting unit, and the number of the invited users who were not registered with the service to which they were invited. It is characterized by:

[0016] An invitation support method according to a second aspect of the present invention comprises: An invitation support method using an invitation support device, a request information acquisition step of acquiring request information including information on a service to which the inviter user is invited and login information of the inviter user; an authentication request step of requesting authentication of the guest user based on the login information acquired in the request information acquisition step; a temporary code generating step of generating a temporary code including information for identifying the inviter user and information about the service when the authentication requested in the authentication requesting step is successful and the inviter user has already registered for the service to which the invitee is invited; The login information can be used in common across multiple services. It is characterized by:

[0017] A program according to a third aspect of the present invention comprises: Computer, a request information acquisition unit that acquires request information including information on a service to which an inviter user is invited and login information of the inviter user; an authentication request unit that requests authentication of the guest user based on the login information acquired by the request information acquisition unit; a temporary code generating unit that generates a temporary code including information for identifying the inviter user and information about the service when the authentication requested by the authentication requesting unit is successful and the inviter user is already registered with the service to which the invitee is invited; The login information can be used in common across multiple services. It is characterized by:

[0018] The program may be recorded on a non-transitory recording medium. The non-transitory recording medium can be distributed and sold independently of the computer. Here, the term "non-transitory recording medium" refers to a tangible recording medium. Examples of non-transitory recording media include compact discs, flexible disks, hard disks, magneto-optical disks, digital video disks, magnetic tapes, and semiconductor memories. Furthermore, the term "transitory recording medium" refers to the transmission medium (propagation signal) itself. Examples of temporary recording media include electrical signals, optical signals, and electromagnetic waves. A temporary storage area is an area for temporarily storing data and programs, such as volatile memory such as RAM (Random Access Memory). [Effects of the Invention]

[0019] According to the present invention, it is possible to provide an invitation support device, an invitation support method, and a program that can facilitate the process of making an invitation for various services. [Brief explanation of the drawings]

[0020] [Figure 1] 2 is a diagram illustrating the relationship between an invitation support device, an account management device, a service providing server, an inviter terminal, and an invitee terminal. [Figure 2] FIG. 1 is a block diagram illustrating an example of an invitation support device. [Figure 3] FIG. 10 is an explanatory diagram illustrating an example of a list of provided information. [Figure 4] FIG. 10 is an explanatory diagram illustrating an example of an output information list; [Figure 5] FIG. 2 is a block diagram illustrating an example of an account management device. [Figure 6] FIG. 10 is an explanatory diagram illustrating an example of account information. [Figure 7] 10 is a flowchart illustrating an example of an invitation support process. [Figure 8] FIG. 10 is an explanatory diagram showing an example of a display on the inviter terminal at the time of an invitation. [Figure 9] FIG. 10 is an explanatory diagram showing an example of a display on the inviter terminal at the time of an invitation. [Figure 10] FIG. 10 is an explanatory diagram showing an example of a display on the inviter terminal at the time of an invitation. [Figure 11] 10 is a flowchart illustrating an example of post-invitation processing. [Figure 12] FIG. 10 is an explanatory diagram showing an example of a display on an invitee terminal after an invitation. [Figure 13] FIG. 10 is an explanatory diagram showing an example of a display on an invitee terminal after an invitation. [Figure 14] FIG. 10 is an explanatory diagram showing an example of a display on an invitee terminal after an invitation. [Figure 15] FIG. 10 is an explanatory diagram showing an example of a display on an invitee terminal after an invitation. DETAILED DESCRIPTION OF THE INVENTION

[0021] (Overall composition) An invitation support device, an invitation support method, and a program according to an embodiment of the present invention will be described in detail with reference to the drawings. Note that identical or corresponding parts in the drawings are designated by the same reference numerals. As shown in Figure 1, an invitation support device 100 according to an embodiment of the present invention is communicably connected to an account management device 200, a service providing server 300, an inviter terminal 400, and an invitee terminal 500 via a computer communication network 800 such as the Internet.

[0022] The invitation support device 100 is a computer such as a server, and has a function to support an invitation from an inviter, who is a user of an inviter terminal 400, to an invitee, who is a user of an invitee terminal 500, to join a service. Specifically, the invitation support device 100 uses account information common to multiple services to support an invitation from the inviter to the invitee to a service to which the inviter is inviting the invitee. For example, if inviter A is a user of three services, service A, service C, and service E, the invitation support device 100 checks the usage status of each service by inviter A based on the account information common to the three services, and generates invitation information to provide to the invitee.

[0023] The account management device 200 is a server that manages account information common to multiple services. Specifically, the account management device 200 has a function of performing user authentication based on account information common to multiple services in response to an authentication request from the invitation support device 100.

[0024] The service providing server 300 is a server that provides each service. As shown in the figure, a service providing server 300 is provided for each service, and each service providing server 300 stores registration information indicating a list of registered users. That is, the service providing server 300 stores the list information of registered users, and has a function of providing the list information of registered users in response to a request from the invitation support device 100.

[0025] The inviter terminal 400 is an information terminal (so-called computer) such as a smartphone, tablet, or PC (Personal Computer) owned by the user who is inviting. There may be multiple inviter terminals 400. When the user who owns the inviter terminal 400 receives an invitation from another user, the inviter terminal 400 functions as the invitee terminal 500. In other words, the inviter terminal 400 may also function as the invitee terminal 500.

[0026] The invitee terminal 500 is an information terminal (so-called computer) such as a smartphone, tablet, or PC owned by the user who is the invitee. There are multiple invitee terminals 500. When the user who owns the invitee terminal 500 invites another user, the invitee terminal 500 functions as the inviter terminal 400. In other words, the invitee terminal 500 may also function as the inviter terminal 400.

[0027] (Functional configuration of the invitation support device) Next, the configuration of the invitation support device 100 will be described with reference to FIG.

[0028] As shown in FIG. 2, the invitation support device 100 includes a storage unit 110, a control unit 120, an input / output unit 130, a communication unit 140, and a system bus (not shown) that interconnects these units.

[0029] The storage unit 110 includes a ROM (Read Only Memory), a RAM (Random Access Memory), etc. The ROM stores a program 111 to be executed by the control unit 120, various data (not shown) required in advance for executing the program 111, a provided information list 112, and an output information list 113.

[0030] The program 111 is a program for executing the invitation support process and post-invitation process described below, and is stored in the storage unit 110 in advance.

[0031] The provided information list 112 is a list (history) of information provided from the inviter to the invitee. Specifically, as shown in FIG. 3, the provided information list 112 includes at least information about the inviter, information about the invitee, account information indicating whether the invitee has an account (an account common to multiple services), target service information indicating the service to which the invitation is directed, and provided information indicating whether the provided information is registration benefit information or usage promotion information. The registration benefit information is information indicating that a benefit, such as points, will be given to the inviter and the invitee. On the other hand, the usage promotion information is information for promoting the use of the target service, such as information indicating convenient functions of the target service and how to use them. The registration benefit information is information provided when the invitee is not registered for the target service. On the other hand, the usage promotion information is information provided when the invitee is already registered for the target service. 3 shows an example in which the inviter is inviter A, the invitee is invitee a, the invitee a has an account shared among multiple services, the service to which the invitation is directed is service A, and the invitee a is an unregistered user of service A, and therefore registration benefit information is provided as the provided information. The contents of the provided information list 112 are registered in the post-invitation process described later (step S41 in FIG. 11).

[0032] The output information list 113 is a list of information extracted for each service from the contents of the provided information list 112. The output information list 113 is provided to each service providing server 300 for each service. For example, the output information list 113 corresponding to service A is output to the service providing server 300 that provides service A. Specifically, the output information list 113 is created for each service as shown in FIG. 4, and includes at least information about the inviter, information about the invitee, account information indicating whether the invitee has an account (an account common to multiple services), and provided information indicating whether the provided information is registration benefit information or usage promotion information.

[0033] The control unit 120 is configured with a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), etc. The control unit 120 operates in accordance with a program 111 stored in the storage unit 110, and executes processing in accordance with the program 111. The control unit 120 includes, as main functional units provided by the program 111 stored in the storage unit 110, a request acquisition unit 121, an authentication processing unit 122, an account information acquisition unit 123, target service registration information 124, a target service registration determination unit 125, a temporary code issuance unit 126, a temporary code etc. provision unit 127, a provision information output unit 128, and a fraud etc. determination unit 129.

[0034] The request acquisition unit 121 is a functional unit having a function to acquire a request from the inviter terminal 400 and a function to acquire a request from the invitee terminal 500. Specifically, the request acquisition unit 121 is a functional unit having a function to acquire a request transmitted based on an operation on the inviter terminal 400 by the inviter to make an invitation, and a function to record a request transmitted based on an operation on the invitee terminal 500 by the invitee to accept the invitation. When the request acquisition unit 121 acquires a request from the inviter terminal 400, the control unit 120 starts an invitation support process, which will be described later. When the request acquisition unit 121 acquires a request from the invitee terminal 500, the control unit 120 starts a post-invitation process, which will be described later. The request includes login information of the users of the inviter terminal 400 and the invitee terminal 500, as well as service identification information that identifies the service to which the invitation is directed. In this embodiment, the login information is composed of an email address and a password, and is part of the account information.

[0035] The authentication processing unit 122 is a functional unit that requests the account management device 200 to authenticate whether the inviter or invitee is a legitimate user. Specifically, the authentication processing unit 122 is a functional unit that transmits login information included in a request acquired by the function of the request acquisition unit 121 to the account management device 200 and requests authentication of the inviter or invitee, i.e., the user. As described above, the account information in this embodiment is account information that can be used in common among multiple services, and the same applies to login information that is a part of the account information.

[0036] The account information acquiring unit 123 is a functional unit that acquires account information corresponding to the inviter or invitee from the account management device 200. Specifically, when the account management device 200 has successfully authenticated the inviter or invitee, the account information acquiring unit 123 is a functional unit that acquires account information transmitted from the account management device 200. Note that the account information includes login information as well as the user's account name, name, gender, age, address, and payment information such as credit card or debit card.

[0037] The target service registration information acquisition unit 124 is a functional unit that acquires registration information of the target service from the service providing server 300. Specifically, the target service registration information acquisition unit 124 is a functional unit that acquires, from the service providing server 300 that provides the service to be invited, information on a list of registrants stored in the service providing server 300.

[0038] The target service registration determination unit 125 is a functional unit that determines whether or not the inviter or the invitee is registered with the target service. Specifically, the target service registration determination unit 125 is a functional unit that determines whether or not the inviter or the invitee is a registrant of the target service, based on the list information of registrants acquired by the function of the target service registration information acquisition unit 124.

[0039] The temporary code issuing unit 126 is a functional unit that issues a two-dimensional code in response to a request from the inviter. Specifically, the temporary code issuing unit 126 is a functional unit that generates a two-dimensional code including the inviter's account information and registration page information for the target service. When the invitee terminal 500 reads the two-dimensional code, the invitee logs in and transitions to a registration page for the invitation target service. Note that in this embodiment, the temporary code issuing unit 126 generates a two-dimensional code. However, other examples include issuing a URL or banner, or issuing an invitation code consisting of numbers, letters, or a combination thereof. Note that when issuing an invitation code, the invitation code may be entered, for example, in an invitation code input field displayed on the invitee terminal 500. Furthermore, for example, the temporary code may be sent directly to the invitee by specifying the invitee's email address.

[0040] The temporary code etc. providing unit 127 is a functional unit that provides temporary codes and other information. Specifically, the temporary code etc. providing unit 127 is a functional unit that has a function to provide the two-dimensional code issued by the function of the temporary code issuing unit 126 to the inviter terminal 400, and a function to provide information indicating registration benefit information or usage promotion information to the invitee terminal 500. The temporary code etc. providing unit 127 also has a function to provide a registration screen for the target service, and also has a function to provide the output information list 113 to each service providing server 300.

[0041] The provided information output unit 128 is a functional unit that registers the contents of the provided information list 112. Specifically, the provided information output unit 128 is a functional unit that has a function of outputting, in a post-invitation process described later, information on the inviter, information on the invitee, information on whether the invitee has an account, information on the target service, and provided information as the provided information list 112. The provided information output unit 128 also has a function of outputting information to the provided information list 112 and generating an output information list 113 by dividing the information in the provided information list 112 by service.

[0042] The fraud etc. determination unit 129 is a functional unit that determines whether the inviter is engaging in fraudulent behavior or is a powerful influencer based on the contents of the provided information list 112. Specifically, the fraud etc. determination unit 129 is a functional unit that calculates a two-dimensional distribution of the proportion of invitees who were not managed by the account management device 200, i.e., the proportion X of invitees who were not registered with the target service, and the proportion Y of invitees who were not registered with the target service, based on the provided information list 112, and determines that an inviter who is an outlier is engaging in fraudulent behavior or is a powerful influencer. The fraud etc. determination unit 129 has a function of determining that the invitee is engaging in fraudulent behavior if the proportion of invitees who were not registered with the account is equal to or greater than a predetermined reference value.

[0043] The input / output unit 130 is a device that is configured with a keyboard, a mouse, a camera, a microphone, a liquid crystal display, an organic EL (Electro-Luminescence) display, and the like, and is used to input and output various types of data.

[0044] The communication unit 140 is a device that enables the invitation support device 100 to communicate with other information terminals, such as the account management device 200, the service providing server 300, the inviter terminal 400, and the invitee terminal 500, via the computer communication network 800. The above is the configuration of the invitation support device 100.

[0045] (Functional configuration of the account management device) Next, the configuration of the account management device 200 will be described with reference to FIG.

[0046] As shown in FIG. 5, the account management device 200 includes a storage unit 210, a control unit 220, an input / output unit 230, a communication unit 240, and a system bus (not shown) that interconnects these units.

[0047] The storage unit 210 includes a ROM, a RAM, etc. The ROM stores a program 211 executed by the control unit 220, various data (not shown) required in advance for executing the program 211, and account information 212.

[0048] The program 211 is a program that executes an account provision process for authenticating users who are inviters and invitees and providing account information of the users, and is stored in the storage unit 210 in advance.

[0049] The account information 212 is information for uniquely identifying users who are inviters and invitees, and includes information on multiple users, as shown in Fig. 6. As shown in the figure, the account information 212 includes at least the user's login information, such as an email address and password, as well as the user's account name, name, gender, age, address, and payment information (such as name and other information) for credit cards, debit cards, etc.

[0050] The control unit 220 is configured with a CPU, an ASIC, etc. The control unit 220 operates in accordance with a program 211 stored in the storage unit 210, and executes processing in accordance with the program 211. The control unit 220 includes a user authentication unit 221 and an account information providing unit 222 as main functional units provided by the program 211 stored in the storage unit 210.

[0051] The user authentication unit 221 is a functional unit that authenticates a user in response to a request from the invitation support device 100. Specifically, the user authentication unit 221 has a function of authenticating whether an inviter or an invitee, whose authentication is requested by the function of the authentication processing unit 122 of the invitation support device 100, is a legitimate user, based on the login information of the inviter or the invitee.

[0052] The account information providing unit 222 is a functional unit that provides the user's account information 212 to the invitation support device 100. Specifically, when user authentication based on the login information of the inviter or invitee is successful, the account information providing unit 222 has a function of providing the invitation support device 100 with the account information 212 corresponding to the login information.

[0053] The input / output unit 330 is a device that includes a keyboard, a mouse, a camera, a microphone, a liquid crystal display, an organic EL display, and the like, and is used to input and output various types of data.

[0054] The communication unit 240 is a device that enables the account management device 200 to communicate with other information terminals such as the invitation support device 100, the inviter terminal 400, and the invitee terminal 500 via the computer communication network 800. The above is the configuration of the account management device 200.

[0055] (operation) Next, the operation of the invitation support device 100 will be described. First, the invitation support process in the invitation support device 100 will be described. The invitation support process is a process performed in the invitation support device 100 until the inviter invites the invitee. FIG. 7 is a flowchart showing an example of the invitation support process in the invitation support device 100. As described above, the invitation support process in this embodiment starts when the request acquisition unit 121 acquires a request from the inviter terminal 400. Specifically, first, as shown in FIG. 8, the inviter performs an invitation operation on the inviter terminal 400 (in the illustrated example, a tap operation on the "Invite Here" button). Next, as shown in FIG. 9, a login screen is displayed on the inviter terminal 400, and when the inviter performs a login operation, a request is transmitted from the inviter terminal 400 to the invitation support device 100. As a result, the request acquisition unit 121 acquires the request from the inviter terminal 400, and the invitation support process starts. Note that, as described above, the request includes service identification information that identifies the service to be invited, in addition to the login information of the user of the inviter terminal 400. In this embodiment, the login information is composed of a combination of an email address and a password.

[0056] When the invitation support process is started, the control unit 120 requests authentication of the user using the function of the authentication processing unit 122 (step S11). Specifically, in the process of step S11, the authentication processing unit 122 transmits an authentication request to the account management device 200 to request authentication of the user based on the login information included in the request acquired by the request acquisition unit 121.

[0057] On the account management device 200 side, when an authentication request is received from the invitation support device 100, the account providing process is started. When the account providing process is started, the control unit 220 authenticates the user using the function of the user authentication unit 221 and determines whether the authentication is successful or not (step S12). Specifically, in the process of step S12, the user authentication unit 221 determines whether the authentication is successful or not by checking whether the login information of the inviter included in the received authentication request is a combination registered in the account information 212.

[0058] If it is determined that the authentication is successful in the processing of step S12 (step S12; Yes), the control unit 220 provides the user's account information using the function of the account information providing unit 222 (step S13), and ends the account providing processing. Specifically, in the processing of step S13, the account information providing unit 222 provides the invitation support device 100 with the account information 212 corresponding to the login information that was successfully authenticated in the processing of step S12. On the other hand, if it is determined that the authentication is unsuccessful in the processing of step S12 (step S12; No), the control unit 220 notifies the invitation support device 100 that no account is registered (step S14), and ends the account providing processing. Specifically, in the processing of step S14, the control unit 220 notifies the invitation support device 100 that the inviter has an unregistered account. Note that in the processing of step S14, for example, it may be notified that there is an error in the login information.

[0059] After executing the processing of step S13 or step S14, the invitation support device 100 determines whether or not it has been notified that the account is not registered (step S15). Specifically, in the processing of step S15, the control unit 120 determines whether or not it has been notified by the account management device 200 that the inviter does not have an account registered. Note that in the processing of step S15, the control unit 120 may determine that it has been notified that the account is not registered because it has not acquired account information from the account management device 200 using the function of the account information acquisition unit 123. If it is determined in the processing of step S15 that the account is not registered (step S15; Yes), the control unit 120 cooperates with the account management device 200 to prompt the inviter terminal 400 to register the account, and performs the registration (step S16).

[0060] After executing the process of step S16, or if it is determined in the process of step S15 that an account is registered (step S15; No), that is, if the account information has been acquired from the account management device 200 by the function of the account information acquisition unit 123, the control unit 120 acquires target service registration information by the function of the target service registration information acquisition unit 124 (step S17). Specifically, in the process of step S17, the target service registration information acquisition unit 124 acquires, from the service providing server 300 that provides the service to be invited, target service registration information that is information on a list of registrants stored in the service providing server 300. Note that the service providing server 300 that provides the service identified by the service identification information included in the acquired request may be identified as the service providing server 300 from which the information is to be acquired.

[0061] After acquiring the target service registration information in the process of step S17, the control unit 120 determines whether the invitee is registered with the target service using the function of the target service registration determination unit 125 (step S18). Specifically, in the process of step S18, the target service registration determination unit 125 determines whether the invitee is registered with the target service by checking whether account information corresponding to the invitee is registered in the acquired target service registration information. Note that in this embodiment, an example is shown in which the target service registration information is acquired from the service providing server 300 in the process of step S17, and the invitation support device 100 determines whether the invitee is registered by executing the process of step S18. However, for example, it is also possible to send a registration confirmation request from the invitation support device 100, and the service providing server 300 determines whether the invitee is registered and transmits the result to the invitation support device 100.

[0062] In the process of step S18, if it is determined that there is no registration (step S18; No), that is, if the inviter is not a registrant of the target service, the control unit 120 cooperates with the service providing server 300 to provide a registration screen to the inviter terminal 400 to prompt registration (step S19), and ends the invitation support process. Note that in this embodiment, an example is shown in which the invitation support process ends after the process of step S19 is executed, but after the process of step S19 is executed, the process may proceed to the process of step S20, which will be described later.

[0063] On the other hand, if it is determined in the processing of step S18 that registration exists (step S18; Yes), that is, if the inviter is a registrant of the target service, the control unit 120 generates a temporary code using the function of the temporary code issuing unit 126 (step S20). Specifically, in the processing of step S20, the temporary code issuing unit 126 generates a two-dimensional code including the inviter's account information and registration page information for the target service. Note that the inviter's account information included in the two-dimensional code may be information that can identify the inviter. Furthermore, an expiration date may be set for the temporary code generated in the processing of step S20, and the expiration date may be provided to the inviter in a visible manner.

[0064] After executing the processing of step S20, the control unit 120 uses the functions of the temporary code issuing unit 126 and the temporary code etc. providing unit 127 to provide the temporary code generated in the processing of step S20 to the inviter terminal 400 (step S21), and ends the invitation support processing. Specifically, in the processing of step S21, the temporary code etc. providing unit 127 provides the two-dimensional code generated in the processing of step S20 to the inviter terminal 400 and displays it on the display unit, as shown in Fig. 10. This makes it possible for the invitee terminal 500 to read the two-dimensional code.

[0065] The above is the operation of the invitation support process in the invitation support device 100. Note that, in this embodiment, for ease of understanding, an example is shown in which, if authentication of the inviting user is successful in the process of step S12, the account information of the user is provided in the process of step S13, and the process proceeds to the process of step S15 and thereafter; however, if once the user has been authenticated, if multiple services are to be consecutively invited, the processes of steps S11 to S16 may be skipped. In other words, once the user has been successfully authenticated, multiple services can be invited without the need for login operations. Note that the period during which login is not required can be set in advance and can be changed as desired.

[0066] Next, post-invitation processing in the invitation support device 100 will be described. The post-invitation processing is processing performed by the invitation support device 100 when the invitee is invited to a target service by the inviter. FIG. 11 is a flowchart showing an example of the post-invitation processing in the invitation support device 100. The post-invitation processing in this embodiment starts when the request acquisition unit 121 acquires a request from the invitee terminal 500. Specifically, as shown in FIG. 12, first, the temporary code displayed on the inviter terminal 400 is read by the invitee terminal 500. Next, as shown in FIG. 13, a login screen is displayed on the invitee terminal 500, and when the invitee performs a login operation, a request is transmitted from the invitee terminal 500 to the invitation support device 100. As a result, the request acquisition unit 121 acquires the request from the invitee terminal 500, and the post-invitation processing starts. Note that, as described above, the request includes service identification information that identifies the service to be invited, in addition to the login information of the user of the invitee terminal 500.

[0067] When the post-invitation process is started, the control unit 120 requests authentication of the user using the function of the authentication processing unit 122 (step S31). Specifically, similar to the process of step S11 shown in Fig. 7, the authentication processing unit 122 transmits an authentication request to the account management device 200 to request authentication of the user based on the login information included in the request acquired by the request acquisition unit 121 in the process of step S31 in Fig. 11.

[0068] On the account management device 200 side, when an authentication request is received from the invitation support device 100, the account providing process is started. When the account providing process is started, the control unit 220 authenticates the user using the function of the user authentication unit 221 and determines whether the authentication is successful or not (step S32). Specifically, in the process of step S12, the user authentication unit 221 determines whether the authentication is successful or not by checking whether the login information of the invitee included in the received authentication request is a combination registered in the account information 212.

[0069] If it is determined that the authentication is successful in the processing of step S32 (step S32; Yes), the control unit 220 provides the user's account information using the function of the account information providing unit 222 (step S33), and ends the account providing processing. Specifically, in the processing of step S33, the account information providing unit 222 provides the invitation support device 100 with the account information 212 corresponding to the login information that was successfully authenticated in the processing of step S32. On the other hand, if it is determined that the authentication is unsuccessful in the processing of step S32 (step S32; No), the control unit 220 notifies the invitation support device 100 that no account is registered (step S34), and ends the account providing processing. Specifically, in the processing of step S34, the control unit 220 notifies the invitation support device 100 that the invitee does not have a registered account. Note that in the processing of step S34, for example, it may be notified that there is an error in the login information.

[0070] After executing the processing of step S33 or step S34, the invitation support device 100 determines whether or not it has been notified that the account is not registered (step S35). Specifically, in the processing of step S35, the control unit 120 determines whether or not it has been notified by the account management device 200 that the invitee does not have an account registered. Note that in the processing of step S35, the control unit 120 may determine that it has been notified that the account is not registered because it has not acquired account information from the account management device 200 using the function of the account information acquisition unit 123. If it is determined in the processing of step S35 that the account is not registered (step S35; Yes), the control unit 120 cooperates with the account management device 200 to prompt the invitee terminal 400 to register the account, and performs the registration (step S36).

[0071] After executing the process of step S36, or if it is determined in the process of step S35 that an account is registered (step S35; No), that is, if the account information has been acquired from the account management device 200 by the function of the account information acquisition unit 123, the control unit 120 acquires target service registration information by the function of the target service registration information acquisition unit 124 (step S37). Specifically, in the process of step S37, the target service registration information acquisition unit 124 acquires, from the service providing server 300 that provides the service to be invited, target service registration information that is information on a list of registrants stored in the service providing server 300. Note that the service providing server 300 that provides the service identified by the service identification information included in the acquired request may be identified as the service providing server 300 from which the information is to be acquired.

[0072] After acquiring the target service registration information in the process of step S37, the control unit 120 determines whether the invitee is registered with the target service using the function of the target service registration determination unit 125 (step S38). Specifically, in the process of step S38, the target service registration determination unit 125 determines whether the invitee is registered with the target service by checking whether account information corresponding to the invitee is registered in the acquired target service registration information. Note that in this embodiment, an example is shown in which the target service registration information is acquired from the service providing server 300 in the process of step S37 and the invitation support device 100 determines whether the invitee is registered by executing the process of step S38. However, for example, it is also possible to send a registration confirmation request from the invitation support device 100, and the service providing server 300 determines whether the invitee is registered and transmits the result to the invitation support device 100.

[0073] In the process of step S38, if it is determined that there is no registration (step S38; No), that is, if the invitee is not a registrant of the target service, the control unit 120 uses the function of the temporary code etc. providing unit 127 to provide registration benefit information to the invitee terminal 400 (step S39). Specifically, in the process of step S39, the temporary code etc. providing unit 127 provides registration benefit information to the invitee terminal 400, which notifies the invitee of the benefits that can be obtained by registering, as shown in Fig. 14 .

[0074] On the other hand, if it is determined in the processing of step S38 that registration exists (step S38; Yes), that is, if the invitee is already a registrant of the target service, the control unit 120 provides usage promotion information to the invitee terminal 400 by the function of the temporary code etc. providing unit 127 (step S40). Specifically, in the processing of step S40, the temporary code etc. providing unit 127 provides information to the invitee terminal 400 to promote the use of the target service by displaying a notice to the invitee about convenient services in the target service, as shown in Fig. 15 .

[0075] 11 , the control unit 120 uses the function of the provided information output unit 128 to output the provided information and the like as the provided information list 112 (step S41). Specifically, in the process of step S41, the provided information output unit 128 associates the content provided in the process of step S30 or step S40 as provided information with information about the inviter, information about the invitee, information about whether the invitee has an account, and information about the target service, and outputs the resulting information as the provided information list 112. In addition to the provided information list 112, the process of step S41 may also output an output information list 113, which is a list of information obtained by extracting the content of the provided information list 112 for each service. The output information list 113 may be periodically provided to each service providing server 300. Based on the content of the provided output information list 113, benefits may be granted to the inviter and the invitee by each service providing server 300.

[0076] After executing the process of step S41, the control unit 120 determines whether the inviter has engaged in fraudulent behavior using the function of the fraud determination unit 129 (step S42), and terminates the post-invitation process. Specifically, in the process of step S42, the fraud determination unit 129 calculates a two-dimensional distribution of the proportion of invitees who have not registered accounts and the proportion of invitees who have not registered for the target service based on the provided information list 112. For an inviter who is an outlier, if the proportion of invitees who have not registered accounts is equal to or greater than a predetermined reference value, the fraud determination unit 129 determines that the inviter is engaging in fraudulent behavior. Otherwise, the inviter is determined to be a powerful influencer. Note that, for an inviter determined to be engaging in fraudulent behavior in the process of step S42, the corresponding account information may be notified to each service providing server 300 as a fraudulent inviter. Each service providing server 300 may then restrict the granting of benefits to the introducer identified by the notification.

[0077] The above is the operation of the invitation support device 100. As described above, according to the invitation support device 100 of this embodiment, a common account is used across multiple services, and once login authentication is completed, invitations to multiple services can be made consecutively. This eliminates the need to log in for each service to which an invitation is made, and makes it easier to process invitations across various services.

[0078] Furthermore, according to the invitation support device 100 of this embodiment, if the invitee is already registered with the target service, usage promotion information that promotes the use of the service is provided. Therefore, it is possible to provide appropriate information depending on whether the invitee has already registered with the target service.

[0079] Furthermore, the invitation support device 100 in this embodiment can determine inviters who are engaging in fraudulent activities, such as fraudulently acquiring invitees to receive benefits.

[0080] (Variation) It should be noted that the present invention is not limited to the above-described embodiments, and various modifications and applications are possible. For example, the invitation support device 100 and the account management device 200 according to the above-described embodiments do not need to have all of the technical features described above, but may have some of the configurations described in the above-described embodiments so as to solve at least one problem in the prior art. Furthermore, at least a portion of each of the following modifications may be combined.

[0081] In the above embodiment, the example of acquiring target service registration information, which is a list of registrants stored in the service providing server 300, in the processing of step S17 in Fig. 7 or step S37 in Fig. 11 is shown, but this is just one example. The target service registration information may be stored in advance in the storage unit 110 of the invitation support device 100. Also, as described above, it is also possible to inquire of each service providing server 300 about whether the inviter or invitee has registered a service, without acquiring the target service registration information.

[0082] In the above embodiment, in the process of step S41 shown in FIG. 11 , the fraud determination unit 129 determines fraud by calculating a two-dimensional distribution of the percentage of unregistered accounts among invitees and the percentage of unregistered target services among invitees. However, this is merely an example. For example, a four-dimensional distribution (four-dimensional distribution of X, Y, A, and B) of the number of unregistered accounts among invitees A and the number of unregistered target services among invitees B may be calculated to determine whether an outlier inviter is engaging in fraudulent behavior or a powerful influencer. Furthermore, the content of the benefit to be granted to the invitee user may be determined based on the percentage of unregistered accounts among invitees, the percentage of unregistered target services among invitees, the number of unregistered accounts among invitees, and the number of unregistered target services among invitees. That is, different types of registration benefit information may be provided to the invitee terminal 500 based on the percentage of unregistered accounts among invitees, the percentage of unregistered target services among invitees, the number of unregistered accounts among invitees, and the number of unregistered target services among invitees. In addition, so that the more invitees an inviter has, the greater the rewards the invitee can receive, for example, by providing registration reward information to the invitee terminal 500 indicating that the reward is 1,000 points for an invitee with 3 to 10 invitees, and providing registration reward information to the invitee terminal 500 indicating that the reward is 1,500 points for an invitee with 11 to 30 invitees. This allows the rewards to vary depending on the number of invitees, thereby encouraging users to invite others. Furthermore, fraudulent activity may be determined based solely on the proportion of invitees not managed by the account management device 200, i.e., the linear distribution of only the proportion X of invitees whose accounts are not registered.

[0083] In the above embodiment, for ease of understanding, if authentication of the invitee user is successful in the processing of step S32, the user's account information is provided in the processing of step S33, and the processing proceeds to step S35 and subsequent steps. However, if the user is once authenticated and then invited to multiple services consecutively, the processing of steps S31 to S36 may be skipped. In other words, once the user authentication is successful, the invitee can receive invitations to multiple services without the need for login operations. This eliminates the need to log in for each service to which an invitation is to be received, and also facilitates the processing of receiving invitations from various services. The period during which login is not required may be set in advance and may be freely changeable.

[0084] The invitation support device 100 and account management device 200 according to the above-described embodiments can be realized using a normal computer, rather than using dedicated devices. For example, the invitation support device 100 that executes the above-described processes may be configured by installing a program for executing any of the above processes on a computer from a recording medium that stores the program. Also, a single invitation support device 100 and account management device 200 may be configured by multiple computers operating in cooperation with each other.

[0085] Furthermore, when the above-mentioned functions are realized by sharing the functions between an OS (Operating System) and an application, or by cooperation between the OS and the application, only the parts other than the OS may be stored on the medium.

[0086] It is also possible to superimpose the program on a carrier wave and distribute it via a communication network. For example, the program may be posted on a bulletin board system (BBS) on the communication network and distributed via the network. These programs may then be started and run under the control of an operating system in the same way as other application programs, thereby enabling the above-mentioned processing to be performed.

[0087] Various aspects of the present disclosure are summarized below as appendices.

[0088] (Appendix 1) a request information acquisition unit that acquires request information including information on a service to which an inviter user is invited and login information of the inviter user; an authentication request unit that requests authentication of the guest user based on the login information acquired by the request information acquisition unit; a temporary code generating unit that generates a temporary code including information for identifying the inviter user and information about the service when the authentication requested by the authentication requesting unit is successful and the inviter user has already registered for the service to which the invitee is invited; The login information can be used in common across multiple services. An invitation support device characterized by:

[0089] (Appendix 2) an account information acquiring means for acquiring account information of the guest user corresponding to the login information when the authentication requested by the authentication requesting unit is successful; a determination result acquisition unit that acquires a determination result of whether the inviter user has registered with the service to which the invitee is invited, based on the account information acquired by the account information acquisition unit; the temporary code generation unit generates the temporary code when the determination result acquisition unit determines that the inviter user has already registered with the service to which the invitee is invited. 2. The invitation support device according to claim 1,

[0090] (Appendix 3) the determination result acquisition unit acquires a determination result as to whether the inviter user has registered for the service to which the invitee user is invited by inquiring of a service providing server that provides the service to which the invitee user is invited; 3. The invitation support device according to claim 2,

[0091] (Appendix 4) the determination result acquisition unit determines whether the inviter user has registered for the service to which the invitee user is invited based on registration information acquired from a service providing server that provides the service to which the invitee user is invited, and acquires the determination result. 3. The invitation support device according to claim 2,

[0092] (Appendix 5) a temporary code providing unit that provides the temporary code generated by the temporary code generating unit to the inviter terminal owned by the inviter user; the request information acquisition unit acquires request information including information on the service to which the invitee user is invited and login information of the invitee user, based on the fact that the temporary code provided to the inviter terminal by the temporary code provision unit is acquired by the invitee terminal owned by the invitee user; the authentication request unit requests authentication of the invited user based on the login information of the invited user acquired by the request information acquisition unit; a notification information providing unit that, when the authentication request unit has succeeded in the authentication requested by the invited user and the invited user has already registered for the service to which the invited user has been invited, provides the invited user terminal with usage promotion information that promotes the use of the service, and, when the invited user has not yet registered for the service to which the invited user has been invited, provides the invited user terminal with registration benefit information that can be obtained by the invited user registering; The invitation support device according to any one of Supplementary notes 1 to 4 further comprises:

[0093] (Appendix 6) a provision information output unit that outputs provision information in which information of the inviting user identified from the temporary code, information of the service identified from the temporary code, information of the invited user who has acquired the temporary code, and information indicating whether the information provided by the notification information providing unit is the use promotion information or the registration benefit information are associated with each other; The invitation support device according to Supplementary Note 5 further comprises:

[0094] (Appendix 7) an output information transmitting unit that transmits the provided information output by the provided information output unit, output information extracted for each piece of information on the service identified from the temporary code, to a service providing server that provides the corresponding service; The invitation support device according to Supplementary Note 6 further comprises:

[0095] (Appendix 8) a fraud determination unit that determines fraudulent behavior by the inviter user based on an outlier of a two-dimensional distribution based on a ratio of the invitee users who failed the authentication requested by the authentication request unit and a ratio of the invitee users who were not registered with the service to which they were invited, The invitation support device according to Supplementary Note 6 further comprises:

[0096] (Appendix 9) The fraud determination unit determines fraudulent behavior by the inviter user based on an outlier of a four-dimensional distribution for the inviter user, which is based on the ratio of the invitee users who failed the authentication requested by the authentication request unit among the invitee users invited by the inviter user, the ratio of the invitee users who were not registered in the service to which the invitee users were invited, the number of the invitee users who failed the authentication requested by the authentication request unit, and the number of the invitee users who were not registered in the service to which the invitee users were invited. 9. The invitation support device according to claim 8,

[0097] (Appendix 10) The notification information providing unit provides different types of registration benefit information according to the ratio of the invited users who failed the authentication requested by the authentication requesting unit, the ratio of the invited users who were not registered with the service to which they were invited, the number of the invited users who failed the authentication requested by the authentication requesting unit, and the number of the invited users who were not registered with the service to which they were invited. 7. The invitation support device according to claim 6,

[0098] (Appendix 11) An invitation support method using an invitation support device, a request information acquisition step of acquiring request information including information on a service to which the inviter user is invited and login information of the inviter user; an authentication request step of requesting authentication of the guest user based on the login information acquired in the request information acquisition step; a temporary code generating step of generating a temporary code including information for identifying the inviter user and information about the service when the authentication requested in the authentication requesting step is successful and the inviter user has already registered for the service to which the invitee is invited; The login information can be used in common across multiple services. An invitation support method.

[0099] (Appendix 12) Computer, a request information acquisition unit that acquires request information including information on a service to which an inviter user is invited and login information of the inviter user; an authentication request unit that requests authentication of the guest user based on the login information acquired by the request information acquisition unit; a temporary code generating unit that generates a temporary code including information for identifying the inviter user and information about the service when the authentication requested by the authentication requesting unit is successful and the inviter user is already registered with the service to which the invitee is invited; The login information can be used in common across multiple services. A program characterized by:

[0100] The present disclosure allows various embodiments and modifications without departing from the broad spirit and scope of the present disclosure. Furthermore, the above-described embodiments are intended to illustrate the present disclosure and do not limit the scope of the present disclosure. That is, the scope of the present disclosure is defined by the claims, not the embodiments. Various modifications made within the scope of the claims and the meaning of equivalent disclosures are considered to be within the scope of the present disclosure. [Industrial Applicability]

[0101] According to the present invention, it is possible to provide an invitation support device, an invitation support method, and a program that can facilitate the process of making an invitation for various services. [Explanation of symbols]

[0102] 100 Invitation support device 110, 310 Storage section 111, 311 Program 112 List of provided information 113 Output Information List 120, 320 control section 121 Request Acquisition Unit 122 Authentication processing section 123 Account Information Acquisition Unit 124 Target service registration information acquisition unit 125 Target service registration determination unit 126 Temporary Code Issuance Department 127 Temporary Code Provision Department 128 Provided information output section 129 Fraud Determination Department 130, 230 input / output section 140, 240 Communications Department 200 Account Management Device 212 Account Information 221 User authentication section 222 Account Information Department 300 Service provider server 313 Viewing Information 321 Request Reception Department 322 Storage Usage Settings 400 Invitee Terminal 500 Invitee terminal 800 Computer Network

Claims

1. a request information acquisition unit that acquires request information including information on a service to which an inviter user is invited and login information of the inviter user; an authentication request unit that requests authentication of the guest user based on the login information acquired by the request information acquisition unit; a temporary code generating unit that generates a temporary code including information for identifying the inviter user and information about the service when the authentication requested by the authentication requesting unit is successful and the inviter user has already registered for the service to which the invitee is invited; The login information can be used in common across multiple services. An invitation support device characterized by:

2. an account information acquiring means for acquiring account information of the guest user corresponding to the login information when the authentication requested by the authentication requesting unit is successful; a determination result acquisition unit that acquires a determination result of whether the inviter user has registered with the service to which the invitee is invited, based on the account information acquired by the account information acquisition unit; the temporary code generation unit generates the temporary code when the determination result acquisition unit determines that the inviter user has already registered with the service to which the invitee is invited. The invitation support device according to claim 1 .

3. the determination result acquisition unit acquires a determination result as to whether the inviter user has registered for the service to which the invitee user is invited by inquiring of a service providing server that provides the service to which the invitee user is invited; 3. The invitation support device according to claim 2.

4. the determination result acquisition unit determines whether the inviter user has registered for the service to which the invitee user is invited based on registration information acquired from a service providing server that provides the service to which the invitee user is invited, and acquires the determination result.

3. The invitation support device according to claim 2.

5. a temporary code providing unit that provides the temporary code generated by the temporary code generating unit to the inviter terminal owned by the inviter user; the request information acquisition unit acquires request information including information on the service to which the invitee user is invited and login information of the invitee user, based on the fact that the temporary code provided to the inviter terminal by the temporary code provision unit is acquired by the invitee terminal owned by the invitee user; the authentication request unit requests authentication of the invited user based on the login information of the invited user acquired by the request information acquisition unit; a notification information providing unit that, when the authentication request unit has succeeded in the authentication requested by the invited user and the invited user has already registered for the service to which the invited user has been invited, provides the invited user terminal with usage promotion information that promotes the use of the service, and, when the invited user has not yet registered for the service to which the invited user has been invited, provides the invited user terminal with registration benefit information that can be obtained by the invited user registering; The invitation support device according to any one of claims 1 to 4, further comprising:

6. a provision information output unit that outputs provision information in which information of the inviting user identified from the temporary code, information of the service identified from the temporary code, information of the invited user who has acquired the temporary code, and information indicating whether the information provided by the notification information providing unit is the use promotion information or the registration benefit information are associated with each other; The invitation support device according to claim 5 further comprises:

7. an output information transmitting unit that transmits the provided information output by the provided information output unit, output information extracted for each piece of information on the service identified from the temporary code, to a service providing server that provides the corresponding service; The invitation support device according to claim 6 further comprising:

8. a fraud determination unit that determines fraudulent activity by the inviter user based on an outlier of a two-dimensional distribution for the inviter user, the outlier being determined based on the ratio of the invitee users who failed the authentication requested by the authentication request unit and the ratio of the invitee users who were not registered in the service to which they were invited, among the inviter users invited by the inviter user; The invitation support device according to claim 6 further comprising:

9. The fraud determination unit determines fraudulent behavior by the inviter user based on an outlier of a four-dimensional distribution for the inviter user, which is based on the ratio of the invitee users who failed the authentication requested by the authentication request unit among the invitee users invited by the inviter user, the ratio of the invitee users who were not registered in the service to which the invitee users were invited, the number of the invitee users who failed the authentication requested by the authentication request unit, and the number of the invitee users who were not registered in the service to which the invitee users were invited.

9. The invitation support device according to claim 8.

10. The notification information providing unit provides different types of registration benefit information according to the ratio of the invited users who failed the authentication requested by the authentication requesting unit, the ratio of the invited users who were not registered with the service to which they were invited, the number of the invited users who failed the authentication requested by the authentication requesting unit, and the number of the invited users who were not registered with the service to which they were invited.

7. The invitation support device according to claim 6.

11. An invitation support method using an invitation support device, a request information acquisition step of acquiring request information including information on a service to which the inviter user is invited and login information of the inviter user; an authentication request step of requesting authentication of the guest user based on the login information acquired in the request information acquisition step; a temporary code generating step of generating a temporary code including information for identifying the inviter user and information about the service when the authentication requested in the authentication requesting step is successful and the inviter user has already registered for the service to which the invitee is invited; The login information can be used in common across multiple services. An invitation support method.

12. Computer, a request information acquisition unit that acquires request information including information on a service to which an inviter user is invited and login information of the inviter user; an authentication request unit that requests authentication of the guest user based on the login information acquired by the request information acquisition unit; a temporary code generating unit that generates a temporary code including information for identifying the inviter user and information about the service when the authentication requested by the authentication requesting unit is successful and the inviter user is already registered with the service to which the invitee is invited; The login information can be used in common across multiple services. A program characterized by:

Images