JP6175730B2 - Management device, terminal device capable of communicating with management device, service providing system, management device control method, terminal device program, and management device program - Google Patents

Description

  The present invention relates to a technology for facilitating an inquiry about a third party having a specific relationship with a specific user who has a specific relationship with a certain service.

  In recent years, services provided on the Internet are rapidly spreading. As one of such services, a website providing SNS (Social Networking Service) is known. This website allows you to build friendships for communication between users. And a means provided by a communication tool such as posting, chatting, and mail between friends is provided. In Patent Document 1, a list of users belonging to a certain community is displayed, and a certain user specifies another user who wants to build a friendship relationship, and the certain user is identified with respect to the identified other user. A technique for transmitting the predetermined information and allowing the other user to select whether or not to approve the construction of the friendship is disclosed.

Special table 2009-520276

Since the friend relationship to be established in Patent Document 1 is a friend relationship on the SNS, even if there is no contact with the application partner, it is possible to apply for friend relationship construction relatively easily. If a friendship on SNS is established, each other's activities (various actions that can be displayed on SNS, such as recent reports, photo submission, sharing of a predetermined link, check-in to a predetermined location, etc.) You can leave comments and invite to events.
This activity is written in a writing area such as a bulletin board on the SNS. However, when the other party's writing area is browsed, a comment or the like left by the other party's friend can be seen.
In other words, the friend (direct friend) on his / her SNS will know the existence of the friend (indirect friend), but since there is often no direct exchange with the indirect friend on the SNS, this indirect Even if the friend is interested, it is often felt psychologically to contact the indirect friend suddenly on the SNS (that is, to send a message to the indirect friend suddenly on the SNS).
The present invention has been made in view of this point, and makes it easier for a specific user who has a specific relationship with a service to make an inquiry regarding a third party who has a specific relationship with the specific user. This is a solution issue.

  Means employed by the present invention to solve the above problems will be described below. In order to facilitate understanding of the present invention, reference numerals in the drawings will be appended in parentheses for convenience in the following, but the present invention is not intended to be limited to the illustrated forms.

In order to solve the above-described problem, a program of a management apparatus according to the present invention is a program of a management apparatus that can communicate with a user terminal device (2) and includes a computer, and the program uses the computer. In response to a request from the terminal device (2) of a predetermined user, an acquisition unit (11) that acquires specific relationship information indicating a specific relationship between users, and the specific user and the specific relationship A first extraction unit (13) for extracting a second specific user having the specific relationship with the first specific user having the specific relationship based on the specific relationship information; and the terminal device (2) of the predetermined user ) In response to a request from the common user having the specific relationship with both the second specific user selected in the terminal device (2) of the predetermined user and the predetermined user. The first specific use A second extraction unit (14) that extracts the first specific user extracted based on the specific relationship information, and the terminal device of the predetermined user (with the common first specific user extracted by the second extraction unit) And an information transmission unit (16) for transmitting information on the second specific user selected in 2).
In the present invention, the specific relationship can include, for example, a friend relationship, but is not limited thereto. In short, any relationship can be used as long as it is established based on a certain rule. The information regarding the second specific user includes information for requesting mediation with the second specific user and information for requesting a relationship with the second specific user. The information indicating the second specific user may be character information such as the name of the second specific user, image information such as an icon, or link information indicating a storage location of the character information or image information. Also good. The information indicating the common first specific user includes an image such as the name and icon of the common first specific user. The information transmission unit only needs to have the common first specific user as a destination, and the transmission method and mode are not limited.

In order to solve the above-described problem, a program of a management apparatus according to the present invention provides a second service to second users including a first user who receives provision of the first service and the second user. Program of a management apparatus comprising a computer that can communicate with the external management apparatus (3) that manages the second specific relationship information indicating a specific relationship between each other and that can communicate with the terminal apparatus (2) of the first user The program is a first identification information for uniquely identifying the computer, the second specific relationship information, and the first user, and a first identifier for uniquely identifying the second user. An acquisition unit (11) that acquires first identification information having a correspondence relationship with two identification information, and the predetermined first user in response to a request from the terminal device (2) of the predetermined first user; The first having the specific relationship A first extraction unit (13) for extracting a second specific user having the specific relationship with the regular user based on the first identification information and the second specific relationship information; and the predetermined first user In response to a request from the terminal device (2) of one user, the second specific user selected in the terminal device (2) of the predetermined first user, the predetermined first user, A second extraction unit (14) for extracting the common first specific user having the specific relationship with respect to both based on the first identification information and the second specific relationship information; and the common And an information transmission unit (16) for transmitting information on the second specific user selected in the terminal device (2) of the predetermined first user with the first specific user as a destination.
In the present invention, the specific relationship can include, for example, a friend relationship, but is not limited thereto. In short, any relationship can be used as long as it is established based on a certain rule. The information regarding the second specific user includes information for requesting mediation with the second specific user and information for requesting a relationship with the second specific user. The information indicating the second specific user may be character information such as the name of the second specific user, image information such as an icon, or link information indicating a storage location of the character information or image information. Also good. The information transmission unit only needs to have the common first specific user as a destination, and the transmission method and mode are not limited.

  In the above-described management device program, the information transmission unit (16) transmits the information regarding the second specific user selected in the terminal device (2) of the predetermined first user to the common first item. You may make it transmit to the said terminal device (2) of 1 specific user.

  In the management device program described above, the information transmission unit (16) transmits information on the second specific user selected in the terminal device (2) of the predetermined first user to the external management device (3). ) And a request to the external management device (3) to transmit the information to the common first specific user as a destination. .

  In the management device program described above, the information transmission unit (16) may send the predetermined first common user selected in the terminal device (2) of the predetermined user to the predetermined user. Information on the second specific user selected in the terminal device (2) of the user may be transmitted.

  In the management device program described above, the information transmission unit (16) selects the terminal device (2) of the predetermined user in response to a request from the terminal device (2) of the predetermined user. You may make it transmit the information regarding the made 2nd specific user.

  In the management device program described above, the acquisition unit (11) acquires first user specifying relationship information indicating a specific relationship between the first users from the management device (1), and the first extraction is performed. The unit (13) is a first user having the specific relationship with the predetermined first user based on the first specific relationship information and the second specific relationship information, and the predetermined first information A person who is a second user having the specific relationship with one user is extracted as the first specific user, is a first user having the specific relationship with the first specific user, and A person corresponding to the second user having the specific relationship with the first specific user is extracted as the second specific user, and the second extraction unit (14) is configured to extract the first specific relationship information and the Based on the second specific relationship information, the selected second feature. A first user having the specific relationship with both the user and the predetermined first user, and the selected second specific user and the predetermined first user; A person who is the second user having the specific relationship with respect to both may be extracted as the common first specific user.

  In the management apparatus program described above, the program causes the computer to further function as a condition setting unit (17) for setting a predetermined condition for the first specific user, and the acquisition unit (11) The registration information of the first user is acquired, and the second extraction unit matches the condition set by the condition setting unit (17) from the extracted common first specific users. The common first specific user may be extracted.

  In the above-described program of the management apparatus, the information regarding the selected second specific user includes the selected second specific user and the selected first specific user. It is also possible to use information for requesting mediation.

  In order to solve the above-described problems, a program of a terminal device according to the present invention is a user terminal device that can communicate with a management device (1) that manages specific relationship information indicating a specific relationship between users and includes a computer. The program has the specific relationship with respect to the first specific user who has the specific relationship with a predetermined user with respect to the management device (1). A first request unit (21) for requesting that two specific users be extracted, and one second specific user among the second specific users extracted in the management device (1), The selection unit (25) to be selected in response to a user's selection instruction, the specific second user selected by the selection unit (25), and the specific user Having a common relationship A second request unit (22) for requesting the management apparatus (1) to extract the first specific user, and the selected second one with the first specific user as a destination. A request for transmitting information related to a specific user is made to function as a third request unit (23) for the management apparatus (1).

  In order to solve the above-described problem, a program of a terminal device according to the present invention provides a second service to a second user including a first user who receives the provision of the first service and the second user. A management device (1) capable of communicating with an external management device (3) that manages second specific relationship information indicating a specific relationship between them, and that provides the first service to the first user A program of a terminal device of a first user that is at least communicable with (1) and includes a computer, wherein the program sends the computer to the management device (1) with the predetermined first user. The first request unit (21) that requests the first specific user having the specific relationship to extract the second specific user having the specific relationship, and extracted by the management device (1) Said A selection unit (25) that selects one of the specific users from the specific user according to the selection instruction of the user, and the one of the second specific users selected by the selection unit (25) A second request for requesting the management device (1) to extract the common first specific user having the specific relationship with both the user and the predetermined first user A request to the management device (1) to send information related to the selected second specific user, with the first specific user as a destination and the unit (22) And function as a third request unit (23) to be performed.

  The program may be stored in a recording medium. If this recording medium is used, the program can be installed in the computer, for example. Here, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM.

  In order to solve the above-described problem, a service providing system according to the present invention includes at least a selection unit (25, 26) for performing a predetermined selection, a user terminal device, and a management device capable of communicating with the terminal device. , And a service providing system for providing a service to the user, the acquisition unit (11) for acquiring specific relationship information indicating a specific relationship between the users, and the specific user and the specific user The first extraction unit (13) that extracts the second specific user having the specific relationship with respect to the first specific user having the relationship based on the specific relationship information and the selection unit (25) are selected. Based on the specific relationship information, a common first specific user who is the first specific user having the specific relationship with both the second specific user and the predetermined user is extracted. Second extraction unit (1 And an information transmission unit (16) for transmitting information on the second specific user selected in the terminal device (2) of the predetermined user, with the one common first specific user as a destination. ).

  In order to solve the above-described problem, the service providing system according to the present invention is capable of communicating with the terminal device of the first user having at least a selection unit (25, 26) for performing a predetermined selection, and the terminal device, A management device capable of communicating with an external management device that provides second services to second users including the first user and manages second specific relationship information indicating a specific relationship between the second users. A service providing system that provides a first service to the first user, wherein the second specific relationship information and the first user are uniquely identified, and the second user is An acquisition unit (11) that acquires first identification information that has a corresponding relationship with second identification information that is uniquely identified, and the first specific user that has the specific relationship with the predetermined first user The second feature with a specific relationship A first extraction unit (13) for extracting a user based on the first identification information and the second specific relationship information; the second specific user selected by the selection unit (25); A common first specific user who is the first specific user having the specific relationship with both of the predetermined users is extracted based on the first identification information and the second specific relationship information. And a request to transmit information related to the second specific user selected by the selection unit (26), with the second common extraction unit (14) and the one common first specific user as a destination. And an information transmission unit (16) for transmitting to the external management device (3).

  In order to solve the above-described problems, the control method of the management apparatus (1) according to the present invention is a control method of the management apparatus (1) that provides services to users, and shows a specific relationship between users. Acquire specific relationship information, and have the specific relationship with the first specific user having the specific relationship with the predetermined user in response to a request from the terminal device (2) of the predetermined user A second specific user is extracted based on the specific relationship information, and information indicating the extracted second specific user is displayed on the display unit (24) of the terminal device (2) of the predetermined user; Both the second specific user selected in the terminal device (2) of the predetermined user and the predetermined user in response to a request from the terminal device (2) of the predetermined user The first specific use in common having the specific relationship to Is extracted based on the specific relationship information, and the extracted information indicating the common first specific user is displayed on the display unit (24) of the terminal device (2) of the predetermined user. The information on the second specific user selected in the terminal device (2) of the predetermined user is transmitted with the first specific user as the destination.

  In order to solve the above-described problems, a control method for a management apparatus according to the present invention is a control method for a management apparatus (1) that provides a first service to a user, and includes a second usage including the first user. A second service is provided to the user, and communication with an external management device (3) that manages the second specific relationship information indicating the specific relationship between the second users is possible. In the control method of the management device (1) capable of communicating with the terminal device (2), the second specific relationship information and the first identification information for uniquely identifying the first user, the second usage First identification information having a correspondence relationship with second identification information for uniquely identifying a user is acquired, and in response to a request from the terminal device (2) of a predetermined first user, the predetermined first user And the specific relationship for the first specific user having the specific relationship The second specific user having the second specific user is extracted based on the first identification information and the second specific relationship information, and information indicating the extracted second specific user is extracted from the terminal device of the predetermined first user (2) displayed on the display unit (24) and selected by the predetermined first user's terminal device (2) in response to a request from the terminal device (2) of the predetermined first user. The first specific user having the specific relationship with both the second specific user and the predetermined first user, the first identification information, and the second specific relationship Extracting based on the information, and displaying the extracted information indicating the common first specific user on the display unit (24) of the terminal device (2) of the predetermined first user, In response to a request from the terminal device (2) of one user, the common first feature The user as a destination, sends a request to transmit the information regarding the second specific user selected in the terminal device (2) of the predetermined first user.

  In order to solve the above-described problem, the management device (1) according to the present invention is a management device capable of communicating with a user terminal device (2), and includes specific relationship information indicating a specific relationship between users. In response to a request from the terminal device (2) of the acquisition unit (11) to be acquired and the predetermined user, the specific user and the specific user having the specific relationship with the specific user A first extraction unit (13) that extracts a second specific user having a relationship based on the specific relationship information, and the predetermined usage in response to a request from the terminal device (2) of the predetermined user The first specific user having the specific relationship with both the second specific user selected in the terminal device (2) of the user and the predetermined user, the specific relationship information The second extraction unit (14) for extracting based on the 1 a specific user as a destination, and a predetermined user of the terminal device (2) information transmitting unit that transmits information about the selected second specific user (16).

  In order to solve the above-described problem, the management apparatus (1) according to the present invention provides the second service to the second user including the first user who receives the provision of the first service and the second use. A management device capable of communicating with the external management device (3) for managing the second specific relationship information indicating the specific relationship between the users, and capable of communicating with the terminal device (2) of the first user, The second identification information and the first identification information for uniquely identifying the first user, the first identification information having a correspondence relationship with the second identification information for uniquely identifying the second user In response to a request from the terminal device (2) of a predetermined first user and an acquisition unit (11) that acquires the first specific user having the specific relationship with the predetermined first user A second specific user having the specific relationship with the first identification information In response to a request from the terminal device (2) of the predetermined first user, the predetermined first user terminal device (13) that extracts based on the specific relationship information The first specific user having the specific relationship with both the second specific user selected in 2) and the predetermined first user, the first identification information, In response to a request from the terminal device (2) of the predetermined first user and the second extraction unit (14) that extracts based on the second specific relationship information, the common first specific user And an information transmission unit (16) for transmitting a request to transmit information on the second specific user selected by the terminal device (2) of the predetermined first user.

  In order to solve the above-described problem, the terminal device (2) according to the present invention is a user terminal device that can communicate with the management device (1) that manages specific relationship information indicating a specific relationship between users. Requesting the management device (1) to extract the second specific user having the specific relationship from the first specific user having the specific relationship with a predetermined user. A request unit (13), and a selection unit (1) selected from the second specific users extracted in the management device (1) according to a selection instruction of the second specific user and the user 25) and the common first specific user having the specific relationship with both the one second specific user selected by the selection unit (25) and the predetermined user. The second request unit that requests the management device (1) to extract 22) and a request to transmit information related to the selected one second specific user to the management apparatus (1), with the selected one first specific user as a destination. A third request unit (23) is provided.

  In order to solve the above-described problem, the terminal device (2) according to the present invention provides the second service to the second user including the first user who receives the provision of the first service and the second use. A management device (1) that can communicate with an external management device (3) that manages second specific relationship information indicating a specific relationship between users, and that provides the first service to the first user A terminal device of a first user who can communicate at least with the device (1), the first specific user having the specific relationship with the predetermined first user with respect to the management device (1) A first request unit (21) that requests to extract a second specific user having the specific relationship, and one of the second specific users extracted in the management device (1). The second specific user is selected according to the user's selection instruction. The selection unit (25), the one second specific user selected by the selection unit (25), and the predetermined first user have the specific relationship. A second request unit (22) for requesting the management device (1) to extract a first specific user, and the selected one of the first specific users as the destination. And a third request unit (23) for making a request to the management apparatus to transmit information related to the second specific user.

