JP2002056000A - Web SERVER MANAGING FRIEND DATABASE BY MEMBER - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a Web server which manages a friend database by members accelerating communication between friends that members themselves have and making the operation of communities smooth. SOLUTION: A Web document 40 of a browsing permission application form for making others browse a friend database 11 of the user by exchanging HTTP requests and responses with member computers 20 is sent, information entered into the browsing permission application form is obtained, and a browsing permission list 12 generated on the basis of the information is stored and managed relatively to the member IDs of members. After the user is made to input a password by exchanging HTTP requests and responses with the user computer 25 and it is confirmed that the password is registered in the browsing permission list 12 of the specific member A, only friend records classified in a category in the friend database 11 that the member A has are enabled to be browsed according to the category information made to correspond to the password.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a Web server that stores and manages friend information of members belonging to a community on the Internet for each friend database and allows other users to browse under certain conditions. .

[0002]

2. Description of the Related Art In the Internet, which is very prosperous, there are a lot of virtual communities called "communities" in which like people gather in various categories. In this community, the majority of its members use email, chat, and communication tools such as electronic bulletin boards. Members use these communication tools to deepen friendship among members in the community or find new friends.

For example, in communication using an electronic bulletin board, a message such as "Recruiting club friends in Shibuya!" Is sent from a member computer connected to the Internet to a Web server that provides an electronic bulletin board service. . The web server receives this message and sends it to the W
Post publicly on eb. Another member views the message published on the web and returns various responses to the web server, for example, "Let's go together!"
Members recruit like-minded friends and experience various encounters by exchanging such messages via the Web server. In this way, information on friends in the community that are gradually collected for each member, for example, friend information such as friend names and their e-mail addresses, is managed by recording them in, for example, an address book on the Web provided by a Web server. .

[0004]

However, the above-mentioned address book on the Web is only allowed to be viewed by each member. For example, even if a friend of a member is allowed to view the friend information by the member,
Web of the friend's computer via the Internet
There was no way to access the server and browse the address book. This can be a major problem in the Internet community where active exchange of opinions and exchanges between members is preferable in terms of operation.

[0005] At the beginning of community operation, frequent exchanges are made among users with the help of unusualness, but if the exchange between users progresses to some extent, this exchange tends to stagnate. It is considered that this is due to the fact that each friend has been fixed, and exchanges outside the friend group do not progress.

SUMMARY OF THE INVENTION The present invention has been made in view of such a conventional problem, and promotes exchange between friends of each member and facilitates community operation, and manages a friend database for each member. Provides a server.

[0007]

The invention for achieving the above object is an invention specified by the following items (1) to (8). (1) An information processing system using a computer,
It communicates with an external computer via a network and
It functions as an eb server and provides information stored in the database as appropriate. (2) Perform member authentication based on the member ID by communicating with the accessing user computer. (3) A friend database for each member is managed in association with a member ID in an appropriate storage resource. (4) The friend database is composed of records for each friend, and each friend record includes personal information such as name, address, and contact information, and various information related to the relationship between the member and the friend. A large number of friends can be classified into a plurality of categories based on this. (5) An HTTP request / response is exchanged with the accessing member computer to allow the registered information of the friend database owned by the member to be browsed and to register, delete, and change the information in the friend database. (6) An HTTP request / response is exchanged with the accessing member computer, a Web document of a browsing permission application for allowing another person to browse the friend database owned by the member is transmitted, and the browsing permission application is transmitted to the member computer. Is obtained, and the browsing permission list created based on the information is stored and managed in association with the member ID of the member. (7) The browsing permission list is classified into a password for each person known to each person who is permitted to browse, and a category corresponding to each password among a plurality of friend records in the friend database. The category information indicating whether the friend record is permitted to be browsed is created as a set. (8) User computer and HTTP that accessed
A request / response is exchanged, the user is required to input the password, and after confirming that the password is registered in the browsing permission list of the specific member A, the password associated with the password is checked. Based on the category information, only the friend records classified into the corresponding category in the friend database owned by the member A are browsed.

