INVITATION SUPPORT DEVICE, INVITATION SUPPORT METHOD, AND PROGRAM

Abstract

An invitation support device, an invitation support method, and a program are provided that can facilitate processing when making invitations for various services. [Solution] Request information including information on a service to which a guest user is invited and login information of the guest user is obtained, and authentication of the guest user is requested based on the login information. Then, if the authentication is successful and the guest user is already registered with the service to which the guest user is invited, a temporary code including information for identifying the guest user and information on the service is generated. The login information can be commonly used for multiple services.

Description

Technical Field

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

Background Art

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

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, there is room for improvement in the above system from the viewpoint of facilitating the processing when issuing invitations in various services.

[0005] The present invention solves the above problems, and an object thereof is to provide an invitation support device, an invitation support method, and a program capable of facilitating the processing when issuing invitations in various services.

Means for Solving the Problems

[0006] The invitation support device according to the first aspect of the present invention a request information acquisition unit that acquires request information including information on a service to be invited by an inviter user and login information of the inviter user; An authentication request unit that requests authentication of the inviter user based on the login information acquired by the request information acquisition unit; A temporary code generation unit that generates a temporary code including information for identifying the inviter user and information on the service when the authentication requested by the authentication request unit is successful and the inviter user is registered in the service to be invited by the inviter user. The login information is commonly usable in a plurality of the services. It is characterized by this.

[0007] Also, in the invitation support device according to the above aspect, Account information acquisition means for acquiring the account information of the inviter user corresponding to the login information when the authentication requested by the authentication request unit is successful; A determination result acquisition unit that acquires a determination result as to whether or not the inviter user is registered in the service to be invited by the inviter user based on the account information acquired by the account information acquisition means. The temporary code generation unit generates the temporary code when the determination result acquisition unit determines that the inviter user is registered in the service to be invited by the inviter user. It is characterized by this.

[0008] Also, in the invitation support device according to the above aspect, The determination result acquisition unit acquires a determination result as to whether or not the inviter user is registered in the service to be invited by the inviter user by inquiring a service providing server that provides the service to be invited by the inviter user. It is characterized by this.

[0009] Also, in the invitation support device according to the above aspect, The determination result acquisition unit determines whether or not the inviter user is registered in the service to be invited by the inviter user based on the registration information acquired from the service providing server that provides the service to be invited by the inviter user, and acquires the determination result. It is characterized by the following.

[0010] Also, in the invitation support device according to the above aspect, It further includes a temporary code providing unit that provides the temporary code generated by the temporary code generation unit to the invitation terminal owned by the inviter user. Based on the fact that the temporary code provided to the invitation terminal by the temporary code providing unit is acquired by the invitee terminal owned by the invitee user, the request information acquisition unit acquires request information including information on the service for which the invitee user is invited and the login information of the invitee user. The authentication request unit requests authentication of the invitee user based on the login information of the invitee user acquired by the request information acquisition unit. When the authentication request unit succeeds in the authentication requested by the invitee user and the invitee user is already registered for the service for which the invitee user is invited, it provides utilization promotion information for promoting the use of the service to the invitee terminal. When the invitee user is not registered for the service for which the invitee user is invited, it provides registration privilege information obtained by the invitee user's registration to the invitee terminal. It is characterized by further including an information providing unit. It is characterized by further including the following.

[0011] Also, in the invitation support device according to the above aspect, It further includes a provided information output unit that outputs provided information in which the information of the inviter user specified from the temporary code, the information of the service specified from the temporary code, the information of the invitee user who acquired the temporary code, and the information indicating whether the information provided by the information providing unit is the utilization promotion information or the registration privilege information are respectively associated. It is characterized by further including the following.

[0012] Also, in the invitation support device according to the above aspect, An output information transmission unit that transmits the provided information output by the provided information output unit to a service providing server that provides a service corresponding to each of the output information extracted for each piece of information of the service specified from the temporary code. It is characterized by further comprising.

[0013] Also, in the invitation support device according to the above aspect, Among the invitee users invited by the inviter user, based on the ratio of the invitee users who failed the authentication requested by the authentication request unit and the ratio of those who were not registered for the service targeted by the invitee users, an irregularity determination unit that determines an act of fraud by the inviter user based on an outlier of a two-dimensional distribution for the inviter user. It is characterized by further comprising.

[0014] Also, in the invitation support device according to the above aspect, The irregularity determination unit determines an act of fraud by the inviter user based on an outlier of a four-dimensional distribution for the inviter user, 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 those who were not registered for the service targeted by the invitee users, the number of invitee users who failed the authentication requested by the authentication request unit, and the number of those who were not registered for the service targeted by the invitee users. This is characterized by.

[0015] Also, in the invitation support device according to the above aspect, The notification information providing unit provides registration privilege information in different modes according to the ratio of the invitee users who failed the authentication requested by the authentication request unit among the invitee users, the ratio of those who were not registered for the service targeted by the invitee users, the number of invitee users who failed the authentication requested by the authentication request unit, and the number of those who were not registered for the service targeted by the invitee users. This is characterized by.

