JP2006031183A - Member information management system and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To input event information within a group to give an incentive for continuing a group registration. <P>SOLUTION: This member information management system 1 for managing information of members inputted from a plurality of cellular phones 4, 6 and 8 by a server to which the cellular phones 5, 6 and 8 are connected through a network comprises a member information master file 10 registering individual identification information of a plurality of members 3 and 5 acquired from the cellular phones 4 and 6 in association with identification information couple-registered by the members 3 and 5; an application acceptance part 20 (evaluation point acceptance means) accepting, in occurrence of an event related to this couple, input of evaluation points of the event from the cellular phones 5 and 6 of the couple-registered members 3 and 5; and a couple registration DB 13 (evaluation point storage means) registering the evaluation points accepted from the members 3 and 5 in association with the kind of the event and the couple identification information. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a system and method capable of registering a relationship of a specific group such as a lover or a friend and storing information for evaluating the closeness of the group.

Conventionally, group registration has been performed in order to increase the sense of belonging among persons having specific relationships such as hobby circles, alumni associations, and lovers and to deepen relationships among group members. In addition, with the recent spread of the Internet, such group registration is also widely performed on the Internet. As an example, services such as couple registration (romance proof) and online marriage registration shown below have been proposed.
http://tunagikei.net/ http://todokede.com/index.html