It is a block diagram of the service provision system which concerns on 1st Embodiment of this invention. It is explanatory drawing which shows the relationship between a SNS user and a golf user. It is explanatory drawing which shows an example of the display screen of a terminal device. It is explanatory drawing which shows an example of the data structure of a golf user information table. It is explanatory drawing which shows an example of the data structure of a SNS user information table. It is explanatory drawing which shows an example of the data structure of a SNS friend information table. It is a block diagram which shows the structure of a management server. It is a block diagram which shows the structure of a terminal device. It is a sequence diagram which shows the operation | movement sequence of the service provision system regarding a display process. It is a sequence diagram which shows the operation | movement sequence of the service provision system regarding a display process. It is explanatory drawing which shows the process which specifies a SNS friend directly. It is explanatory drawing which shows the process which specifies an indirect SNS friend. It is explanatory drawing for demonstrating arrangement | positioning of a direct golf chum and an indirect golf chum. It is explanatory drawing which shows an example of the screen at the time of inviting a golf chum to golf. It is explanatory drawing which shows an example of the screen at the time of selecting the golf chum invited to golf. It is explanatory drawing which shows an example of the screen of the state which selected the golf chum invited to golf. It is explanatory drawing which shows an example of the confirmation screen which invites a golf chum to golf. It is explanatory drawing which shows an example of the screen which performs a golf report. It is explanatory drawing which shows an example of the screen of a golf chum's golf report. It is explanatory drawing which shows an example of a news screen. It is explanatory drawing which shows an example of the data structure of a user log management table. It is explanatory drawing which shows an example of the data structure of an individual log file. It is explanatory drawing which shows an example of the data structure of an individual log file. It is explanatory drawing which shows an example of the input screen of a golf profile. It is explanatory drawing which shows an example of the data structure of the record for every golf user recorded on a golf user information table. It is explanatory drawing which shows an example of the data structure of a setting value management master table. It is explanatory drawing which shows an example of the data structure of a setting value management master table. It is explanatory drawing which shows an example of the data structure of a setting value management master table. It is explanatory drawing which shows an example of the data structure of a setting value management master table. It is explanatory drawing which shows an example of the data structure of a setting value management master table. It is explanatory drawing which shows an example of the data structure of a setting value management master table. It is explanatory drawing which shows an example of the data structure of a setting value management master table. It is explanatory drawing which shows an example of the data structure of a setting value management master table. It is explanatory drawing which shows an example of the data structure of a setting value management master table. It is explanatory drawing which shows an example of the data structure of a setting value management master table. It is a sequence diagram which shows the operation | movement sequence of the service provision system regarding a mediation request process. It is explanatory drawing which shows an example of the screen which displays a common golf chum. It is explanatory drawing which shows an example of the screen which writes a message. It is explanatory drawing which shows an example of the confirmation screen of message transmission. It is explanatory drawing which shows an example of the screen which shows completion of message transmission. It is a sequence diagram which shows the operation | movement sequence of the service provision system regarding the narrowing-down process of a common golf chum. It is a block diagram of the management server which concerns on 2nd Embodiment. It is explanatory drawing which shows an example of the data structure of a golf chum information table. It is a sequence diagram which shows the operation | movement sequence of the service provision system regarding the invitation process which concerns on 2nd Embodiment. It is explanatory drawing which shows the process which specifies an indirect SNS friend. It is explanatory drawing which shows the process which specifies a golf chum directly. It is explanatory drawing which shows the process which specifies an indirect golf chum. It is a block diagram of the service provision system which concerns on 3rd Embodiment. It is a sequence diagram which shows the operation | movement sequence of the service provision system regarding the mediation request process in a modification. It is a block diagram of the service provision system in a modification. It is a block diagram of the service provision system which concerns.

Hereinafter, as an embodiment, a service providing system using a management server according to the present invention will be described with reference to the drawings.
<First Embodiment>
<1. Configuration of service provision system>
FIG. 1 is a block diagram of a service providing system 100 according to an embodiment of the present invention. The service providing system 100 includes a management server 1 that provides a golf information application, a user terminal device 2, and an external management server 3 that provides an SNS site via a communication network NET such as the Internet. In the following description, a user who uses the golf information application of the management server 1 is a golf user (an example of “first user”), and an SNS user of the external management server 3 is an SNS user (“second use”). An example).
The SNS site provided by the external management server 3 provides a communication tool between users (that is, exchange of message management information performed between users. For example, a bulletin board, mail, chat, etc.). In the SNS site, the friendship relationship is established when the action source SNS user makes a friend application and the action destination SNS user approves the friend application. The external management server 3 manages friend information (specific relationship information) indicating an SNS friend relationship that is a specific relationship between SNS users.

The user terminal device 2 can communicate via the communication network NET, and corresponds to, for example, a personal computer, a mobile phone, a smartphone, a tablet terminal, or the like.
The management server 1 provides a specific service. Management server 1 of this embodiment provides a golf information application to a golf user. In this embodiment, the provision of a golf information application will be described as an example. However, the management server 1 provides an application such as a game, provides travel information including hotel reservations, provides concert information, and sells services and goods. May be provided.

In the SNS provided by the external management server 3 (an example of “second service”), not only can a bulletin board, mail, chat, etc. be used, but also social applications such as games and practical tools can be used. it can. This social application may be provided by a provider other than the SNS provider, and the SNS user arbitrarily determines whether or not to use the social application or which social application to use. It can be done. When the SNS user wishes to use a social application, the social application can access the SNS user's profile information and the friend information on the SNS, or the social application can replace the SNS user. There may be cases where permission is required for functions to be posted on bulletin boards. Depending on the social application, the SNS user may be permitted to use these functions, thereby becoming a user of the social application. Such social applications generally display the screen of the social application on the SNS site. Therefore, for SNS users, the social application can be used as if using one of SNS services. Will be used.
The golf information application (an example of “first service”) provided by the management server 1 of the present embodiment is a service provided by a social application as described above, for example. In this embodiment, in order for an SNS user to become a golf user who is a user of a golf information application, the golf information application accesses the profile information of the SNS user and the friend information on the SNS, The golf information application approves a function or the like for posting on a bulletin board or the like instead of the SNS user. When the SNS user performs this approval, the SNS user becomes a golf user.

  That is, the golf user is included in the SNS user as shown in FIG. In other words, the management server 1 provides a golf information application to a golf user, and registers as a golf user of a golf information application only for the SNS user of the external management server 3. On the other hand, the external management server 3 provides SNS with respect to the SNS user containing a golf user. As described above, the golf user is included in the SNS user. Moreover, as described above, the golf information application accesses the profile information of the SNS user and the friend information on the SNS, and the golf information application includes the SNS user. The SNS user has been approved for the function of posting on the bulletin board, etc. Therefore, the management server 2 of 1st Embodiment manages a golf user's friend relationship using a SNS user's friend relationship. In this embodiment, as shown in FIG. 2, a SNS user who has a friendship on a SNS with a certain golf user (hereinafter referred to as golf user A) is directly set as a SNS friend, and directly on a SNS friend and SNS. SNS users who are in a friend relationship are managed as indirect SNS friends. Moreover, the friend who is a direct SNS friend and a golf user is made into a direct golf chum, and the friend who is an indirect SNS friend and is a golf user is managed as an indirect golf chum.

  The function of the management server 1 will be described with reference to FIG. The management server 1 includes a storage unit 15 that stores a golf user information table TBL11, a user log management table TBL13, a set value management master table TBL15, and an individual log file FL10. The storage unit 15 stores a program for controlling the management server 1. The golf user information table TBL11 stores identification information UID that uniquely identifies a golf user. In the user log management table TBL13, a golf user's use history of the golf information application is recorded. Various setting values are recorded in the setting value management master table TBL15 (TBL15a, TBL15b, TBL15c, TBL15d, TBL15e, TBL15f, TBL15g, TBL15h, TBL15i). In the individual log file FL10, from the use history recorded in the user log management table TBL13, a history about actions taken by each golf user and a history about actions taken for each golf user are used for golf. It is extracted and recorded for each person.

  The management server 1 includes an acquisition unit 1, a first extraction unit 13, a display control unit 12, a second extraction unit 14, an information transmission unit 16, and a condition setting unit 17. When the acquisition unit 11 receives a request to display the friendship of the golf user A from the terminal device 2 of the golf user A (an example of “predetermined golf user”), the acquisition unit 11 stores the request stored in the storage unit 15. The golf user A's identification information UID can be acquired, and friend information managed by the external management server 3 can be acquired. Based on the golf user's identification information UID and friend information acquired by the acquisition unit 11, the first extraction unit 13 selects a person corresponding to a golf user among SNS users who have a friendship relationship with the golf user A. It is extracted as a direct golf friend (an example of a “first specific user”), and golf is used among SNS users (indirect SNS friends) who have a friendship with an SNS user who has a friendship with the golf user A. The person corresponding to the person is extracted as an indirect golf chum (an example of “second specific user”). The display control unit 12 includes information necessary for displaying the relationship diagram indicating the relationship between the direct golf chum and the indirect golf chum specified by the first extraction unit 13, and the indirect golf chum and the golf user A described later. A response including information necessary for displaying a common golf chum is transmitted to the terminal device 2 of the golf user A.

  In addition, when one indirect golf chum is selected in the terminal device 2, the second extraction unit 14 extracts a common golf chum that is common to the selected indirect golf chum and the golf user A.

  Furthermore, when one common golf chum is selected from the common golf chum in the terminal device 2 in the terminal device 2, the information transmission unit 16 is selected as information on the selected indirect golf chum with respect to the selected common golf chum. The external management server 3 is requested to transmit information in the external management server 3 to request mediation about going to golf together with the selected indirect golf chum.

In addition, the information transmission part 16 transmits the information to the effect of requesting mediation about going to golf with the selected indirect golf chum to the terminal device 2 of the selected common golf chum. Also good. If it does in this way, when the said common golf chum logs in to a golf information application and opens my page, the information of requesting the above-mentioned mediation can be displayed on the my page. Further, the information transmission unit 16 sends information to the external management server 3 so as to transmit information on requesting mediation about going to golf together with the selected indirect golf chum. And requesting mediation about going to golf with the selected indirect golf chum may be transmitted to the terminal device 2 of the selected common golf chum.
Moreover, the condition setting part 17 can set the conditions for narrowing down the said common golf chum. The second extraction unit 14 extracts a common golf chum that matches the condition set by the condition setting unit 17.

  The function of the terminal device 2 will be described with reference to FIG. The terminal device 2 includes a first request unit 21, a second request unit 22, a third request unit 23, a display unit 24, a first selection unit 25 (an example of a “selection unit”), and a second selection unit. 26 (an example of a “selection unit”).

  The first request unit 21 requests the management server 1 to extract the indirect golf chum of the golf user A who is a user of the terminal device 2. The first selection unit 25 selects one indirect golf chum from the indirect golf chum extracted by the management server 1 according to the selection instruction of the golf user A who is the user of the terminal device 2. The second request unit 22 requests the management server 1 to extract a common golf chum that is common to the one indirect golf chum selected by the first selection unit 25 and the golf user A who has issued the selection instruction. To do. The second selection unit 26 selects one common golf chum from the common golf chum extracted by the management server 1 according to the selection instruction of the golf user A. The 3rd request | requirement part 23 uses the 2nd selection part 26 as the information regarding the selected one indirect golf chum by the 2nd selection part 26 to request the mediation of going to golf with the selected one indirect golf chum. The management server 1 is requested to transmit the selected one common golf chum to the external management server 3 as a destination. The display unit 24 is a relationship diagram showing the relationship between the direct golf chum and the indirect golf chum transmitted from the display control unit 12 of the management server 1, and information necessary for displaying the common golf chum extracted by the management server 1. Etc. are displayed.

  The third request unit 23 selects, as the information about the selected one indirect golf chum, a second selection of information requesting mediation to go to golf with the selected one indirect golf chum. The management server 1 may be requested to transmit to the terminal device 2 of the one common golf chum selected by the unit 26. If it does in this way, when the said common golf chum logs in to a golf information application and opens my page, the information of requesting the above-mentioned mediation can be displayed on the my page. Further, the third requesting unit 23 selects the one common golf chum selected by the second selecting unit 26 for requesting mediation for going to golf with the selected one indirect golf chum. The second selection unit requests information from the external management server 3 to be transmitted to the management server 1 as a destination and requests mediation to go to golf with the selected one indirect golf chum. The management server 1 may be requested to transmit to the terminal device 2 of the one common golf chum selected by H.26.

  FIG. 4 shows the data structure of the golf user information table TBL11. A plurality of records are recorded as registration information in the golf user information table TBL11. One record includes identification information UID that uniquely identifies a golf user, registration date, profile information, and round history information. In the present embodiment, the golf user identification information UID has a correspondence relationship with the SNS user identification information UID. However, the identification information of the SNS user and the identification information of the golf user do not necessarily need to match, and may be different. In this case, the SNS user identification information and the golf user identification information may be recorded in association with the record of the golf user information table TBL11.

  Profile information includes gender, age, and email address. The round history information includes the name of the golf course played, the score, and the round date. Other information may be recorded in the record. Moreover, although the golf user identification information UID is essential as information to be stored in the golf user information table TBL11, other information may be omitted. Further, the golf user information table TBL11 may be composed of a plurality of tables linked with key information (for example, identification information UID), and may be a relational database.

  Returning to FIG. The external management server 3 includes an SNS user information table TBL31 in which identification information for uniquely identifying the SNS user, the name of the SNS user, link information indicating the link destination of the profile image, and the like, and friends of the SNS user An SNS friend information table TBL32 storing friend information indicating the relationship is provided. Furthermore, the external management server 3 can execute various APIs (Application Program Interface), and upon receiving a request including a parameter from the management server 1, a predetermined value is received from the SNS user information table TBL31 or the SNS friend information table TBL32. Information is extracted and sent back to the management server 1.

  The management server 1 provides a My Page to each golf user. Information about various types of golf is collected and displayed on the My Page. FIG. 3 shows an example of My Page. As shown in the figure, the profile image of the golf user A is displayed in the area X1, the profile image of the golf user A's direct golf chum is displayed in the area Y1, and further, the area Y2 is displayed in the area Y2. A profile image of an indirect golf friend is displayed. Thus, since the direct golf chum and the indirect golf chum are displayed in different areas Y1 and Y2, the golf user A can easily grasp the hierarchical friendship. In addition, when displaying a golf chum and an indirect golf chum directly in area | region Y1 and Y2, a closeness is calculated and it displays from the near side in order with a high closeness. A method of calculating the familiarity will be described later.

  Next, the SNS user information table TBL31 and the SNS friend information table TBL32 provided in the external management server 3 will be described. FIG. 5 shows the data structure of the SNS user information table TBL31. A plurality of records are recorded in the SNS user information table TBL31. One record includes a name, sex, address, work place, identification information UID that uniquely identifies the SNS user (functioning as an account), and an e-mail address. These pieces of information are personal information registered by the SNS user.

  FIG. 6 shows the data structure of the SNS friend information table TBL32. A plurality of records are recorded in the SNS friend information table TBL32. One record includes the identification information of the action source, the identification information of the action destination, the status, and the application date / time. The action source is the SNS user who made the friend application, and the action destination is the SNS user who made the friend application. The status indicates the status of the friend application, “0” being applied, and “1” being accepted. In the example shown in FIG. 6, the SNS user with the UID “0zz99x999” is the SNS user with the UID “6zz99x999”. A friend application has been made and accepted.

  When storing the friendship relationship, storing the action source (application source) and the action destination (application destination) separately has the advantage of reducing the storage capacity. If the identification information UID of a certain SNS user and the identification information UID of all SNS users who are in friendship with the SNS user are stored in association with each other, twice the storage capacity is required. For example, it is assumed that SNS user a is an action source and SNS user b is an action destination. When storing the identification information of the SNS user who is in a friend relationship for each SNS user, the fact that the user b is in a friend relationship for the user a is stored, and the user a is a friend in the user b. It is necessary to remember that there is a relationship. On the other hand, in the present embodiment, the action destination identification information and the action source identification information are associated with each other and stored in one record, so that the storage capacity can be halved. Even when the status is updated, the processing is half.

  FIG. 7 shows the configuration of the management server 1. As shown in this figure, the management server 1 includes a CPU (Central Processing Unit) 30 that controls the entire apparatus, a RAM (Random Access Memory) 31 that functions as a work area of the CPU 30, a ROM (Read Only) that stores a boot program and the like. Memory) 32, a hard disk drive 33 for storing various programs and data, an input unit 34 including a keyboard and a mouse, a display 35 for displaying an image, a communication interface 36 for communicating with an external device via a communication network NET, And a reading device 37 for reading an information recording medium such as a compact disk. The hard disk drive 33 corresponds to the storage unit 15 described above, and stores a golf user information table TBL11, a user log management table TBL13, a set value management master table TBL15, and an individual log file FL10. The external management server 3 is configured in the same manner as the management server 1. However, the SNS user information table TBL31 and the SNS friend information table TBL32 are stored in the hard disk drive 33.

  FIG. 8 shows the configuration of the terminal device 2. The terminal device 2 includes a CPU 40 that controls the entire device, a RAM 41 that functions as a work area for the CPU 40, a ROM 42 that stores a boot program, a storage device 43 that stores various programs and data, an input unit 44 including a numeric keypad, an image, and the like. And a communication interface 46 for communicating with an external device via a communication network NET.

