JP2002032492A - Dating support method, dating support device, recording medium recording dating support program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To introduce a person of the opposite or same sex who has interest similar to that of onesef. SOLUTION: A client 10 sends user identifier and sex data to an encounter assisting device 20 to register them. The encounter assisting device 20 analyzes the item browsing/purchase history of a user held in an item browsing/purchase history database 23, detects a user having inter-user correlation with the user, and generates and sends a relative user list to the client 10.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

TECHNICAL FIELD The present invention relates to a method for introducing to a user isomers or homosexuals of similar interest.

[0002]

2. Description of the Related Art Conventionally, evaluation of interest in books and movies (dislike,
MyBest, etc., which uses fireFly's collaborative filtering engine, which introduces those who like and loved each other.

[0003]

These are similar interests by inputting an evaluation of interest in an item (information or product) in advance or registering the genre of the item (information or product) in advance. People could be gathered, but could not be introduced without an interest rating or genre registration.

[0004] An object of the present invention is to provide a meeting support method, a meeting support device, and a meeting support system, in which a user registers a gender and a user identifier, and only accesses a designated site, thereby introducing similar or opposite sexes of similar interest. An object of the present invention is to provide a recording medium on which a support program is recorded.

[0005]

According to the present invention, a user registers his / her own user identifier and gender information in a meeting support device via a network in advance, and stores the user's items (information, merchandise, etc.). Based on the access history, groups with similar interests are found, and users with different genders or the same are introduced from among them.

[0006] The information serving as a source of meeting support is an access history of a user browsing information such as a search site, an electronic mall, and an EC site such as a book. The access history is collected from each site (of course, the own site). May be stored in the meeting support device. Instead of providing the access history, each site pays for providing the access history use fee or the encounter support service on its own site.

For example, searching for a book on a book sales site,
The access history of the browsing of the summary etc. is saved as a log of the WWW server. The information to be stored is, for example, “user identifier, information identifier, access date and time”.

FIG. 10 shows an outline of the present invention.

[0009] The user to whom the encounter information is to be delivered registers an encounter delivery request in advance. At the time of this registration, the user identifier and gender are registered.

When a user uses a search site that provides an access history (item browsing / purchase history) to an encounter support device, an EC site such as an electronic mall or a book, the access history is accumulated in each site. You.

[0011] The access history that the user has accessed is collected from each site. A site that provides an access history requires a give-and-take relationship, such as providing a usage fee for the access history and providing an encounter support service, and requires a contract act as a business partner in advance.

[0012] From the result of analyzing the access history, users with similar interests are extracted, and the names of people of the same or opposite sex are notified to the users.

For analysis of access history, Netperception
You can use collaborative filtering engines such as Firefly and Fire Fly, data mining, neural networks, etc. If you want to analyze only the access history, you should apply for the "recommended information introduction method and system"
It is better to use Japanese Patent Application No. 2000-209827. In this case, the analysis sequence is stopped when the user group is extracted.

After receiving this introduction, the user can send and receive messages using the user identifier as an index.
This technology is not new. Make the user identifier unique within the system. The user who has been introduced transmits the name and message of the other party to the meeting support device as a set. The encounter support device holds a user identifier and a message as a set, and transmits the message when the user with the specified user identifier accesses at a later date.

[0015] Messages can be mutually exchanged by this method.

The user pays a fixed amount or a fee for each number of referrals as a consideration for receiving the encounter referral service.

The company that operates the meeting support device pays an access history usage fee to a site or the like that has provided the access history as compensation. Alternatively, a meeting support service can be provided.

The present invention is characterized in that the data from which the correlation of the user for meeting support is detected is only the access history, and it is not necessary to specify conditions for detecting the correlation of information. . The user only registers the gender for identifying the opposite sex or the same gender, and the name as an identifier for exchanging messages with each other, and registers all information related to privacy and information about his / her preference. The feature is that there is no need.

An advantage of the present invention is that since the data from which the correlation is detected is only the access history, there is no need to perform an evaluation input or to register a genre classification for information in advance. By using the access history that changes, it is possible to detect correlation information that follows a change in the user's interest at that time.

In addition, information for analyzing the compatibility between people is often related to privacy, and the method of the present invention in which only the gender and the user identifier are input leaks the privacy of the user. There is no danger.

The present invention is effective not only for the Internet application but also for the distribution of correlated information based only on the access history in a media and network in which evaluation input is difficult, such as a digital interactive TV and an information home appliance. Become.

If the gender is not registered, the present invention can be applied to a friend introduction device that does not distinguish between men and women.

If not only the access history but also the personal interest is input, the partner to be introduced can be further narrowed down while following a dynamic change in interest.

There is often a security problem if only the user identifier of the user is used. This can be avoided by inputting a password together with the user identifier.

The user identifier is a unique identifier in the system. Apart from this, a unique user identifier in the system by means of a time stamp or the like is automatically stored in a terminal or the like by using a technology such as Cookie. By associating the names with the names, it is possible for the user not to input the names each time the service is used.

[0026]

Next, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a configuration diagram of an encounter support system according to an embodiment of the present invention.

This system comprises a client 10, an encounter support device 20, and an item browsing server 30.

The client 10 is a Web-accessible device such as a personal computer, a digital two-way TV, a mobile phone, or the like, and has a browser 11.

The browser 11 is an information access unit such as a Web browser for searching for an item, purchasing an item, and receiving an item recommendation. The dating support device 20 can be used as an input unit for performing a contract for delivery of the dating information and as an output unit for displaying the dating information. Absent. The item is information that can be browsed through the browser 11, stored in a basket or the like, purchased, and the like, information such as a product, an advertisement, a title of a web page, and the like, and an item identifier (such as a web URL or a product code). ID).