[0016] The invitation support method according to the second aspect of the present invention is an invitation support method by an invitation support device, including a request information acquisition step of acquiring request information including information on a service targeted by an inviter user and login information of the inviter user; an authentication request step of requesting authentication of the inviter user based on the login information acquired in the request information acquisition step; a temporary code generation step of generating a temporary code including information for identifying the inviter user and information on the service when the authentication requested in the authentication request step is successful and the inviter user is registered for the service targeted by the inviter user, wherein the login information is commonly usable in a plurality of the services. Characterized in that.

[0017] The program according to the third aspect of the present invention is to cause a computer to function as a request information acquisition unit that acquires request information including information on a service targeted by an inviter user and login information of the inviter user, an authentication request unit that requests authentication of the inviter user based on the login information acquired by the request information acquisition unit, and a temporary code generation unit that generates a temporary code including information for identifying the inviter user and information on the service when the authentication requested by the authentication request unit is successful and the inviter user is registered for the service targeted by the inviter user, wherein the login information is commonly usable in a plurality of the services. Characterized in that.

[0018] The above 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 non-transitory recording medium refers to a tangible recording medium. Examples of the non-transitory recording medium include a compact disc, a flexible disc, a hard disk, a magneto-optical disk, a digital video disc, a magnetic tape, a semiconductor memory, and the like. Also, the transitory recording medium refers to the transmission medium (propagation signal) itself. Examples of the transitory recording medium include an electric signal, an optical signal, an electromagnetic wave, and the like. Note that the temporary memory area is an area for temporarily storing data and programs, and is, for example, a volatile memory such as a RAM (Random Access Memory).

Effects of the Invention

[0019] According to the present invention, it is possible to provide an invitation support apparatus, an invitation support method, and a program that can facilitate processing when making invitations in various services.

Brief Description of the Drawings

[0020]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Embodiments for Carrying Out the Invention

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

[0022] The invitation support apparatus 100 is a computer such as a server, and has a function of supporting an invitation for service registration from an inviter who is a user of the inviter terminal 400 to an invitee who is a user of the invitee terminal 500. Specifically, the invitation support apparatus 100 supports an invitation for a service that an inviter invites an invitee to, using account information common among a plurality of services. For example, when inviter A is a user of three services, service A, service C, and service E, the invitation support apparatus 100 checks the usage status of each service of inviter A based on the account information common to the three services, and generates invitation information to be provided to the invitee.

[0023] The account management device 200 is a server that manages account information common among a plurality of services. Specifically, the account management device 200 has a function of performing user authentication based on the account information common among a plurality of services in accordance with 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, the service providing server 300 is provided for each service, and registration information indicating a list of users who are registrants is stored in each service providing server 300. That is, the service providing server 300 stores list information of registrants and has a function of providing the list information of the registrants 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 a user who is an inviter. Note that there are a plurality of inviter terminals 400. Also, when a user who is the owner of the inviter terminal 400 receives an invitation from another user, the inviter terminal 400 functions as the invitee terminal 500. That is, the inviter terminal 400 may 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 a user who is an invitee. Note that there are a plurality of invitee terminals 500. Also, when a user who is the owner of the invitee terminal 500 invites another user, the invitee terminal 500 functions as the inviter terminal 400. That is, the invitee terminal 500 may function as the inviter terminal 400.

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

[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 components.

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

[0030] The program 111 is a program that executes the invitation support process and the post-invitation process, which will be described later, 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 the information of the inviter, the information of the invitee, the account information indicating the presence or absence of the invitee's account (an account common among multiple services), the information of the target service indicating the service to be invited, and the provided information indicating whether the provided information is registration privilege information or utilization promotion information. The registration privilege information is information indicating that a privilege such as awarding points is given to the inviter and the invitee. On the other hand, the utilization promotion information is information for promoting the use of the target service, for example, information indicating convenient functions in the target service and how to use them. The registration privilege information is information provided when the invitee is an unregistered user of the target service. On the other hand, the utilization promotion information is information provided when the invitee is already a registered user of the target service. The first row in the provided information list 112 shown in FIG. 3 shows an example where the inviter is Inviter A, the invitee is Invitee a, Invitee a owns an account common among multiple services, the target service to be invited is Service A, and since Invitee a is an unregistered user of Service A, registration privilege information is provided as the provided information. Note that the content of the provided information list 112 is registered in the post-invitation process described later (step S41 in FIG. 11).

[0032] The output information list 113 is a list of information obtained by extracting the content of the provided information list 112 for each service. The output information list 113 is provided to each service provider server 300 for each service. For example, the output information list 113 corresponding to Service A is output to the service provider server 300 that provides Service A. Specifically, as shown in FIG. 4, the output information list 113 is created for each service and includes at least the information of the inviter, the information of the invitee, the account information indicating the presence or absence of the invitee's account (an account common among multiple services), and the provided information indicating whether the provided information is registration privilege information or utilization promotion information.

[0033] The control unit 120 is composed of a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), etc. The control unit 120 operates according to the program 111 stored in the storage unit 110 and executes the processing according to the program 111. As the main functional units provided by the program 111 stored in the storage unit 110, the control unit 120 includes 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 an irregularity etc. determination unit 129.

