JP2011113546A - Information providing device, method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To much more increase the concern of a user with a service, and to keep the concern of the user as long as possible by increasing the user's chance to meet his or her desired partner. <P>SOLUTION: A database group 61 stores each user's attributes and conditions showing attributes requested to his or her partner. A condition generation part 60 relaxes the conditions showing the attributes requested by one user to his or her partner within a prescribed range. An extraction part 55 extracts a user whose attributes are matched with the relaxed conditions of one user. A Web server function 51 notifies the extraction user of one user. A conversation request collation acceptance part 57 accepts an application for contact with one user from the extraction user. When the application for contact with one user is made from the extraction user, the Web server function 51 notifies one user of the application for contact from the extraction user. This invention may be applied to a server. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to an information providing apparatus, method, and program, and more particularly, to an information providing apparatus, method, and program that provide information of the other to one of a plurality of users.

  In recent years, services for introducing marriage partners using websites have been provided.

  FIG. 1 is a diagram showing a configuration of a conventional introduction service system for introducing a marriage partner. The conventional introduction service system includes an introduction server 11, a network 12, a user terminal 13, and a user terminal 14. The introduction server 11 provides each other's user information to the user terminal 13 operated by a male user who desires marriage and the user terminal 14 operated by a female user who desires marriage via the network 12. .

  FIG. 2 is a flowchart illustrating a favorite registration process for registering a female user that a male user of the user terminal 13 likes. When the web page data for acquiring the condition required for the other party is requested from the user terminal 13, the introduction server 11 sends the web page data for acquiring the condition via the network 12 in step S11. It transmits to the user terminal 13. In step S31, the user terminal 13 receives the data of the web page transmitted from the introduction server 11, and displays the web page.

  In step S <b> 32, the user terminal 13 acquires a condition required for the other party, which is input to the displayed web page by the operation of the male user. In step S <b> 33, the user terminal 13 transmits the acquired condition to the introduction server 11 via the network 12. In step S <b> 12, the introduction server 11 receives the condition transmitted from the user terminal 13. In step S13, the introduction server 11 stores the received conditions in a database.

  In step S <b> 14, the introduction server 11 generates a usage history record indicating the usage history of the male user of the user terminal 13 in the database. In step S <b> 15, the introduction server 11 extracts a user who is a partner that matches the stored conditions. In step S <b> 16, the introduction server 11 transmits the extracted user data to the user terminal 13 via the network 12.

  In step S <b> 34, the user terminal 13 receives and displays the extracted user data transmitted from the introduction server 11. In step S <b> 35, the user terminal 13 confirms the data of the displayed counterpart user, and designates one or more counterparts according to the operation of the male user who selected the favorite counterpart. . In step S <b> 36, the user terminal 13 transmits the designated partner data and the registration request data to the favorite server 11 via the network 12, thereby registering the designated partner favorite. Apply.

  In step S <b> 17, the introduction server 11 receives from the user terminal 13 the data of the other party designated as likes and the data of the application for registration to favorites, and accepts the application for registration to favorites. . In step S <b> 18, the introduction server 11 generates a favorite record for storing data of a favorite partner who is applied for by a male user of the user terminal 13, and updates the matching database (DB). The generated favorite record indicates a favorite mode in which the other party is registered as a favorite.

  In step S19, the introduction server 11 is a record that favors storing the male user data of the user terminal 13 for the other user stored in the favorite record, and is liked by the male user of the user terminal 13. A record is generated that is shown to indicate that the matching database is present, and the matching database (DB) is updated.

  In step S20, the introduction server 11 transmits an e-mail addressed to the other party registered as a favorite, notifies the other party that it has been registered as a favorite, and the favorite registration process ends.

  FIG. 3 is a flowchart for explaining a conventional process for inquiring about a conversation request for inquiring about a conversation request from a male user of the user terminal 13 to a partner. In step S <b> 61, the user terminal 13 transmits a request for a favorite page, which is a web page for displaying data of a favorite partner, to the introduction server 11 via the network 12 in accordance with a male user's operation. In step S <b> 51, the introduction server 11 receives a favorite page request from the user terminal 13.

  In step S52, the introduction server 11 generates favorite page data. In step S <b> 53, the introduction server 11 transmits the favorite page data to the user terminal 13 via the network 12. In step S <b> 62, the user terminal 13 receives the favorite page data transmitted from the introduction server 11. In step S63, the user terminal 13 displays a favorite page.

  In step S64, the user terminal 13 confirms the data of the user who is the partner displayed on the favorite page, and one or more people according to the operation of the male user who has selected the partner who wants the conversation. By specifying the other party's partner and transmitting the designated party's data and the desired query data of the conversation to the introduction server 11, the desired query of the conversation with the specified party is made.

  In step S <b> 54, the introduction server 11 receives the designated partner data and conversation request inquiry data transmitted from the user terminal 13, and accepts the conversation request inquiry. In step S55, the introduction server 11 likes the specified partner and updates the display of the conversation request at the user location on the page. As a result, the page that is liked by the designated partner displays that the male user of the user terminal 13 wishes to have a conversation.

  In step S56, the introduction server 11 transmits an e-mail addressed to the designated partner to notify that the conversation is desired, and the process for inquiring about the conversation ends.

  In this way, a conversation is applied from a male user of the user terminal 13 to a female user of the user terminal 14.

  FIG. 4 is a flowchart for explaining a conventional process of accepting a conversation application in which a female user of the user terminal 14 accepts a conversation application from a male user of the user terminal 13. In step S <b> 71, the user terminal 14 is a web page that displays data of a partner who likes himself (in this case, a male user of the user terminal 13) via the network 12 in accordance with the operation of the female user. A favorite page request is transmitted to the introduction server 11. In step S <b> 81, the introduction server 11 receives a favorite page request from the user terminal 14.

  In step S82, the introduction server 11 likes and generates page data. In step S <b> 83, the introduction server 11 transmits the favorite page data to the user terminal 14 via the network 12. In step S72, the user terminal 14 receives the favorite page data transmitted from the introduction server 11. In step S73, the user terminal 14 likes and displays the page.

  In step S74, the user terminal 14 gives an instruction as to whether or not to accept the conversation application in response to an operation by the female user who has confirmed the data of the user who has applied for the conversation and is displayed on the page. get. Then, the user terminal 14 determines whether or not to accept the application for the conversation according to the instruction of the female user. If it is determined in step S 74 that the application for the conversation is accepted, the user terminal 14 transmits data indicating that the application for the conversation is accepted to the introduction server 11 via the network 12.

  In step S <b> 84, the introduction server 11 receives data indicating acceptance of the conversation application transmitted from the user terminal 14. In step S85, the introduction server 11 updates the favorite mode of the favorite record in the matching database (DB) to the conversation mode.

  In step S86, the introduction server 11 sets a bulletin board (electronic bulletin board) for conversation between the male user of the user terminal 13 and the female user of the user terminal 14, and enters the bulletin board on the pages of both users. A bulletin board button is provided.

  In step S87, the introduction server 11 notifies the male user of the user terminal 13 and the female user of the user terminal 14 by e-mail that a bulletin board has been provided, and the process of accepting the conversation application is performed. finish.

  On the other hand, if it is determined in step S74 that the conversation application is not accepted, the bulletin board is not provided, and the conversation application acceptance process ends.

  In this way, information on the male user of the user terminal 13 and the female user of the user terminal 14 is provided to each other.

  Conventionally, when a terminal and a management server are connected on a communication network, and there is a request for matching by both male and female members through the terminal, the management server prepares in advance by referring to a database recording personal data of male and female members In accordance with the compatibility program that has been established, both male and female members are matched. As a result of this data matching, if the desired conditions for both male and female members meet a certain standard, both the male and female anonymous profiles are sent via email. Some of them are trying to introduce them. (For example, refer to Patent Document 1).

Japanese Patent Laid-Open No. 2002-15052

  However, if information is provided in response to a simple match between the condition and the attribute, the opportunity to meet the person you actually want to meet may be lost. In addition, information on the other party who is unlikely to be interested was provided, and the interest in the service was diminished.

  The present invention has been made in view of such a situation, and it is possible to increase an opportunity to meet a user's desired partner, increase the user's interest in the service, and maintain the interest for a longer time. It is what you want to do.

  An information providing apparatus according to an aspect of the present invention is an information providing apparatus that provides information to one of a plurality of users, each of which is a man or a woman, each of the user's own attributes and attributes required of the other party Storage means for storing the condition indicating the condition, relaxation means for relaxing the condition indicating the attribute that one user wants the other party within a predetermined range, and a user with an attribute that matches the relaxed condition of the one user Extraction means for extracting the extraction user, notification means for notifying the extraction user who is the extracted user of the one user, and first reception means for receiving an application for contact with the one user from the extraction user. When the contact with the one user is applied from the extraction user, the notification means notifies the application of the contact from the extraction user to the one user.

  The notification means can notify the one user that the attribute of the extracted user matches the relaxed condition of the one user.

  There may be further provided a second accepting means for accepting acceptance of the contact application from the extraction user from the one user.

  It is possible to further provide providing means for providing an electronic bulletin board for contacting the one user who has accepted the contact application with the extracted user who has applied for contact.

  An information provision method according to one aspect of the present invention includes a storage unit, a relaxation unit, an extraction unit, a notification unit, and a reception unit, and provides the other information to one of a plurality of users who are men or women, respectively. In the information providing method, the storage unit stores each attribute of the user and a condition indicating an attribute required for the other party, and the relaxation unit indicates the attribute desired by the one user for the other party. The condition is relaxed within a predetermined range, the extraction means extracts a user having an attribute that matches the relaxed condition of the one user, and the notification means sends the extracted user who is the extracted user to the extraction user. One user is notified, and the accepting unit accepts an application for contact with the one user from the extracted user, and the notifying unit receives the previous application from the extracted user. If contact with the one user has subscribed, comprising the step of notifying the application of the contact from the extraction user to the one user.

  A program according to one aspect of the present invention stores, on a computer that provides information of the other to one of a plurality of users, each of which is a male or a female, each of the user's own attributes and conditions indicating attributes desired for the other party. Then, the condition indicating the attribute requested by the one user is relaxed within a predetermined range, the user having the attribute that matches the relaxed condition of the one user is extracted, and the extracted user who is the extracted user When the contact with the one user is applied from the extraction user and the contact with the one user is applied from the extraction user, the application for the contact from the extraction user is received. The process including the step of notifying the one user is executed.

  In one aspect of the present invention, each user's own attribute and a condition indicating an attribute desired for the other party are stored, and a condition indicating the attribute desired by one user for the other party is relaxed within a predetermined range, Users with attributes that match the user's relaxed conditions are extracted, one user is notified to the extracted user who is the extracted user, an application for contact with one user is accepted from the extracted user, and When contact with one user is applied, an application for contact from the extraction user is notified to the one user.

  As described above, according to one aspect of the present invention, a user can meet a desired partner. In addition, according to one aspect of the present invention, even if the mutual conditions are not satisfied, an opportunity to meet a user's desired partner is increased, the user's interest in the service is further increased, and the interest is prolonged. Can be maintained.

  Although it is natural to perform matching processing between users whose conditions match in both directions, by adopting the present invention, in addition to being able to perform matching processing for users whose conditions do not match only in one direction, conditions in both directions Matching processing can also be performed for users who do not match. In other words, by extracting the opponent by relaxing the conditions, an unstable state that you would like to generate is generated, and then the offer input from one side is accepted, so it is somewhat stable from the unstable state By transitioning to a state, and further accepting an input of consent from the other, the state is developed from a slightly stable state to a stable state.