The item browsing server 30 includes a search server,
EC that allows you to browse and purchase products and information via the network
It is a server or the like and holds item browsing / purchasing item browsing / purchasing history. The item browsing / purchasing history is held in a format including information such as “user identifier, item ID, browsing date and time”, and means using a web server access history or means using a unique history holding means. There is. The user identifier is managed by the user management unit 27 of the meeting support device 20.

The meeting support device 20 includes the server engine 2
1, a web page 22, an item browsing / purchase history database 23, a browsed item group holding unit 24, a related user group holding unit 25, a billing management unit 26, a user management unit 27, and a control unit 28. The purchase / purchase history is periodically acquired from the item browsing server 30 and held in the item browsing / purchase database 23, the held item browsing / purchase history is analyzed, and the delivery of the encounter information is registered in the encounter support device 20. Delivery of meeting information to existing clients.

The server engine 21 has a URL (Uniform Resource
It receives an HTTP (Hyper Text Transport Protocol) request for accessing the Web page 22 identified by the "urte Locator", and provides the Web page 22 to various clients. The HTTP request can indicate that the client has performed a registration operation to request distribution of the encounter information, and can display the encounter information to the client.

The encounter information is information to extract user identifiers having different genders from a group of users having similar interests obtained as a result of analyzing the item browsing / purchasing history of the client, to make a list, and to provide the client with the list. It is.

Item browsing / purchase history database 23
Holds a browsing / purchase history acquired periodically from the item browsing server 30.

The browsed item group holding unit 24 holds a list of item IDs of items browsed / purchased by a client requesting delivery of encounter information.

The related user group holding unit 25 holds the browsed item group based on the item browse / purchase history browsed by the client requesting the delivery of the encounter information held in the browsed item group hold unit 24. A user who is browsing each item stored in the unit 24 is extracted, and a list of the user identifiers is stored. In addition, as a result of evaluating the held users, a list of user identifiers obtained as a result of narrowing down those that are interested in the client who wants to deliver the encounter information is held.

The user management unit 27 includes a user identifier, which is an identifier of the user, a keyword for identifying the user, a gender, a list of messages from other users, and a source of the message. Manage a list of user identifiers. When a client registers registration of encounter information for the first time, the client registers a user identifier that is an arbitrary character string as a user identifier for globally and uniquely identifying the client. The client may arbitrarily input the user identifier. If another user has already used the user identifier, the user is prompted to re-enter the user identifier, and the client repeats inputting the user identifier until the user identifier becomes unique in the system. The client submits its gender along with the user identifier. The user management unit 27 manages the user identifier and the gender, and as a result of analyzing the item browsing / purchasing history, a group of users (list of user identifiers) having similar interests to the client requesting the encounter information. ), Only users of different genders (user identifiers) can be extracted and sent to the client.