[0008]

DESCRIPTION OF THE PREFERRED EMBODIMENTS === Basic Configuration of Network =
== FIG. 1 is a schematic diagram showing a network configuration including a Web server for managing a friend database according to the present invention. As the network, any network such as a LAN line can be adopted as appropriate, but the Internet is taken as an example here. Through the Internet, the Web server 10 and the member computer 20 and the user computer 25 used by an unspecified number of users are network-connected. The member computer 20 and the user computer 25 may be, for example, a mobile phone with an Internet connection function or a PDA (Personal Digital Assistance) in addition to a personal computer.
t), a TV with a Web browsing function, a game machine, or the like.

[0009] Here, the above member is a Web server 10
Means a registered member of the Internet community provided by. The Internet community is
It is a virtual community where like-minded people gather as members in various categories. In this community, the members deepen friendships or find new friends. Communities are provided mainly for each hobby and age group, and it is common to set a Web page as a common gateway to each community, that is, a portal site, and collectively manage people of various layers. .

[0010] The Web server 10 of the present invention is provided with various databases, and provides the member computer 20 and the user computer 25 accessed by specifying a URL with HTT.
Exchange P request / response. HTTP
(Hypertext Transfer Protocol) is a communication protocol for transmitting and receiving HTML documents between the Web server 10 and the client computer via the Internet. In the present embodiment, for example, first, the member computer 20 (client) transmits a URL (U
niform Resource Locators) to the Web server 10. On the other hand, the Web server 10 transmits the HTML document constituting the community site owned by the Web server 10 to the member computer 20.

By exchanging the HTTP request / response, for example, appropriate data transmission and reception such as screen data of a Web page for inputting / updating friend information are executed. In this way, the Web server 10 accumulates friend information and the like that each member desires to manage in a storage resource such as a hard disk. The friend information of the members taken into their own memory resources is managed for each member and updated as needed. The Web server 10 includes a friend database 11, a browsing permission list 12, and a member database 13 as databases for storing and managing member information and friend information desired to be managed by the member. Of course, these databases may be provided in separate storage devices connected to the network as separate databases, or may be combined as appropriate or provided collectively in one storage device.

The friend database 11 is a database for storing and managing friend information transmitted from the member computer 20 to the Web server 10 in association with a member ID of each member. The friend database 11 is, for example, a type of relational database, and manages a collection of data in the form of a relational table. The relation table here includes a friend ID, personal information such as a name, an address, an e-mail address, and attribute information as column elements, as shown as “friend database 11a of member A” in FIG. The information of each friend is associated as a row element, that is, a friend record, to form a data structure such as a list. In this case, the basic key that specifies each friend record is the friend ID described above.

The attribute information in the friend database 11 is various information relating to the relationship between the member and the friend.
There are various forms of relationships between individuals, such as friendships through hobbies, co-workers of a company, or even families. In the Internet community, there should be many opportunities for people to become friends through hobbies, and in this embodiment, it is assumed that this attribute information is classified according to hobbies. Therefore, “a, b,
Each alphabet of c,... is associated with a name of a hobby such as baseball, outdoor, fishing, etc. Whether or not each friend is related to this attribute information is determined by ""1" is shown, and "0" is shown when there is no relation.

When the member computer 20 accesses the friend database 11 storing friend information structured as described above, for example, SQL (Str) as a simple query language is used.
According to the uctured Query Language, an operation such as data search can be performed by inputting a column element such as the friend ID and the attribute information. Therefore, each friend can be classified into a plurality of categories.

The browsing permission list 12 includes a password for each person known to each member who is permitted to view the member, and an attribute of a number of friend records in the friend database 11 to the person corresponding to each password. Is created as a set of category information indicating whether browsing of a friend record classified as is permitted. It is stored and managed in association with the member ID for each member. Again, the data is managed in the form of a relation table as in the friend database 11 described above. In the figure, it is illustrated as a relation table 12a between the password and the category information corresponding to the password. The member database 13 is a database that stores and manages information of members registered as users in the Internet community. The personal information of the member is stored in association with the member ID.