<2. Operation of the service providing system>
In the service providing system 100 of the present embodiment, the golf user's terminal device 2 can display a relationship diagram showing the hierarchical structure of the golf chum, and the golf user has selected and selected an indirect golf chum. It is possible to request mediation about going to golf together with the selected indirect golf chum with respect to the common golf chum between the indirect golf chum and the golf user. Hereinafter, a display process for displaying a relationship diagram and a mediation request process for requesting mediation for going to golf with a golf chum's golf chum will be described.

<2-1: Display processing>
9 and 10 show an operation sequence of the service providing system related to the display processing. When an SNS user (also a golf user) of the terminal device 2 operates on a web browser or starts an application installed and operated on the terminal device 2 to access the SNS site, the CPU 40 of the terminal device 2 Causes the display 45 to display a login screen. An input box for entering the identification information UID and password is displayed on the login screen. When the user inputs in the input box and presses the transmission button, the CPU 40 of the terminal device 2 transmits a login request including the input identification information UID and password to the external management server 3.

  When the CPU of the external management server 3 receives the login request, the CPU of the external management server 3 executes an authentication process (S300). Specifically, the CPU of the external management server 3 determines whether or not the combination of the identification information UID and the password is stored. If the determination condition is satisfied, the login is permitted and the determination condition is not satisfied. In case it refuses login. Then, the CPU transmits a login response indicating the determination result to the terminal device 2. In the example shown in FIG. 9, it is assumed that login is permitted. The combination of the identification information UID and the password once input at the terminal device 2 may be stored in the terminal device 2 for a predetermined period, and login may be omitted within the predetermined period.

  Thereafter, when the SNS user selects a golf information application from the menu (S200), the CPU 40 of the terminal device 2 transmits a my page browsing request to the management server 1. When receiving the my page browsing request, the CPU 30 of the management server 1 acquires the golf user A's identification information UID included in the my page browsing request, and transmits the golf user A's identification information UID to the external management server 3. (S100).

  When the CPU of the external management server 3 receives the identification information UID of the golf user A, the CPU of the external management server 3 accesses the friend information table TBL, and the identification information UID is recorded as an action source or an action destination. The existing record is extracted (S301). Further, the CPU extracts SNS user information from the SNS user information table TBL31 using the identification information UID recorded as an action source or an action destination in these records as a key (S301). Thereafter, the CPU of the external management server 3 transmits a friend list including the extracted SNS friend information and SNS user information to the management server 1.

  When the CPU 30 of the management server 1 receives the friend list and acquires SNS friend information and SNS user information (S101), the CPU 30 of the management server 1 identifies the direct SNS friend identification information UID of the golf user A. Is specified (S102). Specifically, the CPU 30 identifies the identification information UID excluding the identification information UID of the golf user A and the overlapping identification information UID among the identification information UID recorded as the action source or the action destination in the record of friend information. Is specified as the identification information UID of the direct SNS friend of the golf user A. As a result, as shown in FIG. 11A, a direct SNS friend who is in a friend relationship with the golf user A can be specified. Thereafter, the CPU 30 of the management server 1 directly transmits the SNS friend identification information UID to the external management server 3 (S103).

  When the CPU of the external management server 3 directly receives the SNS friend identification information UID, the CPU of the external management server 3 accesses the SNS friend information table TBL32, and the identification information UID is recorded as the action source or the action destination. Existing records are extracted (S302). Thereafter, the CPU of the external management server 3 transmits a friend list including the extracted SNS friend information to the management server 1.

  When CPU30 of management server 1 receives a friend list and acquires friend information about an indirect SNS friend (S104), CPU30 of management server 1 specifies identification information UID about an indirect SNS friend (S105). Specifically, the CPU 30 specifies the identification information UID excluding the duplicate identification information UID among the identification information UID recorded as the action source or the action destination in the friend information record as the identification information UID of the indirect SNS friend. To do. As a result, as shown in FIG. 11B, the direct SNS friend and the indirect SNS friend who are in a friend relationship with the golf user A can be specified. Thereafter, the CPU 30 of the management server 1 transmits the identification information UID of the indirect SNS friend to the external management server 3 (S106).

  When the CPU 30 of the external management server 3 receives the identification information UID of the indirect SNS friend, the CPU of the external management server 3 accesses the SNS user information table TBL31 and extracts a record in which the identification information UID is recorded. (S303). Thereafter, the external management server 3 transmits the extracted SNS user information to the management server 1.

  When the CPU 30 of the management server 1 receives the SNS user information (S107), as shown in FIG. 10, the golf friend directly based on the identification information UID of the direct SNS friend and the indirect SNS friend and the identification information UID of the golf user. And an indirect golf chum is specified (S108). Specifically, the CPU 30 directly sets the identification information UID of the golf friend directly corresponding to the identification information UID of the golf user among the identification information UID of the direct SNS friend specified in S102. Moreover, CPU30 makes what matches the identification information UID of a golf user among the identification information UID of an indirect SNS friend specified by S105 as identification information UID of an indirect golf chum. Thus, a direct golf chum and an indirect golf chum are specified as shown in FIG.

  Next, the CPU 30 of the management server 1 generates display information for displaying the relationship diagram (S109). Here, CPU30 produces | generates the display information which arrange | positions a golf user's profile image on a screen. In order to reduce the amount of transmission data, the profile image is given as link information indicating the address of the image data. Note that profile image data may be included in the display information instead of the link information.

First, the CPU 30 divides golf friends into “direct golf friends” and “indirect golf friends”, and a relationship diagram in which all “direct golf friends” and “indirect golf friends” are arranged on a virtual screen. Generate. Here, when there are a plurality of direct golf friends, there are various methods for how to arrange them. For example, you may arrange | position at random, or calculate the intimacy of the said golf user A and a direct golf chum, and it is arranged so that the direct golf chum with higher intimacy is arranged near the said golf user A It may be. In this embodiment, the direct golf chum with higher intimacy is displayed on the near side.
In this embodiment, the icon of the profile image of “direct golf chum” is made larger than the icon of the profile image of “indirect golf chum”. When the number of persons to be displayed is large, the screen size is virtually larger than the screen displayed on the display 45 of the terminal device 2. In this case, in the terminal device 2, a virtual screen is cut out to a displayable size and displayed on the display 45.

  The CPU 30 fills “direct golf chum” from the forefront of the virtual screen, and then fills “indirect golf chum”. For example, it is assumed that a screen on which all “direct golf chum” and “indirect golf chum” are arranged is a screen W shown in FIG. The CPU 30 arranges “direct golf chum” on the forefront screen, and arranges “indirect golf chum” after the arrangement of “direct golf chum” is completed. In this case, the CPU 30 arranges “direct golf chum” and “indirect golf chum” in the order of region r1 → region r2 → region r3. The number of people that can be displayed in one area is determined in advance, but may be changed to any number.

  The screen region R1 is first displayed on the display 45 of the terminal device 2. In this case, the area r1 corresponds to the display area Y1 shown in FIG. 3, and the area r2 corresponds to the display area Y2. When the button B2 shown in FIG. 3 is clicked, the CPU 30 causes the display 45 to display the screen area R2. In this case, the region r2 corresponds to the display region Y1 shown in FIG. 3, and the region r3 corresponds to the display region Y2. When the button B2 is clicked in this state, the CPU 30 causes the display 45 to display the screen area R1.

  That is, the display 45 of the terminal device 2 can display a relationship diagram having a size larger than the screen size by sliding the screen in a predetermined direction. When the CPU 30 of the management server 1 cannot arrange “direct golf chum” and “indirect golf chum” on the screen size of the display 45, it arranges “direct golf chum” and “indirect golf chum” in an area larger than the screen size. Display information necessary for displaying the relationship diagram is generated.

  Returning to FIG. Next, the CPU 30 of the management server 1 transmits a my page browsing response including display information to the terminal device 2 (S110). When the CPU 40 of the terminal device 2 receives the my page browsing response, the CPU 40 displays a relationship diagram in which “direct golf chum” and “indirect golf chum” are arranged on the display 45. In this embodiment, as shown in FIG. 3 and FIG. 12, “direct golf chum” is arranged in front, and “indirect golf chum” is arranged behind “direct golf chum”. You can easily grasp the hierarchical relationships of friends. Furthermore, since “direct golf chum” having a deeper relationship with golf user A is displayed with a larger icon than “indirect golf chum”, the hierarchical relationship between the two can be grasped at a glance. In addition, since the “indirect golf chum” has a friendship relationship with each of the golf user A's direct golf chum, there are usually more people than “direct golf chum”. By making the “indirect golf chum” icon smaller than the “direct golf chum” icon, an efficient display is possible.

<2-2: Intimacy calculation method>
Next, the familiarity calculation method in the present embodiment will be described. In the my page shown in FIG. 3, the direct golf chum having higher intimacy in the region Y <b> 1 is displayed on the front side, and the indirect golf chum having higher intimacy in the region Y <b> 2 is displayed on the front side.

The intimacy is a numerical value of the depth of the relationship between the golf user A and the opponent, and this depth of relationship is the golf usage recorded in the user log management table TBL13 and the individual log file FL10. It is judged based on a person's activity and a golf user's profile recorded on golf user information table TBL11.

<2-2-1: Activities that are the basis for calculating intimacy>
In this embodiment, “Invite to golf”, “Perform a golf report”, “Click on a like button for another person's golf report”, “Comment on another person's golf report”, “Log in” ”,“ Click the button for the news! ”And“ Comment on the news ”are recorded in the user log management table TBL13, and the closeness is calculated based on the recorded activity. ing. Hereinafter, these activities will be described.

  In order to invite a golf user to golf in the golf information application of this embodiment, the golf chum displayed directly in the area Y1 is clicked with the My Page shown in FIG. 3 displayed. For example, as shown in FIG. 13, when the direct golf chum icon A <b> 3 displayed in the lower right of the area Y <b> 1 of My Page is clicked, the CPU 40 pops up a notification screen P <b> 5 on the display 45 as shown in FIG. 13. Let CPU40 displays the icon of the directly clicked golf chum in the area | region G1 at the upper left of the information screen P5. The CPU 40 displays the name of the direct golf chum indicated by this icon in the area G2 on the right side of the area G1. Moreover, CPU40 displays the recent posting of the direct golf chum shown by this icon, for example, the golf report mentioned later, etc. on the area | region G3 of the center part of the notification screen P5. In the example shown in FIG. 13, since there is no recent post, the CPU 40 displays “No post”. Further, the CPU 40 displays a button B3 for becoming a friend, a button B4 for inviting golf, and a cancel button B5 at the bottom of the notification screen P5. Then, the CPU 40 displays a cancel button B6 in the upper right corner of the notification screen P5.

  When the cancel button B5 or B6 is clicked, the CPU 40 closes the notification screen P5. When the friend B button B3 is clicked, the CPU 40 transmits a request to the opponent to the effect that he / she wishes to become a golf friend. In the example of FIG. 13, since the golf user of the icon displayed in the region G1 is already a golf chum, display such as “already a golf chum” is performed. Also good. Moreover, in other embodiment, it is not necessary to provide button B3 which becomes a friend.

  When golf user A shown in area X1 of my page shown in FIG. 13 wants to invite a golf user whose icon is displayed in area G1 of notification screen P5 to golf, click button B4 that invites golf. . If button B4 invited to golf is clicked, CPU40 will display the golf chum selection screen P6, as shown in FIG. The CPU 40 displays “invite to golf”, which is an activity to be performed, as a title in the upper left region G4 of the golf chum selection screen P6. The CPU 40 displays the same icon as the area G1 on the notification screen P5 in the area G5 below it. The CPU 40 selects “person who invites golf with Mr. Koichi Sato” in the area G6 to the right of the area G5, including “Koichi Sato” which is the name of the golf user of the icon displayed in the area G5. Please display a message that prompts you to select a golf friend you want to invite to golf. CPU40 displays a golf chum's icon in the area | region G7 of the center part of the golf chum selection screen P6, and can select the golf chum displayed on the area | region G7. In this embodiment, CPU40 is set as the structure by which all the golf friends of the golf user A shown by the area | region X1 are displayed on the area | region G7. Here, among the icons displayed in the region G7, a common golf chum icon between the golf user A and the golf chum shown in the region G5 is displayed as a common friend. Also good. Moreover, in other embodiment, you may comprise so that only a common golf chum may be displayed on the area | region G7.