The billing management unit 26 manages the amount charged for delivery of encounter information. It manages a fixed amount or a pay-as-you-go price for each information delivery together with the user identifier.

The control section 28 controls each section.

Next, the operation of the present embodiment will be described.

1. Acquisition of item browsing / purchasing history (FIG. 2) 1) The item browsing server 30 is held in a format including information of item browsing / purchasing history (for example, “user identifier, item ID, browsing date and time”). Is transmitted to the encounter information device 20 periodically (step 101).

2) Upon receiving the item browsing / purchasing history from the item browsing server 30, the control unit 28 of the encounter support device 20 holds the item browsing / purchasing history in the item browsing / purchase database 23 (step 10).
2).

2. Registration of Delivery of Encounter Information and Registration of User Identifier (FIG. 3) 1) The client 10 uses the browser 11 to access the item browsing server 30 via a network such as the Internet to meet. Registration of information delivery and registration of a user identifier are performed (step 201).

2) The client 10 sends the use identifier, the keyword, the gender, and the billing type to the meeting support device 20 together with the meeting information delivery registration request (step 202). As the charging type, it is possible to select a flat-rate charging or a pay-as-you-go charging according to the information amount of the delivered meeting information.

3) The meeting support device includes 20 control units 28
Confirms that the transmitted user identifier is a globally unique identifier (step 203), and stores the user identifier and the keyword and gender received in 2) in the user management unit 27.
(Step 204), and when it is accessed by the client 10 thereafter, it is used to specify the client, and a meeting information delivery registration notification is returned to the client 10 (step 205).

4) Next, the control unit 2 of the meeting support device 20
8 records the charging type together with the user identifier in the charging management unit 26 (step 206). The billing type is a fixed-rate billing for each fixed period (for example, a fixed-rate billing for each month) or for each amount of information delivered.

5) The control unit 28 of the meeting support device 20
If the sent user identifier is used elsewhere,
This is notified by a user identifier registration rejection notice (step 207).

6) The client 10 which has received the user identifier registration rejection notification repeats the procedure of 2).

7) After receiving the information delivery registration notification, the client 10 inputs a keyword together with the user identifier registered in 2), thereby distributing encounter information,
A message can be sent to other users, and it is introduced as encounter information to other users with similar interests.

8) By using a function such as a cookie and storing the user identifier on the client side, the input of the user identifier and the keyword can be omitted.

3. Delivery and Charging of Encounter Information (FIG. 4) 1) The client 10 sends the encounter information delivery request and the user identifier and the keyword registered at the time of registration of the encounter information delivery. (Step 301).

2) The control unit 28 of the meeting support device 20 that has received the meeting information delivery request searches the use management unit 27,
It is confirmed that the received pair of the user identifier and the keyword was registered at the time of registration of the encounter information delivery (step 302).

3) In step 2), the control unit 28 of the meeting support apparatus 20 that has confirmed the validity of the pair of the usage identifier and the keyword,
According to the procedure shown in FIG. 5, a process of detecting a received user identifier and a user identifier having a correlation between users is performed (step 3).
03). The detection processing result is received as a related user list (a list of related user identifiers).

4) The control unit 28 of the encounter support device 20
Along with the meeting support information notification, the detected related user list is transmitted to the client 10 together with the meeting information delivery response (step 304).

5) Next, the control unit 2 of the meeting support device 20
8 sends the user identifier and the number of user identifiers included in the related user list received in 3) to the charging management unit 26 together with the delivery record request of the encounter information (step 30).
5).