=== Operation Procedure === The Web server 10 that manages the friend database 11
A procedure for storing and managing friend information sent from the member computer 20 in the friend database 11 and allowing other users to browse the information under certain conditions will be described below. FIG. 2 shows the W of the present invention.
FIG. 3 is a flowchart showing an example of an operation procedure of the eb server, and FIG. 3 is an explanatory diagram showing an example of a friend record input / update screen. The web server 10 provides the member computer 20 that has accessed the web server 10 by specifying the URL,
The member authentication screen data (form) including entry fields for the member ID and the password for login is transmitted. Member ID
The Web server 10 that has obtained the password and the password from the member authentication screen data refers to the member ID and the corresponding password in the member ID table 13a and the member password table 13b of the member database 13.

As a result of the inquiry, if the member authentication is completed,
In response to the request of the member, a friend record input / update screen 30 for performing new registration or update of friend information in the friend database 11 is transmitted to the member computer 20. The screen 30 includes a member ID column 31, a password column 32, and a process selection column 33 for selecting processes such as addition, change, deletion, and confirmation of friend information. Here, for example, if "add new friend" is selected from the pull-down menu, a message prompting a new input as shown in the figure "Tell me about new friends" is displayed.
On the other hand, when changing or deleting friend information is specified, a message such as "Please specify the friend ID of the record to be changed (deleted) or its range" is displayed.
When "confirm friend information" is selected, the member can browse a friend record by designating a browsing range in the friend's own database 11.

When a new registration of friend information is performed, a screen 30
Is a friend ID column 34 for entering the ID of a friend to be newly added to the friend database 11, its name column 34a, and address column 3.
5, a contact column 36, an age group column 37, a gender column 38, and the like are displayed. The information entered in these columns is the personal information of each friend. Further, in this embodiment in which the relationship between members and friends is captured as a hobby, a hobby column 39 is provided.
Specify hobbies related to friends. Further, an intimacy column 39a for specifying the intimacy between the member and the friend is also provided. The information entered in the hobby column 39 and the intimacy column 39a is attribute information. The Web server 10 obtains the information entered in each of the above fields from the screen data returned from the member computer 20, and creates a friend record for each friend.
The friend records are sequentially added and stored in a columnar data structure in the friend database 11.

The friend record sequentially stored in the friend database 11 for each member is used not only by the member himself, but also in the present invention, another person is given the opportunity to browse and use the member record with the permission of the member. ing. FIG. 4 is an explanatory diagram showing an example of a screen of a browsing permission application, and FIG. 5 is an explanatory diagram showing an example of a browsing screen of a friend record. One member, “kaor
It is assumed that "un75" is requested by the acquaintance to view the friend record stored in the friend database 11, and the friend is accepted. When instructed, FIG. 4
Is returned from the Web server 10.

This screen 40 includes a member ID column 41, a password column 42, and a process selection column 43. For example, when “add password” is selected in the process selection field 43, a new password and category information corresponding to the new password are added to the browse permission list 12 as a record of the password. In this case, in addition to the above-mentioned columns, a new password is given, that is, a friend ID column 44, a name column 44a, a contact address column 45, and a category information column 46 for designating a viewing permission range are set.
Displayed on screen 40. The Web server 10 receives from the member computer 20 the screen 40 of the browsing permission application in which the required items are entered in each column. At this time, the Web server 10 acquires entry information for each of the filled-in columns. Then, it is stored in the browsing permission list 12. Of course, when storing the password, a password is automatically generated, and the permissible viewing range corresponding to the password is determined from the category information and is associated with each other.