CPU40 displays decision button B30 and cancel button B7 in the lower part of golf chum selection screen P6, and displays cancel button B8 in the upper right corner of golf chum selection screen P6. By clicking the cancel button B7 or B8, the CPU 40 closes the golf chum selection screen P6.
In order to select a person invited to play golf together from the golf chum indicated by the icon displayed in the area G7, the icon displayed in the area G7 is clicked. For example, when the icon A4 and the icon A5 shown in the area G7 are clicked, the CPU 40 displays a check mark A6 in the area G8 indicated by the dotted line in FIG. When the golf chum icon on which the check mark A6 is displayed is clicked again, the CPU 40 erases the check mark A6. Thus, when the golf chum who wants to invite to golf together is selected and the check mark A6 is displayed and the determination button B30 at the bottom of the golf chum selection screen P6 is clicked, the CPU 40, as shown in FIG. The request transmission screen P7 is displayed as a pop-up.

  The CPU 40 displays “request transmission”, which is an activity to be performed, as a title in the upper left area G10 of the request transmission screen P7. CPU40 displays the icon of the golf chum selected first in the area | region G9 under it. The CPU 40 includes “Koichi Sato” who is the name of the golf friend of the icon displayed in the region G9 on the right side of the region G9, and “Do you want to invite Koichi Sato and two others to golf?” Display a message. In this example, as shown in FIG. 15, since two golf friends are selected and the determination button B30 is clicked, the CPU 40 displays “other two names”. The CPU 40 displays a button B31 and a cancel button B9 for inviting golf at the lower part of the request transmission screen P7. The CPU 40 also displays a cancel button B10 in the upper right corner of the request transmission screen P7. When the cancel button B9 or B10 is clicked, the CPU 40 closes the request transmission screen P7. When adding or changing a golf chum who wants to invite to golf, the user may click the cancel button B9 or B10 to return to the golf chum selection screen P6 shown in FIG. 15 and select a golf chum.

When the golf chum who wants to invite to golf is finally decided, the button B8 invited to golf of the request transmission screen P7 shown in FIG. 16 is clicked. As a result, the CPU 40 transmits a request for inviting to golf to the management server 1 together with the identification information of the golf user A and the identification information of the selected golf chum.
The CPU 30 of the management server 1 that has received this request transmits, for example, a fixed message message “I was invited to golf from Mr. Ichiro Tanaka!” To the selected golf chum in the golf information application.

  Then, when each golf friend logs in to the golf information application, a message “Ichiro Tanaka has invited you to play golf!” Pops up on their own My Page.

  Moreover, CPU30 of the management server 1 which received the said request makes the identification information in the SNS of the golf user A which transmitted the request into the identification information of action origin, and the identification information in the SNS of the golf chum selected in the terminal device 2 is used. As the action destination identification information, for example, a fixed message and a transmission request “I was invited to golf from Mr. Ichiro Tanaka!” Are transmitted to the external management server 3.

The CPU of the external management server 3 that has received the information transmits the fixed message as a message from the golf user A to the selected golf chum in the SNS. As a result, when the selected golf chum logs into the SNS, it can be known that a message has arrived from “Ichiro Tanaka”. Then, by performing an operation for confirming the content, a message “Ichiro Tanaka has invited you to play golf!” Is displayed.
In addition, you may comprise so that it may be notified by e-mail that it was invited to golf.

  Next, the golf report activity will be described. As shown in FIG. 17, the CPU 40 displays a pencil icon X2 at the bottom of the My Page. When the pencil icon X2 is clicked, the CPU 40 pops up a golf report screen P8 as shown in FIG.

  CPU40 displays the title "golf report" on the area | region G12 of the upper part of the golf report screen P8. CPU40 displays the input area | region G13 in the center part of the golf report screen P8. CPU40 displays transmission button B11 and cancellation button B12 in the lower part of golf report screen P8. CPU40 displays cancel button B13 in the upper right corner of golf report screen P8. When the cancel button B12 or the cancel button B13 is clicked, the CPU 40 closes the golf report screen P8.

  As shown in FIG. 17, a comment (for example, a golf report) can be input in the input area G13 of the golf report screen P8, and the CPU 40 inputs the comment by clicking the send button B11 after inputting the comment. A comment is transmitted (posted) to the management server 1.

  CPU40 overlaps with the golf user's icon which posted the comment among the golf user's icons displayed in area | region Y1 of my page, for example, the aspect which overlaps with the upper right corner of a golf user's icon, for example. A comment icon indicating that a comment has been posted is displayed. When the comment icon is clicked, the CPU 40 displays a comment display screen P9 as shown in FIG.

  CPU40 displays the icon of the golf user who contributed the comment to area | region G14 at the upper left of comment display screen P9. CPU40 displays the name of the golf user of the icon displayed on the area | region G14 in the area | region G15 right next to the area | region G14. The CPU 40 displays the posted comment and date / time in a region G16 below the region G15. In the example of FIG. 18, the CPU 40 displays a comment “Going golf!”. The CPU 40 displays a comment input area G17 below the area G16, and can input a comment for this posting. The CPU 40 has a send button B14 and a cancel button B15 at the bottom of the comment display screen P9. Button B16 is displayed. The CPU 40 displays a cancel button B17 in the upper right corner of the comment display screen P9. By clicking the cancel button B15 or B17, the CPU 40 closes the comment display screen P9.

  When commenting on the post displayed in the area G16 of the comment display screen P9, the comment is input in the comment input area G17 and the transmission button B14 is clicked. In the case of FIG. 18, a comment “I also went today!” Is input. When the send button B14 is clicked, the CPU 40 causes the management server 1 to display the golf user identification information UID displayed in the area G14 of the comment display screen P9 and the message from the golf user displayed in the area X1 of the My Page. And the input comment is transmitted. CPU30 of the management server 1 which received the said identification information UID and comment is as a message from the golf user displayed on the area | region X1 of my page to the golf user displayed on the area | region G14 of the comment display screen P9. The input comment is transmitted. Therefore, the golf user displayed in the area G14 of the comment display screen P9 can know that there has been a comment from another golf user with respect to the comment he / she posted by logging in to the golf information application. .

  For posts posted in the area G16 of the comment display screen P9, not only write comments but also good! The button B16 can also be clicked. How nice! By clicking the button B16, it is possible to inform the golf user who posted the comment that the posted comment has been read. That's good! When the button B16 is clicked, the CPU 40 may accept the golf user's identification information UID displayed in the area G14 of the comment display screen P9 and the golf user displayed in the area X1 of the My Page for the posting. ! Information indicating that the button B16 has been clicked is transmitted. I like the identification information UID! The CPU 30 of the management server 1 that has received the information indicating that the button B16 has been clicked and the golf user displayed in the area X1 of the My Page is addressed to the golf user displayed in the area G14 of the comment display screen P9. Good for posting! Information indicating that the button B16 has been clicked is transmitted. Therefore, the golf user displayed in the area G14 on the comment display screen P9 can log in to the golf information application, so that other golf users can like the comment he posted! You can know that you clicked the button.

  As shown in FIG. 19, the CPU 40 displays an icon X4 at the lower left of the My Page. When the icon X4 is clicked, the CPU 40 displays a news list screen N1 as shown in FIG. The news list screen N1 displays, for example, a list of a plurality of news titles. When the title of each news displayed on the news list screen N1 is clicked, the CPU 40 displays a news detail screen N2 as shown in FIG. The CPU 40 displays the news title and the delivery date and time in the upper region G18 of the news detail screen N2. The CPU 40 displays the content of news in a region G19 below the region G18. The CPU 40 displays a comment input area G20 below the area G19, and can input a comment on the news displayed in the area G19 of the news detail screen N2. Under the comment input area G20, the CPU 40 has a send button B18 and likes! Button B19 is displayed. The CPU 40 displays a cancel button B20 in the upper right corner of the news detail screen N2. When the cancel button B20 is clicked, the CPU 40 closes the news detail screen N2.

  When a comment is input in the comment input area G20 and the send button B18 is clicked, the CPU 40 writes a comment in the lower part of the area G18 where the content of the news on the news detail screen N2 is displayed. Further, the CPU 40 transmits the input comment to the management server 1 together with a news ID that uniquely identifies the news. The CPU 30 of the management server 1 that has received the news ID and comment manages the received comment as a comment input for the news. Therefore, when another golf user views this news, the comment is displayed as a comment for the news, so that the other golf user can read the comment. Furthermore, since the said other golf user can also write the comment with respect to this comment, mutual communication will deepen.

  Also nice! When the button B19 is clicked, the CPU 40 likes the lower part of the area G18 where the content of the news on the news detail screen N2 is displayed! The number of people who click the button is displayed, so you can see how much you are interested in the news. Also, which golf user is good! You can also see who clicked the button, so you can find golfers interested in a common topic.

<2-2-2: Log management table>
As mentioned above, “Invite to golf”, “Perform golf report”, “Comment on golf report”, “Click on button like golf report!”, “Click on button like news!” Each activity of “commenting news” and an activity of logging in to the golf information application are recorded in the user log management table shown in FIG.

FIG. 20 shows the data structure of the user log management table TBL13. A plurality of records are recorded in the user log management table TBL13. One record includes log identification information LID that uniquely identifies an access history of the golf user U1 and access history information.
The access history information includes golf user identification information UID, time stamp, access destination, news ID, access destination type, comment presence / absence information, and comment content. Of the access history information, the comment presence / absence information and the comment content may be referred to as input history information.

  The access destination indicates identification information UID of another golf user accessed by the golf user. However, it is good for the news as shown in FIG. When the button is clicked or when a comment is written on the news, the access destination is blank. The news ID is recorded only when the access destination is news, and an ID for identifying individual news is recorded.

  The time stamp indicates the date and time when the golf user accessed the access destination (time when the record was recorded in the user log management table TBL13).

  The access destination type indicates the type of activity when the golf user accesses the access destination. When the button B8 for inviting golf shown in FIG. 16 is clicked, the type is “1”. When the golf report is input to the input area G13 of the golf report screen P8 shown in FIG. 17 and the transmission button B11 is clicked, the type is “2”. I like the golf report on the comment display screen P9 shown in FIG. When the button B16 is clicked, the type is “3”. When a comment for the golf report is input in the comment input area G17 of the comment display screen P9 shown in FIG. 18 and the transmission button B14 is clicked, the type is “4”. When logging into the golf information application, the type is “5”. The log-in is recorded every time the user logs in to the golf information application. I like the news displayed on the news detail screen N2 shown in FIG. When the button B19 is clicked, the type is “6”. When a comment is entered in the comment input area G20 of the news detail screen N2 shown in FIG. 19 and the send button B18 is clicked, the type is “7”.

  The comment presence / absence information is information indicating whether or not the golf user has posted a comment at the access destination. “1” is recorded when a comment is made, and “0” is recorded when a comment is not made. The The comment content represents the content of the comment posted by the golf user.

  In the present embodiment, the CPU 30 of the management server 1 records the activity of each golf user in the user log management table TBL13 as described above over a predetermined period, for example, 120 days. Then, based on the user log management table TBL13, the CPU 30 creates or updates the individual log file FL10 for calculating familiarity, for example, once a day. 21 and 22 show the structure of the individual log file FL10. The individual log file FL10 (FL10a) shown in FIG. 21 includes the activity that caused an action from the golf user A, that is, the identification information UID of the golf user A as the identification information UID of the user log management table TBL13 of FIG. This is an extracted record. The individual log file FL10 (FL10b) shown in FIG. 22 is an activity with an action on the golf user A, that is, identification information of the golf user A as an access destination of the user log management table TBL13 of FIG. Is a record that is recorded.

  These individual log files FL10 (FL10a, FL10b) are referred to in the familiarity calculation process described later. Note that these individual log files FL10 (FL10a, FL10b) are created or updated for each golf user.

<2-2-3: Profile that is the basis for calculating intimacy>
In this embodiment, not only the activity of each golf user described above but also the profile information of each golf user is used as a basis for calculating the intimacy. As shown in FIG. 23, the CPU 40 displays the icon of the golf user A in the area X1 at the bottom of My Page. When the icon of the golf user A in the region X1 is clicked, the CPU 40 displays a profile setting screen P10 as shown in FIG. CPU40 displays the message "Please input a golf profile." On the area | region H1 of the upper part of the profile setting screen P10. CPU40 displays the input area H2 for setting own golf history below the area | region H1. The CPU 40 displays pull-downs H3 and H4 for setting the round frequency below the input area H2. The CPU 40 displays pull-downs H5 and H6 for setting the practice frequency below the pull-downs H3 and H4. The CPU 40 displays an input area H7 for setting an average score below the pull-down H5. The CPU 40 displays a scroll bar B21 on the right side of the profile setting screen P10. When the scroll bar B21 is used to scroll the screen, the CPU 40 displays a determination button at the bottom of the profile setting screen P10. And cancel button are displayed. The display of the enter button and the cancel button in FIG. 23 is omitted.

Further, although not shown in FIG. 23, round history information can also be recorded by scrolling the screen using the scroll bar B21. Round history information is information about when, with whom, to which golf course, and the like.
The contents input to each input area described above and the contents selected by each pull-down are transmitted from the CPU 40 to the management server 1, and the CPU 30 of the management server 1 that receives them is a golf user stored in the hard disk 33. These contents are stored in the information table TBL11.

  In addition, the CPU 40 displays a setting icon X5 on the My Page as shown in FIG. 23. By clicking the setting icon X5, the golf user A's name, gender, age, e-mail address, Basic data such as addresses can be edited. These basic data are registered when participating in the golf information application, but can be edited thereafter. These basic data are also transmitted to the management server 1 by the CPU 40, and the CPU 30 of the management server 1 that has received the basic data stores the basic data in the golf user information table TBL 11 stored in the hard disk 33.