[0034] The request acquisition unit 121 is a functional unit having a function of acquiring a request from the inviter terminal 400 and a function of acquiring a request from the invitee terminal 500. Specifically, the request acquisition unit 121 is a functional unit having a function of acquiring a request transmitted based on an operation on the inviter terminal 400 for the inviter to conduct an invitation and a function of recording a request transmitted based on an operation on the invitee terminal 500 for the invitee to accept an invitation. When the request acquisition unit 121 acquires a request from the inviter terminal 400, the control unit 120 starts the invitation support processing described later. Also, when the request acquisition unit 121 acquires a request from the invitee terminal 500, the control unit 120 starts the post-invitation processing described later. Note that the request includes, in addition to the login information of the user of the inviter terminal 400 or the invitee terminal 500, service specification information for specifying the service to be invited. Note that the login information in this embodiment 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 the invitee is a legitimate user. Specifically, the authentication processing unit 122 is a functional unit that transmits the login information included in the request obtained by the function of the request acquisition unit 121 to the account management device 200 and requests authentication of the inviter or the invitee, that is, the user. As described above, the account information in this embodiment is account information that can be commonly used among a plurality of services, and the same applies to the login information that is part of the account information.

[0036] The account information acquisition unit 123 is a functional unit that acquires account information corresponding to the inviter or the invitee from the account management device 200. Specifically, the account information acquisition unit 123 is a functional unit that acquires the account information transmitted from the account management device 200 when the authentication of the inviter or the invitee is successful in the account management device 200. The account information includes, in addition to the login information, information such as the user's account name, name, gender, age, address, and information about payments such as credit cards and debit cards.

[0037] The target service registration information acquisition unit 124 is a functional unit that acquires the 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 the list information of the registrants stored in the service providing server 300 from the service providing server 300 that provides the service to be invited.

[0038] The target service registration determination unit 125 is a functional unit that determines whether or not the target service is registered. Specifically, the target service registration determination unit 125 is a functional unit that determines whether the inviter or the invitee is a registrant of the target service based on the list information of the registrants obtained 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 the registration page information for the target service. When the two-dimensional code is read by the invitee terminal 500, after the invitee logs in, the invitee will be redirected to the registration page for the target service. Note that in the temporary code issuing unit 126 in this embodiment, an example of generating a two-dimensional code is shown. In addition to this, for example, a URL or a banner may be issued, or a number, an alphabet, or a combination thereof may be issued as an invitation code. When issuing an invitation code, for example, the invitation code may be input in the invitation code input field displayed on the invitee terminal 500. Furthermore, by specifying the invitee's email address, for example, the temporary code may be directly sent to the invitee.

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

[0041] The providing information output unit 128 is a functional unit that registers the content of the providing information list 112. Specifically, the providing information output unit 128 is a functional unit having a function of outputting the inviter's information, the invitee's information, the information on whether the invitee has an account, the information on the target service, and the providing information as the providing information list 112 in the post-invitation processing described later. In addition, the providing information output unit 128 has a function of outputting information to the providing information list 112 and generating the output information list 113 by dividing the information of the providing information list 112 for each service.

[0042] The unfairness determination unit 129 is a functional unit that determines whether the inviter is engaged in unfair conduct or is a powerful influencer based on the content of the provided information list 112. Specifically, the unfairness determination unit 129 calculates, based on the provided information list 112, the two-dimensional distribution of the ratio of invitees not managed by the account management device 200, i.e., the unregistered account ratio X of the invitees, and the ratio of invitees not registered for the target service, i.e., the unregistered target service ratio Y of the invitees. The unit determines that an inviter whose data points are outliers is either engaged in unfair conduct or is a powerful influencer. Then, when the unregistered account ratio of the invitees is equal to or higher than a predetermined reference value, the unfairness determination unit 129 has a function to determine that unfair conduct is being carried out.

[0043] The input / output unit 130 is composed of a keyboard, a mouse, a camera, a microphone, a liquid crystal display, an organic EL (Electro-Luminescence) display, etc., and is a device for inputting and outputting various data.

[0044] The communication unit 140 is a device for 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 Account Management Device) Next, with reference to FIG. 5, the configuration of the account management device 200 will be described.