It is a figure which shows the structure of the conventional introduction service system. It is a flowchart explaining the process of the conventional favorite registration. It is a flowchart explaining the process of the inquiry of the hope of the conventional conversation. It is a flowchart explaining the process of consent of the application of the conventional conversation. It is a block diagram which shows the structure of the introduction system of one embodiment of this invention. 3 is a block diagram illustrating a hardware configuration example of an introduction server 31. FIG. It is a figure explaining the data stored in basic information DB71, basic information DB72, and detailed information DB73. It is a figure explaining the data stored in condition DB74, use history DB75, and matching DB76. It is a flowchart explaining the process of registration. It is a figure explaining a favorite page and a favorite page. It is a flowchart explaining the process of registration to a favorite. It is a figure which shows the example of a web page. It is a figure which shows the example of a web page. It is a flowchart explaining the process of generating a favorite record. It is a flowchart explaining the process of the inquiry of the wish of conversation. It is a figure which shows the example of a web page. It is a flowchart explaining the process of consent of the application for conversation. It is a figure which shows the example of a web page. It is a figure which shows the example of a web page. It is a figure explaining a favorite page and a favorite page. It is a flowchart explaining the process of registration to a favorite. It is a flowchart explaining the process which likes and produces | generates a record. It is a flowchart explaining the process of the inquiry of the wish of conversation. It is a flowchart explaining the process of consent of the application for conversation. It is a figure explaining an introduction page. It is a flowchart explaining the process of registration to a favorite. It is a flowchart explaining the production | generation process of an introduction record. It is a flowchart explaining the process of provision of an introduction page. It is a figure which shows the example of a web page. It is a flowchart explaining the process of consent of the application for conversation. It is a figure which shows the example of a web page.

  Embodiments of the present invention will be described below. Correspondences between the configuration requirements of the present invention and the embodiments described in the detailed description of the invention are exemplified as follows. This description is to confirm that the embodiments supporting the present invention are described in the detailed description of the invention. Accordingly, although there are embodiments that are described in the detailed description of the invention but are not described here as embodiments corresponding to the constituent elements of the present invention, It does not mean that the embodiment does not correspond to the configuration requirements. Conversely, even if an embodiment is described here as corresponding to a configuration requirement, that means that the embodiment does not correspond to a configuration requirement other than the configuration requirement. Not something to do.

  An information providing apparatus according to one aspect of the present invention is an information providing apparatus (for example, the introduction server 31 in FIG. 5) that provides the other information to one of a plurality of users who are men or women, and each of the users Storage means (for example, database group 61 in FIG. 5) for storing the self attribute and the condition required for the other party, and the condition indicating the attribute requested by one user to the other party is relaxed within a predetermined range. A mitigating means (for example, the condition generating unit 60 in FIG. 5), an extracting means (for example, the extracting unit 55 in FIG. 5) for extracting a user having an attribute that matches the relaxed condition of the one user, Notification means (for example, the Web server function 51 in FIG. 5) for notifying the extracted user, which is an extracted user, and a first reception for receiving an application for contact with the one user from the extracted user (E.g., a conversation request inquiry receiving unit 57 in FIG. 5), and the notification means applies a contact request from the extracted user when contact is made with the one user from the extracted user. Notify the one user.

  A second accepting unit (for example, the conversation request acceptance accepting unit 58 in FIG. 5) that accepts the acceptance of the contact application from the extracted user from the one user can be further provided.

  The providing means (for example, the electronic bulletin board function 59 in FIG. 3) for providing an electronic bulletin board for contacting the one user who accepted the contact application and the extracted user who applied for the contact may be further provided.

  An information providing method according to one aspect of the present invention includes a storage unit (for example, the database group 61 in FIG. 5), a relaxation unit (for example, the condition generation unit 60 in FIG. 5), and an extraction unit (for example, the extraction unit 55 in FIG. 5). , A notification means (for example, the Web server function 51 of FIG. 5) and a reception means (for example, the conversation request inquiry reception unit 57 of FIG. 5). In the information providing method of the information providing apparatus to be provided, each of the user's own attribute and a condition indicating an attribute required for the other party are stored in the storage means (for example, step S104 in FIG. 9 and FIG. 26). In step S193 of FIG. 27), the mitigating means relaxes the condition indicating the attribute requested by the other user within a predetermined range (for example, the procedure of step S502 in FIG. 27). The user having the attribute that matches the relaxed condition of the one user is extracted by the output means (for example, the procedure of step S504 in FIG. 27), and the extracted user that is the extracted user by the notification means is One user is notified (for example, the procedure of step S513 in FIG. 28), and the application unit accepts an application for contact with the one user from the extracted user (for example, the procedure of step S514 in FIG. 28). When contact with the one user is applied from the extraction user by the notification means, a notification of the contact application from the extraction user is notified to the one user (for example, the procedure of step S523 in FIG. 30) including.

  A program according to one aspect of the present invention stores, on a computer that provides information of the other to one of a plurality of users, each of which is a male or a female, each of the user's own attributes and conditions indicating attributes desired for the other party. (For example, the procedure of step S104 of FIG. 9 and step S193 of FIG. 26), the condition indicating the attribute requested by one user is relaxed within a predetermined range (for example, the procedure of step S502 of FIG. 27), A user having an attribute that matches the relaxed condition of the one user is extracted (for example, the procedure of step S504 in FIG. 27), and the extracted user that is the extracted user is notified of the one user (for example, Step S513 in FIG. 28), accepting an application for contact with the one user from the extracted user (for example, step in FIG. 28) Step 514), when contact with the one user is applied from the extraction user, the application for contact from the extraction user is notified to the one user (for example, step S523 in FIG. 30) The process including is executed.

  FIG. 5 is a block diagram showing a configuration of an introduction system according to an embodiment of the present invention. The referral system provides information on the other side to one of a plurality of users who are respectively men or women who wish to marry. Specifically, the introduction system provides an introduction service for introducing a partner to a user who wishes to marry.

  The introduction system includes an introduction server 31, the Internet 32, user terminals 33-1 to 33-3 operated by a male user who wants to marry, and user terminals 34-1 to 33-3 operated by a female user who wants to marry. 34-3. The introduction server 31 is an example of an information providing device, and includes a dedicated server, a personal computer, a virtual server, or the like. The introduction server 31 may be a system composed of a combination of a dedicated server, a personal computer, or a virtual server.

  The introduction server 31 stores the user's own attributes and conditions indicating the attributes required of the other party. The introduction server 31 extracts a user having an attribute that matches the condition indicating the attribute requested by the target user, who is the focused user, and pays attention to the condition indicating the attribute requested by the extracted user, the extracted user. It is determined whether or not the user attributes match. The introduction server 31 notifies the extracted user of the attribute of the noticed user when it is determined that the attribute of the noticed user matches the condition indicating the attribute requested by the extracted user.

  In addition, the introduction server 31 relaxes the condition indicating the attribute that the focused user, who is the focused user, asks the other party within a predetermined range, and extracts users with attributes that match the relaxed condition of the focused user, The attribute of the user of interest is notified to the extracted user who is the extracted user. Then, the introduction server 31 receives an application for contact with the target user from the extraction user, and notifies the target user of an application for contact from the extraction user when the extraction user applies for contact with the target user.

  The Internet 32 is an example of a network, and includes a wired or wireless general-purpose line or dedicated line, or a plurality of wired or wireless networks such as a LAN (Local Area Network) or a WAN (Wide Area Network).

  The user terminals 33-1 to 33-3 are information terminal devices such as a personal computer and a mobile phone, and are operated by a male user who desires marriage. Each of the user terminals 33-1 to 33-3 requests the introduction server 31 from the male user attribute and the female user partner via the Internet 32 according to the operation of the male user. Various data such as conditions indicating attributes are transmitted. In addition, each of the user terminals 33-1 to 33-3 receives and displays information on the partner who is the female user transmitted from the introduction server 31.

  The user terminals 34-1 to 34-3 are information terminal devices such as a personal computer and a mobile phone, and each is operated by a female user who wishes to marry. Each of the user terminals 34-1 to 34-3 requests the introduction server 31 from the female user attribute and the male user partner via the Internet 32 according to the operation of the female user. Various data such as conditions indicating attributes are transmitted. In addition, each of the user terminals 34-1 to 34-3 receives and displays information on a partner who is a male user transmitted from the introduction server 31.

  Hereinafter, when it is not necessary to individually distinguish the user terminals 33-1 to 33-3, they are simply referred to as user terminals 33. Hereinafter, when it is not necessary to individually distinguish the user terminals 34-1 to 34-3, they are simply referred to as user terminals 34.

  When the introduction server 31 executes the program, the Web server function 51, page data generation unit 52, member registration unit 53, mail function 54, extraction unit 55, determination unit 56, conversation request inquiry reception unit 57, conversation request acceptance reception The unit 58, the electronic bulletin board function 59, the condition generation unit 60, and the database group 61 are realized.

  The Web server function 51 is realized by executing a so-called Web server program such as Apache HTTP Server, for example, and various objects such as text or images are stored on the basis of a procedure defined in HTTP (Hypertext Transfer Protocol). Web page data such as HTML (Hypertext Markup Language) or XML (Extensible Markup Language) is included.

  The page data generation unit 52 generates web page data provided by the web server function 51. The member registration unit 53 acquires the attributes of a male or female user who wishes to marry and records it in the database group 61 to register as a member.

  The mail function 54 is realized by executing a so-called mail program, and transmits electronic mail for various notifications to the user.

  The extraction unit 55 extracts a partner having an attribute that matches a condition indicating an attribute desired for the partner. In addition, the extraction unit 55 extracts a partner having an attribute that matches the relaxed condition, which is a condition indicating the attribute to be obtained from the partner. When a user having an attribute that matches the condition indicating the attribute requested by the target user, who is the focused user, is extracted, the determination unit 56 indicates a condition indicating the attribute requested by the extracted user, who is the extracted user, It is determined whether or not the attribute of the user of interest matches.

  The conversation request inquiry acceptance unit 57 accepts an inquiry for a conversation application with a desired partner from the user. The conversation request acceptance accepting unit 58 accepts the application acceptance from the other party in response to the inquiry about the application for the conversation.

  The condition generation unit 60 generates a relaxed condition from the condition indicating the attribute required for the other party. That is, the condition generation unit 60 relaxes the condition indicating the attribute that the focused user, who is the focused user, asks the other party within a predetermined range.

  The database group 61 includes a plurality of databases and records various data. The database group 61 includes a basic information database (DB) 71, a basic information database (DB) 72, a detailed information database (DB) 73, a condition database (DB) 74, a usage history database (DB) 75, and a matching database (DB). 76.

  The basic information DB 71 stores basic information of each user. The basic information DB 72 stores basic information of each user. The detailed information DB 73 stores detailed information of each user. The condition DB 74 stores conditions indicating attributes required for the other party for each user. The usage history DB 75 stores the usage history of the introduction system for each user. The matching DB 76 stores, for each user, data indicating the status of the other party, such as whether to provide information about a favorite party or whether to talk with the other party.

  Details of data stored in the basic information DB 71, basic information DB 72, detailed information DB 73, condition DB 74, usage history DB 75, and matching DB 76 will be described later with reference to FIGS.

  FIG. 6 is a block diagram illustrating a hardware configuration example of the introduction server 31. In the introduction server 81, a CPU (Central Processing Unit) 81, a ROM (Read Only Memory) 82, and a RAM (Random Access Memory) 83 are connected to each other by a bus 84.

  An input / output interface 85 is further connected to the bus 84. The input / output interface 85 includes an output unit 86 including a speaker, an input unit 87 including a keyboard, a mouse, and a microphone, a display unit 88 including a display, a communication unit 89 including a network interface, a magnetic disk, an optical disk, an optical A drive 90 for driving a removable medium such as a magnetic disk or a semiconductor memory, and a storage unit 91 such as a hard disk or a non-volatile memory are connected.

  The storage unit 91 includes a database group 61 including a basic information DB 71, a basic information DB 72, a detailed information DB 73, a condition DB 74, a usage history DB 75, and a matching DB 76.

  The basic information DB 71, the basic information DB 72, the detailed information DB 73, the condition DB 74, the usage history DB 75, and the matching DB 76 are each constructed directly on the file system provided by the operating system. It may be constructed using a database management system. Further, any one of the basic information DB 71, the basic information DB 72, the detailed information DB 73, the condition DB 74, the usage history DB 75, and the matching DB 76 may be combined to form one database.

  In the introduction server 81 (computer) configured as described above, the CPU 81 loads, for example, a program stored in the storage unit 91 to the RAM 83 via the input / output interface 85 and the bus 84 and executes the program. Thus, a series of processes described later is performed.

  The program executed by the introduction server 81 (CPU 81), which is an example of a computer, is, for example, a magnetic disk (including a flexible disk), an optical disk (CD-ROM (Compact Disc-Read Only Memory), DVD) mounted in the drive 90. (Digital Versatile Disc, etc.), a magneto-optical disk, or a removable medium that is a package medium composed of a semiconductor memory, or a wired or wireless transmission medium such as a local area network, the Internet 32, or digital satellite broadcasting Provided through.

  The program can be installed in the computer by mounting the removable medium in the drive 90 and storing it in the storage unit 91 via the input / output interface 85. Further, the program can be installed in a computer by being received by the communication unit 89 via a wired or wireless transmission medium and stored in the storage unit 91. In addition, the program can be installed in the computer in advance by storing it in the ROM 82 or the storage unit 91 in advance.

  Next, details of data stored in the basic information DB 71, the basic information DB 72, the detailed information DB 73, the condition DB 74, the usage history DB 75, and the matching DB 76 will be described with reference to FIGS.

  In the basic information DB 71, as basic information of each user, the user ID for identifying the user is associated with the date of birth, name, address, telephone number, mail address (e-mail address), Membership date, date of joining the referral service, withdrawal date, date of withdrawal from the referral service, payment method for the referral service, such as credit card and transfer, and identity verification Information such as information is stored.

  In the basic information DB 72, as basic information of each user, an image file in which each user's own image data is stored in association with the user ID, the handle name of each user, and further, gender as the attribute of each user. , Information such as the area where the person lives, height, weight, annual income, family structure, marriage history, presence / absence of children (presence / absence of children), number of children (number of children), and the like are stored.

  In the detailed information DB 73, as detailed information of each user, it is associated with a user ID and a handle name, a comment from the user, a user's favorite type, a user's hobbies, whether or not household cooking is possible (the user can do household and cooking). And the like, and information such as the user's cooking skills are stored.

  In the condition DB 74, as a condition indicating an attribute requested by each user, the user ID is associated with the desired area where the other party lives, the desired age that is the range of the other party's age, and the height of the other party. Desired height, opponent's weight desired weight, opponent's annual income desired income, family composition condition indicating partner's family composition, marriage history condition of partner's marriage history, presence / absence of child indicating presence / absence of partner's child A condition and a condition such as a child number condition indicating the number of children of the other party are stored. For example, as shown in FIG. 8, the condition DB 74 is associated with the user ID in the condition DB 74, a desired area that is Kanto, a desired age that is 31 to 35 years old, a desired height that is 175 cm or more, and 5 million yen or more. The desired annual salary, and the marriage history condition, the child presence / absence condition, and the child number condition without conditions are stored.

  The usage history DB 75 stores a usage history record for each partner in association with the user ID as a history of usage of the introduction system for each user. In each usage history record, the partner user ID that is the user ID for identifying the partner, the date that indicates the date when the usage history record was generated or the status was updated, and the reply that indicates whether there was a reply from the partner Status indicating presence / absence and status of the other party is arranged. In the example of the two usage history records shown in FIG. 8, the date, the presence / absence of a reply indicating that a reply has been received, and the status indicating that the partner has declined are associated with the counterpart user ID of F0000001. In correspondence with the counterpart user ID of F0000010, the date, the presence / absence of a reply indicating waiting for a reply, and the status are stored.

  In the matching DB 76, as a data indicating the state of each user and the partner that the user likes, a favorite record is stored for each favorite partner in association with the user ID. In each favorite record, a partner user ID, which is a user ID for identifying a favorite partner, and a status indicating the state of the partner are arranged. In the example of the three favorite records shown in FIG. 8, the status of the favorite mode indicating that the other user ID is F0000001, the status of the favorite mode indicating that he likes the other party, and the other user ID of F0000022, The status of the favorite mode indicating that the partner is liked and the status of the open mode (conversation mode) indicating that the user is talking to the partner are stored in correspondence with the partner user ID of F0000333.

  In addition, the matching DB 76 stores a favorite record for each favorite partner in association with the user ID as data indicating the state of each user and the partner the user likes. In each favorite record, a partner user ID, which is a user ID for identifying a partner that the user likes, and a status indicating the state of the partner are arranged.

  Hereinafter, a case where a male user likes a female user will be described, but the same applies to a case where the relationship between men and women is reversed.

  Next, the registration process will be described with reference to the flowchart of FIG. As a response to the request from the user terminal 33, in step S101, the Web server function 51 of the introduction server 31 is generated by the page data generation unit 52 via the Internet 32 in the communication unit 89 that is a network interface. The registered data of the male user of the user terminal 33 and the web page data for acquiring the user image are transmitted to the user terminal 33. In step S201, the user terminal 33 receives the web page data transmitted from the introduction server 31, and receives basic information such as the user's date of birth and name, basic information such as the area where the user lives and height, and A registration item including detailed information such as a handle name and a web page for acquiring a user image are displayed.

  When a registration item including basic information, basic information, and detailed information is input to the displayed web page in response to the operation of the male user of the user terminal 33, the user terminal 33 Get the registration information entered on the page. When the file name of the user's image or the like is designated according to the operation of the male user of the user terminal 33, the user terminal 33 acquires the user's image (data) in step S203.

  When transmission is instructed by a male user of the user terminal 33 by clicking a transmission button on the web page or the like, in step S204, the user terminal 33 acquires the registered items and the acquired items via the Internet 32. The user image is transmitted to the introduction server 31.

  In step S102, the web server function 51 of the introduction server 31 causes the communication unit 89, which is a network interface, to receive registration items and user images transmitted from the user terminal 33. In step S103, the member registration unit 53 determines whether or not all necessary information is included in the received registration items, that is, whether or not the registration items are complete. If it is determined in step S103 that the registered items are not complete, the procedure returns to step S101 and the above-described processing is repeated.

  If it is determined in step S103 that the registered items are complete, the procedure proceeds to step S104, and the member registration unit 53 causes the database group 61 to store the registered items and user images. Thus, the basic information DB 71 of the database group 61 records the basic information of the user of the user terminal 33 in association with the user ID that identifies the user of the user terminal 33, and the basic information DB 72 stores the user terminal 33. The basic information of the user of the user terminal 33 is recorded in association with the user ID specifying the user of the user, and the detailed information DB 73 is associated with the user ID and handle name specifying the user of the user terminal 33, Detailed information of the user of the user terminal 33 is recorded.

  In step S105, the page data generation unit 52 of the introduction server 31 generates data of a web page requesting identification confirmation, and the web server function 51 sends the communication unit 89, which is a network interface, to the communication unit 89 via the Internet 32. Then, the web page data for requesting identification is sent to the user terminal 33. In step S <b> 205, the user terminal 33 receives the web page data transmitted from the introduction server 31 and displays a web page for requesting identification.

  In step S206, the user of the user terminal 33 prints a web page as a confirmation document or downloads it from the web page, and describes necessary items on the confirmation document obtained by printing. The signature or seal is sent, and the confirmation document is sent to the service company that manages the introduction server 31. The user of the user terminal 33 writes necessary information on the confirmation document sent by mail or the like from the service company, signs or seals it, and sends the confirmation document to the service company that manages the introduction server 31. You may make it send.

  In step S <b> 106, the service company that manages the introduction server 31 receives the confirmation document sent from the user of the user terminal 33. In step S 107, the member registration unit 53 sets a use start flag in the basic information DB 71 for the user of the user terminal 33 in accordance with the operation of the operator of the service company who has confirmed the items described in the confirmation document. The introduction service is started by setting the use start flag. In step S <b> 108, the member registration unit 53 saves the confirmation items, which are items confirmed by the confirmation document, by causing the basic information DB 71 to record the identity confirmation information indicating that the identity has been confirmed. In step S109, the mail function 54 transmits an e-mail for notifying the start of use to the user of the user terminal 33 that is the registered user, and the registration process ends.

  In this way, the user is registered, the registered user attribute is recorded in the basic information DB 72, and the provision of the introduction service is started. The registration process for the female user of the user terminal 34 is the same.

  Next, registration to favorites will be described.

  In this introduction system, when the male user X of the user terminal 33 registers the female user A and the user B as favorites, for example, as shown in FIG. 10, the introduction server 31 provides the user X to the user terminal 33 of the user X. Of the web pages to be displayed, information on female users A and B is displayed on a favorite page that is a web page that displays data of a favorite partner.

  In this case, when the attribute of the male user X does not match the condition that the female user A wants to request, the web page provided from the introduction server 31 to the user terminal 34 of the user A, The information of the user X is not displayed on the favorite page, which is a web page that displays data of a partner who likes him / her. On the other hand, when the male user Y registers the female user A as a favorite, when the attribute of the male user Y matches the condition indicating the attribute requested by the female user A, Information about the user Y is displayed on a favorite page provided from the introduction server 31 to the user terminal 34 of the user A.

  FIG. 11 is a flowchart for explaining the process of registration to favorites. As a response to the request from the user terminal 33, in step S111, the Web server function 51 of the introduction server 31 is generated by the page data generation unit 52 via the Internet 32 in the communication unit 89 that is a network interface. The web page data for acquiring the conditions is transmitted to the user terminal 33. Here, the condition indicates an attribute that the user seeks from the other party.

  In step S <b> 211, the user terminal 33 receives the web page data transmitted from the introduction server 31 and displays a web page for acquiring conditions.

  When a condition is input to the displayed web page according to the operation of the male user of the user terminal 33, in step S212, the user terminal 33 acquires the condition input to the web page. When transmission is instructed from a male user of the user terminal 33 by clicking a transmission button on the web page, the user terminal 33 introduces the acquired condition via the Internet 32 in step S213. Send to server 31.

  In step S112, the web server function 51 of the introduction server 31 causes the communication unit 89, which is a network interface, to receive the conditions transmitted from the user terminal 33. In step S <b> 113, the web server function 51 stores the received condition in the condition DB 74 in association with the user ID that identifies the male user of the user terminal 33.

  In step S114, the usage history DB 75 generates a usage history record associated with the user ID. In step S115, the extraction unit 55 extracts a user who has an attribute that matches the received condition. That is, in step S115, the extraction unit 55 extracts a user having an attribute that matches a condition indicating an attribute required for the other party of the focused user (in this case, the male user of the user terminal 33) who is the focused user.

  More specifically, in step S115, the extraction unit 55 uses the condition indicating the attribute requested from the other party as a key from the basic information DB 72, and selects users having attributes that match all of the attributes indicated by the condition. Find the user ID to identify.

  In step S <b> 116, the web server function 51 transmits the extracted user data to the user terminal 33. More specifically, in step S116, the page data generation unit 52, from the basic information DB 72, the image file, the handle name, the region, and the like associated with the user ID that identifies the extracted partner user. And the comment associated with the extracted user ID and handle name for identifying the user as the other party is read out from the detailed information DB 73. Then, the page data generation unit 52 uses the read image, handle name, comment, region, and other attributes to generate web page data for displaying the extracted user attributes, images, and the like. Then, the web server function 51 sends the web page data for displaying the extracted attributes and images of the other user via the Internet 32 to the user terminal 33 via the Internet 32. Send it.

  In step S214, the user terminal 33 receives and displays the data of the extracted partner user transmitted from the introduction server 31. That is, in step S214, the user terminal 33 receives the web page data transmitted from the introduction server 31 for displaying the extracted user attributes and images, and the extracted partner. A web page that displays user attributes and images is displayed.

  FIG. 12 and FIG. 13 are diagrams showing examples of web pages that display the extracted attributes and images of the other user. As shown in FIG. 12, from the web page for selecting an introduction method, a button labeled “To introduction list” linked to a web page for “introducing the person you want” is clicked. Then, the web page shown in FIG. 13 for displaying the extracted user attributes and images is displayed. This web page displays, for example, the age of the partner, the area where he / she lives, a comment, and an image of the partner for each extracted partner, as well as a button (in FIG. 13) for indicating a favorite partner. A button labeled “Register to Favorites”).

  The male user of the user terminal 33 looks at the displayed web page, and if there is a favorite partner (female user) among the extracted partners, he / she operates the user terminal 33 and clicks a button. Therefore, in step S215, the user terminal 33 designates one or more partners instructed by the male user from the extracted partners. In step S216, the user terminal 33 transmits the application data for registration to favorites to the introduction server 31 along with the data of the designated partner via the Internet 32, thereby registering to the favorite of the designated partner. Apply.

  In step S117, the Web server function 51 of the introduction server 31 receives the data of the designated partner and the application for registration to the favorite transmitted from the user terminal 33, and applies for the registration to the favorite. Accept. In step S118, the web server function 51 supplies the specified partner data to the matching DB 76, and the matching DB 76 is associated with the user ID that identifies the male user of the user terminal 33, and the male ID of the user terminal 33 is stored. The favorite record including the partner user ID for identifying the partner that the user likes is generated, the matching DB 76 is updated, and the process of registering the favorite is completed. In this case, one favorite record is generated for each favorite partner, and one partner user ID is stored in one favorite record.

  In this way, a partner user ID for identifying a favorite partner is stored in the favorite record.

  Next, a process for generating a favorite record for generating a favorite record for a partner whom a male user of the user terminal 33 likes will be described with reference to a flowchart of FIG. In step S <b> 121, the determination unit 56 reads from the condition DB 74 the conditions of all favorite opponents that the male user of the user terminal 33 likes as indicated by the favorite record. That is, the determination unit 56 reads the partner user ID from the favorite record associated with the user ID that identifies the male user of the user terminal 33 among the favorite records in the matching DB 76. Then, the determination unit 56 reads the condition associated with the same user ID as the read partner user ID from the condition DB 74.

  In step S <b> 122, the determination unit 56 reads out the attributes of the male user of the user terminal 33, i.e., the favorite user from the basic information DB 72. More specifically, the determination unit 56 reads out the attribute of the male user of the user terminal 33 attached to the user ID that identifies the male user of the user terminal 33 from the basic information DB 72.

  In step S123, the determination unit 56 selects one partner from the partners whose conditions are read in the procedure in step S121. In step S124, the determination unit 56 determines whether or not the attribute of the male user of the user terminal 33, that is, the favorite user satisfies the conditions of the selected favorite partner. In other words, in step S <b> 124, the determination unit 56 determines whether the extracted user (in this case, for example, the female user of the user terminal 34) who is the extracted user is interested in the condition indicating the attribute to be requested (the user in this case, the user). It is determined whether or not the attributes of the male user (terminal 33) match.

  If it is determined in step S124 that the user's favorite attribute satisfies the condition of the selected favorite partner, the procedure proceeds to step S125, and the determination unit 56 likes the partner in the matching DB 76 and generates a record. The matching DB 76 is updated. That is, the matching DB 76 is a favorite record associated with the user ID of the selected favorite partner, and generates a favorite record that stores a user ID that identifies a male user as the partner user ID. To do.

  In step S126, the mail function 54 notifies the user that the record has been liked and has been generated by an e-mail addressed to the selected partner, and the procedure proceeds to step S127. In this case, the other party's e-mail address is read from the basic information DB 71 using the other party's user ID as a key.

  On the other hand, if it is determined in step S124 that the user's favorite attribute does not satisfy the condition of the selected favorite partner, the procedure in steps S125 and S126 is skipped and the record is not generated. The procedure proceeds to step S127.

  In step S127, the determination unit 56 determines whether or not the processing of all the partners whose conditions have been read has been completed. If it is determined that the processing of all the partners has been completed, the determination unit 56 likes the generation of the record. The process ends. If it is determined in step S127 that the processing of all the opponents has not been completed, the procedure returns to step S123, and the above-described processing is performed until the next partner is selected and the processing of all the opponents is completed. Repeated.

  In this way, if your attributes satisfy the conditions of your favorite opponent, the other party will like you and a record will be generated. If your attributes do not satisfy your favorite opponent's conditions, you will like your opponent. Records are not generated. By doing so, only information about those who are likely to be impressed with them will be provided with their information.

  Next, the user's user terminal 34 and the introduction server 31 of the user who has liked and generated the favorite record described with reference to the flowchart of FIG. Explain the processing of a query. When the female user likes the web page that displays data of the person he / she likes (in this case, the male user of the user terminal 33) to the user terminal 34 and instructs the display of the page, in step S331, the user terminal 34 sends a request for a favorite page to the introduction server 31 via the Internet 32. In step S <b> 131, the web server function 51 of the introduction server 31 receives the request transmitted from the user terminal 34.

  In step S132, the page data generation unit 52 likes the matching user ID associated with the user ID that identifies the female user of the user terminal 34 from the matching DB 76 and stores the partner user ID stored in the record (male of the user terminal 33). (Including a specific user ID that identifies the user). Then, the page data generation unit 52 reads the attributes such as the image file, the handle name, and the region associated with the same user ID as the counterpart user ID from the basic information DB 72, and further, from the detailed information DB 73, A comment or the like associated with the same user ID and handle name as the counterpart user ID is read. The page data generation unit 52 uses the read image, handle name, comment, region, and other attributes, etc. to generate data of the page that is liked to display the data of the other party that likes it.

  In step S133, the Web server function 51 causes the communication unit 89, which is a network interface, to transmit the favorite page data generated by the page data generation unit 52 to the user terminal 34 via the Internet 32. That is, in step S133, the Web server function 51 determines the condition indicating the attribute to be requested of the other party of the extraction user (in this case, the female user of the user terminal 34). When it is determined that the attributes match, the extracted user is notified of the attribute of the user of interest.

  In step S <b> 332, the user terminal 34 receives favorite page data transmitted from the introduction server 31. In step S333, the user terminal 34 likes and displays the page. On the favorite page, attributes and images of male users who like female users of the user terminal 34 (in this case, including male users of the user terminal 33) are displayed.

  FIG. 16 is a diagram illustrating an example of a favorite page. As shown in FIG. 16, on the favorite page, attributes and images of a male user who likes the female user of the user terminal 34 are displayed. That is, the favorite page displays, for each partner, for example, the partner's age, the area where he / she lives, points that the female user of the user terminal 34 likes, and an image of the partner, as well as a request for conversation. Button (button labeled “Speak let's talk application” in FIG. 16) is arranged.

  A female user of the user terminal 34 likes a page, and if there is a partner who wants to talk among those who like himself, the user terminal 34 is operated, and a button for inquiring about the wish of the conversation is displayed. Since the user who wants to talk is indicated by clicking or the like, in step S334, the user terminal 34 is instructed by the female user of the user terminal 34 from one or more of those who have liked himself / herself. Inquire about the person you want to talk to. That is, in step S334, the user terminal 34 transmits the inquiry data of the conversation request together with the designated partner data to the introduction server 31 via the Internet 32, so that the conversation with the designated party can be performed. Make the desired inquiry.

  In step S134, the web server function 51 of the introduction server 31 receives the data of the other party who wishes to talk and the data of the inquiry of the conversation desired transmitted from the user terminal 34, and receives the conversation request inquiry accepting unit 57. To supply. More specifically, for example, when a female user of the user terminal 34 desires a conversation with a male user of the user terminal 33, the conversation request inquiry reception unit 57 displays data of a partner who desires a conversation (for example, a user A favorite record associated with a user ID for identifying a male user of the user terminal 33 in the matching DB 76, which receives the user ID of the male user of the terminal 33) and the inquiry data of the desired conversation. By storing status data indicating that conversation is desired from the user specified by the partner user ID in the favorite record in which the partner user ID for identifying the female user of the user terminal 34 is stored, Accept the desired inquiry.

  In step S135, the introduction server 31 updates the display of the conversation request on the user location on the favorite page of the partner with whom the conversation is desired (for example, a male user of the user terminal 33). As a result, the fact that the female user of the user terminal 34 wishes to have a conversation is displayed on the favorite page of the partner with whom the conversation is desired, and a button for accepting the conversation request (conversation application) is arranged. Is done. That is, in this case, a message indicating that the female user of the user terminal 34 desires a conversation is displayed on the favorite page of the male user of the user terminal 33.

  In step S136, the mail function 54 notifies the user that the conversation is desired (conversation has been applied) by an e-mail addressed to the person whose conversation is desired, and inquires about the desired conversation with the favorite person. This process ends. In this case, the electronic mail address of the other party with whom the conversation is desired is read from the basic information DB 71 using the other party's user ID as a key.

  In this way, it is possible to select a favorite partner from the favorite partners and inquire about the wish of the conversation.

  Next, a process for accepting a conversation application when a conversation is applied from a female user of the user terminal 34 to a male user of the user terminal 33 (conversation is desired) will be described.

  FIG. 17 is a flowchart for explaining the process of accepting a conversation application. When a male user instructs the user terminal 33 to display a favorite page, the user terminal 33 transmits a request for a favorite page to the introduction server 31 via the Internet 32 in step S241. In step S <b> 141, the web server function 51 of the introduction server 31 receives the request transmitted from the user terminal 33. In step S <b> 142, the page data generation unit 52 generates favorite page data for displaying data of a partner that the user likes.

  More specifically, in step S142, the page data generation unit 52 selects the partner user ID stored in the favorite record associated with the user ID that identifies the male user of the user terminal 33 from the matching DB 76. (Including a specific user ID that identifies a female user of the user terminal 34). Then, the page data generation unit 52 reads the attributes such as the image file, the handle name, and the region associated with the same user ID as the counterpart user ID from the basic information DB 72, and further, from the detailed information DB 73, A comment or the like associated with the same user ID and handle name as the counterpart user ID is read. The page data generation unit 52 uses the read image, handle name, comment, region, and other attributes to generate favorite page data for displaying the other party's favorite data.

  In step S143, the Web server function 51 causes the communication unit 89, which is a network interface, to transmit the favorite page data generated by the page data generation unit 52 to the user terminal 33 via the Internet 32.

  In step S <b> 242, the user terminal 33 receives favorite page data transmitted from the introduction server 31. In step S243, the user terminal 33 displays a favorite page. On the favorites page, the attributes and images of the female user of the partner who the male user of the user terminal 33 likes are displayed.

  FIG. 18 is a diagram illustrating an example of a favorite page. As shown in FIG. 18, on the favorite page, attributes and images of a female user of a partner who the male user of the user terminal 33 likes are displayed. That is, for each partner, for example, the partner's age, the area where he / she lives, the points that the user of the woman likes, and the image of the partner are displayed, and a button for inquiring about the wish of the conversation (A button labeled “Let's talk application” in FIG. 18) is arranged.

  Also, in the favorite page, when a conversation application is requested from the other party (when a conversation is desired), a button for accepting the conversation application from the other party ("Speak Consent" in FIG. 18). Button) is placed.

  The male user of the user terminal 33 looks at the favorite page, and if there is a partner who wants to talk among the partners who have applied for the conversation, the user operates the user terminal 33 and clicks a button for accepting the conversation application. Click to accept the conversation application. In step S244, the user terminal 33 determines whether or not to accept the conversation application depending on whether or not a button for accepting the conversation application is clicked. If it is determined in step S244 that the conversation application is accepted, the procedure proceeds to step S245, and the user terminal 33 transmits to the introduction server 31 that the conversation application is accepted. That is, the user terminal 33 transmits data indicating acceptance of the conversation application to the introduction server 31 along with data (for example, a user ID) specifying the partner who has applied for the conversation via the Internet 32.

  In step S144, the web server function 51 of the introduction server 31 transmits data (for example, a user ID) that is transmitted from the user terminal 33 and identifies a partner who has applied for the conversation, and data indicating that the application for the conversation is accepted. Receive. The web server function 51 supplies the conversation request acceptance reception unit 58 with data specifying the partner who has applied for the conversation and data indicating that the application for the conversation is accepted.

  In step S145, the conversation request acceptance acceptance unit 58 updates the favorite mode of the matching DB 76 to the conversation mode. More specifically, for example, when a female user of the user terminal 34 desires a conversation with a male user of the user terminal 33 and the male user of the user terminal 33 accepts this, it is stored in the matching DB 76. Among the favorite records, the status stored in the favorite record associated with the user ID specifying the male user of the user terminal 33 and storing the counterpart user ID specifying the female user of the user terminal 34 is , The favorite mode indicating that the other party likes is updated to the conversation mode indicating that the other party is talking.

  In step S146, the electronic bulletin board function 59 of the introduction server 31 sets an electronic bulletin board (hereinafter also referred to as a bulletin board) with the party to whom the conversation has been applied, and the introduction server 31 provides bulletin board buttons on the pages of both users. .

  FIG. 19 is a diagram showing an example of a user page provided with a bulletin board button. As shown in FIG. 19, on the user's page, for example, the age of the partner, the area where he / she lives, and the image of the partner are displayed for each partner provided with the bulletin board, and the bulletin board for entering the bulletin board. Buttons (buttons labeled "To talk board" in FIG. 19) are arranged.

  Thereby, the male user of the user terminal 33 and the partner who has applied for the conversation can enter the bulletin board by clicking the bulletin board button, and can talk to each other on the bulletin board.

  In step S147, the mail function 54 reads the male user of the user terminal 33 and the email address of the other party from the basic information DB 71, and sends a bulletin board to both the male user of the user terminal 33 and the party who has applied for the conversation. The process of accepting the conversation application is completed.

  If it is determined in step S244 that the conversation application is not accepted, steps S144 to S147 are skipped, the bulletin board is not set, and the conversation application acceptance process ends.

  In this way, it is possible to accept an application for a conversation from the other party, and if accepted, a conversation can be made on the bulletin board.

  In the present introduction system, the male user X of the user terminal 33 registers the female user A and the user B as favorites, and the attribute of the male user X is set on the condition indicating the attribute requested by the female user A. If the mismatch does not match, the web page provided from the introduction server 31 to the user terminal 34 of the user A is the web page that displays the data of the person who likes him / her. Information about the user X is displayed on a favorite page. In this case, the page that the user A likes is also displayed that the attribute of the male user X does not match the condition indicating the attribute requested by the female user A.

  FIG. 21 is a flowchart for explaining the registration process to favorites. As a response to the request from the user terminal 33, in step S151, the web server function 51 of the introduction server 31 is generated by the page data generation unit 52 via the Internet 32 in the communication unit 89 that is a network interface. The web page data for acquiring the conditions is transmitted to the user terminal 33.

  In step S251, the user terminal 33 receives the web page data transmitted from the introduction server 31, and displays the web page for acquiring the conditions.

  When a condition is input to the displayed web page according to the operation of the male user of the user terminal 33, the user terminal 33 acquires the condition input to the web page in step S252. When transmission is instructed by a male user of the user terminal 33 by clicking a transmission button on the web page, the user terminal 33 introduces the acquired conditions via the Internet 32 in step S253. Send to server 31.

  In step S152, the web server function 51 of the introduction server 31 causes the communication unit 89, which is a network interface, to receive the condition transmitted from the user terminal 33. In step S153, the web server function 51 stores the received condition in the condition DB 74 in association with the user ID that identifies the male user of the user terminal 33.

  In step S154, the usage history DB 75 generates a usage history record associated with the user ID. In step S155, the extraction unit 55 extracts a user who is a partner having an attribute that matches the received condition, in the same procedure as in step S115. In step S <b> 156, the web server function 51 transmits the extracted user data to the user terminal 33.

  More specifically, in step S156, the page data generation unit 52 generates web page data for displaying the extracted user attributes and images in the same procedure as in step S116. The web server function 51 causes the communication unit 89, which is a network interface, to transmit, to the user terminal 33, web page data for displaying the extracted attributes and images of the other user via the Internet 32. .

  In step S254, the user terminal 33 receives and displays the data of the extracted partner user transmitted from the introduction server 31. That is, in step S254, the user terminal 33 receives the web page data transmitted from the introduction server 31 for displaying the extracted user attributes and images, and the extracted partner. A web page that displays user attributes and images is displayed.

  The male user of the user terminal 33 looks at the displayed web page, and if there is a favorite partner (female user) among the extracted partners, he / she operates the user terminal 33 and clicks a button. Therefore, in step S255, the user terminal 33 designates one or more partners designated by the male user from among the extracted partners. In step S <b> 256, the user terminal 33 transmits the application data for registration to favorites to the introduction server 31 along with the designated partner data via the Internet 32, thereby registering the designated partner to favorites. Apply.

  In step S157, the web server function 51 of the introduction server 31 receives the data of the designated partner and the application data for registration to the favorites transmitted from the user terminal 33, and applies for the registration to the favorites. Accept. In step S158, the Web server function 51 supplies the specified partner data to the matching DB 76 in the same procedure as in step S118, and associates the matching DB 76 with the user ID that identifies the male user of the user terminal 33. Then, a favorite record including a partner user ID for identifying a partner whom the male user of the user terminal 33 likes is generated, the matching DB 76 is updated, and the process of registering as a favorite ends.

  In this way, a partner user ID for identifying a favorite partner is stored in the favorite record.

  Next, processing for generating a favorite record for a partner who has a small attribute difference with respect to the condition will be described with reference to the flowchart of FIG. In step S <b> 161, the determination unit 56 reads out from the condition DB 74 the conditions of all of the favorite opponents that the male user of the user terminal 33 likes, which is stored in the favorite record. That is, the determination unit 56 reads the partner user ID from the favorite record associated with the user ID that identifies the male user of the user terminal 33 among the favorite records in the matching DB 76. Then, the determination unit 56 reads the condition associated with the same user ID as the read partner user ID from the condition DB 74.

  In step S <b> 162, the determination unit 56 reads out the attributes of the male user of the user terminal 33, that is, the favorite user from the basic information DB 72. More specifically, the determination unit 56 reads out the attribute of the male user of the user terminal 33 attached to the user ID that identifies the male user of the user terminal 33 from the basic information DB 72.

  In step S163, the determination unit 56 selects one partner from the partners whose conditions are read in the procedure in step S161. In step S164, the determination unit 56 extracts a difference between the condition of the favorite partner and the attribute of the user who likes (male user of the user terminal 33). In step S165, the determination unit 56 determines whether the number of extracted difference items is within N, which is a predetermined number. For example, N is any one of 1 to 3.

  If it is determined in step S165 that the number of difference items is within N, the procedure proceeds to step S166, and the determination unit 56 determines whether the difference between the difference item values is within a predetermined allowable range. Determine whether or not. For example, the allowable range is made smaller than the unit of change representing the attribute indicated in the condition. More specifically, for example, when the annual income as an attribute indicated in the condition is expressed in units of 1 million yen, the allowable range is less than 1 million yen. For example, when the height as the attribute indicated in the condition is expressed in 5 cm increments, the allowable range is less than 5 cm.

  Further, the allowable range may be determined by multiplying the attribute indicated by the condition by a predetermined ratio. Specifically, for example, if the item is an annual income, the allowable range is 10% of the lower limit of the annual income as an attribute indicated in the condition of the favorite partner. Further, for example, if the item is age, the allowable range is set to 5% of the upper limit of age as an attribute indicated in the condition of the favorite partner.

  That is, in step S165 and step S166, the determination unit 56 determines a condition indicating an attribute to be obtained from the other party of the extraction user (in this case, a female user of the user terminal 34) and a target user (in this case, a male user of the user terminal 33). ) Is determined whether or not the difference from the attribute is within a predetermined range. The range of this difference is assumed to be an allowable range by supplementing an attribute whose attribute is insufficient when other attributes sufficiently satisfy the condition.

  If it is determined in step S166 that the difference between the values of the difference items is within the allowable range, the attribute difference with respect to the condition is very small, so the procedure proceeds to step S167, and the determination unit 56 stores the matching user ID in the matching DB 76. As a favorite record associated with the user ID of the selected favorite partner, in which a user ID for identifying a male user is stored, and a difference item between a condition and an attribute and a difference value Is generated and a matching record is updated.

  If the number of difference items is within N and the difference between the difference item values is within an allowable range, and a favorite record is generated, a user with an attribute that does not meet the condition is also liked and Although it is generated, I like the records for such users so that I can reduce the threshold of matching and increase the chances of contact in consideration of the fact that I like them. It is.

  In step S168, the mail function 54 reads out the other party's e-mail address from the basic information DB 71 using the other party's user ID as a key, and notifies the other party of the e-mail address that he / she liked and generated the record. Advances to step S169.

  If it is determined in step S165 that the number of difference items is not less than N, the difference in attributes with respect to the condition is not very small. Therefore, the procedure from step S166 to step S168 is skipped and the record is not generated. The procedure proceeds to step S169.

  If it is determined in step S166 that the difference between the values of the difference items is not within the allowable range, the attribute difference with respect to the condition is not very small in this case as well, so the procedure from step S167 to step S168 is skipped and is liked. Is not generated, and the procedure proceeds to step S169.

  In step S169, the determination unit 56 determines whether or not the processing of all the opponents whose conditions have been read has been completed. If it is determined that the processing of all the opponents has been completed, the determination unit 56 likes the record generation. The process ends. If it is determined in step S169 that the processing of all opponents has not been completed, the procedure returns to step S163, and the above processing is performed until the next opponent is selected and the processing of all opponents is completed. Repeated.

  In this way, if the difference between your attribute and your favorite partner's condition is very small, the other party will like it and a record will be generated, and the difference between your attribute and your favorite partner's condition will not be very small If the other party likes it, no record is generated.

  Next, with reference to the flowchart of FIG. 23, the user terminal 34 of the user who generated the favorite record including the user whose attribute difference with respect to the condition is very small and the introduction partner 31 of the user with the favorite partner. Explain the processing of the desired query for the conversation. When the female user likes the web page that displays data of the person he / she likes (in this case, the male user of the user terminal 33) to the user terminal 34 and instructs the user terminal 34 to display the page, in step S371, the user terminal 34 sends a request for a favorite page to the introduction server 31 via the Internet 32. In step S <b> 171, the web server function 51 of the introduction server 31 receives a request transmitted from the user terminal 34. In step S172, the page data generating unit 52 likes to display data of a partner who likes himself / herself and likes to indicate that the partner does not meet the condition for which the attribute difference with respect to the condition is small. Generate page data. Details of the procedure in step S172 are the same as those in step S132.

  In step S173, the web server function 51 causes the communication unit 89, which is a network interface, to transmit the favorite page data generated by the page data generation unit 52 to the user terminal 34 via the Internet 32.

  In step S372, the user terminal 34 receives the data of the favorite page transmitted from the introduction server 31. In step S373, the user terminal 34 likes and displays the page. In this favorite page, the attributes and images of the male user who likes the female user of the user terminal 34 are displayed, and the male terminal of the partner who has a very small difference in attributes with respect to the conditions is displayed on the user terminal 34. It is displayed that the female user does not meet the requirements for the other party.

  A female user of the user terminal 34 likes a page, and if there is a partner who wants to talk among those who like himself, the user terminal 34 is operated, and a button for inquiring about the wish of the conversation is displayed. Click to indicate the person you want to talk to. Moreover, the female user of the user terminal 34 can also instruct | indicate as the other party who wants to talk about the other party man whose attribute difference with respect to conditions is minute.

  In step S374, the user terminal 34 includes one or more instructed by the female user of the user terminal 34 from the partners who liked the user, including partners whose attribute differences with respect to the condition are small. Specify the other party and inquire about the desired conversation. That is, in step S374, the user terminal 34 transmits the inquiry data for the conversation request together with the designated partner data to the introduction server 31 via the Internet 32, thereby enabling the conversation with the designated partner. Make the desired inquiry.

  In step S 174, the web server function 51 of the introduction server 31 receives the data of the other party who wants to talk and the data of the inquiry of the conversation desired transmitted from the user terminal 34, and receives the conversation request inquiry acceptance unit 57. To supply. More specifically, for example, when a female user of the user terminal 34 desires a conversation with a male user of the user terminal 33, the conversation request inquiry reception unit 57 displays data of a partner who desires a conversation (for example, a user A favorite record associated with a user ID for identifying a male user of the user terminal 33 in the matching DB 76, which receives the user ID of the male user of the terminal 33) and the inquiry data of the desired conversation. By storing status data indicating that conversation is desired from the user specified by the partner user ID in the favorite record in which the partner user ID for identifying the female user of the user terminal 34 is stored, Accept the desired inquiry.

  In step S175, the introduction server 31 updates the display of the conversation request on the user part of the favorite page of the partner with whom the conversation is desired (for example, the male user of the user terminal 33). As a result, the fact that the female user of the user terminal 34 wishes to have a conversation is displayed on the favorite page of the partner with whom the conversation is desired, and a button for accepting the conversation request (conversation application) is arranged. Is done. That is, in this case, a message indicating that the female user of the user terminal 34 desires a conversation is displayed on the favorite page of the male user of the user terminal 33.

  In step S176, the mail function 54 reads out the e-mail address of the other party whose conversation is desired from the basic information DB 71, and the conversation is requested by the e-mail addressed to the other party who desires the conversation (the conversation has been applied). ) Is notified, and the process of inquiring about the desired conversation with the favorite party ends.

  In this way, it is possible to inquire about a conversation request by selecting a favorite partner from a favorite partner including a partner having a small attribute difference with respect to a condition.

  FIG. 24 is a flowchart for explaining a process of accepting a conversation application when a conversation is applied from a female user of the user terminal 34 to a male user of the user terminal 33 (conversation is desired). When the male user instructs the user terminal 33 to display a favorite page, the user terminal 33 transmits a request for a favorite page to the introduction server 31 via the Internet 32 in step S281. In step S <b> 181, the web server function 51 of the introduction server 31 receives the request transmitted from the user terminal 33. In step S182, the page data generation unit 52 generates favorite page data for displaying the partner data that the user likes in the same procedure as in step S142. In step S183, the web server function 51 causes the communication unit 89, which is a network interface, to transmit the favorite page data generated by the page data generation unit 52 to the user terminal 33 via the Internet 32.

  In step S <b> 282, the user terminal 33 receives the favorite page data transmitted from the introduction server 31. In step S283, the user terminal 33 displays a favorite page. On the favorites page, the attributes and images of the female user of the partner who the male user of the user terminal 33 likes are displayed.

  On the favorites page, when a conversation application is requested from the other party (when a conversation is desired), a button for accepting the conversation application from the other party (“Accept Speak” in FIG. 18) is described. Button) is placed.

  The male user of the user terminal 33 looks at the favorite page, and if there is a partner who wants to talk among the partners who have applied for the conversation, the user operates the user terminal 33 and clicks a button for accepting the conversation application. Click to accept the conversation application. In step S284, the user terminal 33 determines whether or not to accept the conversation application based on whether or not a button for accepting the conversation application is clicked. If it is determined in step S284 that the application for conversation is accepted, the procedure proceeds to step S285, and the user terminal 33 transmits to the introduction server 31 that the application for conversation is accepted. That is, the user terminal 33 transmits data indicating acceptance of the conversation application to the introduction server 31 along with data (for example, a user ID) specifying the partner who has applied for the conversation via the Internet 32.

  In step S184, the web server function 51 of the introduction server 31 receives the data transmitted from the user terminal 33 for specifying the partner who has applied for the conversation and the data for accepting the application for the conversation. The web server function 51 supplies the conversation request acceptance reception unit 58 with data specifying the partner who has applied for the conversation and data indicating that the application for the conversation is accepted.

  In step S185, the conversation request acceptance acceptance unit 58 updates the favorite mode of the matching DB 76 to the conversation mode. More specifically, for example, when a female user of the user terminal 34 desires a conversation with a male user of the user terminal 33 and the male user of the user terminal 33 accepts this, it is stored in the matching DB 76. Among the favorite records, the status stored in the favorite record associated with the user ID specifying the male user of the user terminal 33 and storing the counterpart user ID specifying the female user of the user terminal 34 is , The favorite mode indicating that the other party likes is changed to the conversation mode indicating that the other party is talking.

  In step S185, the electronic bulletin board function 59 of the introduction server 31 sets an electronic bulletin board with the partner who has applied for the conversation, and the introduction server 31 provides a bulletin board button on the page of both users.

  In step S187, the mail function 54 notifies by e-mail that a bulletin board has been provided for both the male user of the user terminal 33 and the partner who has applied for the conversation, and the process for accepting the application for conversation ends. .

  In this way, it is possible to accept an application for a conversation from the other party, and if accepted, a conversation can be made on the bulletin board. If the difference between your attributes and the condition of the other party is very small, you may be able to talk to the other party, increasing the chances of having a conversation with the other party.

  Further, as shown in FIG. 25, in the present introduction system, when the attribute of the female user A does not satisfy the conditions required for the male user X, the introduction server 31 changes the user terminal 34 to the user A. The information of the user X is displayed on an introduction page different from the favorite page among the provided web pages. In this case, the male user X is not notified that the female user A is introduced to the female user A, and the introduction page of the female user A is “close to the desired female image”. Is displayed.

  FIG. 26 is a flowchart for explaining the registration process to favorites. As a response to the request from the user terminal 33, in step S191, the web server function 51 of the introduction server 31 is generated by the page data generation unit 52 via the Internet 32 in the communication unit 89 that is a network interface. The web page data for acquiring the conditions is transmitted to the user terminal 33.

  In step S291, the user terminal 33 receives the web page data transmitted from the introduction server 31, and displays the web page for acquiring the conditions.

  When a condition is input to the displayed web page according to the operation of the male user of the user terminal 33, in step S292, the user terminal 33 acquires the condition input to the web page. When transmission is instructed by a male user of the user terminal 33 by clicking the transmission button on the web page, the user terminal 33 introduces the acquired condition via the Internet 32 in step S293. Send to server 31.

  In step S192, the web server function 51 of the introduction server 31 causes the communication unit 89, which is a network interface, to receive the conditions transmitted from the user terminal 33. In step S193, the web server function 51 stores the received condition in the condition DB 74 in association with the user ID that identifies the male user of the user terminal 33.

  In step S194, the usage history DB 75 generates a usage history record associated with the user ID. In step S195, the extraction unit 55 extracts a user who is a partner with an attribute that matches the received condition, in the same procedure as in step S115. In step S196, the web server function 51 transmits the extracted user data to the user terminal 33.

  More specifically, in step S196, the page data generation unit 52 generates web page data for displaying the extracted user attributes and images, etc., in the same procedure as in step S116. The web server function 51 causes the communication unit 89, which is a network interface, to transmit, to the user terminal 33, web page data for displaying the extracted attributes and images of the other user via the Internet 32. .

  In step S294, the user terminal 33 receives and displays the data of the extracted partner user transmitted from the introduction server 31. That is, in step S294, the user terminal 33 receives the web page data transmitted from the introduction server 31 for displaying the extracted user attributes and images, and the extracted partner. A web page that displays user attributes and images is displayed.

  The male user of the user terminal 33 looks at the displayed web page, and if there is a favorite partner (female user) among the extracted partners, he / she operates the user terminal 33 and clicks a button. Therefore, in step S295, the user terminal 33 designates one or more partners instructed by the male user from the extracted partners. In step S 296, the user terminal 33 transmits the application data for registration to favorites to the introduction server 31 along with the data of the designated partner via the Internet 32, thereby registering the designated partner to favorites. Apply.

  In step S197, the web server function 51 of the introduction server 31 receives the data of the designated partner and the application data for the favorite registration transmitted from the user terminal 33, and the application for the registration to the favorite data is received. Accept. In step S198, the Web server function 51 supplies the specified partner data to the matching DB 76, and the matching DB 76 is associated with the user ID that identifies the male user of the user terminal 33, and the male ID of the user terminal 33 is stored. The favorite record including the partner user ID for identifying the partner that the user likes is generated, the matching DB 76 is updated, and the process of registering the favorite is completed. In this case, one favorite record is generated for each favorite partner, and one partner user ID is stored in one favorite record.

  In this way, a partner user ID for identifying a favorite partner is stored in the favorite record.

  FIG. 27 shows the generation of an introduction record for introducing a male user of the user terminal 33 to a female user of the user terminal 34 having an attribute that does not satisfy the conditions required by the male user of the user terminal 33 slightly. It is a flowchart explaining the process of.

  In step S <b> 501, the condition generation unit 60 associates from the condition DB 74 with a user ID that identifies a male user of the user terminal 33 (a condition indicating an attribute that the male user of the user terminal 33 requests from the other party). Is read. In step S <b> 502, the condition generation unit 60 relaxes the male user condition of the user terminal 33 within a predetermined range. In other words, in step S502, the condition generation unit 60 relaxes the condition indicating the attribute required for the other party of the focused user (in this case, the male user of the user terminal 33) who is the focused user.

  More specifically, for example, in step S <b> 502, the condition generation unit 60 relaxes the condition by multiplying the condition indicating the attribute that the user of interest requests from the opponent by a predetermined ratio. Specifically, the condition generation unit 60 relaxes the condition by multiplying the condition indicating the upper limit of age by 1.05. Also, for example, in step S502, the condition generation unit 60 relaxes the condition by adding a predetermined value to the condition indicating the attribute requested by the user of interest from the other party. Specifically, the condition generation unit 60 relaxes the condition by multiplying the condition indicating the number of children by 1.

  In step S503, the extraction unit 55 extracts a user who is a partner that matches the relaxed condition. More specifically, the extraction unit 55 reads the attribute that matches the relaxed condition from the basic information DB 72 and acquires the user ID associated with the read attribute, thereby reducing the relaxed condition. The user who becomes the partner who matches is extracted. That is, in step S503, the extraction unit 55 extracts a user having an attribute that matches the relaxed condition of the user of interest.

  In step S504, the extraction unit 55 selects one person from the extracted counterpart users. In step S <b> 505, the extraction unit 55 causes the matching DB 76 to generate an introduction record of the selected partner user and update the matching DB 76. The introduction record is a favorite record or a record different from the favorite record, and is associated with a user ID that identifies the selected partner, and a user ID that identifies a male user of the user terminal 33 as the partner user ID Is stored.

  In step S506, the mail function 54 reads the selected partner's email address from the basic information DB 71 using the partner's user ID as a key, and notifies the partner that the introduction record has been generated by email.

  In step S507, the determination unit 56 determines whether or not the processing of all the opponents has been completed. If it is determined that the processing of all the opponents has been completed, the process of generating the introduction record ends. If it is determined in step S507 that the processing of all the opponents has not been completed, the procedure returns to step S504, and the above-mentioned process is performed until the next partner user is selected and the processing of all the opponents is completed. The process is repeated.

  In this way, the male user of the user terminal 33 is not notified that the introduction record for introducing himself / herself to the other party has been generated, and the other party who does not satisfy the conditions of the male user of the user terminal 33 slightly. In addition, an introduction record for introducing a male user of the user terminal 33 is generated.

  Processing for providing an introduction page that presents an introduction page for introducing a male user of the user terminal 33 to a female user of the user terminal 34 that is a partner who does not satisfy the conditions of the male user of the user terminal 33 slightly. Will be described with reference to the flowchart of FIG.

  When the female user instructs the user terminal 34 to display the introduction page, the user terminal 34 transmits a request for the introduction page to the introduction server 31 via the Internet 32 in step S711. In step S 511, the web server function 51 of the introduction server 31 receives the request transmitted from the user terminal 34. In step S <b> 512, the page data generation unit 52 generates data of an introduction page that displays data of a partner who does not satisfy the required conditions of the female user attribute of the user terminal 34 slightly.

  More specifically, in step S512, the page data generation unit 52 reads from the matching DB 76 the counterpart user ID (this is stored in the introduction record associated with the user ID that identifies the female user of the user terminal 34). In the case, a specific user ID that identifies a male user of the user terminal 33 is read). Then, the page data generation unit 52 reads the attributes such as the image file, the handle name, and the region associated with the same user ID as the counterpart user ID from the basic information DB 72, and further, from the detailed information DB 73, A comment or the like associated with the same user ID and handle name as the counterpart user ID is read. The page data generation unit 52 uses the read image, handle name, comment, region, and other attributes to generate introduction page data for displaying the data of the person who likes him.

  In step S513, the Web server function 51 causes the communication unit 89, which is a network interface, to transmit the introduction page data generated by the page data generation unit 52 to the user terminal 34 via the Internet 32. That is, in step S513, the Web server function 51 assigns the attribute of the user of interest (in this case, the male user of the user terminal 33) to the extracted user (in this case, the female user of the user terminal 34). Notice.

  In step S712, the user terminal 34 receives the data of the introduction page transmitted from the introduction server 31. In step S713, the user terminal 34 displays an introduction page. On the introduction page, the attributes and images of the other male user who does not satisfy the required conditions of the female user attribute of the user terminal 34 are displayed together with a message such as “close to the desired female image”. The

  FIG. 29 is a diagram illustrating an example of an introduction page. As shown in FIG. 29, the introduction page includes a message such as “You are close to the requested female image”, and the condition of the female user attribute of the user terminal 34 is slightly satisfied. The attributes and images of the other male user are displayed. That is, for each partner, for example, the partner's age, the area where he / she lives, and the partner's image are displayed on the introduction page, and a button for inquiring about a conversation request (see “Speak” in FIG. 29). The button labeled “Apply” is placed.

  The female user of the user terminal 34 looks at the introduction page and, if there is a partner who wants to talk, operates the user terminal 34 and clicks a button for inquiring about the wish of the conversation. In step S714, the user terminal 34 designates one or more partners designated by the female user of the user terminal 34 from among the partners, and makes an inquiry about the desired conversation. . That is, in step S714, the user terminal 34 transmits the inquiry request data for the conversation together with the designated partner data to the introduction server 31 via the Internet 32, so that the conversation with the designated partner can be performed. Make the desired inquiry.

  In step S 514, the web server function 51 of the introduction server 31 receives the data of the other party who wants to talk and the data of the inquiry of the conversation desired transmitted from the user terminal 34, and receives the conversation request inquiry acceptance unit 57. To supply. More specifically, for example, when a female user of the user terminal 34 desires a conversation with a male user of the user terminal 33, the conversation request inquiry receiving unit 57 requests the conversation with the data of the other party who desires the conversation. Introducing the matching DB 76, the counterpart user ID for identifying the male user of the user terminal 33, which is associated with the user ID for identifying the female user of the user terminal 34 in the matching DB 76, is stored. By storing the status data indicating that a conversation is desired from the user specified by the user ID in the record, an inquiry about the desired conversation is accepted. As described above, in step S514, the conversation request inquiry receiving unit 57 extracts the application for contact with the user of interest (in this case, the male user of the user terminal 33) (in this case, the female user of the user terminal 34). Accept from.

  In step S515, the introduction server 31 updates the display of the conversation request in the user introduction portion of the introduction page in the page of the other party (for example, the male user of the user terminal 33) with whom the conversation is desired. As a result, a message indicating that the female user of the user terminal 34 wishes to talk is displayed on the introduction page of the other party who wished to talk, and a button for accepting the conversation request (conversation application) is arranged. Is done.

  In step S516, the mail function 54 notifies the user that the conversation is desired (conversation has been applied) by an e-mail addressed to the person whose conversation is desired, and the process of providing the introduction page ends.

  In this way, it is possible to inquire about a conversation request by selecting a partner who does not satisfy the conditions for which his / her attributes are required and who is favorite from among the introduced partners.

  FIG. 30 is a flowchart for explaining the process of accepting a conversation application. When the male user instructs the user terminal 33 to display the introduction page, the user terminal 33 transmits a request for the introduction page to the introduction server 31 via the Internet 32 in step S621. In step S <b> 521, the web server function 51 of the introduction server 31 receives the request transmitted from the user terminal 33. In step S522, the page data generation unit 52 generates data of an introduction page that introduces the partner who has applied for the conversation on the introduction page of the other party.

  More specifically, in step S522, the page data generation unit 52 is an introduction record in which the user ID for identifying the male user of the user terminal 33 is stored as the counterpart user ID from the matching DB 76, and the conversation is desired. The user ID (in this case, including the specific user ID that identifies the female user of the user terminal 34) that is associated with the status introduction record indicating that it has been read is read. Then, the page data generation unit 52 reads the attributes such as the image file, the handle name, and the region associated with the read user ID from the basic information DB 72, and further reads the read user from the detailed information DB 73. Reads comments etc. associated with ID and handle name. The page data generation unit 52 uses the read image, handle name, comment, region, and other attributes to generate introduction page data that introduces the other party who has applied for the conversation on the other party's introduction page.

  In step S522, the page data generation unit 52 slightly satisfies the condition of the other party who requires the attribute of the male user of the user terminal 33 in addition to the other party who applied for the conversation on the other party's introduction page. You may make it produce | generate the data of the introduction page which introduces the other party who does not exist.

  In step S523, the web server function 51 causes the communication unit 89, which is a network interface, to transmit the introduction page data generated by the page data generation unit 52 to the user terminal 33 via the Internet 32. That is, in step S523, the web server function 51 applies the contact with the target user (in this case, the male user of the user terminal 33) from the extraction user (in this case, the female user of the user terminal 34). The notice user is notified of the contact application from the extraction user.

  In step S <b> 622, the user terminal 33 receives introduction page data transmitted from the introduction server 31. In step S623, the user terminal 33 displays an introduction page. In the introduction page, the attributes of the female user who is a partner who does not satisfy the conditions required by the male user of the user terminal 33 and who has applied for a conversation with the male user of the user terminal 33, and An image is displayed.

  FIG. 31 is a diagram illustrating an example of an introduction page. As shown in FIG. 31, on the introduction page, the attributes and images of the other party whose attributes do not satisfy the conditions required by the male user of the user terminal 33 are displayed. That is, on the introduction page, for example, the age of the other party, the area where he lives, and the other party's image are displayed for each partner whose attributes do not satisfy the conditions required by the male user of the user terminal 33. In addition, a button for accepting a conversation request (a button labeled “Accept a talk” in FIG. 31) is arranged.

  The male user of the user terminal 33 looks at the introduction page, and if there is a partner who wants to talk among the partners who have applied for the conversation, the user operates the user terminal 33 and clicks a button for accepting the application for the conversation. Click to accept the conversation application. In step S624, the user terminal 33 determines whether or not to accept the conversation application depending on whether or not a button for accepting the conversation application is clicked. If it is determined in step S624 that the conversation application is accepted, the procedure proceeds to step S625, and the user terminal 33 transmits to the introduction server 31 that the conversation application is accepted. In other words, the user terminal 33 accepts the conversation application by sending data to the introduction server 31 together with the data specifying the partner who has applied for the conversation to the introduction server 31 via the Internet 32. To do.

  In step S524, the web server function 51 of the introduction server 31 receives the data transmitted from the user terminal 34 for specifying the other party to whom the conversation has been applied and the data for accepting the application for the conversation. The web server function 51 supplies the conversation request acceptance reception unit 58 with data specifying the partner who has applied for the conversation and data indicating that the application for the conversation is accepted.

  In step S525, the conversation request acceptance acceptance unit 58 updates the introduction mode of the matching DB 76 to the conversation mode. More specifically, for example, when a female user of the user terminal 34 desires a conversation with a male user of the user terminal 33 and the male user of the user terminal 33 accepts this, it is stored in the matching DB 76. Among the introduction records, the status stored in the introduction record that is associated with the user ID that identifies the female user of the user terminal 34 and that stores the counterpart user ID that identifies the male user of the user terminal 33 is The mode is changed from the introduction mode to the conversation mode indicating that the user is talking to the other party.

  In step S525, the electronic bulletin board function 59 of the introduction server 31 sets a bulletin board with the partner who applied for the conversation, and the introduction server 31 provides a bulletin board button on both users' pages.

  Thereby, the male user of the user terminal 33 and the partner who has applied for the conversation can enter the bulletin board by clicking the bulletin board button, and can talk to each other on the bulletin board.

  In step S527, the mail function 54 notifies by e-mail that a bulletin board has been provided for both the male user of the user terminal 33 and the partner who has applied for the conversation, and the process for accepting the conversation application ends. .

  If it is determined in step S624 that the conversation application is not accepted, steps S524 to S527 are skipped, and the conversation application acceptance process ends.

  In this way, it is possible to accept an application for a conversation from a partner having an attribute that does not satisfy the required condition, and if it is accepted, a conversation can be made on the bulletin board.

  As a result, the total number of times a conversation is applied will also increase, and even if you have an attribute that does not meet the requirements that you want, you may be asked if you are applying for a conversation. You will be conscious and your willingness will increase.

  As described above, the case where the male user likes the female user and the case where the male user is introduced to the female user have been described. However, the case where the female user likes the male user and the case where the male user likes the male user. The same process is performed for introducing a female user, and the process is not limited by either male or female.

  In addition, the conversation on the electronic bulletin board has been described as an example of the user's contact, but the user's contact is not limited to this, and the user's contact is, for example, meeting directly and speaking, talking on the phone, and exchanging by email. Contact through direct or various media such as, through a social network service limited to users, or through an instant messenger. In addition, contact is not limited to the meaning of approaching and touching, but means having a relationship or having some kind of negotiation with another person.

  In addition, although the display by the website has been described as an example of the notification to the user, the notification to the user is not limited to this, and it is sufficient if the desired contents can be transmitted, and various media such as an e-mail, a voice message, and a facsimile. Can be notified through.

  In this way, when one user is provided with information on the attribute of the other user, the user can meet a desired partner. In addition, each user's own attribute and a condition indicating an attribute required for the other party are stored, and a condition indicating the attribute requested by one user for the other party is relaxed within a predetermined range, and the one user's relaxed condition is stored The user with the attribute that matches is extracted, one user is notified to the extracted user who is the extracted user, the application for contact with the one user is accepted from the extracted user, and the contact with the one user from the extracted user is If the application is made, if one user is notified of the application for contact from the extraction user, the chance to meet the user's desired partner will be increased, the user's interest in the service will be increased, and the Interest can be maintained longer.

  It is natural to perform matching processing between users whose conditions match in both directions, but by adopting this mechanism, in addition to being able to perform matching processing for users whose conditions do not match only in one direction, conditions in both directions Matching processing can also be performed for users who do not match. In other words, by extracting the opponent by relaxing the conditions, an unstable state that you would like to generate is generated, and then the offer input from one side is accepted, so it is somewhat stable from the unstable state By transitioning to a state, and further accepting an input of consent from the other, the state is developed from a slightly stable state to a stable state.

  The series of processes described above can be executed by hardware or can be executed by software. When a series of processing is executed by software, a program constituting the software executes various functions by installing a computer incorporated in dedicated hardware or various programs. For example, it is installed from a program recording medium in a general-purpose personal computer or the like.

  The program executed by the computer may be a program that is processed in time series in the order described in this specification, or in parallel or at a necessary timing such as when a call is made. It may be a program for processing.

  The embodiments of the present invention are not limited to the above-described embodiments, and various modifications can be made without departing from the scope of the present invention.