Further, a dating game machine capable of registering dating records of couples has been proposed in the following patent documents.
JP 2000-305903 A

  By the way, in Patent Document 1, the number of times such as dates and calls are tabulated and presented, or the number of days from the date of dating is counted up. In the service of Non-Patent Document 1, it is also proposed to record the past two people's schedules and use them as a dating diary.

  However, simply providing uniform information such as the dating period and the number of dates and past facts lacks originality and is not sufficient as a merit or motivation to continue couple registration. Therefore, even if such aggregated information attracts interest at the beginning of dating (registration), it is difficult to fix the system because interest may gradually fade and registration of events may be neglected or couple registration may be canceled It becomes.

  The present invention has been made for the purpose of solving the above-mentioned problems. According to a first main aspect of the present invention, member information input from a terminal by a server in which a plurality of terminals are connected to the network. Member information management system for managing the membership information storage means for associating and registering personal identification information of a plurality of members acquired through the terminal and identification information of a group to which these members belong, When a predetermined event related to at least two members belonging to the group occurs, evaluation point receiving means for acquiring evaluation points of the event from terminals of a plurality of members who are parties, and from the party members Evaluation point storage means for registering the received evaluation points in association with the event type and group identification information Member information management system is provided, wherein the door.

  According to a second main aspect, there is provided a member information management method for managing member information input from a terminal by a server in which a plurality of terminals are connected to the network, wherein the server is connected through the terminal. A member information storage step of registering in the database the personal identification information of a plurality of members acquired and the identification information of the group to which these members belong, and a predetermined event related to at least two members belonging to the group A database in which an evaluation point receiving step of acquiring evaluation points of the event from terminals of a plurality of members who are parties and the evaluation points received from the party members are associated with an event type and group identification information A member information management method characterized by executing an evaluation point storing step registered in It is subjected.

  According to the present invention, since a plurality of group-registered members accumulate points for evaluating a predetermined event, a plurality of group members such as a couple are evaluated differently each time even in the same event. Or the same evaluation will be added twice, three times, etc. As a result, the accumulated points are closely related to the new density and specificity among group members, and the originality and sense of belonging of the group can be enhanced. Then, every time an event occurs, an incentive to evaluate and register points can be continuously given, and sufficient merit and motivation to continue group registration can be provided.

  Further, since the evaluation point information for each event input by the member as needed is accumulated in association with the attribute information of the member or group, useful statistical information can be collected. In other words, in addition to conventional uniform statistical information such as the average lifetime of the group, the total number of members, and the average number of events, the date of birth, blood type, and age of members (including other members who evaluated the event) The activity history (record) of the group based on various attributes such as occupation, constellation, zodiac, residential area, educational background, etc. is accumulated together with the evaluation points of a plurality of members at the time of the event occurrence. For example, for couples (groups) dating (events), it is expected that the evaluation points will differ due to various factors such as the age difference of the couple, the residential area, the season and dating period, just after the birthday, and the period elapsed since the previous date. Is done. Such individual specific dating records are extremely useful information when considering marketing strategies for each age group.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, exemplary embodiments of the invention will be described with reference to the accompanying drawings. In the following, an example in which a plurality of members who are lovers register as a group as a couple will be described.

  (overall structure)

  FIG. 1 is a diagram showing an overall network configuration and a schematic configuration of a member information management system according to the present embodiment. The member information management system 1 is provided in one or more servers of the management center 2 and includes a mobile phone 4 of the first member 3 who desires couple registration via a WEB server or a firewall (not shown) and the like. The member 3 is connected to the mobile phone 6 of the second member 5 (lover) who wants to be registered as a couple via a public line communication network such as the Internet. In the present embodiment, the terminal 9 dedicated to point input is installed in event facilities such as tourist spots, restaurants, hotels, halls, and sports facilities that couples are likely to visit on a date or travel, and couples use these facilities. In this case, points can be input from the dedicated terminal 9. In the following description, for convenience of explanation, the first member who applies for couple registration is referred to as a registration application member 3, and the second member for which couple registration is applied is referred to as a registration target member 5.

  (Schematic configuration of member information management system)

  The member information management system 1 exhibits various functions of the present embodiment described later by cooperating server hardware and software. Specifically, a data storage area and a program storage area are provided on a bus to which a CPU, RAM, ROM, input / output device and communication device are connected.

  The data storage area includes a member information master file 10 (member information storage means), a temporary data table 11, a point table 12, and a couple registration database (DB) 13 (group information storage means). Each of these databases 10 to 13 is a fixed area secured in the storage area of the server, and constitutes a relational database that can be referred to each other. Each of these databases can be integrated into one database, or each database can be divided into a plurality of databases.

  The member information master file 10 stores member bibliographic items, mobile phone identification IDs, and the like. Specifically, the member's name (nickname), face photo and portrait, address (region, prefecture, municipality), date of birth, gender, mobile phone identification ID, mobile phone number and email address, constellation, zodiac , Age, etc. are stored. The constellation, zodiac, age, etc. are automatically identified from the date of birth entered and the calendar function of the computer system. In addition to the aggregated prefectures and municipalities in administrative divisions such as Kanto and Yamagata Shonai, the address area is divided into prefectures and municipalities such as Shonan area, Keihin area, and metropolitan areas by arbitrary boundaries. Including area. In addition, it may be registered in association with the constituencies of the national election. For these area divisions, it is preferable that a separate area division table is provided so that member information can be aggregated in an arbitrary area, or one member can be associated with a plurality of areas.

  Here, this mobile phone identification ID is not something that a user (member) can set or change arbitrarily, such as an e-mail address. For example, a mobile phone manufacturer's preset serial number and communication carrier are used. The symbol shown and the user identification information acquired from the user at the time of the cellular phone use contract are combined. Therefore, as will be described later, by performing authentication based on the mobile phone ID, it is possible to simultaneously identify individual members and mobile phones. In addition, even when the member has a plurality of mobile phones, the individual member can be identified, so that duplicate registration can be checked. It is also possible to use a mobile device such as a member's home PC or PDA.

  The temporary data table 11 temporarily stores information necessary for the individual authentication of the applicant when an application for member registration or couple registration is accepted through a mobile phone. Specifically, when a new member registration application is accepted, the mobile phone identification ID of the applicant is temporarily stored. Further, when an application for couple registration is accepted from the registration application member 3, the mobile phone identification ID of the registration application member 3 and the e-mail address of the mobile phone 6 of the registration target member 5 are temporarily stored. The information stored in the temporary data table 11 is deleted after member registration or couple registration is completed. It is preferable that all data is automatically deleted at a predetermined time and a predetermined cycle such as 0:00 every day.

  The point table 12 stores basic evaluation points for each event related to a couple. For example, as shown in FIG. 2, the basic evaluation point 15 for each event and the anniversary addition / subtraction points 16 and 17 such as the birthday of the member and the X-year anniversary are stored in association with the event name 18 and the event ID 19. . “Anniversary” is registered for each couple in the couple registration DB 13. The anniversary addition / subtraction points 16 and 17 are for adding / subtracting the basic evaluation point 15 with respect to an event occurring on the registered anniversary. For example, when the date of one member's birthday, which is a registered anniversary, is dated, 1.5 pt obtained by adding 0.5 pt to 1 Pt, which is the basic date of dating, becomes the basic point. On the other hand, when the date is not set despite the birthday, 0.5 pt is subtracted and 0.5 pt becomes the basic point. In addition, when no point is registered from any member on the birthday, the dating record update unit 23 described later automatically recognizes the birthday by referring to the member information master file 10 and reads “date of birthday”. 0.5pt is subtracted assuming that the event was a negative event. Thus, by performing passive point registration (subtraction), the evaluation point can be an appropriate reference indicating the closeness of the registered couple.

  A member who has registered as a couple can register by arbitrarily increasing or decreasing these basic evaluation points (points after adding / subtracting points) when an event occurs. In addition, since evaluation points are useful basic data of statistical data, it is preferable to set a range that can be modified by members and an increment / decrement unit for each event in consideration of objectivity, universality, and the load of aggregation. . For example, an ordinary date is set so that it can be corrected in units of 0.1 pt within a range of 0.5 pt above and below the basic point 1 pt.

  The couple registration database 13 stores event evaluation points and association records (including anniversary dates) for each registered couple in association with the mobile phone identification ID and group ID of the target member. The dating record includes, for example, the event name 18 selected from a pull-down menu of a dating record field (not shown), arbitrarily inputted event information, a member's evaluation comment on the event, and the like. Here, the group ID is a number / symbol with a predetermined number of digits generated by applying the mobile phone identification IDs and names of two members who are registered as couples to a predetermined random number generation algorithm, or the member ID is arbitrary at the time of couple registration ID (a combination of the birthdays of two people, a combination of a date of start of dating and an initial, etc.).

  In the program storage area, in addition to a main program (not shown), as a functional unit related to the present invention, an application receiving unit 20 that receives application for membership registration and couple registration and registers application information in the temporary table 11, member registration and An authentication unit 21 for authenticating a member based on the mobile phone identification ID of the member information master file 10 when applying for couple registration or inquiring about couple registration, a couple registration processing unit 22 for performing processing necessary for couple registration, and events related to couples , A dating record update unit 23 for updating dating records in the couple registration DB 13, a registration inquiry process for accepting a couple registration inquiry of another member from a third member (registration inquiry member 7) and answering a search result Part 24, if no dating record etc. is input from any member for a predetermined period or more A database update unit 25 (registration cancellation means) that updates the member information master file 10 and the couple registration DB 13 when receiving an application, a data transmission unit 26 that transmits various data and messages to the member's email address, Stored is a data totaling unit 27 that counts some or all of the members' points at predetermined intervals for each member attribute or group type.

  Here, the application receiving unit 20 displays a menu screen as shown in FIG. 3 on the member's mobile phone, and receives input of various information through this screen. The example of this figure shows an initial screen displayed when a registered member 3 who is registered as a couple accesses the WEB site of the system 1 from the mobile phone 4. In this example, the registered application member 3 and the registration target member 5 are displayed together with their names (nicknames) and face photographs, and event evaluation points of the couple. For example, the mobile phone 4 is configured to receive various interface generation programs from the member information management system 1 of the present invention and execute them on a Web browser installed in the mobile phone.

  In the present embodiment, as described above, the terminal 9 dedicated to point input is installed in the event facility. By using this dedicated terminal 9, the member numbers and evaluation points of two people can be input simultaneously, and member authentication and point input for two people can be performed easily and in a short time. In addition, when the manager or manager of the facility sponsors the dedicated terminal 9 to be installed and points are input from the dedicated terminal 9, the application receiving unit 20 (evaluation point receiving means) together with the points The identification information of the terminal 9 is acquired and registered. Then, preferential information can be provided from the sponsor to the couple, or the sponsor fee can be determined in proportion to the operating status of the terminal 9.

  The dating record update unit 23 has a function of registering dating record information input from a member in the couple registration DB 13 and, when a predetermined event occurs, refers to the point table 12 and evaluates the event ( And the function of updating the information in the couple registration DB 13 is extracted. Specifically, when the event update or point input is received from one couple member, the point update function sends the event and evaluation point to the other member and accepts the correction / confirmation response of the evaluation point . When the correction of the evaluation point is accepted, the average value of both is calculated and registered in the couple registration DB 13. Both input points may be added and registered. In addition, when an event is input from a member, an event can be generated by using the timer function / calendar function built into the computer system to determine the member's birthday or anniversary date (1st anniversary, 1 month) This includes the case of automatically recognizing the arrival of a memorial etc.). In this case, the event evaluation points extracted from the point table 12 are transmitted to both members, and a correction / confirmation response is accepted. Note that, from the viewpoint of collecting statistical data, it is preferable to register the points inputted separately from the average value and the total value in association with the attribute of each member. Thereby, the data which can grasp | ascertain the difference of the evaluation of the woman and man with respect to the same event can be accumulated.

  As shown in FIG. 1, the registration inquiry processing unit 24 obtains identification information such as a mobile phone number and an address of another member from the registration inquiry member 7 through the mobile phone 8, and accepts an inquiry as to whether or not a couple is registered. In this case, the member information master file 10 and the couple registration DB 13 are referred to and searched for whether or not the member to be referred is registered as a couple. In response to this inquiry, from the viewpoint of protecting personal information and preventing troubles between members, it is preferable not to include information on other members registered as a couple. On the other hand, the event evaluation points of the couple are also presented. In this way, it is possible to provide useful reference information indicating the dating period and intimacy. That is, the registered inquiring member 7 can determine the possibility of new association with the inquired member with reference to the presented points.

  For example, when the event evaluation points and the dating record are not input for more than a predetermined period (for example, one month) from any member registered as a couple, the database update unit 25 sends the data transmission unit 26 the target member Issue a command to notify the mail address of the final confirmation message. When a response to delete the couple registration is received or when a predetermined period (for example, one week) has passed since the notification, the couple is considered to have “naturally disappeared” and the couple registration is deleted. Even in this case, the couple's dating record is stored in association with the attribute information. This makes it possible to collect useful dating data that matches the actual dating situation.

  The data totaling unit 27 includes at least member attributes, group types, individual events (events that occur irregularly such as dates and trips), and regular events (such as various anniversary dates that occur annually and monthly at a predetermined cycle). It is preferable to count the evaluation points for each of them. Thereby, for example, statistical data in which the age difference between couples, the dating period, two constellations, the ratio of dating on the anniversary day (regular event), the contents of dating, and the like can be collected. Further, it is preferable that the data totaling unit 27 performs totaling by performing predetermined weighting for each event type. As a result, for example, evaluation points for daily events such as dates and telephone calls can be aggregated as they are, and irregular event points such as trips can be aggregated by multiplying by a predetermined coefficient (× 1.2, etc.). In the case of long-distance romance even on the same date (two or more couples' prefectures are separated, travel time by public transport is 3 hours or more, or transportation cost is 10,000 yen or more, etc.) Data can be aggregated by multiplying by the coefficient of. In this way, by counting points in association with member attributes, event types, etc., points can be counted and analyzed from various viewpoints such as age group, season, anniversary, dating period, compatibility by two constellations, etc. become able to. Such information is extremely useful and highly useful in marketing and generational trend analysis.

  In addition, the data is aggregated regularly according to preset search conditions. For example, a specific company or the like is given access authority to the couple registration DB 13, and the search conditions are received from this company each time by SQL and irregularly. You may make it total. In this case, the access authority and authentication information for each company are stored in the member information master file 10, and when the application receiving unit 20 receives an aggregation request from this company, the authentication unit 21 stores the member information master file 10. Refer to authority authentication. When authority authentication is affirmative, the data transmission unit 26 transmits the data aggregated based on the search condition by the data aggregation unit 27 to the application company.

  Each functional unit described above is actually a computer software program installed in a computer system (server) or a subroutine in one program. Each function of the present invention is achieved by being called and executed on the RAM by the central processing unit (CPU) of the computer system.

  (Member registration processing flow)

  Next, a processing flow for new member registration will be briefly described with reference to FIG. S1 to S7 shown in FIG. 1 correspond to the following processing steps.

  First, the registration application member 3 (applicant) inputs the member registration email address of the management center 2 or clicks the hyperlink of the member registration email address on the WEB site of the system 1 to the system 1. An empty mail is transmitted (S1). The mail address and identification ID of the mobile phone 4 of the applicant 3 are automatically recognized from the blank mail received by the application reception unit 20 and stored in the temporary data table 11 (S2).

  Next, the data transmission unit 26 generates a reply mail displaying the URL of the member registration screen and transmits it to the mail address of the mobile phone 4 of the applicant 3 (S3). When the applicant 3 clicks the URL displayed in the reply mail, the application reception unit 20 acquires the mobile phone identification ID (access ID) again, and the authentication unit 21 refers to the information stored in the temporary data table 11. The applicant 3 is authenticated (S4). If the authentication is valid, the application receiving unit 20 displays a member registration page and accepts input of necessary information such as the name of the applicant 3 (S5). Thereafter, the input information and the mail address and identification ID of the mobile phone stored in the temporary data table 11 are registered in the member information master file 10 (S6) and stored in the temporary data table 11. The information is deleted (S7). This completes member registration.

  (Processing procedure)

  Next, the processing procedure of the present invention and the above-described functional units will be described in detail with reference to the flowcharts of FIGS. 4 is a flowchart for couple registration, FIG. 5 is a flowchart for evaluation point registration, and FIG. 6 is a flowchart for registration inquiry.

  (Couple registration procedure)

  First, the couple registration processing procedure of FIG. 4 will be described. In this process, first, when the registered application member 3 uses the mobile phone 4 to access the couple registration screen of the present system 1 (step S10), the application receiving unit 20 identifies the mobile phone 4 from the access information. The ID is extracted and transferred to the authentication unit 21. The authentication unit 21 performs member authentication and personal authentication based on the acquired mobile phone identification ID (steps S11 to S13). In the member authentication, it is determined whether the member is a member based on whether the mobile phone identification ID is registered in the member information master file 10. Also, in the personal authentication, it is determined whether or not the registration application member 3 is registered as a couple by referring to the couple registration DB 13. If the member is not registered (No in step S11), the process proceeds to the member registration flow described in FIG. 1 (step S13). If the couple is registered (Yes in step S12), the data transmission unit 26 generates a reply mail including a message “Duplicate couple registration is not possible” and sends it to the address of the registered member 3 (Step S14).

  If both member authentication and personal authentication are positive (Yes in step S11, No in S12), the application reception unit 20 displays a couple registration screen on the mobile phone of the registered application member 3 and is necessary for registration. The input of correct information is accepted (step S15). Specifically, it accepts the input of specific information such as the mobile phone number and name of the lover who is the subject of registration. The application reception unit 20 passes the input information to the authentication unit 21 and performs the member authentication and personal authentication of the registration target person in the same manner as the registration applicant (steps S16 and S17). The authentication unit 21 first performs member authentication with reference to the acquired information and the information in the member information master file 10 (Yes in step S16). If this authentication is positive, the couple is not registered. Such personal authentication is performed (step S17).

  When the member authentication of the person to be registered is negative (member registration is not registered) (No in step S16), the data transmission unit 26 indicates that “the couple registration partner is not registered as a member. If you wish, please notify us of your e-mail address "and send it to the registered member 3 (step S18). When the e-mail address of the registration partner is acquired from the registered application member 3, the data transmission unit 26 transmits a message to the address indicating that the registration target person is requested to register as a member and that the registration applicant has applied for couple registration. (Step S19).

  When the application reception unit 20 receives an application for member registration from a person to be registered within a predetermined period (three days or the like) (Yes in step S20), the application registration unit 20 performs the member registration process shown in FIG. This is performed (step S21). In other words, in this case, it is determined that the intention to desire member registration is consent for couple registration with the registered member 3. On the other hand, if the registration receiving unit 20 does not accept the application for membership registration from the registration target person within the predetermined period (No in step S20, Yes in S22), the data transmission unit 26 indicates that “the registration target person is with you. The standard message “It seems that the couple registration is not desired” is transmitted to the e-mail address of the registration applicant 3 (step S23). If the personal authentication of the member to be registered is negative (couple registration is performed) in step S17, the process proceeds to step S14 and a standard message is transmitted.

  If both authentications are positive (Yes in step S16, No in S17), the couple registration processing unit 22 mainly performs the following couple registration process. That is, the couple registration processing unit 22 searches the member information master file 10 for the e-mail address and the mobile phone identification ID of the member 5 to be registered (step S24), and passes the e-mail address to the data transmission unit 26. The data transmission unit 26 generates an application mail displaying the URL of the couple registration page and transmits it to this address (step S25). At this time, the cellular phone identification IDs of the registration application member 3 and the registration target member 5 are stored in the temporary data table 11 (step S26).

  Next, when the registration target member 5 clicks the URL on the couple registration page within a predetermined application period (such as 3 days) (Yes in step S27), the registration reception unit 20 passes the access information to the authentication unit 21 and accesses Personal authentication is performed by matching the ID with the ID registered in the temporary data table 11 (step S28). If the authentication is positive, the couple registration page is displayed and input of information necessary for couple registration is accepted (step S29).

  When all the information is input, the couple registration processing unit 22 generates and inputs a couple identification ID based on the membership number of the registered applicant member 3 and the member 5 to be registered or information (initial etc.) designated by the member. The registered information is registered in the couple registration DB 13 together with the information (step S30). Thereby, couple registration is completed.

  On the other hand, if there is no application for couple registration from the registration target member 5 within the application period (No in step S27), the process proceeds to step S23 and a standard message is transmitted. Finally, the information stored in the temporary data table 11 is deleted, and this process is terminated (step S31).

  (Event registration / evaluation point registration procedure)

  Next, the event registration / evaluation point registration processing procedure shown in FIG. 5 will be described. In this process, first, when one member 3 who has been registered as a couple applies for registration by clicking the “2. Event registration / point registration” button 40 on the member-dedicated page (see FIG. 3) (step S40). The registration receiving unit 20 extracts the mobile phone identification ID from the access information and delivers it to the authentication unit 21 to perform member authentication and couple authentication (whether the couple is registered) (step S41).

  When both authentications are valid, the dating record update unit 23 searches the member information master file 10 for the email address of the other member who is registered as a couple, and the temporary data table 11 together with the mobile phone identification ID of the applicant member. (Step S42). In addition, the registration receiving unit 20 receives an input by presenting an input screen for the type of event and the date / point of occurrence (step S43). Events registered in the point table 12 can be selected from a pull-down menu, and any other event can be input. When a registered event is selected, the dating record update unit 23 searches the point table 12 for the basic evaluation point and the addition / subtraction point of the event and displays them on the input screen. As described above, this basic evaluation point can be corrected by the member within a predetermined range.

  When an event and a point are input, the dating record update unit 23 extracts the mail address of the other member from the temporary data table 11 and passes it to the data transmission unit 26. The data transmission unit 26 generates a mail that prompts the user to input points regarding the accepted event, and transmits the mail to this address (step S44).

  When a point input (same point, correction point) is received from the other member within a predetermined point reception period (24 hours, etc.) (Yes in step S45), the dating record update unit 23 calculates the average value of the two points. Calculate and register in the couple registration DB 13 (step S46). If no point is input within the point reception period (No in step S45, Yes in S47), it is determined that 0 points have been input (step S48), and an average value is calculated (step S46). Finally, the information stored in the temporary data table 11 is deleted and this process is terminated (step S49).

  (Processing procedure for couple registration inquiry)

  Finally, with reference to FIG. 6, a processing procedure when an inquiry as to whether another member (member to be inquired) is registered as a couple from one member (registration inquiry member 7) will be described.

  First, the application reception unit 20 receives an inquiry from the registered inquiry member 7, extracts the mobile phone identification ID of the member 7, and causes the authentication unit 21 to perform member authentication (steps S50 and S51). If not registered, the process proceeds to the member registration process of FIG. 1 (step S52). If the member authentication is valid, the registration inquiry processing unit 24 displays an inquiry screen on the mobile phone 8 of the registered inquiry member 7 and accepts input of member identification information such as the mobile phone number, e-mail address, and name of the member to be inquired ( Step S53). The registration inquiry processing unit 24 searches the member information master file 10 and the couple registration DB 13 for the relevant person based on the input member identification information, and whether the registered member is registered as a couple and whether the registration continues. It is determined whether the registration has been deleted (steps S54 to S56). When the couple registration is continued (No in step S56), the registration inquiry processing unit 24 searches the couple registration DB 13 for the accumulated points of the couple and calculates the number of days elapsed since the latest point registration date (step). S57, S58). These pieces of information are useful reference information indicating the closeness of the couple and the possibility of canceling the couple registration. Then, the data transmission unit 26 generates these information and a message “Mr. XX is registered as a couple” and transmits it to the address of the registered inquiry member 7 (step S59).

  If the corresponding person cannot be searched in step S54, the data transmitting unit 26 generates a message “No corresponding person found” and transmits it to the address of the registered inquiry member 7 (step S60). Also, if the couple is not registered or if the registration has already been canceled (No in step SS55, No in S56), a message “Registered member is not registered” is generated. 7 is sent to the address (step S61). If the registered reference member 7 wishes to register a couple with the member to be referred (Yes in step S62), the process proceeds to the couple registration flow (step S24) in FIG.

  (Effect of embodiment)

  According to the above-described configuration of the present embodiment, since the members registered as couples accumulate the points at which the event is evaluated, it is possible to accumulate and present useful indicators representing the intimacy of the couple to the parties. In this way, since the parties can register different evaluation points for each event, it is possible to give a sufficient incentive to continue event and point registration and couple registration. Further, since the points are registered in association with the event or member attribute information, the points can be totaled for each of various attributes, and statistical data with high utility value can be obtained.

  Further, duplicate registration can be prevented beforehand by performing member authentication and personal authentication based on the mobile phone identification ID. As a result, the reliability and validity of couple registration can be expected to be maintained and improved.

  That is, the couple registration, online marriage registration, and dating game machines described above as the prior art allow one person to dating (marriage) with a plurality of opponents. For example, when a couple is registered in Non-Patent Document 1, personal authentication is merely performed using a mail address of a mobile phone, and a person who has a plurality of addresses can use them separately to register with a plurality of persons. Patent Document 1 also proposes to own and use a game machine for each of the favorite and the spare (0053 etc.).

  For this reason, even a couple who has registered a romantic relationship using the conventional mechanism cannot completely eliminate the suspicion that the other party is bifurcated. Further, even if a proof is obtained by checking whether or not the other party has registered other couples using these mechanisms, it is not reliable. After all, the conventional mechanism only registers love (marriage) as a play, and just provides an unfavorable social system for young people as well as “dating sites”.

  On the other hand, in the configuration of the present embodiment, the above problem can be solved by performing a couple registration after performing personal authentication with an identification ID set at the time of contracting a mobile phone, not an ID that can be arbitrarily set / changed by a member. Can be solved.

  (Modification)

  In addition, this invention is not limited to said embodiment, A various deformation | transformation is possible in the range which does not change the summary of invention.

  For example, in the above-described embodiment, couple registration has been described as an example, but the present invention can be similarly applied to other group registrations (circles, alumni associations, friends, companies, workplaces, etc.). In this case, the event type, basic evaluation points, etc. are set according to the group attributes.

  In addition, the mobile phone identification ID is exemplified for member authentication and personal authentication. However, the identification information is not limited to this as long as it is identification information that can identify an individual. For example, biometrics such as iris and fingerprint, and random numbers of cards issued to members are used. You can also

  Furthermore, the owner or the pet can become a member, and a group of pets can be registered. For example, in addition to the Kennel Club breed registration, a parent / child / brother relationship is registered, or a group registration is made for the same dog breed in the vicinity. In these cases as well, related members (pets or owners) will register and accumulate points when events such as owners interact (off-off events or competitions) or common parent dog birthdays occur. . As a result, even hybrids that cannot be registered can be registered, and the accumulated points serve as an objective indicator of the activity status of the group.

It is a figure which shows schematic structure of the whole network structure and member information management system of this embodiment. It is a conceptual diagram which shows an example of the data stored in a point table. It is a figure which shows the example of the menu screen displayed on a member's mobile phone. FIG. 4 is a flowchart showing a processing procedure at the time of couple registration. FIG. 5 is a flowchart showing a processing procedure at the time of evaluation point registration. FIG. 6 is a flowchart showing a processing procedure at the time of registration inquiry.

Explanation of symbols

1 ... Member information management system 2 ... Management center 3 ... Registration application member (first member)
4, 6, 8 ... mobile phone 5 ... registered member (second member)
7… Registration inquiry member (third member)
9 ... Point input terminal 10 ... Member information master file 11 ... Temporary data table 12 ... Point table 13 ... Couple registration database (DB)
DESCRIPTION OF SYMBOLS 20 ... Application reception part 21 ... Authentication part 22 ... Couple registration process part 23 ... Relationship record update part 24 ... Registration inquiry process part 25 ... DB update part 26 ... Data transmission part 27 ... Data total part

Claims (14)

A member information management system for managing member information input from a terminal by a server in which a plurality of terminals are connected to the network,
The server
Member information storage means for registering the personal identification information of a plurality of members acquired through the terminal and the identification information of the group to which these members belong,
When a predetermined event related to at least two members belonging to the group occurs, evaluation point receiving means for acquiring evaluation points of the event from terminals of a plurality of members who are parties;
A member information management system comprising: evaluation point storage means for registering evaluation points received from said party members in association with event types and group identification information. The member information management system according to claim 1,
The server further acquires personal identification information of the member who desires group registration and personal identification information of one or more other members that the member desires to register in the group to which the member belongs. A member information management system comprising group registration acceptance means for accepting application for group registration. The member information management system according to claim 2,
The server further includes:
If the registration applicant accepts an application for registration as a group in which the person to be registered, who is a lover, a fiancee or a spouse (hereinafter collectively referred to as “lover”), receives a registration application, And a romance registration availability determination means for searching the group DB based on personal identification information of the person to be registered and determining whether or not a romance relationship is already registered for at least one of them. A unique member information management system. The member information management system according to claim 1,
The evaluation point receiving means of the server adds all the points input from a plurality of members, or calculates an average value of all the points,
The evaluation point storage means is for registering the points of the sum value or the average value. The member information management system according to claim 1,
The server further includes a point table in which event types and evaluation points are described in association with each other.
The member information management system, wherein the evaluation point receiving means of the server automatically acquires points with reference to a point table when the event occurs. The member information management system according to claim 5,
The point table describes a correction coefficient for adding or subtracting a basic evaluation point and a basic evaluation point in relation to a specific event. The member information management system according to claim 1,
The server further comprises a counting unit that counts a part or all of the accumulated member points at predetermined intervals for each member attribute or group type. The member information management system according to claim 7,
The events include individual events that occur individually in relation to a plurality of members belonging to the group, and periodic events that occur annually and monthly at a predetermined cycle,
The member information management system, wherein the tabulating means tabulates evaluation points for each of at least one of a member attribute, group type, individual event, and periodic event. The member information management system according to claim 7,
The membership means is a member information management system characterized in that the event type associated with the evaluation points is aggregated by performing predetermined weighting. The member information management system according to claim 1,
The server further comprises inquiry reception processing means for acquiring personal identification information of another member from the member and receiving an inquiry as to whether the other member is registered as a group. system. The member information management system according to claim 1,
The terminal is installed in a predetermined event facility such as a sightseeing spot, a restaurant, a hotel, a hall, or a sports facility,
The member information management system, wherein the evaluation point receiving means of the server acquires the evaluation point inputted by the member from the terminal together with the identification information of the event facility. The member information management system according to claim 1,
The server further includes:
Group information registration means for registering event information related to the group acquired from any group registered member together with the registration date;
Member information comprising: a group information registration unit that searches for a group information at a predetermined period, and a group deletion unit that cancels the registration of the group for which a predetermined period has elapsed since the previous event information registration date Management system. The member information management system according to claim 12,
The evaluation point storage means of the server is for registering the date of registration of the evaluation point,
The member deregistration means is for deregistering a group for which a predetermined period has elapsed from the registration date of the previous event or evaluation point. A member information management method for managing member information input from a terminal by a server in which a plurality of terminals are connected to a network,
The server is
A member information storage step of registering in a database the personal identification information of a plurality of members acquired through the terminal and the identification information of the group to which these members belong;
An evaluation point receiving step of acquiring evaluation points of the event from terminals of a plurality of members who are parties when a predetermined event related to at least two members belonging to the group occurs;
A member information management method comprising: performing an evaluation point storing step of registering an evaluation point received from the party member in a database in association with an event type and group identification information.

Images