6) The accounting management unit 26 records the number of user identifiers received in 5) and the number of user identifiers included in the related user list and the current date and time (step 306).

7) The client 10 that has received the encounter information delivery response displays the sent related user list on the browser 11
(Step 307).

4. Detection of Correlated User (FIG. 5) The details of the process of detecting the user identifier received in 3.4) and the user identifier correlated between the users are shown in FIG. 11 together with FIG. Here, the user identifier requesting the encounter information is referred to as a base user identifier to distinguish it from the user identifier to be introduced.

1) The control unit 28 of the meeting support device 20
From the item browsing / purchase history database 23, the client 10 browses / purchases the item browsing / purchasing history (related item group G1) using the base user identifier as a key, generates a browsing item list, and displays the browsing item. Write to the group holding unit 24 (step 401,
402).

In the present embodiment, the browse item list is represented by, for example, “item ID, number of browse / purchase, browse time, latest browse / purchase date”. Based on the acquired item browsing / purchasing history, the browsing / purchasing history for the same item is folded into the expression form by incrementing the number of browsing / purchasing and updating the latest browsing / purchasing date and time (same item ID) Is not recorded more than once).

2) Narrowing down the browsed item list The control unit 28 of the encounter support device 20 determines the items in the browsed item list held in the browsed item group holding unit 24 as “number of times the client has browsed / purchased”. Sort according to the most frequent order, the longest "time the client browsed", or the most recent "latest date and time when the client browsed / purchased", or sorted according to these three combined conditions. The remaining items are overwritten in the browsed item group holding unit 24 as a new browsed item list (step 403). Here, Ng1 is an arbitrary positive integer.

3) Extraction of the related user list The control unit 28 of the encounter support device 20 uses the item ID of each item of the browsed item list held in the browsed item group holding unit 24 as a key, The browsing / purchasing history is acquired from the item browsing / purchasing history database 23, a related user list of the related user G2 is generated, and written to the related user holding unit 25 (step 404). In the present embodiment, the related user list is represented by, for example, “user identifier, number of overlaps with the browsed item group”. The number of overlaps with the browsed item group is the number of items that are browsed / purchased by each client in the related user list and overlap with the items in the browsed item list held in the browsed item group holding unit 24. is there.

4) Refinement of Related User List The control unit 28 of the encounter support device 20 searches the client in the related user list held in the related user group holding unit 25 for the browse item in the related user list. Sorting is performed in descending order of the number of overlaps with the group, and the upper Ng2 is retained, and a related user group holding unit 25 is set as a new related user list.
Is overwritten (step 405). Here, Ng2 is an arbitrary positive integer.

5) Narrowing down by gender The control unit 28 of the encounter support device 20 includes a user management unit 27
To obtain the gender of the base user identifier and the gender of each user identifier in the related user list, leaving only the user identifier that is different from the gender of the base user identifier, and adding a new related user. It overwrites the related user group holding unit 25 as a list (step 406).

6) The related user list narrowed down in 5) is returned as the detection processing result of the detection processing of the user identifier correlated with the base user identifier shown in 3.3).

5. Message Registration (FIG. 5) The client 10 that has received the related user list together with the meeting information delivery response in 4. transmits the message to the client identified by the user identifier included in the related user list. A message can be sent (step 501).

1) The client 10 selects one user identifier from the related user list by operating the browser 11 (step 501). When choosing,
Input devices such as a mouse, a keyboard, a mouse pad, and an infrared controller can be used.

2) The client 10 inputs a message to the client identified by the user identifier selected in 1) using an input device such as a keyboard (step 502). The message is an arbitrary string.

3) The client 10 transmits the use identifier of the client 10, the user identifier to which the message is to be transmitted, and the message together with the message transmission request to the encounter support device 20 (step 50).
3).

4) The controller 28 of the meeting support device 20
Along with the message recording request, the sender's user identifier,
The user identifier and message of the transmission destination are stored in the user management unit 27.
(Step 505).

5) The user management unit 27 additionally records the received message in the message list of the user identifier corresponding to the received user identifier of the transmission destination (step 50).
5).