<2-2-4: Golf user information table>
FIG. 24 is a diagram showing details of the record RCD1 for each golf user recorded in the golf user information table TBL11. The record RCD1 for each golf user shown in FIG. 24 includes a plurality of fields for recording identification information, profile information, and round history information. The identification information UID is recorded in the field F1. The profile information includes name, registration date, gender, age, e-mail address, address, golf history, hometown, round frequency, practice frequency. The name, registration date, gender, age, and mail address are recorded in the fields F1 to F6, respectively. The field in which the address is recorded is divided into, for example, a field F7 in which the prefecture is recorded, a city or a ward in the field F8, and a field F9 in which other addresses are recorded. Golf history is recorded in field F10, and hometown is recorded in field F11. The round frequency and the practice frequency are recorded in the fields F12 and F13, respectively. These fields are a field in which a unit of “year”, “month” or “week” is recorded, and the number of times is recorded. It is divided into fields. The round history information includes a round date, a golf course, a score, and a party. The round date, golf course, and score are recorded in fields F14 to F16, respectively. The party is information about golf users who have rounded together. In the present embodiment, as an example, an identification number UID of a golf user who has rounded together is recorded in the field F17.

  Information that is not related to golf, such as name, gender, age, address, birthplace, and e-mail address, is not necessarily stored in the golf user information table TBL11, and is acquired from the external management server 3 as necessary. You may make it do.

<2-2-5: Specific example of calculating intimacy>
In the present embodiment, six types of indices are used as indices representing intimacy, and the intimacy is calculated comprehensively by weighting each index. The indicators used in the present embodiment are as follows: indicator 1: actual exchange frequency (k0), indicator 2: exchange frequency (k1) in the golf information application, indicator 3: action frequency (k2) in the golf information application, indicator 4: Address proximity (k3), index 5: age proximity (k4), index 6: golf frequency (k5), the above six types of indices.
For the quantification of each index, the set value management master table TBL15 (TBL15a to TBL15i) shown in FIGS. 25 to 34 is used. Hereinafter, the digitization of each index will be described with reference to FIGS.

  The actual AC frequency (k0) of the index 1 is determined with reference to the log of the type “1” recorded in the individual log file FL10 (FL10a, FL10b). As described above, when the user invites the golf chum to golf by clicking the button B8 that invites the golf shown in FIG. 16, the CPU 30 of the management server 1 displays the time stamp in the user log management table TBL13 shown in FIG. The identification information UID of the invited golf user, the identification information (access destination) of the invited golf chum, and “1” are recorded as the type. Therefore, a log when the golf user is invited is recorded in the individual log file FL10a, and a log when the golf user is invited is recorded in the individual log file FL10b.

  In order to digitize the actual exchange frequency (k0) for a certain golf chum, first, the CPU 30 records the identification information of the golf chum specified by the method described above in the individual log file FL10 (FL10a, FL10b). Determine whether or not. When the identification information of the golf chum is not recorded in the individual log file FL10 (FL10a, FL10b), the CPU 30 sets the actual exchange frequency for the golf chum to 0 points.

  Next, when the identification information of the golf chum is recorded in the individual log file FL10 (FL10a, FL10b), the CPU 30 determines whether or not there is a log of type “1” in the recorded logs. judge. When there is no log of the type “1” in the recorded logs, the CPU 30 sets the actual exchange frequency for the golf chum to 0 points.

  When the identification information of the golf chum is recorded in the individual log file FL10 (FL10a, FL10b) and there is a log of the type “1”, the CPU 30 refers to the time stamp of the log, It is determined how many days from the current date when the log is recorded is determined. The day when the log of type “1” is recorded in the individual log file FL10a represents the day invited to golf, and the day when the log of type “1” is recorded in the individual log file FL10b is the day invited to golf Will be expressed.

  Then, the CPU 30 refers to the set value management master table TBL15a shown in FIG. 25 to determine the day when the log is recorded, that is, the day when the golf chum is invited to golf or the day when the golf chum is invited. If the current exchange frequency is within 30 days, the actual exchange frequency (k0) is 20 points, 15 points if within 60 days, 10 points if within 90 days, and if earlier than 90 days 5 points. When there are a plurality of corresponding logs, the log closest to the current date may be adopted.

  CPU30 performs the above process about all the direct golf chums and indirect golf chums, makes each identification information respond | correspond, and memorize | stores the point of actual alternating current frequency (k0). These points of actual AC frequency (k0) may be temporarily stored in the hard disk drive 33 or may be stored as data of the golf user information table TBL11. Of course, instead of temporarily storing the data in the hard disk drive 33, the data may be stored in the RAM 31.

  The CPU 30 determines the AC frequency (k1) in the golf information application of the index 2 with reference to the log of the type “3” or “4” recorded in the individual log file FL10 (FL10a, FL10b). As mentioned above, I like the golf report shown in FIG. When the button B16 is clicked, the CPU 30 adds a time stamp to the user log management table TBL13 shown in FIG. The identification information UID of the golf user who clicked the button, the identification information (access destination) of the golf chum who made the golf report, and “3” as the type are recorded. Moreover, if a comment is input with respect to the golf report shown in FIG. 18 and transmission button B14 is clicked, CPU30 will display the time stamp and the golf user who transmitted the comment in user log management table TBL13 shown in FIG. Identification information UID, identification information (access destination) of the golf chum who made the golf report, and “4” as the type. Therefore, the individual log file FL10a is good for the golf user to the other person's golf report! When the button is clicked and when a golf user leaves a comment on another person's golf report, a log is recorded, and the individual log file FL10b is good for a golf user's golf report! When is clicked, and when a comment is left on the golf user's golf report, a log is recorded.

  In order to digitize the exchange frequency (k1) in the golf information application for a certain golf chum, first, the CPU 30 uses the individual log file FL10 (FL10a, FL10b) to identify the golf chum identified by the above-described method. ) Is recorded. When the identification information of the golf chum is not recorded in the individual log file FL10 (FL10a, FL10b), the CPU 30 sets the exchange frequency (k1) 0 points in the golf information application for the golf chum.

  Next, when the identification information of the golf chum is recorded in the individual log file FL10 (FL10a, FL10b), the CPU 30 stores a log of the type “3” or “4” in the recorded log. Determine if it exists. If there is no log of type “3” or “4” in the recorded log, the CPU 30 sets the exchange frequency (k1) in the golf information application for the golf chum to 0 points.

  When the identification information of the golf chum is recorded in the individual log file FL10 (FL10a, FL10b) and there is a log of the type “3” or “4”, the CPU 30 records each log. Calculate the number of times.

  Then, the CPU 30 refers to the setting value management master table TBL15b shown in FIG. 26, that is, the number of times the log of the type “3” is recorded, that is, it is good! Like the number of clicks on the button! If the total number of times the button is clicked is 91 times or more, then it is good! The frequency (k1-1) is 10 points, 7 points if 61 to 90 times, 4 points if 31 to 60 times, and 1 point if 1 to 30 times. In this way, the CPU 30 is good first! Points of the frequency (k1-1).

  Next, similarly, the CPU 30 refers to the set value management master table TBL15b shown in FIG. 26, the number of times the log of the type “4” is recorded, that is, the number of times that a comment is left on the golf report, If the total number of comments received regarding the golf report is 91 times or more, the comment frequency (k1-2) is 10 points, 7 points if 61 to 90 times, 4 points if 31 to 60 times. If it is 1 to 30 times, it is 1 point. In this way, the CPU 30 calculates the points of the comment frequency (k1-1).

  Finally, CPU30 is good to calculate as above! The points of the frequency (k1-1) and the points of the comment frequency (k1-1) are totaled to calculate the points of the exchange frequency (k1) in the golf information application.

  CPU30 performs the above process about all the direct golf chum and indirect golf chum, makes each identification information respond | correspond, and memorize | stores the point of the alternating current frequency (k1) in a golf information application. The points of the AC frequency (k1) in these golf information applications may be temporarily stored in the hard disk drive 33, or may be stored as data in the golf user information table TBL11. Of course, instead of temporarily storing the data in the hard disk drive 33, the data may be stored in the RAM 31.

  The CPU 30 indicates that the action frequency (k2) in the golf information application of the index 3 is “2”, “5”, “6”, “7” as the types recorded in the individual log files FL10 (FL10a, FL10b). Judge by referring to the log. As described above, when the golf report shown in FIG. 17 is written and the transmission button B11 is clicked, the CPU 30 stores the time stamp and the golf user who transmitted the golf report in the user log management table TBL13 shown in FIG. The identification information UID and “2” are recorded as the type. Each time the user logs in to the golf information application, the CPU 30 records “5” as the time stamp, the identification information UID of the logged-in golf user in the user log management table TBL13 shown in FIG. . Also, for the news shown in FIG. When the button B19 is clicked, the CPU 30 adds a time stamp to the user log management table TBL13 shown in FIG. The identification information UID of the golf user who clicked the button, the news ID, and “6” as the type are recorded. When a comment is input to the news shown in FIG. 19 and the send button B18 is clicked, the CPU 30 stores a time stamp and identification of the golf user who input the comment in the user log management table TBL13 shown in FIG. The information UID, news ID, and “7” are recorded as the type. Therefore, in the individual log file FL10a, the activity logs as described above are recorded for each golf chum and each golf chum golf chum.

  In order to digitize the action frequency (k2) in the golf information application for a certain golf chum, the CPU 30 first refers to the individual log file FL10 (FL10a, FL10b) of the golf chum specified by the method described above. . Next, the CPU 30 determines whether or not there is a log of type “2”, “5”, “6”, “7” in the individual log file FL10 (FL10a, FL10b) of the golf chum. When there is no log of type “2”, “5”, “6”, “7” in the recorded log, the CPU 30 determines the action frequency (k2) in the golf information application for the golf chum. ) Is 0 points.

  When the individual log file FL10 (FL10a, FL10b) of the golf chum has logs of type “2”, “5”, “6”, “7”, the CPU 30 recorded each log. Calculate the number of times.

  Then, the CPU 30 refers to the set value management master table TBL15c shown in FIG. 27, calculates the number of times that the log of type “2” is recorded, that is, the number of times that the golf report has been made, and stores it as n1. Further, the CPU 30 calculates the number of times the log of the type “5” is recorded, that is, the number of times of logging in to the golf information application, and stores it as n2. Further, the CPU 30 is good for the number of times the log of type “6” is recorded, that is, news! The number of times the button is clicked is calculated and stored as n3. Then, the number of times the log of the type “7” is recorded, that is, the number of times the comment is posted on the news is calculated and stored as n4.

  The CPU 30 sums up the respective times n1, n2, n3, and n4 recorded as described above. If the total number is 46 times or more, the action frequency (k2) in the golf information application is 10 points. 7 points if 31 to 45 times, 4 points if 16 to 30 times, 1 point if 1 to 15 times. Thus, CPU30 calculates the point of action frequency (k2) within a golf information application.

  CPU30 performs the above process about all the direct golf chum and indirect golf chum, makes each identification information respond | correspond, and memorize | stores the point of action frequency (k2) in a golf information application. The points of the action frequency (k2) in the golf information application may be temporarily stored in the hard disk drive 33 or may be stored as data of the golf user information table TBL11. Of course, instead of temporarily storing the data in the hard disk drive 33, the data may be stored in the RAM 31.

  For the address proximity (k3) of the index 4, the CPU 30 records RCD1 for each golf user recorded in the golf user information table TBL11 shown in FIG. 24, the set value management master table TBL15d shown in FIG. It is digitized by referring to the set value management master table TBL15e shown in FIG.

  In order to digitize the address proximity (k3) of a golf chum, the CPU 30 first refers to the record RCD1 for each golf user in the golf user information table TBL11 of the golf chum specified by the method described above. Then, the prefecture of the address of the golf chum recorded in the field F7 is read. Similarly, the CPU 30 refers to the record RCD1 for each golf user in the golf user information table TBL11 of the golf user A, and determines the prefecture of the address of the golf user A recorded in the field F7. read.

  And CPU30 searches the row | line | column which matches the prefecture of the said golf chum's address from the column where the prefecture of the setting value management master table TBL15d shown in FIG. 28 was recorded. Next, the CPU 30 searches a column that matches the prefecture of the address of the golf user A from the row in which the prefecture of the set value management master table TBL15d shown in FIG. 28 is recorded. And CPU30 reads the numerical value currently recorded on the area | region specified by the said row and column. For example, when the prefecture of the golf friend's address is “Aomori Prefecture” and the prefecture of the golf user A's address is “Iwate Prefecture”, the CPU 30 sets the numerical value to “1”. In the set value management master table TBL15d, “0” indicates that the prefectures match, “1” indicates that the prefectures are close to each other, and “2” indicates the other.

In addition, when the prefecture of the address is not recorded in the record RCD1 for each golf user in the golf user information table TBL11 of the golf chum, or when it is recorded but not set to private The CPU 30 sets the address proximity (k3) to 0 points.
Next, the CPU 30 refers to the setting value management master table TBL15e shown in FIG. 29, and when the value read from the setting value management master table TBL15d is “0”, the address proximity (k3) is 20 points. , “1” is 10 points, and “2” is 5 points.

  CPU30 performs the above process about all the direct golf chums and indirect golf chums, matches each identification information, and memorize | stores the point of address proximity (k3). These points of the address proximity (k3) may be temporarily stored in the hard disk drive 33 or may be stored as data of the golf user information table TBL11. Of course, instead of temporarily storing the data in the hard disk drive 33, the data may be stored in the RAM 31.