[0021] The person (user) who has obtained the viewing permission from the member is
The password is obtained through an appropriate route such as e-mail or fax from the member or the Web server 10, or telephone or verbal communication. Then, when the user browses the friend record in the friend database 11, the user computer 25 is made to access the Web server 10. The Web server 10 exchanges HTTP requests / responses with the accessing user computer 25 and delivers appropriate authentication screen data and the like. The user inputs the password on the screen, and authenticates that the password is registered in the browsing permission list 12 of a specific member (in this case, a member having a member ID of “kaorun75”).

With this authentication, after confirming that the user has been formally authorized to browse by the predetermined member, the user refers to the category information stored in the browse permission list 12 in association with the password. The browsing range indicated in the category information is designated by SQL, and only the friend records classified into the corresponding category in the friend database 12 owned by the member are extracted. In the friend record browsing screen 50 of FIG. 5, a certain user is authenticated by the password authentication as described above and is allowed to browse the friend record.
This shows a situation where a browseable category is selected.

As an example, the authenticated "2ru5 \ u $ 9" is shown in the password display field 51, and the member ID "kaorun75"
Are shown in the permitted member name column 52. Here, it is assumed that the user has selected “baseball” in the category selection field 53. Then, the friend record display column 54 displays “kaorun7
A friend record having the attribute information of "baseball" is selected from the friend records held by the member having the member ID of "5." The data is appropriately tabulated and displayed as the friend record browsing screen 50. It is delivered to the computer 25. Of course, the extraction of the friend record according to the category information from the friend database 11 may be an extraction in which a plurality of attributes are intertwined. A browsing permitted range such as "male over 40" may be set as category information.

[0024]

According to the present invention, each member can mutually refer to friend information (friend record) held in the friend database. This solves the conventional problem that, at the beginning of community operation, frequent exchanges between members are helped by the unusualness, but if the exchange between users progresses to a certain extent, this exchange tends to stagnate,
Active exchange and exchange of opinions among members in the Internet community are greatly promoted. Thus, it becomes possible to provide a Web server that manages a friend database for each member, which promotes interaction between friends held by the members and facilitates the operation of the community.

[Brief description of the drawings]

FIG. 1 is a schematic diagram showing a network configuration including a Web server of the present invention.

FIG. 2 is a flowchart showing an example of an operation procedure of a Web server of the present invention.

FIG. 3 is an explanatory diagram showing an example of a friend record input / update screen.

FIG. 4 is an explanatory diagram showing an example of a screen of a browsing permission application.

FIG. 5 is an explanatory diagram showing an example of a friend record browsing screen.

[Explanation of symbols]

 10 Web server 11 Friends database 12 Permission list 20 Member computer 25 User computer 40 Permission permission application screen (Web document)

Claims (1)

[Claims] 1. The invention specified by the following items (1) to (8). (1) An information processing system using a computer,
It communicates with an external computer via a network and
It functions as an eb server and provides information stored in the database as appropriate. (2) Perform member authentication based on the member ID by communicating with the accessing user computer. (3) A friend database for each member is managed in association with a member ID in an appropriate storage resource. (4) The friend database is composed of records for each friend, and each friend record includes personal information such as name, address, and contact information, and various information related to the relationship between the member and the friend. A large number of friends can be classified into a plurality of categories based on this. (5) An HTTP request / response is exchanged with the accessing member computer to allow the registered information of the friend database owned by the member to be browsed and to register, delete, and change the information in the friend database. (6) An HTTP request / response is exchanged with the accessing member computer, a Web document of a browsing permission application for allowing another person to browse the friend database owned by the member is transmitted, and the browsing permission application is transmitted to the member computer. Is obtained, and the browsing permission list created based on the information is stored and managed in association with the member ID of the member. (7) The browsing permission list is categorized into a password for each person known to each person who is permitted to browse and a category corresponding to each password among a large number of friend records in the friend database. The category information indicating whether the friend record is permitted to be browsed is created as a set. (8) User computer and HTTP that accessed
A request / response is exchanged, the user is required to input the password, and after confirming that the password is registered in the browsing permission list of the specific member A, the password associated with the password is checked. Based on the category information, only the friend records classified into the corresponding category in the friend database owned by the member A are browsed.