6. Message Delivery and Billing (FIG. 7) 1) The client 10 sends a user identifier and a keyword registered at the time of registration of encounter information delivery to the encounter support device 20 together with a message delivery request. (Step 601).

2) Upon receiving the message delivery request, the control unit 28 of the meeting support apparatus 20 confirms that the received pair of the user identifier and the keyword is the one registered at the time of registration of meeting information delivery (step). 602), the received user identifier and the keyword are transmitted to the user management unit 27 together with the message read request to read the message (step 603).

If it is already confirmed that the pair of the user identifier and the keyword is normal according to 3. or 5., the keyword can be omitted.

3) When the user management unit 27 confirms that the received user identifier and the keyword match the keyword stored together with the user identifier registered at the time of registration of the encounter information delivery, 5 The list of messages recorded by the .. and the list of user identifiers of the transmission source together with the message read response and the meeting support device 2
Return to 0 (step 604).

4) The control unit 28 of the encounter support device 20
The list of the message and the list of the user identifier of the transmission source are transmitted to the client 10 together with the message delivery response (step 605).

5) Next, the control unit 2 of the meeting support device 20
8 transmits the user identifier of the client together with the message delivery record request and the number of messages included in the message list transmitted in 4) to the accounting management unit 26 (step 606).

6) The accounting management unit 21 records the user identifier and the number of messages received in 5) and the current date and time (step 607).

7) Upon receiving the message delivery response, the client 10 displays a list of the transmitted messages and a list of the user identifier of the transmission source on the browser 11 (step 608).

8) The client 10 can also perform registration processing for returning a message to the transmission source client included in the user identifier list displayed in 7) by the procedure shown in 5).

8. Aggregation of Billing Information 1) The control unit 28 of the encounter support device 20 periodically (eg, every month) makes the billing management unit 26 3.6) or 6.
The accounting process is performed based on the accounting information recorded in 6) (step 701).

2) The control unit 28 of the meeting support device 20
The accounting processing request is sent to the accounting management unit 26 periodically (for example, every month) (step 702).

3) The charge management unit 26 reads out the charge type and the charge information sequentially for each client type.

4) When the charging type registered in 2.4) is the fixed-rate system, the charging management unit 26 checks that the delivery of the encounter information is performed regularly, and then sets the charging value as a charging amount. Integration is performed (step 704).

5) If the charging type registered in 2.4) is the metering system, the charging management unit 26 adds up the charging value of the number of encounter information deliveries and the number of message deliveries as a billing amount (step 705). By separately managing the accounting value for each delivery number of the encounter information and the accounting value for each message delivery number, different accounting can be performed. In addition, either one can be free.

The following can be considered as another embodiment of the present invention.

The network is not limited to the Internet. There are a digital interactive TV and an information home appliance network.

Clients include PCs, mobile phones, digital two-way TVs, information home appliances, word processors capable of two-way communication,
Game equipment capable of two-way communication, clock capable of two-way communication,
There are mobile communication terminals such as PDAs.

The input / output is not limited to the Web, and an electronic mail is used, and a delivery request of the encounter information, a user identifier, and the like are transmitted as an electronic mail document or as a title.
An email address may be used instead of the user identifier. Delivery of encounter information can also be sent as an e-mail document.

The display of the encounter information can be, for example, superimposed on the television screen and superimposed on the game display.

It is not necessary to limit the timing of delivery of meeting information when the client makes a meeting information delivery request. The meeting support device can automatically access and write to the storage device of the client periodically.

The message to be delivered can be not only a character string but also multimedia information such as images, pictures, sounds, and music.

When delivering encounter information, not only user identifiers but also multimedia information such as images, pictures, sounds, and music can be delivered / displayed as a list of related users, in addition to character strings.

There are various variations in the billing method.

The user to be introduced is not limited to the opposite sex, but may be the same sex, or may be both the same sex and the same sex.