In the above-described example, only the prefectures in the address are compared. However, it is also possible to compare the city or ward, or a more detailed address in the same manner, and add the respective numerical values.
Moreover, the set value management master table TBL15d ′ shown in FIG. In the set value management master table TBL15d ′ shown in FIG. 30, the reference prefecture and the neighboring prefectures associated with the reference prefecture are recorded. For example, when the reference prefecture is “Chiba prefecture”, “Ibaraki prefecture”, “Saitama prefecture”, “Tokyo metropolitan area”, and “Kanagawa prefecture” are recorded as the neighboring prefectures corresponding thereto. When the set value management master table TBL15d ′ shown in FIG. 30 is used, the CPU 30 first refers to the record RCD1 for each golf user in the golf user information table TBL11 of the golf user A and records it in the field F7. The prefecture of the address of the golf user A is read. Further, the CPU 30 refers to the record RCD1 for each golf user in the golf user information table TBL11 of the golf chum specified by the method described above, and reads the prefecture of the address of the golf chum recorded in the field F7. Next, the CPU 30 specifies the reference prefecture of the set value management master table TBL15d ′ that matches the prefecture of the address of the golf user A. Then, the CPU 30 sets the numerical value to “0” when the prefecture of the address of the golf chum matches the specified reference prefecture. Further, when the prefecture of the address of the golf chum matches with the specified reference prefecture, the CPU 30 sets the numerical value to “1”. If the prefecture of the golf chum's address does not match the specified neighboring prefecture, the CPU 30 sets the numerical value to “2”. After determining the numerical value in this way, the address proximity (k3) point may be determined with reference to the set value management master table TBL15e shown in FIG. It should be noted that the reference prefecture and the neighboring prefectures may be stored by using identification information associated with each prefecture name in advance instead of the prefecture name.

  The CPU 30 uses the record RCD1 for each golf user recorded in the golf user information table TBL11 shown in FIG. 24 and the set value management master table TBL15f shown in FIG. 31 for the age proximity (k4) of the index 5. It is digitized by reference.

  In order to quantify the age proximity (k4) of a golf chum, the CPU 30 first refers to the record RCD1 for each golf user in the golf user information table TBL11 of the golf chum specified by the method described above. The age of the golf chum recorded in the field F5 is read. Similarly, the CPU 30 refers to the record RCD1 for each golf user in the golf user information table TBL11 of the golf user A, and reads the age of the golf user A recorded in the field F5.

  Then, the CPU 30 calculates the difference between the age of the golf chum and the age of the golf user A, and refers to the set value management master table TBL15f shown in FIG. 31, when the difference is ± 0. Age proximity (k4) is 16 points, 14 points for -3, 12 points for +3, 10 points for -5, 8 points for +5, less than -5 6 points in the case, and 4 points if it is larger than +5.

  The above process is performed for all direct golf chums and indirect golf chums, and the points of age proximity (k4) are stored in association with the respective identification information. These points of age proximity (k4) may be temporarily stored in the hard disk drive 33 or may be stored as data in the golf user information table TBL11. Of course, instead of temporarily storing the data in the hard disk drive 33, the data may be stored in the RAM 31.

  As for the golf frequency (k5) of the index 6, the CPU 30 records RCD1 for each golf user recorded in the golf user information table TBL11 shown in FIG. 24, the set value management master table TBL15g shown in FIG. It is digitized by referring to the set value management master table TBL15h shown in FIG.

  In order to digitize the golf frequency (k5) for a certain golf chum, the CPU 30 first refers to the record RCD1 for each golf user in the golf user information table TBL11 of the golf chum specified by the method described above, The round frequency of the golf chum recorded in the field F12 and the practice frequency of the golf chum recorded in the field F13 are read. Similarly, the CPU 30 refers to the record RCD1 for each golf user in the golf user information table TBL11 of the golf user A, the round frequency of the golf user A recorded in the field F12, and the field The practice frequency of the golf user A recorded in F13 is read.

  The round frequency and the practice frequency are each composed of data on units of “year”, “month”, and “week” and data on the number of times. First, the CPU 30 searches the row that matches the data about the unit of the round frequency of the golf user A from the column of option 1 of the set value management master table TBL15g of FIG. Next, the CPU 30 searches the row that matches the data about the number of round frequencies of the golf user A from the column of option 2 in the row. Then, the CPU 30 reads the numerical value of the rank column corresponding to the row. For example, if the round frequency of the golf user A is “yearly” or “2-3 times”, the CPU 30 sets the rank to “2”. Similarly, CPU30 reads the rank of the said golf chum's round frequency, and calculates the difference of the said golf user's A round frequency rank and the said golf chum's round frequency. For example, if the round frequency of the golf chum is “annual” or “five times or more”, the CPU 30 sets the round frequency rank of the golf chum to “3” and ranks the round frequency of the golf user A. The difference from “2” is +1.

  Similarly, CPU30 reads the rank of practice frequency of the said golf user A and the said golf chum also about practice frequency, and calculates | requires a difference. Note that the CPU 30 sets the rank to “0” when “almost not go” is selected for both the round frequency and the practice frequency.

  Then, the CPU 30 refers to the set value management master table TBL15h shown in FIG. 33. First, when the round frequency rank difference is 0, the round frequency point (k5-1) is 10 points within ± 2. 5 points, 1 point if within ± 3, 0 point if ± 4 or more. Similarly, the CPU 30 calculates the practice frequency point (k5-2).

  Finally, the CPU 30 adds the round frequency point (k5-1) and the practice frequency point (k5-2) to calculate the golf frequency (k5) point for the golf chum.

  CPU30 performs the above process about all the direct golf chum and indirect golf chum, makes each identification information respond | correspond, and memorize | stores the point of age proximity (k4). These points of age proximity (k4) may be temporarily stored in the hard disk drive 33 or may be stored as data in the golf user information table TBL11. Of course, instead of temporarily storing the data in the hard disk drive 33, the data may be stored in the RAM 31.

  CPU30 is about the point of actual exchange frequency (k0), the point of exchange frequency (k1) in a golf information application, the point of action frequency (k2) in a golf information application, and address proximity (k3) about a certain friend. After the points, the age proximity (k4) point, and the golf frequency (k5) point are calculated, the set value management master table TBL15i shown in FIG. To do.

  In the example shown in FIG. 34, the CPU 30 is 1.2 for the point of the actual exchange frequency (k0), 1 for the point of the exchange frequency (k1) in the golf information application, and the action frequency (k2) in the golf information application. ) Point is 0.8, address proximity (k3) point is 0.6, age proximity (k4) point is 0.4, and golf frequency (k5) point is .0. Multiply each by 2, add up all the points, and calculate intimacy points.

  CPU30 performs the above process about all the direct golf chum and indirect golf chum, matches each identification information, and memorize | stores the point of intimacy. These intimacy points may be temporarily stored in the hard disk drive 33 or may be stored as data in the golf user information table TBL11. Of course, instead of temporarily storing the data in the hard disk drive 33, the data may be stored in the RAM 31.

<2-3: Mediation request processing>
Next, the mediation request process in this embodiment will be described with reference to FIGS. FIG. 35 shows an operation sequence of the service providing system related to the mediation request process. First, when the golf user of the terminal device 2 selects one indirect golf chum, for example, by clicking the icon A1 among the indirect golf chum displayed in the area Y2 in the my page shown in FIG. 3 (S210), The CPU 40 of the terminal device 2 manages the common friend page request together with the identification number UID of the golf user A who is the user of the terminal device 2 and the identification information UID of the indirect golf chum associated with the icon A1. 1 (S211). When the CPU 30 of the management server 1 receives the identification information UID of the golf user A, the identification information UID of the indirect golf chum, and the common friend page request, the received identification information UID of the golf user A and the indirect The golf friend's identification information UID is transmitted to the external management server 3 (S120). In addition, although the display information of the direct golf chum icon displayed on the area | region Y1 and the display information of the indirect golf chum icon displayed on the area | region Y2 are the information transmitted from the management server 1, this implementation In the form, it is assumed that the display information includes the direct golf chum identification information UID and the indirect golf chum identification information UID.
In addition, although this embodiment demonstrated the case where the subsequent process (after S211 of FIG. 35) was performed by clicking the icon of the indirect golf chum displayed on the my page shown in FIG. In the form, a button such as “request mediation” may be provided, and after this button is clicked and an indirect golf chum is selected, a process for extracting a common golf chum may be performed.

  When the CPU of the external management server 3 receives the identification information UID of the indirect golf chum, the CPU of the external management server 3 accesses the friend information table TBL32, and the identification information UID is recorded as the action source or the action destination. Existing records are extracted (S320). Further, the CPU extracts SNS user information from the SNS user information table TBL31 using the identification information UID recorded as an action source or an action destination in these records as a key (S320). Similarly, when the CPU of the external management server 3 receives the identification information UID of the golf user A, the CPU of the external management server 3 accesses the friend information table TBL32 and the identification information UID is the action source or action destination. The record recorded as is extracted (S320). Further, the CPU extracts SNS user information from the SNS user information table TBL31 using the identification information UID recorded as an action source or an action destination in these records as a key (S320). Thereafter, the CPU of the external management server 3 includes a friend list including SNS friend information and SNS user information extracted for the indirect golf chum, and SNS friend information and SNS user information extracted for the golf user A. Is sent to the management server 1 (S321).

  CPU30 of management server 1 receives these friend lists, SNS friend information and SNS user information about the indirect golf chum, and SNS friend information and SNS user information about the golf user A (S121), the CPU 30 of the management server 1 refers to the golf user information table TBL11, and specifies a golf chum who is a golf user from the extracted SNS friends. Furthermore, CPU30 of the management server 1 extracts the common golf chum who is a golf chum common to the said indirect golf chum and the said golf user A, and produces | generates a common golf chum page (S123).

  Specifically, firstly, the CPU 30 identifies the indirect golf chum's identification information UID and overlapping identification information among the identification information UID recorded as an action source or an action destination in a record in which the status of the friend information is acceptance. The identification information UID excluding the UID is specified as the identification information UID of the SNS friend of the indirect golf chum.

  2ndly, CPU30 acquires golf user identification information UID with reference to golf user information table TBL11.

  3rdly, CPU30 specifies the golf user's identification information UID which corresponds to the indirect golf chum's SNS friend's identification information UID as 1st golf chum's identification information UID.

  4thly, CPU30 remove | excluded the said golf user's A identification information UID and the overlapping identification information UID among the identification information UID currently recorded on the record of consent as an action origin or action destination in the record of consent. The identification information UID is specified as the identification information UID of the SNS friend of the golf user A.

  Fifth, the CPU 30 refers to the golf user information table TBL11 and acquires the golf user identification information UID.

  Sixth, the CPU 30 specifies the golf user identification information UID that matches the SNS friend identification information UID as the second golf chum identification information UID.

  Seventh, the CPU 30 compares the identification information UID of the first golf chum and the identification information UID of the second golf chum, specifies the matching identification information UID, and uses the indirect golf chum and the golf use. The common golf chum's identification information UID common to the person A is extracted.

  Eighth, CPU30 produces | generates a common golf chum page using SNS user information corresponding to the identification information UID of a common golf chum.

  Thereafter, the CPU 30 of the management server 1 transmits a common golf chum page response to the terminal device 2 (S123). CPU40 of the terminal device 2 which received the common golf chum page response displays a common golf chum page on the display 45 (S211). An example of a common golf chum page is shown in FIG. In this example, the CPU 40 displays the common golf chum page P1 in the form of a pop-up display on the my page shown in FIG. CPU40 displays the title "you and Yoko Yamada's common golf chum" on the uppermost area C1 of the common golf chum page P1. In this embodiment, the case where the name of the golf chum of the golf chum displayed by icon A1 of FIG. 3 is "Yoko Yamada" is shown. In other words, the title displayed in the area C1 includes the name of the golf chum selected by the golf user A. The CPU 40 displays the icon of the golf user A in the lower left area C2 of the area C1, and displays the icon of the indirect golf chum selected by the golf user A in the area C3 adjacent to the right. CPU40 displays the button for closing common golf chum page P1 in area | region C4 of the upper right end part of common golf chum page P1. The CPU 40 displays an operation screen for narrowing down friends in the area C5 at the lower right of the area C1. The CPU 40 displays a condition for narrowing down friends together with a radio button in a region C6 at the left end of the operation screen. In the present embodiment, the conditions “not specified”, “same generation”, “close golf history”, “neighborhood”, and “hometown” are displayed. The example of FIG. 36 shows a state where “undesignated” is selected. Further, the CPU 40 displays an execution button in the area C7 at the lower end of the area C5. The golf chum narrowing process will be described later.

  CPU40 displays a common golf chum's icon in the area | region C8 of the center part of the common golf chum page P1, and the area | region C9 and area | region C10 which follow it. In the example shown in FIG. 36, the CPU 40 displays the common golf chum icon only in the area C8, but also displays it in the area C9 and the area C10 according to the number of extracted common golf chum. The CPU 40 displays a button at the right and left ends of the region C8, the region C9, and the region C10, or at the bottom of the region C10, and displays so that more common golf friends can be displayed in response to clicking the button. You may make it scroll. In the present embodiment, as an example, the golf user A and the golf chum having higher intimacy are displayed above. That is, the golf chum displayed in the area C8 has the highest intimacy, and the intimacy decreases as the area C9 and the area C10 decrease. In addition, as described above, the intimacy is calculated when the golf chum is displayed in the area Y1 of the My Page and the golf chum of the golf chum is displayed in the area Y2, and is recorded in the golf user information table TBL11. And However, it may be recorded in a table different from the golf user information table TBL11.

  The description returns to FIG. The CPU 40 displays the common golf chum page P1 as described above, and the golf chum selected by the golf user A from the golf chum displayed in the areas C8 to C10 of the common golf chum page P1. The selection of the golf chum who requests mediation about going to golf with the golf chum is accepted (S212). In the example shown in FIG. 36, if the golf chum displayed with the icon A2 is selected, as shown in FIG. 37, the CPU 40 displays the message page P2 in a pop-up manner over the icon A2 (S213).

  CPU40 displays the icon of the selected golf chum in the area | region D1 at the upper left of the message page P2. In the example shown in FIG. 37, the same icon as the icon A2 is displayed. The CPU 40 displays an execution button in which “Do you want to ask this person for mediation?” Is displayed in a region D2 on the right side of the region D1. The CPU 40 displays a button for closing the message page P2 in the upper right area D3 of the message page P2. The CPU 40 displays a message entry field for entering a message for mediation request in the center area D4 of the message page P2. The CPU 40 displays a button for attaching an image or a moving image in the lower right area D5 of the message page P2. The CPU 40 displays a message posting date and time in an area D6 below the central area D4.

  In the message entry field, for example, enter a message such as “I would like to play golf with Yoko Yamada. Please set.” Then, when the execution button described in the area D2 “Do you want to ask this person for mediation?” Is clicked, the CPU 40 accepts the selection of mediation request (S214), and the request as shown in FIG. A transmission confirmation dialog P3 is displayed. The CPU 40 displays a title such as “request transmission confirmation dialog” in the upper left area E1 of the request transmission confirmation dialog P3. The CPU 40 displays a message such as “Would you like to tell Mr. Ichiro Tanaka that you want to play golf with this person?” In the area E2 below the area E1. In the example shown in FIG. 38, the case where the name of the golf chum displayed by icon A2 is Ichiro Tanaka is shown. That is, the CPU 40 displays the name of the golf chum who requests mediation in the area E2. The CPU 40 displays a send button in the area E3 below the area E2, and displays a cancel button in the area E4 adjacent to the right. When the cancel button displayed in the area E4 is clicked, the CPU 40 returns to the previous display state in which the request transmission confirmation dialog P3 shown in FIG. 38 is displayed. On the other hand, when the transmission button displayed in the area E3 is clicked and the CPU 40 accepts selection of transmission (S216), the CPU 40 of the terminal device 2 sends the identification information UID of the golf user A to the management server 1; A message transmission request is transmitted together with the identification information UID of the golf chum who requests mediation, the content of the message, etc. (S217). The CPU 30 of the management server 1 that receives the identification information UID of the golf user A, the identification information UID of the golf chum who requests mediation, the message content, and the message transmission request, requests mediation from the golf user A A transmission request process is performed with respect to the external management server 3 so as to transmit a message addressed to the golf friend to be transmitted with the content (S124). The CPU of the external management server 3 that has received the transmission request transmits a message of the content to the golf chum who requests mediation from the golf user A (S322). The CPU 40 of the terminal device 2 displays a transmission completion message P4 as shown in FIG. 39 (S217).

  Then, when the golf chum who requested the mediation logs in to the SNS site, the message from the golf user A can be read. As a result, it is expected that the golf chum who has read this message mediates going to golf with the golf user A for the golf chum of the selected golf chum. Thus, even if it is a golf chum of a golf chum who is not directly related, by requesting mediation from the golf chum, the possibility of going to golf together increases.