31 Introducing Server, 32 Internet, 33-1 to 33-3 and 33 User Terminal, 34-1 to 34-3 and 34 User Terminal, 51 Web Server Function, 52 Page Data Generation Unit, 53 Member Registration Unit, 54 Mail Function , 55 extraction unit, 56 determination unit, 57 conversation request inquiry reception unit, 58 conversation request acceptance reception unit, 59 electronic bulletin board function, 60 condition generation unit, 61 database group, 71 basic information database, 72 basic information database, 73 detailed information Database, 74 condition database, 75 usage history database, 76 matching database, 81 CPU, 82 ROM, 83 RAM, 89 communication unit, 91 storage unit

Claims (6)

In the information providing apparatus that provides the other information to one of a plurality of users who are each male or female,
Storage means for storing each user's own attribute and a condition indicating an attribute to be requested of the other party;
A mitigating means for mitigating the condition indicating an attribute requested by one user within a predetermined range;
Extraction means for extracting a user having an attribute that matches the relaxed condition of the one user;
A notification means for notifying the extracted user, which is an extracted user, of the one user;
First accepting means for accepting an application for contact with the one user from the extracted user;
The said notification means notifies an application of the contact from the said extraction user to the said one user, when the contact with the said one user is applied from the said extraction user. The information providing apparatus according to claim 1,
The notification means notifies the one user that the attribute of the extracted user matches the relaxed condition of the one user. The information providing apparatus according to claim 1,
An information providing apparatus further comprising second accepting means for accepting acceptance of a contact application from the extracted user from the one user. In the information provision apparatus of Claim 3,
An information providing apparatus further comprising providing means for providing an electronic bulletin board for contacting the one user who has accepted the contact application with the extracted user who has applied for contact. In the information providing method of the information providing apparatus, comprising a storage means, a relaxation means, an extraction means, a notification means, and a reception means, and providing the other information to one of a plurality of users who are men or women,
In the storage means, each of the user's own attribute and a condition indicating an attribute required for the other party are stored,
The relaxation means relaxes the condition indicating the attribute that one user wants the other party within a predetermined range,
The extraction means extracts users with attributes that match the relaxed condition of the one user,
The notification means notifies the extracted user, which is an extracted user, of the one user,
The accepting means accepts an application for contact with the one user from the extracted user,
An information providing method including a step of notifying the one user of a contact application from the extraction user when the notification means applies a contact with the one user from the extraction user. Computers that provide information to one of multiple users, each male or female,
Storing each user's own attribute and a condition indicating an attribute desired for the other party;
Relaxing the condition indicating the attribute that one user wants to the other party within a predetermined range,
Extracting users with attributes that match the relaxed condition of the one user;
Notifying the extracted user who is the extracted user of the one user,
Accepting an application for contact with the one user from the extracted user;
A program for executing processing including a step of notifying the one user of an application for contact from the extracted user when contact with the one user is applied from the extracted user.

Images