FIG. 9 is another configuration diagram of the meeting support device 20 in FIG. 1. A communication device 61 is for communicating with the client 10 and the item browsing server 30. The browsing / purchase history database 62 stores the item browsing /
This corresponds to the purchase history database 23. The storage device 63 corresponds to the browsed item group holding unit 24, the related client group holding unit 25, and the user management unit 27 in FIG. The storage device 64 is a hard disk. The display device 65 is a display. Storage medium 66 is a floppy disk, CD
An encounter support program by the control unit 28 shown in FIGS. 2 to 8 is recorded on a ROM, a magneto-optical disk, or the like. The data processing device 67 includes a CPU and an interface, reads the encounter support program from the recording medium 66, and executes the program.

[0098]

As described above, according to the present invention,
The user can be provided with encounter information according to the user's interests and changes in interests at any time without the trouble of inputting evaluations and registering genre categories for prior information, and the privacy of users is leaked. Nothing to do.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of an encounter support system according to an embodiment of the present invention.

FIG. 2 is a flowchart of acquiring an item browsing / purchase history.

FIG. 3 is a flowchart of registration of delivery of encounter information and registration of a user identifier.

FIG. 4 is a flowchart of delivery and charging of encounter information.

FIG. 5 is a flowchart of detecting a correlated user.

FIG. 6 is a flowchart of message registration.

FIG. 7 is a flowchart of message delivery and billing.

FIG. 8 is a flowchart of counting of billing information.

9 is another configuration diagram of the encounter support device 20. FIG.

FIG. 10 is a diagram showing an outline of the present invention.

FIG. 11 is an explanatory diagram of creating a related user list.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 10 Client 11 Browser 20 Encounter support device 21 Server engine 22 Web page 23 Item browsing / purchase history database 24 Browsing item group holding unit 25 Related user group holding unit 26 Charge management unit 27 User management unit 28 Control unit 30 Item browsing server 61 communication device 62 browsing / purchase history database 63, 64 storage device 65 display device 66 recording medium 67 data processing device 101, 102, 2010 to 207, 301 to 307,
401 to 407, 501 to 505, 601 to 608, 7
01-705 steps

Claims (21)