<2-4: Narrowing processing>
Next, the common golf chum narrowing-down process in the present embodiment will be described with reference to FIGS. As shown in FIG. 40, CPU40 of the terminal device 2 displays the common golf chum page P1 (S211). As shown in FIG. 36, the CPU 40 displays an operation screen in the area C5 of the common golf chum page P1. The CPU 40 displays a condition for narrowing down friends together with a radio button in a region C6 at the left end of the display screen. In the present embodiment, the conditions “not specified”, “same generation”, “close golf history”, “neighborhood”, and “hometown” are displayed. When a radio button corresponding to a desired condition is clicked, the CPU 40 sets a narrowing condition (S220). When the execution button displayed in the area C7 is clicked and the CPU 40 accepts selection of execution of the narrowing process (S221), the CPU 40 of the terminal device 2 transmits a narrowing process request to the management server 1 (S222). When the CPU 30 of the management server 1 receives the narrowing processing request, the CPU 30 of the management server 1 extracts a common golf chum that matches the set conditions from the common golf chum (S130).

  What is necessary is just to perform the extraction process of the common golf chum matching the set conditions by the method according to the calculation of the familiarity mentioned above. For example, if “same generation” is a condition, the golf user A and the same age group are extracted by comparing the age data recorded in the field F5 shown in FIG. That's fine. As a specific example, when the difference is within 3 years based on the data of the age of the golf user A is set in advance, and when the “same generation” is selected, the golf user It is assumed that A age data and common golf chum age data are compared to perform processing for extracting common golf chum that meets the conditions. The “age data” may be configured to use registered age information, if there is registered. If birthday information is registered, the age is calculated from the birthday information and the current date. It is also good.

  When “goal golf history is close” is a condition, the golf user A and the common golf chum having a close golf history are extracted by comparing the golf history data recorded in the field F10 shown in FIG. What should I do? When a specific example is given, “difference is within two years based on the golf history data of the golf user A” is set in advance, and when “close golf history” is selected, The golf user A's golf history data and the common golf chum's golf history data are compared, and a process of extracting a common golf chum corresponding to the condition is performed. “Golf history data” refers to pre-registered golf history data.

  When "Neighborhood" is a condition, the golf user A and the common golf chum in the neighborhood are extracted by comparing the address data recorded in the fields F7 to F9 shown in FIG. do it. Note that a method similar to the method for determining the address proximity used for calculating the familiarity may be used as a method for determining whether the addresses are close.

When the “birthplace” is a condition, the common golf where the golf user A and the prefecture of origin (prefecture) match by comparing the data of the birthplace recorded in the field F11 shown in FIG. You just have to extract friends.
In addition, when “not specified” is selected as the condition and execution of the narrowing process is selected, all the common golf friends who are not performing the narrowing process are displayed.

  Note that a plurality of conditions may be set when performing the narrowing process. In addition to selecting conditions prepared in advance, the user may be allowed to input a free keyword to extract a common golf chum in which a keyword matching the keyword is recorded in the record RCD1. .

  As described above, the golf user A requests mediation with the indirect golf chum that the golf user A wants to round together by displaying the common golf chum in descending order of closeness or narrowing down the common golf chum under the selected condition. You will be able to easily select common golf friends that are easy to use.

  In addition, the transmission of the message addressed to the common golf friend requesting the mediation may use the message transmission function of SNS, or may use e-mail. Moreover, you may make it display the said message on the display area of the my page and notification of the said golf user A in SNS, and the display area of my page and notification in the SNS of the common golf chum who requests mediation. Further, a message function in the golf information application may be used. In this case, the message function in the golf information application may be used while using the message transmission function of the SNS, or only the message function in the golf information application is used without using the message transmission function of the SNS. May be.

Second Embodiment
The service providing system 100 according to the first embodiment described above manages the SNS user's friend information in the external management server 3, and the management server 1 does not independently manage the friend information. On the other hand, the service providing system 100 of the second embodiment is the same as the service providing system 100 of the first embodiment shown in FIG. 1 except that the management server 1A is used instead of the management server 1.

  FIG. 41 shows a block diagram of the management server 1A. The management server 1A is different from the management server 1 in that the storage unit 15 includes a golf chum information table TBL12. FIG. 42 shows the data structure of the golf chum information table TBL12. A plurality of records are recorded in the golf chum information table TBL12. One record includes the identification information of the action source, the identification information of the action destination, the status, and the application date / time. The action source is the golf user who made the golf chum application, and the action destination is the SNS user who applied for the golf chum. The status indicates the state of the golf chum application, and “0” indicates that the application is in progress, and “1” indicates that the application is approved.

  Next, display processing according to the second embodiment will be described. In the first embodiment, similarly to the first embodiment described with reference to FIG. 9, the identification information UID and the SNS user about the SNS friend of the golf user A and the SNS friend of the SNS friend from the external management server 3. Get information.

The management server 1A has identification information UID and SNS user information about the golf user A, the SNS friend of the golf user A, and the SNS friend's SNS friend acquired as shown in FIG. 9 at a predetermined timing. And based on golf user information table TBL11 memorize | stored in the memory | storage part 15, golf chum information table TBL12 is created and it memorize | stores in the memory | storage part 15. FIG.
In the display process, first, as shown in FIG. 44A, the direct SNS friend and the indirect SNS friend of the golf user A are specified. FIG. 43 shows the contents of the display information generation process executed by the CPU 30 of the management server 1A.

  CPU30 extracts a direct SNS friend or an indirect SNS friend, and a golf chum directly (S140). Specifically, first, the CPU 30 extracts a record in which the identification information UID is an action source or an action destination from the golf chum information table TBL12 using the golf user A's identification information UID as a key, and directly plays golf. The identification information UID of the friend is specified. Secondly, as shown in FIG. 9, the CPU 30 acquires the identification information UID of the SNS friend or the identification information UID of the indirect SNS friend directly from the external management server 3, and the acquired direct SNS friend identification information UID or indirect SNS friend. The identification information UID and the identification information UID of the direct golf chum match are extracted, and the extracted identification information UID is set as the direct golf chum to be displayed. The reason why the direct golf chum managed by the management server 1A is filtered by the SNS chum managed by the external management server 3 is that golf friendship presupposes SNS friendship. For example, it is assumed that the friendship between the golf user A and the SNS is canceled after a lapse of time for the direct golf friend who was the golf user A and the SNS friend at a certain time. In this case, the friendship of golf is not necessarily eliminated. Therefore, the golf friends were directly filtered by SNS friends. As a result, the direct golf chum to be displayed is specified as shown in FIG. 44B. In addition, the direct golf chum of the part Fx shown to the same figure is also an indirect SNS chum. This is because an SNS user who is an indirect SNS friend and does not correspond to a golf user may become a golf friend directly with the golf user A by inviting the golf information application.

  Then, CPU30 extracts a direct SNS friend or an indirect SNS friend, and an indirect golf chum (S141). Specifically, first, the CPU 30 extracts the record whose identification information UID is the action source or the action destination from the golf chum information table TBL12 using the golf chum identification information UID as a key, The identification information UID is specified. Secondly, as shown in FIG. 9, the CPU 30 acquires the identification information UID of the SNS friend or the identification information UID of the indirect SNS friend directly from the external management server 3, and the acquired direct SNS friend identification information UID or indirect SNS friend. The identification information UID and the indirect golf chum's identification information UID are extracted, and the extracted identification information UID is set as the indirect golf chum to be displayed. As a result, the indirect golf chum to be displayed is specified as shown in FIG. 44C. In addition, the indirect golf chum of the part Fy shown to the same figure is also a direct SNS chum. This is because an indirect golf chum who is in direct friendship with a golf chum includes SNS friends directly.

  Thus, CPU30 performs S140 and S141, and the golf friend information (an example of "1st specific relationship information") read from the memory | storage part 15 and the SNS friend information ("2nd specification" acquired in the acquisition part 11). SNS user (“second user”) having a friendship relationship (an example of “specific relationship”) and the golf user A (an example of “predetermined user”) based on “an example of relationship information”) Example)) and a direct SNS friend and an indirect SNS friend who is a SNS user who has a friendship with the direct SNS user as a specific SNS user, a golf use having a friendship with the golf user A A person who is a person (an example of “first user”) and who is a specific SNS user as a direct golf friend (an example of “first specific user”) and has a direct friendship with a golf friend A Ruff user, and functions as a specifying unit for specifying a person who is a specific SNS user as indirect golf friends (an example of "second specific user").

  Next, CPU30 produces | generates the display information which displays a relationship diagram (S142), and transmits display information to the terminal device 2 (S143). The generation of display information is the same as the process of S109 described with reference to FIG. As a result, also in the second embodiment, the my page shown in FIGS. 3 and 12 can be displayed on the display 45 of the terminal device 2 as in the first embodiment. Can be easily grasped.

  In the My Page displayed as described above, when one indirect golf chum is selected from the indirect golf chum, the CPU 40 of the terminal device 2 identifies the golf user A who is the user of the terminal device 2. A common friend page request is transmitted to management server 1A with number UID and identification information UID of the golf chum of the golf chum associated with icon A1. When the CPU 30 of the management server 1A receives the identification information UID of the golf user A, the identification information UID of the indirect golf chum, and the common friend page request, the received identification information UID of the golf user A and the indirect The golf friend's identification information UID is transmitted to the external management server 3.

  When the CPU of the external management server 3 receives the identification information UID of the indirect golf chum, the CPU of the external management server 3 accesses the friend information table TBL32, and the identification information UID is recorded as the action source or the action destination. To extract records. Further, the CPU extracts the SNS user information from the SNS user information table TBL31 using the identification information UID recorded as the action source or the action destination in these records as a key. Then, CPU of the external management server 3 transmits the friend list containing the SNS friend information extracted about the said indirect golf chum and SNS user information to the management server 1A.

If CPU30 of management server 1A receives these friend lists and acquires SNS friend information and SNS user information about the indirect golf chum, CPU30 of management server 1A will refer to golf chum information table TBL12. The common golf chum which is a golf chum common to the indirect golf chum and the golf user A is extracted, and a common golf chum page is generated.
At this time, the familiarity described in the first embodiment is calculated, the process of displaying the common golf chum page according to the familiarity, the process of setting conditions to narrow down the common golf chum, and the selected common golf chum The process for requesting mediation for rounding golf with the selected indirect golf chum is the same as in the first embodiment.

<Third Embodiment>
A service providing system 100A according to the third embodiment will be described with reference to FIGS. 45 and 46. FIG. The service providing system 100A of the third embodiment is obtained by removing the external management server 3 from the service providing system 100A of the second embodiment. FIG. 45 shows a block diagram of a service providing system 100A according to the third embodiment. In the service providing system 100A, the golf user is not included in the SNS user as in the first embodiment and the second embodiment.

1 A of management servers are provided with the memory | storage part 15 which memorize | stored golf user information table TBL11, golf chum information table TBL12, user log management table TBL13, setting value management master table TBL15, and individual log file FL10. The storage unit 15 stores a program for controlling the management server 1A. When the CPU 30 of the management server 1A receives a request to display the friendship of the golf user A from the CPU 40 of the terminal device 2 of the golf user A (an example of “predetermined golf user”), the golf friend information Based on this, the direct golf chum (an example of “first specific user”) having a friendship with the golf user A is extracted, and the indirect golf chum having a friendship with the direct golf chum (“second specific use”). When the indirect golf chum is selected in the terminal device 2 and the first indirect golf chum is extracted from the first extracting unit 13 that extracts one example), a common golf chum common to the selected indirect golf chum and the golf user A is selected. The second extraction unit 14 to be extracted, and the My Page browsing response including information necessary for displaying the relationship diagram indicating the relationship between the direct golf chum and the indirect golf chum extracted by the first extraction unit 13 are described above. And a display control unit 12 to be transmitted to the terminal device 2 of Ruff user A, a. In this case, the first extraction unit 13 and the second extraction unit 14 refer to the golf user information table TBL11 and the golf chum information table TBL12 stored in the storage unit 15.
Also in this case, the management server 1A generates display information in the same manner as S109 described with reference to FIG. 10 in the first embodiment. As a result, in the third embodiment, similarly to the first embodiment, the My Page shown in FIG. 3 and FIG. 12 can be displayed on the display 45 of the terminal device 2, and the golf user has a hierarchical relationship of golf friends. Can be easily grasped.

Next, the mediation request process in this embodiment will be described with reference to the flowchart of FIG. In the My Page displayed as described above, one indirect golf chum is selected from the indirect golf chum, and when the CPU 40 of the terminal device 2 accepts this selection (S210), the CPU 40 of the terminal device 2 A common friend page request is transmitted to the management server 1 together with the identification number UID of the golf user A who is the user of the terminal device 2 and the identification information UID of the indirect golf chum associated with the icon A1 (S211). When the CPU 30 of the management server 1A receives the identification information UID of the golf user A, the identification information UID of the indirect golf chum, and the common friend page request, the CPU 30 refers to the golf chum information table TBL12, and A common golf chum who is a golf chum common to the golf user A is extracted (S140), and a common golf chum page is generated (S141).
At this time, the familiarity described in the first embodiment is calculated, the process of displaying the common golf chum page according to the familiarity, and the process of setting conditions to narrow down the common golf chum are the same as in the first embodiment. is there. Moreover, it is the same as that of 1st Embodiment about the process (S211-S216) which asks the selected common golf chum for the mediation about rounding golf with the selected indirect golf chum. After the process of step S216, the CPU 40 of the terminal device 2 transmits a message to the management server 1A together with the identification information UID of the golf user A, the identification information UID of the golf chum who requests mediation, the content of the message, and the like. A request is transmitted (S217). The CPU 30 of the management server 1A that has received the identification information UID of the golf user A, the identification information UID of the golf chum who requests mediation, the message content, and the message transmission request, requests mediation from the golf user A The message addressed to the golf chum to be transmitted is transmitted to the golf chum requesting the mediation (S140).

  Specifically, an e-mail may be transmitted from the management server 1A to the common golf chum's terminal device 2, or a message function such as a My Page of the golf information application of the common golf chum may be used. Further, a message function in the golf information application may be used. In this case, the message function in the golf information application may be used while using the message transmission function of the SNS, or only the message function in the golf information application is used without using the message transmission function of the SNS. May be. Further, the CPU 30 of the management server 1A transmits a message indicating that the transmission of the message has been completed to the terminal device 2 of the golf user who requested the mediation, and the CPU 40 of the terminal device 2 that has received the message transmits the message as shown in FIG. A transmission completion message P4 is displayed (S217). Thus, mediation about rounding golf with the selected indirect golf chum can be requested without using the SNS provided by the external management server.