[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 components.

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

[0048] The program 211 is a program that performs authentication of users who are invitors or invitees and executes an account providing process for providing the user's account information, and is stored in the storage unit 210 in advance.

[0049] The account information 212 is information for uniquely identifying a user who is an invitor or an invitee, and as shown in FIG. 6, the account information 212 includes information of a plurality of users. As shown in the drawing, the account information 212 includes at least the user's login information such as an email address and a password, in addition to the user's account name, name, gender, age, address, and information about payments such as credit cards and debit cards (name and other information).

[0050] The control unit 220 is composed of a CPU, an ASIC, and the like. The control unit 220 operates according to the program 211 stored in the storage unit 210 and executes the processing according to the program 211. As a main functional unit provided by the program 211 stored in the storage unit 210, the control unit 220 includes a user authentication unit 221 and an account information providing unit 222.

[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 or not the invitor or invitee who is requested to be authenticated 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 invitor or 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 the authentication of the user based on the login information of the inviter or the invitee is successful, the account information providing unit 222 has a function of providing the account information 212 corresponding to the login information to the invitation support device 100.

[0053] The input / output unit 330 is a device composed of a keyboard, a mouse, a camera, a microphone, a liquid crystal display, an organic EL display, etc., and is used for inputting and outputting various data.

[0054] The communication unit 240 is a device for 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 by 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, in this embodiment, the invitation support process starts when the request acquisition unit 121 acquires a request from the inviter terminal 400. Specifically, first, as shown in FIG. 8, an invitation operation by the inviter to the inviter terminal 400 (in the illustrated example, a tap operation on the "Invitation Here" button) is performed. Subsequently, as shown in FIG. 9, a login screen is displayed on the inviter terminal 400, and when a login operation by the inviter is performed, a request is transmitted from the inviter terminal 400 to the invitation support device 100. As a result, the request acquisition unit 121 acquires a request from the inviter terminal 400, and the invitation support process is started. Note that, as described above, the request includes, in addition to the login information of the user of the inviter terminal 400, service identification information for identifying the service to be invited. Note that the login information in this embodiment is composed of a combination of an email address and a password.

[0056] When the invitation support process starts, the control unit 120 requests user authentication by 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 in order to request the account management device 200 to authenticate the user based on the login information included in the request acquired by the request acquisition unit 121.

[0057] On the side of the account management device 200, when receiving an authentication request from the invitation support device 100, it starts the account providing process. When starting the account providing process, the control unit 220 authenticates the user by the function of the user authentication unit 221 and determines whether the authentication is successful (step S12). Specifically, in the process of step S12, the user authentication unit 221 determines whether the authentication is successful 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 process of step S12 (step S12; Yes), the control unit 220 provides the user's account information by the function of the account information providing unit 222 (step S13) and ends the account providing process. Specifically, in the process of step S13, the account information providing unit 222 provides the account information 212 corresponding to the login information that was successfully authenticated in the process of step S12 to the invitation support device 100. On the other hand, if it is determined that the authentication fails in the process of step S12 (step S12; No), the control unit 220 notifies that there is no account registration (step S14) and ends the account providing process. Specifically, in the process of step S14, the control unit 220 notifies the invitation support device 100 that the inviter is an unregistered account user. Note that in the process of step S14, for example, it may notify that there is an error in the login information.

[0059] After executing the process of step S13 or step S14, on the side of the invitation support device 100, it is determined whether it has been notified that there is no account registration (step S15). Specifically, in the process of step S15, the control unit 120 determines whether it has been notified from the account management device 200 that the inviter is a person without an account registration. Note that in the process of step S15, the control unit 120 may determine that it has been notified that there is no account registration because it has not obtained account information from the account management device 200 by the function of the account information acquisition unit 123. If it is determined in the process of step S15 that there is no account registration (step S15; Yes), the control unit 120 cooperates with the account management device 200 to prompt the invitation terminal 400 to register the account and perform the registration (step S16).

[0060] After executing the process of step S16, or if it is determined in the process of step S15 that there is an account registration (step S15; No), that is, when the account information acquisition unit 123 has obtained account information from the account management device 200, the control unit 120 obtains 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 of the target service registration information acquisition unit 124 obtains target service registration information, which is a list of registered persons stored in the service providing server 300, from the service providing server 300 that provides the service to be invited. Note that the service providing server 300 that provides the service specified by the service specific information included in the obtained request may be specified as the target service providing server 300 for acquisition.

[0061] After acquiring the target service registration information in the process of step S17, the control unit 120 determines whether the inviter is registered for the target service by means of 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 inviter is registered for the target service by checking whether the account information corresponding to the inviter is registered in the acquired target service registration information. 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 process of step S18 is executed to determine whether the inviter is registered on the side of the invitation support device 100. However, for example, a registration confirmation request may be sent from the side of the invitation support device 100, the service providing server 300 may determine whether the inviter is registered, and the result may be sent 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 collaborates with the service providing server 300 to provide a registration screen to the inviter terminal 400 to prompt for registration (step S19), and ends the invitation support process. In this embodiment, an example is shown in which the invitation support process ends after the execution of the process of step S19. However, after the execution of the process of step S19, the process may proceed to step S20 described later.

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

[0064] After executing the process of step S20, the control unit 120 provides the temporary code generated in the process of step S20 to the inviter terminal 400 by the function of the temporary code issuing unit 126 and the function of the temporary code etc. providing unit 127 (step S21), and ends the invitation support process. Specifically, in the process of step S21, as shown in FIG. 10, the temporary code etc. providing unit 127 provides the two-dimensional code generated in the process of step S20 to the inviter terminal 400 and displays it on the display unit. Thereby, the two-dimensional code can be read on the invitee terminal 500.

[0065] The above is the operation of the invitation support process in the invitation support device 100. In this embodiment, for easy understanding, when the authentication of the user who is the inviter is successful in the process of step S12, the user's account information is provided in the process of step S13, and an example of the subsequent processes after step S15 is shown. However, when inviting a plurality of services continuously after the user's authentication has been performed once, the processes of steps S11 to S16 may be skipped. That is, once the user's authentication is successful, a plurality of services can be invited without a login operation. Note that the period without a login requirement can be set in advance and can be arbitrarily changed.

[0066] Next, the post-invitation processing in the invitation support device 100 will be described. The post-invitation processing is a process performed by the invitation support device 100 when the invitee is invited by the inviter to the target service. 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, first, as shown in FIG. 12, the temporary code displayed on the inviter terminal 400 is read by the invitee terminal 500. Subsequently, as shown in FIG. 13, a login screen is displayed on the invitee terminal 500, and when a login operation is performed by the invitee, a request is sent from the invitee terminal 500 to the invitation support device 100. As a result, the request acquisition unit 121 acquires a request from the invitee terminal 500, and the post-invitation processing is started. As described above, the request includes, in addition to the login information of the user of the invitee terminal 500, service identification information for identifying the service to be invited.

[0067] When the post-invitation processing starts, the control unit 120 requests user authentication by the function of the authentication processing unit 122 (step S31). Specifically, similar to the processing in step S11 shown in FIG. 7, in the processing of step S31 in FIG. 11, the authentication processing unit 122 requests the account management device 200 to authenticate the user based on the login information included in the request acquired by the request acquisition unit 121, and thus sends an authentication request to the account management device 200.

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

[0069] When it is determined that authentication is successful in the process of step S32 (step S32; Yes), the control unit 220 provides the user's account information by the function of the account information providing unit 222 (step S33), and ends the account providing process. Specifically, in the process of step S33, the account information providing unit 222 provides the account information 212 corresponding to the login information that has been successfully authenticated in the process of step S32 to the invitation support device 100. On the other hand, when it is determined that authentication fails in the process of step S32 (step S32; No), the control unit 220 notifies that there is no account registration (step S34), and ends the account providing process. Specifically, in the process of step S34, the control unit 220 notifies the invitation support device 100 that the invitee is an unregistered account user. Note that in the process of step S34, for example, it may be notified that there is an error in the login information.

[0070] After executing the process of step S33 or step S34, on the side of the invitation support device 100, it is determined whether it has been notified that there is no account registration (step S35). Specifically, in the process of step S35, the control unit 120 determines whether it has been notified from the account management device 200 that the invitee is an unregistered account user. Note that in the process of step S35, the control unit 120 may determine that it has been notified that there is no account registration because it has not obtained the account information from the account management device 200 by the function of the account information acquisition unit 123. When it is determined that there is no account registration in the process of step S35 (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 perform the registration (step S36).

[0071] After executing the process of step S36, or when it is determined in the process of step S35 that there is an account registration (step S35; No), that is, when the account information is obtained from the account management device 200 by the function of the account information acquisition unit 123, the control unit 120 acquires the 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 the target service registration information, which is the list information of the registrants stored in the service providing server 300, from the service providing server 300 that provides the service to be invited. Note that the service providing server 300 that provides the service specified by the service specific information included in the acquired request may be specified as the acquisition destination service providing server 300.

[0072] After acquiring the target service registration information in the process of step S37, the control unit 120 determines whether the invitee is registered in the target service by 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 in the target service by checking whether the 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 process of step S38 is executed to determine whether the invitee is registered on the side of the invitation support device 100. However, for example, a registration confirmation request may be transmitted from the side of the invitation support device 100, the service providing server 300 may determine whether the invitee is registered, and the result may be transmitted 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 provides the registration privilege information to the invitee terminal 400 through the function of the temporary code etc. providing unit 127 (step S39). Specifically, in the process of step S39, as shown in FIG. 14, the temporary code etc. providing unit 127 provides the invitee terminal 400 with the registration privilege information for notifying the invitee of the privileges obtained by registration.

[0074] On the other hand, in the process of step S38, if it is determined that there is registration (step S38; Yes), that is, if the invitee is already a registrant of the target service, the control unit 120 provides the utilization promotion information to the invitee terminal 400 through the function of the temporary code etc. providing unit 127 (step S40). Specifically, in the process of step S40, as shown in FIG. 15, the temporary code etc. providing unit 127 provides the invitee terminal 400 with the information for promoting the utilization of the target service by displaying and notifying the invitee of the convenient services in the target service.

[0075] After executing the process of step S39 or step S40 shown in FIG. 11, the control unit 120 outputs the provided information etc. as a provided information list 112 through the function of the provided information output unit 128 (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 the provided information with the information of the inviter, the information of the invitee, the information on whether the invitee has an account, and the information of the target service, and outputs it as the provided information list 112. Also, in the process of step S41, in addition to the provided information list 112, an output information list 113 which is a list of information extracted for each service from the content of the provided information list 112 may be output. The output information list 113 may be provided to each service providing server 300 periodically, and based on the content of the provided output information list 113, privileges may be granted to the inviter and the invitee from each service providing server 300.

[0076] After executing the process of step S41, the control unit 120 determines whether the inviter has committed an improper act by the function of the improper act determination unit 129 (step S42), and ends the post-invitation process. Specifically, in the process of step S42, the improper act determination unit 129 obtains the two-dimensional distribution of the unregistered ratio of the invitee's account and the unregistered ratio of the target service of the invitee based on the provided information list 112. For an inviter whose value is an outlier, when the unregistered ratio of the invitee's account is equal to or higher than a predetermined reference value, it is determined that the inviter has committed an improper act, and for other invitees, it is determined that they are powerful influencers. Note that for an inviter determined to have committed an improper act in the process of step S42, the corresponding account information may be notified to each service providing server 300 as an improper inviter. On the side of each service providing server 300, the awarding of privileges may be restricted for the introducer specified 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 in this embodiment, a common account is used among a plurality of services, and once login authentication can be performed, invitations can be continuously sent to a plurality of services. Therefore, the operation of logging in for each service to be invited becomes unnecessary, and the process of sending invitations in various services can be facilitated.

[0078] Also, according to the invitation support device 100 in this embodiment, when the invitee is already a registrant of the target service, utilization promotion information for promoting the use of the service is provided. Therefore, appropriate information can be provided according to whether the invitee is already registered for the target service.

[0079] Also, according to the invitation support device 100 in this embodiment, it is possible to determine an inviter who has committed an improper act of illegally obtaining the number of invitees to obtain privileges.

[0080] (Modification example) Note 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 necessarily have all the technical features shown above, and may have some of the configurations described in the above-described embodiments so as to solve at least one problem in the prior art. Also, at least a part of each of the following modification examples may be combined with each other.

[0081] In the above-described embodiment, an example of acquiring target service registration information, which is a list of registered users stored in the service providing server 300 in the process of step S17 in FIG. 7 or step S37 in FIG. 11, is shown, but this is just an 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, without acquiring the target service registration information, it may be possible to inquire of each service providing server 300 whether the service of the inviter or the invitee is registered.

[0082] Also, in the above-described embodiment, in the process of step S41 shown in FIG. 11, an example was shown in which the fraud determination unit 129 obtains a two-dimensional distribution of the unregistered ratio of the invitee's account and the unregistered ratio of the invitee's target service and determines fraud. However, this is just an example. For example, in addition to this, a four-dimensional distribution (a four-dimensional distribution of X, Y, A, and B) of the number A of unregistered accounts of the invitee and the number B of unregistered target services of the invitee may be obtained, and for an inviter who is an outlier, it may be determined that the inviter is engaging in fraudulent behavior or is a powerful influencer. Also, according to the unregistered ratio of the invitee's account, the unregistered ratio of the invitee's target service, the number of unregistered accounts of the invitee, and the number of unregistered target services of the invitee, the content of the privilege given to the user who is the invitee may be determined. That is, different modes of registration privilege information may be provided to the invitee terminal 500 according to the unregistered ratio of the invitee's account, the unregistered ratio of the invitee's target service, the number of unregistered accounts of the invitee, and the number of unregistered target services of the invitee. For example, so that the more invitees an inviter has, the more privileges can be obtained. When the invitation is from an inviter with 3 to 10 invitees, registration privilege information in a mode where the score obtained is 1000 points may be provided to the invitee terminal 500, and when the invitation is from an inviter with 11 to 30 invitees, registration privilege information in a mode where the score obtained is 1500 points may be provided to the invitee terminal 500. According to this, since the privilege obtained varies according to the number of invitees, the invitation motivation of the user can be promoted. Also, it may be determined that fraud is being committed based only on the primary distribution of only the ratio of invitees not managed by the account management device 200, that is, the unregistered ratio X of the invitee's account.

[0083] In the above-described embodiment, for ease of understanding, when the authentication of the user who is the invitee is successful in the process of step S32, the account information of the user is provided in the process of step S33, and an example of the subsequent process after step S35 is shown. However, when inviting a plurality of services continuously after the user authentication is once performed, the processes of steps S31 to S36 may be skipped. That is, once the invitee successfully authenticates the user, the invitee can receive invitations for a plurality of services without performing a login operation. Therefore, the operation of logging in for each service to be invited becomes unnecessary, and the process of receiving invitations in various services can also be facilitated. Note that the period during which login is not required can be set in advance and can be arbitrarily changed.

[0084] Note that the invitation support device 100 and the account management device 200 according to the above-described embodiment can be realized not by a dedicated device but by using a normal computer. For example, an invitation support device 100 that executes the above-described processing may be configured by installing a program for executing any of the above in a computer from a recording medium storing the program. Further, one invitation support device 100 and account management device 200 may be configured by a plurality of computers operating in cooperation.

[0085] Also, when the above-described functions are realized by sharing between the OS (Operating System) and the application or by cooperation between the OS and the application, only the part other than the OS may be stored in the medium.

[0086] It is also possible to superimpose a 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 the program may be distributed via the network. Then, these programs are started and configured to execute the above-described processing by being executed in the same manner as other application programs under the control of an operating system.

[0087] Hereinafter, various aspects of the present disclosure will be summarized and described as appendices.

[0088] (Appendix 1) A request information acquisition unit that acquires request information including information on a service to be invited by an inviter user and login information of the inviter user; An authentication request unit that requests authentication of the inviter user based on the login information acquired by the request information acquisition unit; A temporary code generation unit that generates a temporary code including information for identifying the inviter user and information on the service when the authentication requested by the authentication request unit is successful and the inviter user is registered for the service to be invited; The login information can be commonly used in a plurality of the services. An invitation support device characterized by the above.

[0089] (Appendix 2) An account information acquisition means that acquires account information of the inviter user corresponding to the login information when the authentication requested by the authentication request unit is successful; A determination result acquisition unit that acquires a determination result as to whether or not the inviter user is registered for the service to be invited based on the account information acquired by the account information acquisition means; and The temporary code generation unit generates the temporary code when the determination result acquisition unit determines that the inviter user is registered for the service to be invited. The invitation support device according to Supplementary Note 1, characterized in that...

[0090] (Supplementary Note 3) The determination result acquisition unit acquires a determination result as to whether or not the target of the invitation by the inviter user is already registered in the service, by inquiring a service providing server that provides the service to the target of the invitation by the inviter user. The invitation support device according to Supplementary Note 2, characterized in that...

[0091] (Supplementary Note 4) The determination result acquisition unit determines whether or not the target of the invitation by the inviter user is already registered in the service, based on the registration information acquired from a service providing server that provides the service to the target of the invitation by the inviter user, and acquires the determination result. The invitation support device according to Supplementary Note 2, characterized in that...

[0092] (Supplementary Note 5) The invitation support device further includes a temporary code providing unit that provides the temporary code generated by the temporary code generation unit to an inviter terminal owned by the inviter user. The request information acquisition unit acquires request information including information on the service that the invitee user is invited to and login information of the invitee user, based on the fact that the temporary code provided to the inviter terminal by the temporary code providing unit is acquired by an invitee terminal owned by the invitee user. The authentication request unit requests authentication of the invitee user based on the login information of the invitee user acquired by the request information acquisition unit. When the authentication request unit succeeds in the authentication requested by the invitee user and the invitee user is already registered in the service that the invitee user is invited to, a use promotion information providing unit that provides use promotion information for promoting use of the service to the invitee terminal, and when the invitee user is not registered in the service that the invitee user is invited to, a notification information providing unit that provides registration privilege information obtained by the invitee user registering to the invitee terminal. The invitation support device according to any one of Appendices 1 to 4, further provided.

[0093] (Appendix 6) A provided information output unit that outputs provided information in which the information of the inviter user specified from the temporary code, the information of the service specified from the temporary code, the information of the invitee user who acquired the temporary code, and information indicating whether the information provided by the information providing unit is the utilization promotion information or the registration privilege information are respectively associated. The invitation support device according to Appendix 5, further provided.

[0094] (Appendix 7) An output information transmission unit that transmits the output information obtained by extracting the provided information output by the provided information output unit for each service information specified from the temporary code to a service providing server that provides the corresponding service. The invitation support device according to Appendix 6, further provided.

[0095] (Appendix 8) An illegal determination unit that determines illegal behavior of the inviter user based on an outlier of a two-dimensional distribution based on the ratio of the invitee users who failed the authentication requested by the authentication request unit among the invitee users and the ratio of those who were not registered for the service targeted by the invitee users. The invitation support device according to Appendix 6, further provided.

[0096] (Appendix 9) The illegal determination unit determines illegal behavior of the inviter user based on an outlier of a four-dimensional distribution for the inviter user 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 those who were not registered for the service targeted by the invitee users, the number of invitee users who failed the authentication requested by the authentication request unit, and the number of those who were not registered for the service targeted by the invitee users. The invitation support device according to Appendix 8, characterized in that.

[0097] (Appendix 10) The invitation information providing unit provides registration privilege information in different modes according to the ratio of the invited users who failed the authentication requested by the authentication request unit among the invited users, the ratio of the invited users who were not registered for the service targeted by the invitation, the number of the invited users who failed the authentication requested by the authentication request unit, and the number of the invited users who were not registered for the service targeted by the invitation. The invitation support device according to Appendix 6, characterized in that.

[0098] (Appendix 11) An invitation support method by an invitation support device, comprising: A request information acquisition step of acquiring request information including information on a service targeted by an inviter user and login information of the inviter user; An authentication request step of requesting authentication of the inviter user based on the login information acquired in the request information acquisition step; A temporary code generation step of generating a temporary code including information for identifying the inviter user and information on the service when the authentication requested in the authentication request step is successful and the inviter user is registered for the service targeted by the invitation. The login information is commonly usable in a plurality of the services. The invitation support method, characterized in that.

[0099] (Appendix 12) A computer, A request information acquisition unit that acquires request information including information on a service targeted by an inviter user and login information of the inviter user; An authentication request unit that requests authentication of the inviter user based on the login information acquired by the request information acquisition unit; When the authentication requested by the authentication request unit is successful and the service to be invited by the inviter user is already registered, it functions as a temporary code generation unit that generates a temporary code including information for identifying the inviter user and information on the service. The login information can be commonly used in a plurality of the services. A program characterized by this.

[0100] The present disclosure can be implemented in various embodiments and variations without departing from the broad spirit and scope of the present disclosure. Also, the above-described embodiments are for explaining this disclosure and do not limit the scope of the present disclosure. That is, the scope of the present disclosure is indicated by the claims rather than the embodiments. And various modifications made within the scope of the claims and within the scope of the meaning equivalent to the disclosure are considered to be within the scope of this 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 processing when making an invitation in various services.

Explanation of Signs

[0102] 100 Invitation support device 110, 310 Storage unit 111, 311 Program 112 List of provided information 113 List of output information 120, 320 Control unit 121 Request acquisition unit 122 Authentication processing unit 123 Account information acquisition unit 124 Target service registration information acquisition unit 125 Target service registration determination unit 126 Temporary code issuance unit 127 Temporary code etc. providing unit 128 Provided information output unit 129 Illegal Equality Judgment Unit 130, 230 Input / Output Unit 140, 240 Communication Unit 200 Account Management Device 212 Account Information 221 User Authentication Unit 222 Account Information Provision Unit 300 Service Provision Server 313 Browsing Information 321 Request Reception Unit 322 Usage Storage Setting Unit 400 Inviter Terminal 500 Invitee Terminal 800 Computer Communication 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 configured to generate 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 registered for the service to which the inviter user is invited; The login information can be commonly used across multiple services. An invitation support device comprising:

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 or not 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 generating unit generates the temporary code when the determination result acquiring unit determines that the inviter user has registered with the service to which the invitee is invited.

2. The invitation support device according to claim 1.

3. the determination result acquisition unit acquires a determination result of whether the inviter user has registered for the service to which the inviter user is invited by inquiring of a service providing server that provides the service to which the inviter 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 inviter user is invited based on registration information acquired from a service providing server that provides the service to which the inviter 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 a guest terminal owned by the guest 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 temporary code provided to the inviter terminal by the temporary code provision unit being 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 provides, 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, to the invited user terminal with usage promotion information that promotes the use of the service, and that provides, when the invited user has not yet registered for the service to which the invited user has been invited, to 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 inviter user specified from the temporary code, information of the service specified from the temporary code, information of the invitee user who obtained the temporary code, and information indicating whether the information provided by the notification information providing unit is the utilization promotion information or the registration benefit information are associated with each other; The invitation support device according to claim 5 .

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 specified by the temporary code, to a service providing server that provides the corresponding service, The invitation support device according to claim 6 .

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

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 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 are not registered in the service to which the invitee users are 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 are not registered in the service to which the invitee users are invited; 9. The invitation support device according to claim 8.

10. the notification information providing unit provides different types of registration privilege information according to a ratio of the invited users who have failed the authentication requested by the authentication request unit among the invited users, a ratio of the invited users who have not been registered in the service to which the invited users have been invited, a number of the invited users who have failed the authentication requested by the authentication request unit, and a number of the invited users who have not been registered in the service to which the invited users have been invited.

7. The invitation support device according to claim 6.

11. An invitation support method by an invitation support device, a request information acquisition step of acquiring request information including information on a service to which an 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 request step is successful and the inviter user has already registered for the service to which the inviter user is invited; The login information can be commonly used across multiple services. The invitation support method according to the present invention.

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 registered with the service to which the invitee is invited; The login information can be commonly used across multiple services. A program characterized by:

Images