[Claims] Claims 1. An item browsing / purchase history of a user is collected from each server and stored in an item browsing / purchase history database, and a user identifier transmitted by a user who wishes to deliver encounter information via a network is provided. Register the gender, analyze the item browsing / purchase history stored in the item browsing / purchase history database according to the encounter information delivery request from the user, and detect the user who has a correlation between the user and the user. A meeting support method for creating a related user list as a list of detected users, transmitting the related user list as meeting information to the user via a network, and performing a charging process for providing the meeting information. 2. When a user identifier and a gender are registered, a keyword transmitted from the user is further registered, and when a user having a correlation between users is detected, a pair of the user identifier and the keyword of the user is paired. The method according to claim 1, wherein the validity is confirmed. 3. Using the user identifier of the user who has requested delivery of the encounter information as a key, the item browsing / purchase history is acquired from the item browsing / purchase history database. Browse /
A browsed item list that is purchase information is created, the items in the browsed item list are sorted under predetermined conditions, and a top browsed Ng item (Ng1 is an arbitrary positive integer) is left as a new browsed item list. An item browsing / purchasing history is acquired from the item browsing / purchasing history database using the item ID of each item in the item list as a key, and a user identifier of another user other than the user concerned and the user browsing / purchasing. A related user list including the number of items in the browsed item list that overlaps with the related item list is created, and the users in the related user list are sorted according to predetermined conditions.
Leaving a list of related users (Ng2 is an arbitrary positive integer), and among the users in the related user list, only users having the same and / or different gender as the relevant user. 3. The method according to claim 1 or 2, wherein a list of related users is left to be transmitted to the user. 4. When a user who has received the related user list transmits his / her own user identifier, a message, and a user identifier of a user to which the message is to be transmitted, together with a message transmission request, Additionally recording the message in the message list of the destination user, transmitting the message list and the list of the user identifier of the transmission source to the user, and performing accounting processing for the transmission of the message list;
A method according to any one of claims 1 to 3. 5. The method according to claim 1, wherein the related user list is periodically transmitted to a user. 6. The method according to claim 1, wherein said users communicate over the Internet. 7. The method of claim 1, wherein the user communicates through a digital interactive TV. 8. The method according to claim 1, wherein the user communicates through an information home appliance network. 9. The method according to claim 1, wherein the user is a terminal capable of performing mobile communication. 10. The method according to claim 9, wherein the user is a mobile phone. 11. The method of claim 9, wherein said user is a digital interactive TV. 12. The method according to claim 9, wherein the user is an information appliance. 13. The method according to claim 9, wherein the user is a word processor capable of two-way communication. 14. The method according to claim 9, wherein said user is a communicable game machine. 15. The user is a communicable clock.
The method according to claim 9. 16. The method of claim 9, wherein said user is a PDA. 17. A user management unit that manages a user identifier, which is a user identifier, and a gender; an item browsing / purchasing history database that holds user browsing / purchasing histories obtained from various servers; Obtain the user's item browsing / purchase history from the various servers, hold the user's item browsing / purchase history in the browsing / purchase history database, and identify the user's own identifier and gender transmitted by the user who wants to deliver the encounter information via the network The user management unit analyzes the item browsing / purchase history stored in the item browsing / purchase history database in response to the encounter information delivery request from the user, and analyzes the correlation between the user and the user. A user is detected, a related user list that is a list of the detected users is created, and the relevant user is encountered via a network as encounter information. A control unit for transmitting Te met support apparatus having a charging management unit which executes a charging process for providing the meeting information. 18. The control unit, when registering a user identifier and gender, stores the transmitted keyword in the user management unit, and when detecting a user having a correlation between users, the control unit stores the keyword with the user identifier. Check the validity of keyword pairs,
The device according to claim 17. 19. A browsing item group holding unit that holds a browsing item list that is a list of item IDs of items browsed / purchased by a user who requests delivery of encounter information, and a browsing item group holding unit that holds the browsing item list. A related user group holding unit that holds a related user list that is a list of user identifiers of users who are browsing each item, wherein the control unit uses the user identifier as a key and A browsing item list of the user is created, written in the browsing item group holding unit, the items in the browsing item list held in the browsing item group holding unit are sorted according to predetermined conditions, and the top Ng1 items (Ng1) are sorted. Is overwritten in the browsed item group holding unit as a new browsed item list, and stored in the browsed item group storage unit. Using the item ID of each item in the browsed item list as a key, an item browse / purchase history is obtained from the item browse / purchase history database, and the user identifier and the user of the user identifier browsed / purchased. Among the items, a related user list including a number of items overlapping with the items in the browse item list held in the browse item group holding unit is generated, and the related user list is held in the related user group holding unit. Sort the users in the related user list held in the holding unit under predetermined conditions, and rank the top two Ng (Ng2 is an arbitrary positive integer)
Overwriting the related user group holding unit as a new related user list while leaving only the user identifiers different from and / or identical to the gender of the user, and as a new related user list, 19. The apparatus according to claim 17, wherein the related user group holding unit is overwritten, and the related user list thus narrowed down is transmitted to the user via the network. 20. The control unit, wherein the user who has received the related user list transmits, together with a message transmission request, a user identifier of the user, a message, and a usage identifier of a user to which the message is transmitted. When it comes
The message is additionally recorded in a message list of a destination user, and the message list and a list of user identifiers of a transmission source are transmitted to a user. The charging management unit charges the transmission of the message list. 20. Apparatus according to any one of claims 17 to 19, which performs processing. 21. A procedure for collecting a user's item browsing / purchasing history from each server and storing it in an item browsing / purchasing history database, and a user transmitted via a network by a user who wishes to deliver encounter information. Analyze the item browsing / purchasing history stored in the item browsing / purchasing history database according to the procedure for registering the identifier and gender and the meeting information delivery request from the user, and use the correlated user with the user. A related user list which is a list of detected users, and transmits the relevant user as encounter information via a network; anda procedure for performing a charging process for providing the encounter information. Recording medium for recording an encounter support program for causing a computer to execute the program.