<Modification>
The present invention is not limited to the above-described embodiments, and various modifications described below are possible. Of course, each modification and each embodiment may be appropriately combined.

<Modification 1>
In each of the above-described embodiments, as an example, the case of requesting mediation about rounding golf with an indirect golf friend has been described. However, the present invention is not limited to this, and the friend's friend and the golf Any service may be used as long as it requests mediation for a common existence so as to be in contact with the user A.

<Modification 2>
Moreover, in each embodiment mentioned above, after extracting a common golf chum, it was set as the structure which the said golf user A operates the terminal device 2 and selects one common golf chum, but this invention is limited to this. When the extracted common golf chum is not one, the process of selecting the common golf chum by the golf user A is omitted, and the selected indirect golf chum is selected with respect to the extracted common golf chum. It is good also as a structure which performs the process which requests the mediation about rounding golf together.

  Moreover, in each embodiment mentioned above, after extracting a common golf chum, it was set as the structure which the said golf user A operates the terminal device 2 and selects one common golf chum, but this invention is limited to this. The process of omitting the process of selecting one of the common golf friends, not the one, and the process of requesting mediation for rounding golf together with the selected indirect golf friend to all the extracted common golf friends It is good also as a structure to perform.

  Moreover, in each embodiment mentioned above, after extracting a common golf chum, it was set as the structure which the said golf user A operates the terminal device 2 and selects one common golf chum, but this invention is limited to this. If a common golf chum is extracted instead of a common golf chum, a dialog for automatically requesting mediation is performed. If a common golf chum is extracted, a dialog with a send button E3 and a cancel button E4 is provided. You may make it the structure which displays and processes the request | requirement of mediation to the extracted common golf chum. In these cases, it is preferable to use a configuration in which preset fixed sentences are transmitted.

<Modification 3> Note that, in calculating the intimacy, not only the parameters described above but also the data of the record RCD1 shown in FIG. 24, for example, the intimacy is calculated using parameters such as golf history and hometown. You may make it do. Further, data necessary for calculating the familiarity may be acquired from the external management server 3.

<Modification 4>
In each of the above-described embodiments, the case where the subsequent processing (after S211 in FIG. 35) is performed by clicking the icon of the indirect golf chum displayed on the My Page shown in FIG. 3 has been described. Is not limited to such a configuration, and a button such as “Request Mediation” is provided, and after this button is clicked and an indirect golf chum is selected, a process for extracting a common golf chum is performed. May be.

<Modification 5>
The transmission of the message addressed to the common golf chum requesting the mediation may use the message transmission function of SNS, or may use e-mail. Moreover, you may make it display the said message on the display area of the my page and notification of the said golf user A in SNS, and the display area of my page and notification in the SNS of the common golf chum who requests mediation. Further, a message function in the golf information application may be used. In this case, the message function in the golf information application may be used while using the message transmission function of the SNS, or only the message function in the golf information application is used without using the message transmission function of the SNS. May be.

<Modification 6>
Moreover, in each embodiment mentioned above, although the provision service of golf information was demonstrated as an example as a service which the management server 1 or 1A provides, this invention is not limited to this, The management server 1 or 1A is Any service may be provided. For example, the present invention can be applied to everything that establishes a specific relationship on an application based on a common theme among users. The common theme may be sports such as marathon and badminton, shogi, games, hobbies such as shogi, games, etc., or may be related to business. Further, the specific relationship is not limited to the friend relationship. For example, a relationship between a boss and a subordinate may be used, or a relationship between a wholesaler and a retailer may be used. In short, any relationship can be used as long as it is established based on a certain rule.

<Modification 7>
Each of the acquisition unit 11, display control unit 12, first extraction unit 13, second extraction unit 14, information transmission unit 16, and condition setting unit 17 described in each embodiment and each modification described above is the management server 1. Alternatively, either 1A or the terminal device 2 may be provided. In this case, when the terminal device 2 employs the configuration including the first extraction unit 13, the first request unit 21 of the terminal device 2 described in the above embodiments and modifications may be omitted. Moreover, when the terminal device 2 employs a configuration including the second extraction unit 14, the second request unit 22 of the terminal device 2 described in the above embodiments and modifications may be omitted. Moreover, when the terminal device 2 employs a configuration including the information transmission unit 16, the third request unit 23 of the terminal device 2 described in each of the above-described embodiments and modifications may be omitted. When the terminal device 2 includes a part or all of the acquisition unit 11, the display control unit 12, the first extraction unit 13, the second extraction unit 14, the information transmission unit 16, and the condition setting unit 17, the management is performed. The device 1 has a role as a device that provides software (program) that can realize these functions.

<Modification 8>
In each embodiment and each modification described above, an example in which the management server 1 or the management server 1A includes the storage unit 15 and stores each table, log file, and the like in the storage unit 15 has been described. However, the present invention is not limited to such an example, and as shown in FIGS. 47 and 48, the storage server 4 that can communicate with the management server 1 or the management server 1A via the communication network NET is provided. The storage server 4 may include the storage unit 15. 47 corresponds to FIG. 1, and FIG. 48 corresponds to FIG. When the storage server 4 is provided as described above, the acquisition unit 11 can acquire the identification information UID from the golf user information table TBL11 stored in the storage unit 15 of the storage server 4 and from the friend information table TBL12. It is comprised so that the friend information between users can be acquired.

<Others>
Note that a program for realizing the functions of the present invention may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read by a computer system and executed. Here, the “computer system” includes an OS and hardware such as peripheral devices. Further, the “computer system” may include a plurality of computer devices connected via a network including a communication line such as the Internet, WAN, LAN, and dedicated line. The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Furthermore, the “computer-readable recording medium” holds a program for a certain period of time, such as a volatile memory (RAM) inside a computer system that becomes a server or a client when the program is transmitted via a network. Including things. The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, what is called a difference file (difference program) may be sufficient. Also, a distribution server that distributes a program for realizing the function of the present invention or a part thereof, a storage medium provided in the distribution server, and a distribution server that exists outside the distribution server and distributes the program by the distribution server A storage medium stored for this purpose is also included in the scope of the present invention.

  In addition, some or all of the functions described above may be realized as an integrated circuit such as an LSI (Large Scale Integration). Each function described above may be individually made into a processor, or a part or all of them may be integrated into a processor. Further, the method of circuit integration is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. Further, in the case where an integrated circuit technology that replaces LSI appears due to progress in semiconductor technology, an integrated circuit based on the technology may be used.

  Moreover, the present invention is not limited to the above-described embodiments and modifications, and modifications within the scope of the gist of the present invention are included in the present invention.

NET: Communication network, 1, 1A ... Management server, 2 ... Terminal device, 3 ... External management server, 11 ... Acquisition unit, 12 ... Display control unit, 13 ... First extraction unit, 14 ... ... 2nd extraction part, 15 ... Storage part, 16 ... Information transmission part, 17 ... Condition setting part, 21 ... 1st request part, 22 ... 2nd request part, 23 ... 3rd request part, 24 …… Display unit, 25 …… First selection unit, 26 …… Second selection unit.

Claims (13)

An external management device that provides a second service to second users including a first user who receives the first service and manages second specific relationship information indicating a specific relationship between the second users. And a management device program comprising a computer capable of communicating with the terminal device of the first user, the program comprising:
The second identification information and the first identification information for uniquely identifying the first user, the first identification information having a correspondence relationship with the second identification information for uniquely identifying the second user An acquisition unit for acquiring
In response to a request from the terminal device of a predetermined first user, a second specific user having the specific relationship with the first specific user having the specific relationship with the predetermined first user Is extracted based on the first identification information and the second specific relationship information,
Both the second specific user selected in the terminal device of the predetermined first user and the predetermined first user in response to a request from the terminal device of the predetermined first user A second extraction unit that extracts the common first specific user having the specific relationship based on the first identification information and the second specific relationship information;
In response to a request from the terminal device of the predetermined first user, the second specific selected in the terminal device of the predetermined first user with the common first specific user as a destination An information transmitter for transmitting information about the user;
A management apparatus program characterized in that it functions as a computer program.   The information transmitting unit transmits information on the second specific user selected in the terminal device of the predetermined first user to the terminal device of the common first specific user. The management apparatus program according to claim 1. The information transmitting unit transmits information on the second specific user selected in the terminal device of the predetermined first user to the external management device, and transmits the information to the common information in the external management device. The management apparatus program according to claim 1 , wherein a request for transmission to the first specific user is transmitted to the external management apparatus. The information transmission unit is configured to select the second selected at the terminal device of the predetermined user with the common first specific user selected at the terminal device of the predetermined user as a destination. The management apparatus program according to any one of claims 1 to 3 , wherein information on a specific user is transmitted. The information transmission unit transmits information on a second specific user selected by the terminal device of the predetermined user in response to a request from the terminal device of the predetermined user. The program of the management apparatus as described in any one of Claims 1 thru | or 4. Wherein the acquisition unit acquires the first specific relationship information indicating a specific relationship between the first user from the management device,
The first extraction unit is a first user having the specific relationship with the predetermined first user based on the first specific relationship information and the second specific relationship information, and the predetermined A person who is the second user having the specific relationship with the first user is extracted as the first specific user, the first user having the specific relationship with the first specific user, and A person corresponding to the second user having the specific relationship with the first specific user is extracted as the second specific user;
The second extraction unit is configured to provide the selected second specific user and the predetermined first user based on the first specific relationship information and the second specific relationship information. A first user having a specific relationship and a second user having the specific relationship with both the selected second specific user and the predetermined first user Are extracted as the common first specific user,
The management apparatus program according to claim 1 , wherein: The program further causes the computer to function as a condition setting unit that sets a predetermined condition for the first specific user,
The acquisition unit acquires registration information of each first user,
The second extraction unit extracts the common first specific user that matches the condition set by the condition setting unit from the extracted common first specific user. The program of the management apparatus as described in any one of Claim 1 thru | or 6. Information about said selected second particular user, and wherein the relative pre-Symbol first specific user is information indicating that a request for mediation with the selected second specific user The program of the management apparatus as described in any one of Claim 1 thru | or 7 . An external management device that provides a second service to second users including a first user who receives the first service and manages second specific relationship information indicating a specific relationship between the second users. A terminal device program of a first user, which is at least communicable with a management device that provides the first service to the first user and comprises a computer. , The computer
To the management apparatus, a first request for requesting that the extracting the second specific user having the specific relationship with the first specific user having the specific relation to Jo Tokoro first user of And
A selection unit that selects one of the second specific users extracted from the second specific user in the management device according to a selection instruction of the predetermined first user;
The fact that the common first specific user having the specific relationship with both the one second specific user selected by the selection unit and the predetermined first user is extracted. A second request unit for requesting the management device;
A third request unit that makes a request to the management device to transmit information related to the selected one second specific user, with the one first specific user as a destination;
A program for a terminal device, which is made to function as: A terminal device of a first user having at least a selection unit for performing a predetermined selection, and capable of communicating with the terminal device, providing a second service to a second user including the first user and And a management device that can communicate with an external management device that manages second specific relationship information indicating a specific relationship between second users, and provides a first service to the first user. And
An acquisition unit that uniquely identifies the second specific relationship information and the first user, and acquires first identification information having a corresponding relationship with second identification information that uniquely identifies the second user;
Based on the first identification information and the second specific relationship information, the second specific user having the specific relationship with respect to the first specific user having the specific relationship with the predetermined first user. A first extraction unit for extracting,
The common first specific user who is the first specific user having the specific relationship with both the second specific user selected by the selection unit and the predetermined user, A second extraction unit for extracting based on the first identification information and the second specific relationship information;
Previous SL common first specific user as a destination, information transmission to send the information about the second specific user selected by the selection unit a request to transmit in the external management device, to the external management device And
Comprising
A service providing system characterized by that. A control method of a management device that provides a first service to a user,
It is possible to communicate with an external management device that provides second service to second users including the first user and manages second specific relationship information indicating a specific relationship between the second users, and In the control method of the management device capable of communicating with the terminal device of the first user,
Before Stories second particular relationship information, and said first user a first identification information for uniquely identifying a first identification having a corresponding relationship with the second identification information that uniquely identifies the second user Get information,
In response to a request from the terminal device of a predetermined first user, a second specific user having the specific relationship with the first specific user having the specific relationship with the predetermined first user Is extracted based on the first identification information and the second specific relationship information,
Displaying the extracted information indicating the second specific user on the display unit of the terminal device of the predetermined first user;
Both the second specific user selected in the terminal device of the predetermined first user and the predetermined first user in response to a request from the terminal device of the predetermined first user Extracting the common first specific user having the specific relationship with respect to the first identification information and the second specific relationship information;
Displaying the extracted information indicating the common first specific user on the display unit of the terminal device of the predetermined first user;
In response to a request from the terminal device of the predetermined first user, the second specific selected in the terminal device of the predetermined first user with the common first specific user as a destination Send a request to send information about the user,
A control method for a management apparatus. An external management device that provides a second service to second users including a first user who receives the first service and manages second specific relationship information indicating a specific relationship between the second users. And a management device that can communicate with the terminal device of the first user,
The second identification information and the first identification information for uniquely identifying the first user, the first identification information having a correspondence relationship with the second identification information for uniquely identifying the second user An acquisition unit for acquiring
In response to a request from the terminal device of a predetermined first user, a second specific user having the specific relationship with the first specific user having the specific relationship with the predetermined first user Is extracted based on the first identification information and the second specific relationship information,
Both the second specific user selected in the terminal device of the predetermined first user and the predetermined first user in response to a request from the terminal device of the predetermined first user A second extraction unit that extracts the common first specific user having the specific relationship based on the first identification information and the second specific relationship information;
In response to a request from the terminal device of the predetermined first user, the second specific selected in the terminal device of the predetermined first user with the common first specific user as a destination An information transmission unit that transmits a request to transmit information about the user;
A management apparatus comprising: An external management device that provides a second service to second users including a first user who receives the first service and manages second specific relationship information indicating a specific relationship between the second users. a management apparatus at least capable of communicating first user of the terminal device for providing the first service to be communicable management device the first user and,
To the management apparatus, a first request for requesting that the extracting the second specific user having the specific relationship with the first specific user having the specific relation to Jo Tokoro first user of And
A selection unit that selects one of the second specific users extracted from the second specific user in the management device according to a selection instruction of the predetermined first user;
The fact that the common first specific user having the specific relationship with both the one second specific user selected by the selection unit and the predetermined first user is extracted. A second request unit for requesting the management device;
A third request unit that makes a request to the management apparatus to transmit information related to the selected second specified user, with the selected first specified user as the destination. When,
A terminal device comprising:

Images