JPWO2008126838A1 - Information / service providing system, information sharing system, and methods thereof - Google Patents

Abstract

It facilitates the setting and management of privacy protection for community participants, and provides a filter function for selecting the provider of information and services. As shown in FIG. 34 (A), a user for whom “sneak quinn” is set as the provision attribute cannot receive any information / service from any user regardless of participation or non-participation in the community. A user for whom “community only” is set can receive information and services only from users participating in the community. A user for whom “buddy only” is set can receive information and services only from users included in a preset list. Users who are set to “Public” can receive information and services provided by all users. By setting such attributes, filtering of information / service providers is performed.

Description

  The present invention provides information and services or information / service providing systems that provide any one of these (information / services) to a community in which one or more users participate, information among users belonging to the community, and the like. The present invention relates to an information sharing system to be shared and these methods.

Many companies and organizations operate their own websites on the Internet in order to send various information such as company information, sales promotion information, and advertisement information to an unspecified number of general consumers and customers.
General consumers, customers, etc. (users; users include natural persons and corporations and other organizations / organizations (natural persons and corporations are collectively referred to as “people”)) are personal computers (PC) From a terminal such as the above, a search engine or the like is used to connect to a web server (web page) in which desired information is present to issue a request, and the desired information is downloaded from the web server.
In such an information acquisition procedure, a user cannot obtain desired information unless he / she requests it. A system that distributes information in such a procedure is called a pull-type information distribution system.

In order for users to retrieve information that matches their interests and interests from a vast amount of information using a pull-type information distribution system, the user is forced to perform a very time-consuming and time-consuming work. It will be.
In the pull type information distribution system, even if the information is updated after the user obtains the information, the updated information cannot be obtained unless the user requests the information again. .

On the other hand, a system that distributes information by the reverse mechanism of a pull-type information distribution type system is called a push-type information distribution system. Since the server side unilaterally distributes information at a predetermined timing, the user can always obtain the latest information.
However, in order to use the push-type information distribution system, the user needs to activate client software on his / her PC, select a category (channel) of information of interest, and perform registration.

Therefore, the information provider cannot distribute information unless client software for push-type information distribution is distributed to users and installed in advance on the PC.
In addition, since it is necessary to distribute a large amount of information with the same content to the user's PC, the transmission bandwidth required for distribution increases, and the load on the network and the web server (push server) for push type information distribution is increased. It gets bigger.
In order to solve the problems of the push-type delivery system described above, in Patent Document 1, the information delivery side can narrow down the types of users and control the user's channel subscription start and subscription end. Disclosed is a push-type information distribution system in which the load on a push server is reduced and information can be distributed continuously and stably to a large number of users.
However, when the push-type information distribution system described above is generalized, it becomes necessary to protect good users from malicious information providers and information users.
JP 2003-150487 A

The present invention has been made from the background as described above, and can provide information and services to users efficiently or share information between users by push-type information distribution. An object is to provide an improved information / service providing system, an information sharing system, and a method thereof.
Another object of the present invention is to provide an improved information / service providing system, an information sharing system, and a method thereof that can protect good users from malicious information providers and information users. And

  In order to achieve the above-mentioned object, the first information / service providing system according to the present invention provides information and services to a community in which one or more users participate as a provider who is not participating in the community. Alternatively, an information / service providing system that provides any of these (hereinafter referred to as “information / service”), user profile information storage means (306) for storing user profile information including at least a plurality of user identifiers A community in which each identifier of the community is associated with at least an identifier of zero or more users belonging to the community, and a mode in which each user belonging to the community receives the provided information / service Community memorizing member information Included in the stored community member information for each user participating in the community based on bar information storage means (316), the stored user profile information, and the stored community member information And providing means (50) for providing information and services by the provider.

  The second information / service providing system according to the present invention is the information and / or service (hereinafter referred to as “information / service”) made to the first community in which one or more users each participate. A system for providing information / service to a user who wishes to provide information / service in response to a request for provision of information). Community profile information storage means (308) associating at least a dynamically created second community identifier with predetermined information / service provision modes, each of the community identifiers, and 0 belonging to the community A community that stores community member information at least associated with identifiers of more than one user Member information storage means (316), based on the stored community profile information and the stored community member information, a user requesting participation in the second community is sent to the predetermined community According to an information / service provision mode, the information processing apparatus includes provision means (50) for controlling whether or not the user who has requested to participate participates and providing information / service.

  The third information / service sharing system according to the present invention is an information sharing system for sharing information among users in a community in which one or more users each participate, and includes at least identifiers of a plurality of users. User profile information storage means (306) for storing user profile information, each of the community identifiers, an identifier of zero or more users belonging to the community, and each of the users belonging to the community share the information. Community member information storage means (316) for storing community member information associated with at least the mode of time, participation in the community based on the stored user profile information and the stored community member information User Between, in a manner that is included in the stored community member information, and a shared unit (50) to share information.

According to the information / service providing system, the information sharing system, and these methods according to the present invention, it is possible to efficiently provide information / service to users or share information between users by push type information distribution.
Further, according to the information / service providing system, the information sharing system, and these methods according to the present invention, good users can be protected from malicious information providers and information users.

It is a figure which illustrates the structure of the community information search system concerning this invention. It is a figure which illustrates the hardware constitutions of each cluster node, such as client PC shown in FIG. It is the 1st figure which illustrates the community shown by the community information used as the object of search by the community information search system shown in FIG. It is the 2nd figure which illustrates the community shown by community information used as a candidate for search by the community information search system shown in Drawing 1, and (A) is a community before the community shown in Drawing 3 is formed. The state of the user of an information search system is shown, (B) shows formation of the community shown in FIG. 3, (B) shows the change of the community shown in FIG. FIG. 6 is a third diagram illustrating a community indicated by community information to be searched by the community information search system shown in FIG. 1. It is a figure which illustrates the user profile information which the data access apparatus shown in FIG. 1 reads from a data access apparatus and an external profile information management apparatus or either of these according to the request | requirement from a client PC. It is a figure which illustrates community profile information. It is a figure which illustrates community list information. It is a figure which illustrates community member information. It is a figure which illustrates reverse lookup buddy list information. It is a figure which illustrates identification table information. It is a figure which illustrates the profile specification information memorize | stored and managed by the data access apparatus and profile specification information management apparatus which were shown in FIG. It is a figure which shows the reference relationship etc. of the information shown in FIGS. It is a figure which illustrates the profile information memorize | stored and managed by the data access apparatus shown in FIG. It is a figure which shows the structure of the profile information operation program run on the data access apparatus shown in FIG. It is a figure which shows the structure of the profile information search part shown in FIG. It is a figure which shows the process of the data access apparatus specific | specification part shown in FIG. It is a figure which shows the structure of the profile information storage part shown in FIG. It is a figure which shows the structure of the profile information deletion part shown in FIG. It is a figure which shows the structure of the profile specification information confirmation program which operate | moves on a data access apparatus. It is a figure which shows the structure of the profile specification information operation program 42 which operate | moves on a profile specification information management apparatus (FIG. 1). It is a figure which shows the structure of the profile information search program which operate | moves on an external profile information management apparatus (FIG. 1). It is a figure which shows the structure of the profile specification information operation program which operate | moves on management PC (FIG. 1). First part of first communication sequence illustrating operations (S10) of client PC, data access device, profile specification management device, external profile management device, policy server and service execution device in community information search system (FIG. 1) FIG. Second part of the first communication sequence illustrating the operations (S10) of the client PC, data access device, profile specification management device, external profile management device, policy server and service execution device in the community information search system (FIG. 1) FIG. Third part of the first communication sequence illustrating the operations (S10) of the client PC, data access device, profile specification management device, external profile management device, policy server, and service execution device in the community information search system (FIG. 1) FIG. Fourth part of the first communication sequence illustrating the operations (S10) of the client PC, data access device, profile specification management device, external profile management device, policy server, and service execution device in the community information search system (FIG. 1) FIG. The fifth part of the first communication sequence illustrating the operations (S10) of the client PC, data access device, profile specification management device, external profile management device, policy server, and service execution device in the community information search system (FIG. 1) FIG. FIG. 24B is a sequence diagram illustrating operations performed simultaneously when the data access device searches the profile specification information management device for profile specification information in response to a request from the client PC shown in FIG. 24A. FIG. 24A is a sequence diagram illustrating a process in which the data access device shown in FIG. 24A retrieves profile specification information (FIG. 12) from the profile specification information cache DB of the data access device or the profile specification information DB of the profile specification information management device. It is. It is a figure which illustrates matching with the memory | storage position of profile information, and the kind of profile information. FIG. 24B is a sequence diagram exemplifying operations performed simultaneously when a data access device searches for profile information for another data access device in response to a request from the client PC shown in FIG. 24A. FIG. 24B is a sequence diagram illustrating a process in which the data access device illustrated in FIG. 24A searches for profile information for another data access device. FIG. 25D is a sequence diagram illustrating operations performed simultaneously when the data access device searches the external profile information management device for profile information in response to a request from the client PC shown in FIG. 24D. FIG. 25D is a sequence diagram illustrating a process in which the data access device illustrated in FIG. 24D searches the external profile information management device for profile information. First part of second communication sequence illustrating operations (S20) of client PC, data access device, profile specification management device, external profile management device, policy server and service execution device in community information search system (FIG. 1) FIG. Second part of second communication sequence illustrating operations (S20) of client PC, data access device, profile specification management device, external profile management device, policy server and service execution device in community information search system (FIG. 1) FIG. Third part of second communication sequence illustrating operations (S20) of client PC, data access device, profile specification management device, external profile management device, policy server and service execution device in community information search system (FIG. 1) FIG. Fourth part of second communication sequence illustrating operations (S20) of client PC, data access device, profile specification management device, external profile management device, policy server and service execution device in community information search system (FIG. 1) FIG. The fifth part of the second communication sequence illustrating the operation (S20) of the client PC, data access device, profile specification management device, external profile management device, policy server, and service execution device in the community information search system (FIG. 1) FIG. First part of the third communication sequence illustrating the operations (S30) of the client PC, data access device, profile specification management device, external profile management device, policy server, and service execution device in the community information search system (FIG. 1) FIG. Second part of the third communication sequence illustrating the operations (S30) of the client PC, data access device, profile specification management device, external profile management device, policy server and service execution device in the community information search system (FIG. 1) FIG. Third part of the third communication sequence illustrating the operations (S30) of the client PC, data access device, profile specification management device, external profile management device, policy server and service execution device in the community information search system (FIG. 1) FIG. Fourth part of the third communication sequence illustrating the operation (S30) of the client PC, data access device, profile specification management device, external profile management device, policy server, and service execution device in the community information search system (FIG. 1) FIG. The fifth part of the third communication sequence illustrating the operations (S30) of the client PC, data access device, profile specification management device, external profile management device, policy server and service execution device in the community information search system (FIG. 1) FIG. FIG. 4A is a chart showing attributes used for control for information / service provision and information sharing to a community, and (A) shows a case where a user who does not participate in a community becomes an information / service provider, The provision attribute used for the control for providing information / service to the member is shown, and (B) shows what kind of user in the community dynamically generated in accordance with the offer of provision of information / service by the provider. The participation attribute for controlling whether or not to allow participation is shown, and (C) shows the sharing attribute for information sharing among the members of the community. It is a figure which illustrates provision of information and services from outside the community. It is a figure which illustrates participation in the community created dynamically. It is a figure which illustrates the information sharing in a community. It is a figure which shows the structure of the data access server program performed in the data access server shown in FIG. FIG. 35 is a flowchart showing a process (S52) for providing information / service from outside the community shown in FIG. FIG. 35 is a sequence diagram showing a control process (S40) for providing information / service from outside the community shown in FIG. 34 (A). It is a flowchart which shows the control processing (S54) for participation in the community created dynamically. It is a flowchart which shows the service session control process (S56) shown by FIG. It is a communication sequence figure showing control processing (S46) for participation in the community created dynamically. It is a flowchart which shows the control processing (S58) for information sharing. It is a communication sequence diagram which shows the control process (S60) for information sharing.

[Information and service provision system 1]
FIG. 1 is a diagram illustrating the configuration of an information / service providing system 1 according to the present invention.
As shown in FIG. 1, the information / service providing system 1 according to the present invention includes a company server 102-1 to 102-n, a management PC 104, a profile specification management device 12, an external profile management device 14-1 to 14-n, External profile information storage devices 15-1 to 15-n, policy servers 16-1 to 16-n, service execution devices 18-1 to 18-n, and client PCs 2-1 to 2-n used by users # 1 to #n (May be a mobile phone or a portable computer), data access devices 3-1 to 3-n, data access server 5, community-related data management device 7 and identifier management device 8 are connected to a mobile communication network, the Internet or a LAN (Local Area Network) or the like, and are configured to be communicably connected to each other.

The information / service providing system 1 creates and stores data (community information) indicating the community formed by the user by using these components, and stores the stored community information according to the request of the user or application (program). A search is performed, and the search result is used to provide various information and services or any one of them (information / service) and share information between users.
In the information / service providing system 1, the community-related data management device 7 uses various tables (association role (AR) tables) used by the data access server 5 to cache community information in the memory area. A T-node identifier (ID (Identifier)) table and an A-node identifier (ID) table; FIGS. 14 to 16) are created.
In addition, the data access devices 3-1 to 3-n and the external profile information management devices 14-1 to 14-n store and manage community information as a plurality of types of profile information in a distributed manner.
Further, the profile specification information management device 12 stores and manages information (profile specification information) related to community information (profile information).

In FIG. 1 and each of the following figures, n is an integer of 1 or more, and not all n are the same number.
Further, when any one of a plurality of possible components such as the company servers 102-1 to 102-n is indicated without being specified, it may be simply referred to as the company server 102.
In addition, in FIG. 1 and each of the following figures, components that can be the subject of communication and information processing, such as the company server 102, the profile specification management device 12, and the client PC 2, may be collectively referred to as cluster nodes.
Further, in the information / service providing system 1, any two or more cluster nodes can be appropriately integrated as long as there is no contradiction in function or the like.
In the following drawings, substantially the same components and processes are denoted by the same reference numerals.

FIG. 2 is a diagram illustrating a hardware configuration of each cluster node such as the client PC 2 shown in FIG.
As shown in FIG. 2, each cluster node of the information / service providing system 1 includes a cluster node main body 110 including a CPU 112 and a memory (memory area) 114, an input / output device 116 including a display device and a keyboard, and a recording device 118. And a communication device 122 used for communication with other cluster nodes.
That is, each cluster node of the information / service providing system 1 includes a hardware component as a computer capable of communicating with other cluster nodes.
An OS (not shown) is installed and executed on each cluster node of the information / service providing system 1.
Various programs installed in each cluster node are executed by specifically using the hardware of each cluster node via the OS.
The memory 114 is composed of a semiconductor memory (ROM, RAM, etc.).
The recording device 118 is, for example, a disk recording device such as a CD device, a DVD device, or an HDD device, and records and reproduces data on a recording medium 120 such as a CD, DVD, HD, and FD.
In general, the storage capacity of the memory 114 is smaller than the storage capacity of the recording device 118.
On the other hand, generally, the data transfer rate of data transferred between the CPU 112 and the memory 114 is higher than the data transfer rate of data transferred between the CPU 112 and the recording device 118.

[community]
Before explaining the details of the information / service providing system 1, first, a community will be explained for understanding.
FIG. 3 is a first diagram illustrating a community indicated by community information to be searched by the information / service providing system 1 shown in FIG.
For example, when the company server 102-1 shown in FIG. 1 manages the subscribers of the game magazine A published by the company / publisher X among the users of the information / service providing system 1, as shown in FIG. In addition, the subscribers # 1 to #n of the game magazine A form one community (game magazine A subscriber community).

4 is a second diagram illustrating the community indicated by the community information to be searched by the information / service providing system 1 shown in FIG. 1. FIG. 4A shows the community shown in FIG. The state of the user of the information / service providing system 1 before being formed is shown, (B) shows the formation of the community shown in FIG. 3, and (C) shows the derivation of the community shown in FIG.
As shown in FIG. 4A, before the publisher X manages the subscribers of the game magazine A by the company server 102, at least a community related to the subscribers of the game magazine A of the publisher X is formed. It has not been.
That is, in the information / service providing system 1, the user has no relationship with respect to the subscription of the game magazine A of the publisher X.

Next, as shown in FIGS. 3 and 4B, some of the users of the information / service provision system 1 become subscribers # 1 to #n of the game magazine A of the publisher X, and the publisher X However, when the subscribers are managed by the company server 102, in the information / service providing system 1, a community related to the subscribers of the game magazine A of the publisher X is formed.
Further, as shown in FIG. 4C, the game maker Y issues an advertisement message of the online game B to the community of the subscriber of the game magazine A.
In response to this advertisement, some of the subscribers of the game magazine A become online game participants # 1 to #n, and when the game maker Y manages the participants by the company server 102, the online game The community of participants in B is derived from the community of subscribers of publisher X's game magazine A.

When the game magazine A is suspended or the online game B service is terminated, the community of the game magazine A or the community of the participants of the online game B disappears, and the game magazine A subscription or online Regarding participation in the game B, the user of the information / service providing system 1 returns to an unrelated state as shown in FIG.
That is, as shown in FIGS. 4A to 4C, in the information / service providing system 1, various communities are formed, changed, derived from other communities, and further disappeared.

FIG. 5 is a third diagram illustrating a community indicated by community information to be searched by the information / service providing system 1 shown in FIG.
As shown in FIG. 5, each user of the information / service providing system 1 is a community of the game magazine A shown in FIGS. 3 and 4B and the online game B shown in FIG. Can be arbitrarily added to the community of the participants and the community of the subscribers of the other magazines C. Therefore, the members in the community in the information / service providing system 1 may overlap.

[Profile Information]
Hereinafter, profile information handled in the information / service providing system 1 will be described.
FIG. 6 is a diagram illustrating user profile information that the data access server 5 shown in FIG. 1 reads from the data access device 3 and / or the external profile information management device 14 in response to a request from the client PC 2. is there.
In the information / service providing system 1, the user profile information itself exists independently of the formation and deletion of the community, and the user profile information is identified by a path and becomes a search target.
As shown in FIG. 6, the user profile information includes a path and one or more attributes.
The path includes a combination of a profile name and a user ID (profile name and user ID will be described later).
In addition to these pieces of information, the path may include elements other than the profile name and user ID, such as attribute names included in the user profile information.

The profile name indicates the name of user profile information.
The user ID indicates a value for identifying the user.
The attribute is data constituting user profile information, and the user profile information includes one or more attributes.
Each attribute in the user profile information is identified by an attribute name and has an attribute value as a value.
The user profile information shown in FIG. 6 includes additional attributes such as a “name”, “age”, and “gender” attributes of a user, an “movie” attribute that the user likes, and “others”. Including attributes, each of which includes an attribute name and an attribute value.

FIG. 7 is a diagram illustrating community profile information.
FIG. 8 is a diagram illustrating community list information.
FIG. 9 is a diagram illustrating community member information.
FIG. 10 is a diagram illustrating reverse buddy list information.
FIG. 11 is a diagram illustrating identifier table information.
The community profile information, community list information, community member information, and reverse buddy list information shown in FIGS. 7 to 10 have the same configuration as the user profile information shown in FIG.
In response to a request from the client PC 2, the information is read from the data access device 3 and / or the external profile information management device 14 by the data access server 5 (FIG. 1).

When the community profile information is realized by a relationship table, one record corresponds to one community.
As shown in FIG. 7, community profile information includes a profile name and a community ID, and includes, as attributes, a name of the community, a date and time when the community was created, a creator of the community, and community member information.
One record of community list information corresponds to one user, and the community list information includes an ID list of a community to which each user belongs as an attribute.
Each community ID refers to a corresponding record in community profile information.
As shown in FIG. 8, the community list information includes a profile name and a user ID, and includes, as attributes, community IDs of all communities to which the user indicated by the user ID belongs.
The community member information is referred to by a pointer attribute included in the (record) of the community profile information, and one table thereof corresponds to one community, and each table stores user IDs and statuses of all users belonging to the community. Is done.
As shown in FIG. 9, the community member information includes a profile name and a community ID, and indicates the user IDs of all users belonging to the community and the status in the community (for example, online, offline, busy, etc.). Information) as an attribute.

One record of reverse lookup buddy list information corresponds to one user.
The reverse buddy list can be considered as one community, and the corresponding record of the reverse buddy list information is referred to by the user ID of the community list information.
As shown in FIG. 10, the reverse lookup buddy list information includes a profile name and a user ID, and includes user IDs of all users who are buddy of the user as attributes.
The reverse lookup buddy list is used to improve the efficiency and speed of the search.
As shown in FIG. 11, the identifier table information is stored in the identifier management device 8, and is represented as an identifier (for example, a character string) having a large amount of data used for communication between the information / service providing system 1 and the outside. SIP URI, etc.) and an identifier (for example, unsigned integer type (32 bits) data) with a small amount of data used in the information / service providing system 1 is used. In the providing system 1, it is used to uniquely identify a user.
The information shown in FIGS. 6 to 10 is created by, for example, the client PC 2 or the company server 102, and sent to and stored in the data access device 3 and the external profile management device 14.

For example, when there are 10 million users in the information / service providing system 1, the user profile information has a data amount of about 10 Gbytes for each type of profile (such as the preference information regarding the movie shown in FIG. 6). Expected to be.
In general, a user profile includes basic information (age, occupation, address, etc.) representing user characteristics, as well as preferences, matters of interest, interests, purposes, knowledge, etc., which are identified (distinguished). A profile type is used for this purpose.
The community profile information is expected to have a data amount of about 100 Gbytes for the information / service providing system 1 as a whole.
The community list information is expected to have a data amount of about 100 Gbytes as a whole of the information / service providing system 1.
The community member information is expected to have a data amount of about 100 Mbytes for each community.
The reverse lookup buddy list information is expected to have a data amount of about 100 GB for the information / service providing system 1 as a whole.
Further, the identifier table information is expected to have a data amount of about 1 Gbyte for the information / service providing system 1 as a whole.
Among these pieces of information, the reverse lookup buddy list information and the identifier table information are stored in the memory 114 for speeding up the processing, and all the other information is stored in the recording device 118. It is cached in the memory 114 for speeding up.

[Profile specification information]
FIG. 12 is a diagram illustrating profile specification information stored and managed in the profile specification information management apparatus 12 shown in FIG.
The profile specification information is metadata of profile information, and corresponds to each of the information shown in FIGS.
As shown in FIG. 12, the profile specification information includes profile name, schema information, data source, data access device information, and execution service information.
Further, the data access device information includes a key filter and a key hash table.

The profile name describes the name of the associated profile information and is used for identifying the profile specification information.
The schema information describes the data structure of profile information.
The data source describes in which cluster node the profile information is stored.
The data access device information indicates in which data access device the profile information is stored.
The execution service information is included in the profile specification information as necessary, and indicates a service that is executed in accordance with the operation of the profile information.

The key filter is a function (specifically, a hash function such as MD5 or SHA1) used to generate a fixed-length pseudorandom number from a given message (in this specification, a user ID or community ID). )
Note that a fixed-length pseudo-random number generated by the key filter is referred to as a key filter value.
The key hash table describes a table associating key filter values with data to be searched (values identifying the data access device 3 shown in FIG. 1).
Hereinafter, the “value for identifying the data access device 3” is described as “data access device ID”.

FIG. 13 is a diagram illustrating the reference relationship of the information illustrated in FIGS.
As already described, the user profile information itself exists independently of community formation and deletion.
In addition, when the community profile information is implemented in a relationship table, one record corresponds to one community.
The community member information is referred to by a pointer attribute included in the (record) of the community profile information, and one table thereof corresponds to one community, and each table stores user IDs and statuses of all users belonging to the community. Is done.
In addition, the community list information corresponds to one user, includes the ID list of the community to which each user belongs as an attribute, and the corresponding record in the community profile information is referenced by each community ID .
Also, reverse record buddy list information also has one record corresponding to one user.
The reverse buddy list is also considered as one community, and the corresponding record of the reverse buddy list information is referred to by the user ID of the community list information.
As shown in FIG. 13, information such as the schema and data source of the corresponding user profile information is read from the profile specification information identified by the profile name, and the user ID converted for internal use of the system is used. User profile information is identified.
User information (FIG. 6) is referred to by the profile specification information.
An external identifier (for example, SIP URI) is converted into an identifier (user ID) used inside the information / service providing system 1 by the identifier table information, and used as an ID of user profile information and community list information.

The community profile information is referred to by an attribute indicating the community ID of each community to which each user included in the community list information belongs.
The reverse buddy list information is referred to by the user ID included in the community list information.
The community member information is referred to by a pointer attribute included in the community profile information (record thereof), and one table corresponds to one community.
Each table of community member information stores user IDs and statuses of all users belonging to the community.
The community member information is updated as needed according to the user joining and leaving the community, and is updated as needed as the user profile information and community profile information are changed.

FIG. 14 is a diagram illustrating profile information stored and managed in the data access device 3 shown in FIG.
The profile name, user ID or community ID (ID), key filter value, and profile information are as described above.
Whether or not the flag is profile information stored in the data access device 3 associated with the data access device ID when a certain data access device ID is no longer associated with the key filter value in the key hash table. Indicates.

Thus, the profile name in the path is used for the data access device 3 to identify and search the profile specification information.
Further, the retrieved profile specification information and path are used for the data access device 3 to retrieve the profile information.
The path can be used not only to search the entire profile information but also to search a part of the profile information.

[Data access device 3]
The data access device 3 shown in FIG. 1 executes a profile information operation program 30 described later with reference to FIGS. 15 to 19 and performs the following processes (1) to (3).

(1) Profile information search processing:
When the user operating the client PC 2 (FIG. 1) designates a path known to the user and instructs the retrieval of information (FIGS. 6 and 14), the client PC 2 accepts the designation and instruction, and the data access device 3 to send.
The data access device 3 instructed to search searches for profile information.
The data access device 3 transmits the searched profile information to the client PC 2 that requested the search.

(2) Profile information storage processing:
As in “(1) Profile information search process” described above, when the user specifies a path and profile information to be stored and instructs storage of the profile information, the client PC 2 accepts the specification and instruction, and data Transmit to the access device 3.
The data access device 3 instructed to store stores profile information.

(3) Profile information deletion processing:
As in the above-described “(1) Profile information search process”, when the user designates a path and instructs deletion of profile information, the client PC 2 accepts the designation and instruction and transmits it to the data access device 3. .
Note that the user can specify a path and profile information to be deleted.
The data access device 3 instructed to delete deletes the profile information.

Further, the data access device 3 executes a profile specification information confirmation program 40, which will be described later with reference to FIG.
(4) Profile specification information confirmation processing:
When the profile specification information update unit 426 (FIG. 21) updates the profile specification information (FIG. 12), the data access device 3 reads the updated profile specification information and changes it to the key hash table included in the profile specification information. Check if there was any.

Further, the data access device 3 performs the following process (5) in cooperation with the profile specification information management device 12 (FIG. 1).
(5) Profile specification information search processing:
If the profile specification information search unit 324 (FIG. 16) cannot search the desired profile specification information (FIG. 12) from the profile specification information cache DB 302, the data access device 3 Request a search for profile specification information that could not be searched.
The profile specification information management apparatus 12 requested to search searches for profile specification information.

Further, the data access device 3 performs the following process (6) in cooperation with the external profile information management device 14 (FIG. 1).
(6) Profile information search processing:
A search for profile information by the data access device 3 (a search process in the profile information search unit 338, which will be described later with reference to FIG. 16) has been performed. If the desired information (FIGS. 6 to 10) is not stored in the list information DB 310 and the reverse lookup buddy list information DB 312 and cannot be searched, the data access device 3 searches the external profile information management device 14 for search. Request a search for profile information that could not be done.
The external profile information management device 14 requested to search searches for profile information.

[Profile Information Operation Program 30]
FIG. 15 is a diagram showing a configuration of the profile information operation program 30 executed on the data access device 3 shown in FIG.
As shown in FIG. 15, the profile information operation program 30 includes a communication processing unit 300, a profile specification information cache DB 302, a profile information cache DB 304, a user profile information DB 306, a community profile information DB 308, a community list information DB 310, and a reverse buddy list information. It comprises a DB 314, an identifier table information DB 316, a community member information DB 312, a profile information search unit 32, a profile information storage unit 36 and a profile information deletion unit 38.

The communication processing unit 300 performs processing necessary for communicating with other cluster nodes.
The profile specification information cache DB 302 stores profile specification information (FIG. 12) as cache data.
Details of the cache processing will be described later with reference to FIGS. 25 and 26.
The profile information cache DB 304 stores the information shown in FIGS. 6 to 11 as cache data.
Details of the cache processing will be described later with reference to FIGS.
The user profile information DB 306 stores user profile information (FIG. 6).
The community profile information DB 308 stores community profile information (FIG. 7).
The community member information DB 312 stores the community member information DB 312 (FIG. 8).
The community list information DB 310 stores community list information (FIG. 9).
The reverse lookup buddy list information DB 314 stores reverse lookup buddy list information (FIG. 10).
The identifier table information DB 316 stores identifier table information (FIG. 11).

FIG. 16 is a diagram showing the configuration of the profile information search unit 32 shown in FIG.
As shown in FIG. 16, the profile information search unit 32 includes a user interface (UI) unit 320, a request interpretation unit 322, a profile specification information search unit 324, a data access device identification unit 326, an access control unit 334, and a service execution control unit. 336, a profile information search unit 338, and a cluster node specifying unit 340.
Further, the data access device specifying unit 326 includes a key filter value calculation unit 328, a data access device ID acquisition unit 330, and a data access device ID determination unit 332.
Further, the cluster node specifying unit 340 includes a data source reading unit 342, a profile information search unit 344, and a profile information storage unit 346.

The profile information search unit 32 includes the communication processing unit 300, profile specification information cache DB 302, profile information cache DB 304, user profile information DB 306, community profile information DB 308, community list information DB 310, and reverse lookup buddy list information DB 314 based on these components. In cooperation with the community member information DB 312 and the cluster node specifying unit 340, the above-described “(1) profile information search process” is performed.
Similarly, the profile information search unit 32 performs the above-described “(2) Profile information storage process” in cooperation with the profile information storage unit 36 (described later with reference to FIG. 18) and the like.
Similarly, the profile information search unit 32 performs “(3) profile information deletion processing” in cooperation with the profile information deletion unit 38 (described later with reference to FIG. 19) and the like.

The UI unit 320 provides a user interface for assisting the operation of the user of the data access device 3.
Similarly, the UI unit 320 is a user interface for assisting the user of another cluster node such as the client PC 2 through the network 100 to operate the data access device 3 (profile information operation program 30). I will provide a.
Further, the UI unit 320 accepts an operation performed on the user interface, and outputs data indicating the accepted operation to the request interpretation unit 322.

The request interpreter 322 performs conversion into a user ID in the system based on information in the identifier table information DB 314, and interprets user operations (command type / path, etc.) and profile information input from the UI unit 320. To do.
When the command transmitted from the client PC 2 requests “(1) profile information search processing”, the request interpretation unit 322 uses the interpreted path as the profile specification information search unit 324, key filter value calculation unit 328, data access. The information is output to device ID determination unit 332, profile information search unit 338, and profile information search unit 344.

When the command transmitted from the client PC 2 requests “(2) profile information storage processing”, the request interpretation unit 322 uses the interpreted path as the profile specification information search unit 324, the key filter value calculation unit 328, and the like. The data is output to the data access device ID determination unit 332.
Further, the request interpretation unit 322 outputs the interpreted path to the profile information storage unit 362 (described later with reference to FIG. 18).
Further, the request interpreting unit 322 outputs the interpreted profile information to the precondition checking unit 360 (described later with reference to FIG. 18) and the profile information storage unit 362.

When the command transmitted from the client PC 2 requests “(3) profile information deletion processing”, the request interpreting unit 322 uses the interpreted path as the profile specification information searching unit 324, key filter, and the like shown in FIG. Output to the value calculation unit 328 and the data access device ID determination unit 332.
Further, the request interpretation unit 322 outputs the interpreted path to the profile information deletion unit 380 (described later with reference to FIG. 19).
Furthermore, if there is interpreted profile information, the request interpreting unit 322 outputs the profile information to the precondition checking unit 360 (described later with reference to FIG. 19) and the profile information deleting unit 380.

As shown in FIG. 12, the profile name is uniquely defined for each profile specification information (FIG. 12).
Accordingly, the profile specification information can be searched using the profile name included in the path output from the request interpreter 322.
The profile specification information search unit 324 uses the profile name input from the request interpretation unit 322 to search for profile specification information from the profile specification information cache DB 302 or the like.
In “(1) Profile information search processing”, the profile specification information search unit 324 converts the searched profile specification information into a key filter value calculation unit 328, a data access device ID acquisition unit 330, a service execution control unit 336, and a data source read. Output to the unit 342.
In “(2) Profile information storage process”, the profile specification information search unit 324 uses the searched profile specification information (FIG. 12) as a key filter value calculation unit 328, a data access device ID acquisition unit 330, and service execution control. To the unit 336.
Further, the profile specification information search unit 324 outputs the searched profile specification information to the profile information storage unit 362 (described later with reference to FIG. 18).

In “(3) Profile information deletion process”, the profile specification information search unit 324 converts the searched profile specification information (FIG. 12) into a key filter value calculation unit 328, a data access device ID acquisition unit 330, and a service execution control. To the unit 336.
Furthermore, the profile specification information search unit 324 outputs the searched profile specification information to the profile information deletion unit 380 (described later with reference to FIG. 19).

FIG. 17 is a diagram showing processing of the data access device specifying unit 326 shown in FIG.
The key filter value calculation unit 328 of the data access device specifying unit 326 includes a user ID or community ID (ID) included in the path input from the request interpretation unit 322 and profile specification information input from the profile specification information search unit 324. Is used to calculate a key filter value and output it to the data access device ID acquisition unit 330.
Specifically, the key filter value calculation unit 328 calculates the key filter value by substituting the ID into the key filter.

The data access device ID acquisition unit 330 uses the key filter value input from the key filter value calculation unit 328 and the key hash table included in the profile specification information input from the profile specification information search unit 324. An identifier (data access device ID) for identifying the data access device 3 is derived.
The data access device ID acquisition unit 330 outputs the derived data access device ID to the data access device ID determination unit 332.

The data access device ID determination unit 332 is a data indicating that the data access device 3 corresponding to the data access device ID input from the data access device ID acquisition unit 330 operates the profile information operation program 30. It is determined whether or not the access device ID is included.
For example, when the profile information operation program 30 is executed on the data access device 3-i (i = 1 to n), the data access device ID determination unit 332 included in the profile information operation program 30 It is determined whether or not the data access device 3-i is included in one or more data access devices 3 corresponding to the device ID.
The data access device ID determination unit 332 does not include the data access device ID in which the profile information operation program 30 is operating (in the above example, one or more data access devices 3 corresponding to the data access device ID are If it is determined that the data access device 3-i is not included, the following processing is performed.

The data access device ID determination unit 332 specifies the path input from the request interpretation unit 322 to the data access device 3 corresponding to the data access device ID input from the data access device ID acquisition unit 330, and sets the path A search for the associated information (FIGS. 6 to 10) is requested.
At this time, a communication error may occur, for example, the data access device 3 requested to search refuses access.
When a communication error occurs in the data access device 3 requested to be searched, the access device ID determination unit 332 records that the data access device 3 that has denied access is in an error state.
Furthermore, the access device ID determination unit 332 prevents the access device 3 in which the error is recorded from requesting search for profile information.

Specifically, the access device ID determination unit 332 sends an error of the cluster node or the access device 3 to an SNMP (Simple Network Management Protocol) agent (not shown) connected to the information / service providing system 1 (FIG. 1). Send status.
The network administrator can manage an error state transmitted from the SNMP agent by an SNMP manager (not shown) connected to the information / service providing system 1.
Thereafter, the same processing is performed when various communication errors occur.

If the processing is not interrupted due to a communication error or the like, the data access device 3 requested to search searches the user profile information DB 306 or the like for profile information associated with the designated path.
The data access device 3 requested to search transmits the searched profile information to the data access device ID determination unit 332.

In “(1) Profile information search process”, the data access device ID determination unit 332 transmits the profile information returned from the data access device 3 to the client PC 2 that requested the search.
After the data access device ID determination unit 332 appropriately transmits the profile information to the client PC, the profile information operation program 30 ends the search process.
In “(2) Profile information storage process” and “(3) Profile information deletion process”, the data access device ID determination unit 332 uses the profile information returned from the data access device 3 as the precondition check unit 360 (FIG. 18). And to be described later with reference to FIG.
On the other hand, when the data access device ID determination unit 332 determines that the data access device 3 on which the profile information operation program 30 is operating is included, the profile information operation program 30 moves the operation process to the access control unit 334.

The access control unit 334 determines whether or not the access from the client PC 2 that has requested the operation processing to the data access device 3 is permitted according to the access policy.
Specifically, the access control unit 334 inquires to the policy server 16 whether or not the data access device 3 can be accessed from the client PC 2 that has requested the operation processing.
The policy server 16 that has received the inquiry transmits to the data access device 3 whether access is permitted.
When the policy server 16 permits access, the profile information operation program 30 moves the operation process to the service execution control unit 336.
On the other hand, when the policy server 16 denies access, the profile information operation program 30 moves the operation process to the cluster node specifying unit 340.

The service execution control unit 336 reads execution service information included in the specification information input from the profile specification information search unit 324.
The service execution control unit 336 requests the service execution device 18 to execute a service based on the content of the read execution service information.
Note that the timing at which the service is executed may be before or after the profile information is manipulated.
Also, no service is required.
After the service execution apparatus 18 requested to execute the service appropriately executes the service, the profile information operation program 30 moves the operation process to the profile information search unit 338.

The profile information search unit 338 receives information (FIGS. 6 to 10) from the profile information cache DB 304, the user profile information DB 306, the community profile information DB 308, the community list information DB 310, the reverse lookup buddy list information DB 314, and the community member information DB 312. Search for.
Alternatively, the profile information search unit 338 receives information from any one of the profile information cache DB 304, the user profile information DB 306, the community profile information DB 308, the community list information DB 310, and the reverse lookup buddy list information DB 314 (FIGS. 6 to 10). Search for.
Since the path is unique for each profile information, the profile information search unit 338 uses the path input from the request interpretation unit 322 to search for profile information associated with the path.

In “(1) Profile information search processing”, the profile information search unit 338 searches for profile information, and transmits the searched profile information to the client PC 2 that requested the search.
After the profile information search unit 338 appropriately returns the profile information to the client PC 2, the profile information operation program 30 ends the search process.
If the profile information search unit 338 cannot search for profile information, such as when an error occurs during the process, the profile information operation program 30 moves the operation process to the cluster node specifying unit 340.

The cluster node specifying unit 340 searches for profile information from other cluster nodes when access is denied by the access control unit 334 and when profile information cannot be searched by the profile information search unit 338.
The data source reading unit 342 uses the data source included in the profile specification information (FIG. 12) input from the profile specification information search unit 324 to derive a cluster node in which information (FIGS. 6 to 10) is stored. To do.
The data source reading unit 342 outputs the derived cluster node information to the profile information search unit 344.

The profile information search unit 344 reads the cluster node information input from the data source reading unit 342.
Further, the profile information search unit 344 designates the path input from the request interpretation unit 322 to the read cluster node and requests a search for profile information associated with the path.

The cluster node requested to search searches the user profile information DB 306 of the cluster node for information (FIGS. 6 to 10) associated with the path designated by the profile information search unit 344.
Details of this search process will be described later with reference to FIG.
Further, the cluster node requested to search searches for profile information, and then transmits the searched profile information to the profile information search storage unit 346.

In “(1) Profile information search process”, the profile information storage unit 346 transmits the profile information transmitted from the cluster node to the client PC 2 that requested the search.
Further, the profile information storage unit 346 stores the profile information transmitted from the cluster node in the profile information cache DB 304.
After the profile information storage unit 346 appropriately processes the profile information, the profile information operation program 30 ends the search process.

In “(2) Profile information storage process” and “(3) Profile information deletion process”, the profile information storage unit converts the profile information transmitted from the cluster node into the precondition checking unit 360 (see FIGS. 18 and 19). To be described later.
Further, the profile information storage unit 346 stores the profile information transmitted from the cluster node in the profile information cache DB 304.

FIG. 18 is a diagram showing a configuration of the profile information storage unit 36 shown in FIG.
As shown in FIG. 18, the profile information storage unit 36 includes a precondition check unit 360 and a profile information storage unit 362.
The profile information storage unit 36 performs the above-described “(2) Profile information storage process” in cooperation with the profile information search unit 32 and the like.
Further, the profile information storage unit 36 informs the client PC 2 that requested the storage that the information (FIGS. 6 to 10) is appropriately stored in addition to “(2) Profile information storage processing” as necessary. Notice.

The precondition checking unit 360 reads the information (FIGS. 6 to 10) input from the request interpreting unit 322 shown in FIG. 16, and determines whether or not the preconditions for storing these information match. Check.
Whether or not the preconditions match each other indicates, for example, whether or not a value of a certain attribute is within a predetermined range, whether or not it conforms to a format, and the like.
After the precondition checking unit 360 confirms that the preconditions match, the profile information operation program 30 moves the storage process to the profile information storage unit 362.

The profile information storage unit 362 reads a data source included in the profile specification information input from the profile specification information search unit 324.
Further, the profile information storage unit 362 specifies the path transmitted from the request interpretation unit 322 for the cluster node associated with the read data source, and stores the profile information input from the request interpretation unit 322. Request.

When there are a plurality of cluster nodes associated with the read data source, the load on the network 100 may increase.
In order to avoid a high load state of the network 100, the profile information storage unit 362 performs service execution by the service execution control unit 336 (FIG. 16) that is generated along with the profile information storage processing for all cluster nodes. In addition, the confirmation of the precondition by the precondition confirmation unit 360 may not be requested, or may be requested to some cluster nodes as necessary.
Further, the profile information storage unit 362 updates the information (FIGS. 6 to 10) by specifying the path input from the request interpretation unit 322 with respect to the user profile information DB 306 and the like.
After the profile information storage unit 362 appropriately stores and updates, the profile information operation program 30 ends the storage process.

FIG. 19 is a diagram showing a configuration of the profile information deletion unit 38 shown in FIG.
As shown in FIG. 19, the profile information deleting unit 38 includes a precondition checking unit 360 and a profile information deleting unit 380.
The profile information deletion unit 38 performs the above-described “(3) Profile information deletion process” in cooperation with the profile information search unit 32 and the like using these components.
Further, the profile information deleting unit 38 requests that the information (FIGS. 6 to 10) is appropriately stored in addition to “(3) Profile information deleting process” as necessary. Notify

The precondition checking unit 360 reads the profile information input from the profile information search unit 338 or the profile information storage unit 346 shown in FIG. 16, and determines whether the preconditions for deleting the profile information match. Check.
After the precondition checking unit 360 confirms that the preconditions match, the profile information operation program 30 moves the deletion process to the profile information deleting unit 380.

The profile information deletion unit 380 reads the data source included in the profile specification information (FIG. 12) input from the profile specification information search unit 324 shown in FIG.
Further, the profile information deleting unit 380 specifies the path input from the request interpreting unit 322 shown in FIG. 16 for the cluster node associated with the read data source, and sets the profile information associated with the path. Make a request to delete.
Further, the profile information deletion unit 380 deletes the description regarding the cluster node associated with the read data source from the read data source.

Note that if there are a plurality of cluster nodes associated with the read data source, the load status of the network 100 (FIG. 1) may increase.
In order to avoid a high-load state of the network, the profile information deletion unit 380 may perform the service execution by the service execution control unit 336 (FIG. 16) that can occur with the storage of the profile information for all of the plurality of cluster nodes. The execution and the confirmation of the precondition by the precondition checking unit 360 may not be requested.
Furthermore, the profile information deletion unit 380 specifies a path with respect to the user profile information DB 306 and the like, and deletes information associated with the path (FIGS. 6 to 10).
After the profile information deletion unit 380 appropriately deletes, the profile information operation program 30 ends the deletion process.

[Profile Specification Information Confirmation Program 40]
The data access apparatus 3 (FIG. 1) executes the profile specification information confirmation program 40 shown in FIG.
FIG. 20 is a diagram showing the configuration of the profile specification information confirmation program 40 that operates on the data access device 3.
As shown in FIG. 20, the profile specification information confirmation program 40 includes a communication processing unit 300 and a profile specification information confirmation unit 400.

When the profile specification information is updated, the data access device 3 receives the profile specification information from the profile specification information management device 12 (described later with reference to FIG. 21).
The data access device 3 checks whether there is a change in information regarding the data access device 3 that is currently processing in the key hash table included in the profile specification information received via the communication processing unit 300.
In other words, the data access device 3 does not describe the key filter value associated with the data access device 3 that is currently processing due to the update of the key hash table, and the profile specification information stored in the data access device 3 It is checked whether or not it is necessary to move the data to another data access device 3.
If the key hash table has not been updated, and if the key hash table has been updated but the key filter value associated with the data access device 3 currently performing processing has not been updated, the profile specification information confirmation The program 40 ends the confirmation process.
On the other hand, when the key filter value associated with the data access device 3 that is currently processing is not described due to the update of the key hash table, the profile specification information stored in the data access device 3 is changed to other data. It is necessary to move to the access device 3.

Specifically, the data access device 3 performs the following processing.
The data access device 3 sets the flag included in the profile specification information to be moved to be invalid, and prevents access from other cluster nodes while the flag is set to invalid.
Furthermore, the data access device 3 stores the profile specification information to be moved in the data access device 3 that is supposed to store the profile specification information in the updated key hash table.
After the data access device 3 appropriately stores the profile specification information, the profile specification information confirmation program 40 ends the confirmation process.
By such processing, data movement between the data access devices 3 is minimized.

[Profile Specification Information Management Device 12]
The profile specification information management device 12 (FIG. 1) executes the profile specification information operation program 42 shown in FIG. 21, and in addition to the above-mentioned “(5) profile specification information search process”, the following (7) to (7) Process (9) is performed.

(7) Profile specification information storage processing:
When profile specification information is designated and storage of the profile specification information is requested, the profile specification information management device 12 stores the profile specification information.

(8) Profile specification information update processing:
When the profile name and profile specification information are specified and the profile specification information associated with the profile name is requested to be updated to the specified profile specification information, the profile specification information management device 12 updates the profile specification information. To do.

(9) Profile specification information deletion processing:
When the profile name is designated and the deletion of the profile specification information associated with the profile name is requested, the profile specification information management apparatus 12 deletes the profile specification information.

[Profile Specification Information Operation Program 42]
FIG. 21 is a diagram showing a configuration of the profile specification information operation program 42 operating on the profile specification information management apparatus 12 (FIG. 1).
As shown in FIG. 21, the profile specification information operation program 42 includes a communication processing unit 300, a request interpretation unit 420, a profile specification information search unit 422, a profile specification information storage unit 424, a profile specification information update unit 426, and a profile information deletion unit. 428 and profile specification information DB 430.
The profile specification information operation program 42 uses these components to perform the above-mentioned “(5) Profile specification information search process”, “(7) Profile specification information storage process”, “(8) Profile specification information update process” and “( 9) The process “profile specification information deletion process” is performed.

The request interpreter 420 interprets instructions (command types, profile names, etc.) and profile specification information transmitted from other cluster nodes via the communication processor 300.
When a command transmitted from another cluster node requests “(5) profile specification information search processing”, the request interpreter 420 outputs the interpreted profile name to the profile specification information search unit 422.

  When an instruction transmitted from another cluster node requests “(7) Profile specification information storage processing”, the request interpreter 420 sends the interpreted profile name and profile specification information to the profile specification information storage 424. Output.

  When an instruction transmitted from another cluster node requests “(8) Profile specification information update processing”, the request interpreter 420 sends the interpreted profile name and profile specification information to the profile specification information update unit 426. Output.

  When the command transmitted from the other cluster node requests “(9) Profile specification information deletion processing”, the request interpretation unit 420 outputs the interpreted profile name to the profile specification information deletion unit 428.

In “(5) Profile specification information search process”, the profile specification information search unit 422 searches for the profile specification information, and sends the searched profile specification information to the cluster node that requested the search via the communication processing unit 300. Send.
After the profile specification information search unit 422 appropriately transmits the profile specification information, the profile specification information operation program 42 ends the search process.

In “(7) Profile specification information storage process”, the profile specification information storage unit 424 uses the profile name input from the request interpretation unit 422 to convert the profile specification information input from the request interpretation unit 422 into profile specification information. Store in the DB 430.
After the profile specification information storage unit 424 appropriately stores the profile specification information, the profile specification information operation program 42 ends the storage process.

  In “(8) Profile specification information storage process”, the profile specification information update unit 426 uses the profile name input from the request interpretation unit 420 to obtain profile specification information associated with the profile name from the profile specification information DB 430. Search for.

Further, the profile specification information update unit 426 updates the searched profile specification information to the profile specification information input from the request interpretation unit 420.
Further, the profile specification information storage unit 424 transmits the stored profile specification information to the data access device 3 and requests confirmation of the profile specification information as described above with reference to FIG.
After the profile specification information update unit 426 appropriately updates the profile specification information, the profile specification information operation program 42 ends the update process.

In “(9) Profile specification information deletion process”, the profile specification information deletion unit 428 uses the profile name input from the request interpretation unit 420 to transmit profile specification information associated with the profile name from the profile specification information DB 430. delete.
After the profile specification information deletion unit 428 appropriately deletes the profile specification information, the profile specification information operation program 42 ends the deletion process.
The profile specification information DB 430 stores profile specification information.

[Profile information search program 44]
The external profile information management apparatus 14 (FIG. 1) executes the profile information search program 44 shown in FIG. 22 and performs the above-mentioned “(6) Profile information search process”.
FIG. 22 is a diagram showing the configuration of the profile information search program 44 that operates on the external profile information management apparatus 14 (FIG. 1).
As shown in FIG. 22, the profile information search program 44 includes a communication processing unit 300, a profile information search unit 440, a user profile information DB 306, a community profile information DB 308, a community list information DB 310, a reverse lookup buddy list information DB 312 and community member information. It consists of DB316.

The communication processing unit 300 receives a profile information search request from the data access device 3 and outputs it to the profile specification information search unit 440.
In response to the search request input from the communication processing unit 300, the profile information search unit 440 searches for information (FIGS. 6 to 10) from the user profile information DB 306 and the like.
After searching for profile information, the profile information search unit 440 transmits the searched profile information to the data access device 3 via the communication processing unit 300.
After the profile information search unit 440 appropriately transmits the profile specification information, the profile information search program 44 ends the search process.

Among the client PCs 2, the client PC 2 operated by the administrator of the external profile information management apparatus 14 is used as the management PC 104.
The management PC 104 executes the profile specification information operation program 46 shown in FIG. 23 and performs the following process (10).
(10) Instruction transmission processing:
When an administrator operating the management PC 104 designates a profile name and profile specification information known to the administrator and instructs the operation, the management PC 104 accepts the instruction, and the profile specification information management apparatus 12 (FIG. 1). Send to.

FIG. 23 is a diagram showing the configuration of the profile specification information operation program 46 that runs on the management PC 104 (FIG. 1).
As shown in FIG. 23, the profile specification information operation program 46 includes a communication processing unit 300, a UI unit 320, a request interpretation unit 420, a profile specification information search unit 422, a profile specification information storage unit 424, a profile specification information update unit 426, and The profile specification information deletion unit 428 is configured.

The request interpreter 420 interprets an instruction (instruction type, profile name, etc.) and profile specification information (FIG. 12) issued from the management PC 104, a profile specification information search unit 422, a profile specification information storage unit 424, a profile The data is output to the specification information update unit 426 or the profile specification information deletion unit 428.
When the request interpretation unit 420 determines that the request from the management PC 104 is a search request, the profile specification information operation program 46 searches the profile specification information by the profile specification information search unit 422.
When the request interpretation unit 420 determines that the request from the management PC 104 is a storage request, the profile specification information operation program 46 stores the profile specification information by the profile specification information storage unit 424.

When the request interpretation unit 420 determines that the request from the management PC 104 is an update request, the profile specification information operation program 46 updates the profile specification information by the profile specification information update unit 426.
When the request interpretation unit 420 determines that the request from the management PC 104 is a deletion request, the profile specification information operation program 46 deletes the profile specification information by the profile specification information deletion unit 428.

The profile specification information storage unit 422 requests the profile specification information management apparatus 12 (FIG. 1) to search for the profile specification information input from the request interpretation unit 420.
When the profile specification information management apparatus 12 that has been requested to search appropriately searches the profile specification information as shown in FIG. 21, the profile specification information operation program 46 ends the search process.

The profile specification information storage unit 424 requests the profile specification information management apparatus 12 (FIG. 1) to store the profile specification information input from the request interpretation unit 420.
When the profile specification information management apparatus 12 requested to store the profile specification information appropriately stores the profile specification information as shown in FIG. 21, the profile specification information operation program 46 ends the storage process.

The profile specification information update unit 426 sends profile specification information corresponding to the profile name input from the request interpreter 420 to the profile specification information management apparatus 12 (FIG. 1). Request to update to information.
When the profile specification information management apparatus 12 requested to store the profile specification information appropriately stores the profile specification information as shown in FIG. 21, the profile specification information operation program 46 ends the storage process.

The profile specification information update unit 428 requests the profile specification information management apparatus 12 (FIG. 1) to delete the profile specification information corresponding to the profile name input from the request interpretation unit 420.
When the profile specification information management apparatus 12 requested to be deleted appropriately deletes the profile specification information as shown in FIG. 21, the profile specification information operation program 46 ends the deletion process.

As described above, the administrator can update the profile specification information from the management PC 104 via the profile specification information management device 12.
Also, the administrator can operate the data access device by updating the key hash table in the profile specification information as follows.
The administrator can add a new data access device 3 to the information / service providing system 1 (FIG. 1) by adding information on the new data access device 3 to the key hash table.
Similarly, the administrator can delete the data access device 3 from the information / service providing system 1 by deleting the information of the data access device 3 from the key hash table.
Furthermore, the administrator can distribute the load on the data access device 3 of the information / service providing system 1 by changing the association between the key filter value and the data access device ID in the key hash table.

[Operations of Client PC 2, Data Access Device 3, Profile Specification Management Device 12, External Profile Management Device 14, Policy Server 16, and Service Execution Device 18]
The operations of the client PC 2, the data access device 3, the profile specification management device 12, the external profile management device 14, the policy server 16, and the service execution device 18 except for the data access server 5 are described below. Will be explained.
24A to 24E show operations of the client PC 2, the data access device 3, the profile specification management device 12, the external profile management device 14, the policy server 16, and the service execution device 18 in the information / service providing system 1 (FIG. 1) (S10). ) Is a first communication sequence diagram illustrating processing when a profile information search request is issued from the client PC 2 to the data access device 3 and the profile information operation program 30 is activated.

[Search Profile Information]
As shown in FIG. 24A, in step 100 (S100), the client PC 2 requests the data access device 3 to search for information (FIGS. 6 to 10) by specifying a path.
In step 102 (S102), the data access device 3 requested to search searches the profile specification information management device 12 for profile specification information (FIG. 12) associated with the designated profile name.
In step 104 (S104), after the profile specification information is obtained, the profile specification information management device 12 transmits the obtained profile specification information to the data access device 3.

FIG. 25 is a sequence diagram illustrating operations performed simultaneously when the data access device 3 searches the profile specification information management device 12 for profile specification information in response to a request from the client PC 2 shown in FIG. 24A. is there.
As shown in FIG. 25, the profile specification information (S102) retrieved from the profile specification information management device 12 can be transmitted to the data access device 3 (S104) and stored as cache data in the profile specification information cache DB 302.
By such processing, the profile specification information can be searched by the data access device 3 without searching the profile specification information management device 12 for the profile specification information.

26, the data access device 3 shown in FIG. 24A retrieves profile specification information (FIG. 12) from the profile specification information cache DB 302 of the data access device 3 or the profile specification information DB 430 of the profile specification information management device 12. It is a sequence diagram which illustrates the process to perform.
As shown in FIG. 25, once the profile specification information is retrieved in step 104 (S104), it is stored in the profile specification information cache DB 302 as cache data.
Therefore, when the data access device 3 is requested to search, first, the profile specification cache DB 302 is searched (S102-1). After the profile specification information is obtained, the obtained profile specification information is accessed as data. It holds in the device 3 (S104-1).

Only when the desired profile specification information cannot be searched from the profile specification cache DB 302, the data access device 3 searches the profile specification information DB 430 of the profile specification information management device 12 (S102-2).
After the profile specification information is obtained from the profile specification information DB 430, the profile specification information management device 12 transmits the obtained profile information to the data access device 3 (S104-2).
By such processing, the data access device 3 can perform a search more efficiently.

Hereinafter, returning to FIG. 24A, the continuation of the processing in step 104 (S104) will be described.
In step 104 (S104), the data access device 3 reads the data access device information and the data source included in the searched profile specification information.
The data access device 3 obtains the storage position of the profile information associated with the designated path based on the read data access device information and data source.

The profile information operation program 30 determines the type of profile information and search processing in the profile information operation program 30 according to the storage location of the profile information.
The same applies to the storage processing and deletion processing in the profile information operation program 30 below.

FIG. 27 is a diagram illustrating the association between the storage position of profile information and the type of profile information.
As shown in FIG. 27, the profile information is classified into physical profile information, external profile information, and logical profile information according to the storage location of the profile information derived from the processing of S104 (FIG. 24A).
The data access device 3 uses the part of the profile specification information (data source and data access device information) obtained by the process of step 104 (S104) to determine the storage location of the profile information, and from that storage location Search for profile information.

[Physical profile information]
If nothing is described in the data source as indicated by the symbol a in FIG. 27, the data access device 3 determines that the profile information is stored in the data access device 3 (s). .
At this time, the data access device 3 specifies the data access device 3 in which the profile information is stored using the data access device information.

As a method of specifying the data access device 3, as shown in FIG. 17, a method using a key filter and a key hash table is adopted.
As described above, the profile information stored in the specified data access device 3 is referred to as physical profile information.

[External profile information]
As shown in FIG. 27 with reference symbol b, when the data source has a description (for example, URL) identifying the external profile information management device 14, the data access device 3 indicates that the profile information is external profile information. It is determined that it is stored in the management device 14 (plurality).
At this time, the data access device 3 specifies the external profile information management device 14 in which the profile information is stored using the description of the data source.

The external profile device means a device connected to an existing DB that stores profile information (for example, a DB used before the information search system is constructed).
Thus, the profile information stored in the identified external profile device 14 is referred to as external profile information.

The external profile information can be stored in the profile information cache DB 304 using the data access device information.
This process makes profile information redundant.

[Logical profile information]
As shown in FIG. 27 with reference symbol c, when the profile name is described in the data source, the data access device 3 describes the storage location of the profile information in the profile specification information associated with the profile name. Then, it is determined that the profile information is stored in the profile information data access device 3 (s) and the external profile information management device 14 (s).
Thus, the profile information stored in the identified data access device 3 and external profile information management device 14 is referred to as logical profile information.
Similar to the external profile information, the logical profile information can be stored in the profile information cache DB 304 using the data access information.

Hereinafter, returning to FIG. 24A, the continuation of the processing in step 104 (S104) will be described.
When the profile information operation program 30 determines from the profile specification information read in step 104 (S104) that the storage location is the data access device 3 (= physical profile information), the processing of S106 to S120 (FIG. 24B). The process of S122 to S132 (described later with reference to FIG. 24C) is performed.

If the profile information operation program 30 determines that the storage location is the external profile information device 14 (= external profile information) from the profile specification information read in the processing of step 104 (S104), the processing of S134 to S148 (Described later with reference to FIG. 24D).
If the profile information operation program 30 determines from the profile specification information read in step 104 (S104) that the storage location is the data access device 3 and the external profile information device 14 (= logical profile information), the process proceeds to S150. The process of S162 is performed (described later with reference to FIG. 24E).

[Search physical profile information (1)]
In step 104 (S104), after deriving the data access device ID using the profile specification information, the data access device 3 performs a search process on the data access device 3 associated with the derived data access device ID. It is determined whether or not the data access device 3 is included.
When the data access device 3 performing the search process is not included, the profile information operation program 30 performs the processes of S106 to S120.
On the other hand, when the data access device 3 performing the search process is included, the profile information operation program 30 performs the processes of S122 to S132.
Hereinafter, the processing of each step will be described.

In step 106 (S106) shown in FIG. 24B, the data access apparatus 3 that has received the search request receives the data access apparatus 3 associated with the data access apparatus ID derived by the process of S104 in the process of S100. A search for information (FIGS. 6 to 10) is requested by specifying the specified path.
In step 108 (S108), the policy server 16 is inquired as to whether or not the data access device 3 is accessible from the client PC 2 that has issued the search request.
In step 110 (S110), the policy server 16 checks whether or not access is possible, and transmits it to the data access device 3 requested to be searched in the process of S106.

In step 112 (S112), the data access device 3 requested to search in the process of S106 reads the execution service information included in the profile specification information (FIG. 12) searched in the process of S104.
Further, the data access device 3 requested to search in the process of S106 requests the service execution device 18 to execute a service based on the read execution service information.

Note that the profile information operation program 30 may or may not execute the service in the process of S112 before or after searching for profile information.
The same applies to service execution associated with storing and deleting profile information.
After the service execution device 18 appropriately executes the service (S114), the data access device 3 requested to search in the process of S106 searches the user profile information DB 306 and the like for information (FIGS. 6 to 10) ( S116).
The data access device 3 requested to search in step 106 (S106) searches the information (FIGS. 6 to 10), and then transmits the searched profile information to the data access device 3 that has received the search request from the client PC 2. (S118).

FIG. 28 is a sequence diagram illustrating operations performed simultaneously when the data access device 3 retrieves profile information from another data access device 3 in response to a request from the client PC 2 shown in FIG. 24A. .
As shown in FIG. 28, profile information (S116) retrieved from another data access device 3 that has received the path designation can be transmitted to the data access device 3 and stored as cache data in the profile information cache DB 304. (S118).
By such processing, the profile information can be searched by the data access device 3 without searching the profile information for another data access device 3.

FIG. 29 is a sequence diagram illustrating a process in which the data access device 3 illustrated in FIG. 24A searches for profile information for another data access device 3.
As shown in FIG. 28, in step 118 (S118), once the profile information is retrieved, it is stored as cache data in the profile information cache DB 304.
Therefore, the data access device 3 searches the profile information stored in the profile information cache DB 304 (S116-1) to obtain profile information before specifying a path to another data access device 3 (S106). After being obtained, the obtained profile information is held in the data access device 3 (S118-1).

Only when the desired profile information is not stored in the profile information cache DB 304, a search is performed by designating a path to another data access device 3 (S106 to S116-2).
After the profile information is obtained, the other data access device 3 that has received the path designation transmits the obtained profile information to the data access device 3 (S118-2).
By this processing, the data access device 3 can perform a search more efficiently.
After the profile information is obtained, the other data access device 3 that has received the path designation transmits the obtained profile information to the data access device 3 (S118-2).
By this processing, the data access device 3 can perform a search more efficiently.

Hereinafter, returning to FIG. 24B, the processing after step 120 (S120) will be described.
The data access device 3 that has received the profile information in step 118 (S118) transmits the received profile information to the client PC 2 that requested the search (S120).
After the client PC 2 receives the transmitted profile information, the profile information operation program 30 ends the physical profile information search process.

[Search physical profile information (2)]
In step 122 (S122) shown in FIG. 24C, the data access device 3 inquires of the policy server 16 whether or not the client PC 2 that requested the search can access the data access device 3.
In step 124 (S124), the policy server 16 checks whether access is possible and transmits it to the data access device 3.

In step 126 (S126), the data access device 3 reads the execution service information included in the profile specification information searched in step 104 (S104).
Further, the data access device 3 requests the service execution device 18 to execute a service based on the execution service information.
When the service execution device 18 appropriately executes the service (S128), the data access device 3 searches the profile information cache DB 304 or the like for profile information (S130).
The data access device 3 transmits the profile information searched by the process of step 130 (S130) to the client PC 2 that requested the search (S132).
After the client PC 2 receives the transmitted profile information, the profile information operation program 30 ends the physical profile information search process.

[Search external profile information]
In step 134 (S134) shown in FIG. 24D, the data access device 3 that has received the search request from the client PC 2 determines that it is the storage location of the profile information from the client PC 2 that issued the search request by the processing of S104 (FIG. 24A). The policy server 16 is inquired of whether or not the external profile information management device 14 thus made accessible.
In step 136 (S136), the policy server 16 checks whether access is possible and transmits it to the data access device 3.

In step 138 (S138), the data access device 3 reads the execution service information included in the profile specification information (FIG. 12) retrieved in S104 (FIG. 24A).
Further, the data access device 3 requests the service execution device 18 to execute the service based on the read execution service information.
When the service execution device 18 appropriately executes the service (S140), the data access device 3 sends the profile information to the external profile information management device 14 determined as the storage location of the profile information in the processing of S104 (FIG. 24A). A search is requested (S142).
The external profile information management device 14 requested to search in step 142 (S142) searches the profile information DB 306 or the like for information (FIGS. 6 to 10) (S144).
After retrieving the profile information, the external profile information management device 14 transmits the retrieved profile information to the data access device 3 in step 146 (S146).

FIG. 30 is a sequence diagram illustrating operations performed simultaneously when the data access device 3 searches the external profile information management device 14 for profile information in response to a request from the client PC 2 shown in FIG. 24D. .
As shown in FIG. 30, in response to a search request from the data access device 3 (S142), the profile information searched from the external profile information management device 14 (S144) is transmitted to the data access device 3 (S146). , And can be stored in the profile information cache DB 304.
By this processing, the profile information can be searched by the data access device 3 without searching the profile information with respect to the external profile information management device 14.

FIG. 31 is a sequence diagram illustrating a process in which the data access device 3 illustrated in FIG. 24D searches the external profile information management device 14 for profile information.
As shown in FIG. 31, as shown in the process of S146 (FIG. 30), once the profile information is retrieved, it is stored as cache data in the profile information cache DB 304 of the data access device 3.

Therefore, the data access device 3 first searches the profile information stored in the profile information cache DB 304 before requesting the external profile information management device 14 to search (step 142 (S142)) (S144). -1) After the profile information is obtained, the obtained profile information is held in the data access device 3 (S146-1).
Only when the corresponding profile information is not stored in the profile information cache DB 304 of the data access device 3, the data access device 3 requests the external profile information management device 14 to search (S142), and the external profile information management device 14 Performs a search for the user profile information DB 306 and the like (S144-2).
After obtaining the profile information, the external profile information management device 14 transmits the obtained profile information to the data access device 3 (S146-2).
By this processing, the data access device 3 can perform a search more efficiently.

Hereinafter, returning to FIG. 24D, the processing after step 148 (S148) will be described.
After receiving the profile information transmitted in step 146 (S146), the data access device 3 transmits the profile information to the client PC 2 that requested the search (S148).
After the client PC 2 receives the transmitted profile information, the profile information operation program 30 ends the external profile information search process.

[Search logical profile information]
As shown in FIG. 24E, in step 150 (S150), the data access device 3 determines the data access device 3 and the external profile information management determined as the storage location of the profile information by the processing of S104 from the client PC 2 that requested the search. The policy server 16 is inquired whether the device 14 is accessible.
In step 152 (S152), the policy server 16 checks whether access is possible and transmits it to the data access device 3.

In step 154 (S154), the data access device 3 reads the execution service information included in the profile specification information (FIG. 12) retrieved in the process of S104.
Further, the data access device 3 requests the service execution device 18 to execute a service based on the read execution service information.

When the service execution device 18 appropriately executes the service (S156), the data access device 3 and the external profile information management device 14 retrieve information (FIGS. 6 to 10) from the user profile information DB 306 and the like (S158). .
In step 160 (S160), the data access device 3 and the external profile information management device 14 transmit the profile information retrieved in the process of S158 to the data access device 3.

The data access device 3 receives the profile information transmitted in step 160 (S160), and transmits it to the client PC 2 that requested the search (S162).
After the client PC 2 receives the transmitted profile information, the profile information operation program 30 ends the logical profile information search process.

[Storing profile information]
32A to 32E show operations of the client PC 2, the data access device 3, the profile specification management device 12, the external profile management device 14, the policy server 16 and the service execution device 18 in the information / service providing system 1 (FIG. 1) (S20). FIG. 6 is a second communication sequence diagram illustrating a).
32A to 32E show processing when a profile information storage request is issued from the client PC 2 to the data access device 3 and the profile information operation program 30 is activated.

In step 200 (S200) shown in FIG. 32A, the client PC 2 specifies the path and profile information and requests the data access device 3 to store the profile information.
In step 202 (S202) shown in FIG. 32B, the data access device 3 that has received the search request from the client PC 2 specifies the path and profile information for the data access device 3 that has been set as the storage location by the processing of S104, and the profile Request storage of information.
In step 204 (S204), the data access device 3 confirms whether or not the profile information specified in the process of S200 satisfies a precondition for storing the profile information.
After confirming that the preconditions match, the data access device 3 sends a profile information storage request to all the data access devices 3 determined as the storage location of the profile information in step S104 in step 206 (S206).

The data access device 3 that has received the storage request in step 206 (S206) and has stored the profile information transmits the success or failure of the storage to the data access device 3 that has received the storage request from the client PC 2 (S208).
The data access device 3 that has received the storage request from the client PC 2 transmits the success or failure of the transmitted storage to the client PC 2 that issued the storage request (S210).
After the client PC 2 receives the success or failure of storage, the profile information operation program 30 ends the physical profile information storage process.

If there are a plurality of data access devices 3 determined to be storage locations in step 104 (S104), the processing of S108 (inquiry of accessibility), the processing of S110 (accessibility), the processing of S112 (service execution request), The process of S114 (service execution) and the process of S204 (precondition check) need only be performed for one of them.
Similarly, in FIG. 32C, the processing in step 122 (S122) (accessibility inquiry), the processing in S123 (accessability), the processing in S126 (service execution request), the processing in S128 (service execution), and the processing in S212 (Precondition check) may be performed for only one of them.

Similarly, in FIG. 32D, when there are a plurality of data access devices 3 determined to be storage locations, the processing of S134 (inquiry of accessibility), the processing of S136 (accessibility), the processing of S138 (service execution request) The processing of S140 (service execution) and the processing of S218 (prerequisite check) need only be performed for one of them (hereinafter, the same applies when deleting profile information).
When the data access apparatus 3 confirms the precondition in step 218 (S218), the data access apparatus 3 requests the external profile information management apparatus 14 to store the profile information in the process of S220.

Similarly, in FIG. 32E, when there are a plurality of data access devices 3 determined to be storage locations, the processing of S150 (inquiry of accessibility), the processing of S152 (accessibility), the processing of S154 (service execution request) The processing of S156 (service execution) and the processing of S228 (precondition check) need only be performed for one of them (hereinafter, the same applies when deleting profile information).
FIG. 32E shows an example in which service execution is requested only from the data access device 3 (S154), and the precondition is confirmed only in the data access device 3 (S228).

[Delete Profile Information]
33A to 33E show operations of the client PC 2, the data access device 3, the profile specification management device 12, the external profile management device 14, the policy server 16, and the service execution device 18 in the information / service providing system 1 (FIG. 1) (S30). FIG. 6 is a third communication sequence diagram illustrating a).
33A to 33E show processing when a profile specification information deletion request is issued from the client PC 2 to the data access device 3 and the profile information operation program 30 is activated.

As shown in FIG. 33A, in step 100 (S100), the client PC 2 requests the data access device 3 to delete information (FIGS. 6 to 10) by specifying a path.
At this time, the client PC 2 can specify profile information to be deleted for the data access device 3.
In step 204 (S204) shown in FIG. 33B, if there is profile information specified by the process of S200, the data access device 3 deletes the profile information as in the process of S204 (FIG. 32A). Check whether the prerequisites for doing so are met.
In step S204, the data access device 3 confirms that the preconditions match. In step 300 (S300), the data access device 3 stores the profile information in all the data access devices 3 determined as the storage location of the profile information in step S104. Send a delete request.

After the data access device 3 that has received the deletion request from the client PC 2 transmits the success or failure of the deletion to the client PC 2, the profile information operation program 30 ends the physical profile information deletion process.
Similarly to step 204 (S204), whether or not the preconditions for deleting the profile information match in the processing of S212 (FIG. 33C), S218 (FIG. 33D), and S228 (FIG. 33E). Check.
In FIG. 33D, after confirming the precondition in the process of S218, the data access apparatus 3 requests the external profile management apparatus 14 to delete the profile information in the process of S304.
Similarly to the processing in step 300 (S300), also in S302 (FIG. 33C), S306 (FIG. 33D), and S308 (FIG. 33E), the profile information is deleted and the success or failure of deletion is requested to the client PC 2 that requested the deletion. After the transmission, the profile information operation program 30 ends the deletion process.

As described above, in the information / service providing system 1, the client PC 2, the data access device 3, the profile specification management device 12, the external profile management device 14, the policy server 16, and the service execution device 18 ensure system redundancy. The load on cluster nodes constituting the system can be distributed.
In the information / service providing system 1, the client PC 2, the data access device 3, the profile specification management device 12, the external profile management device 14, the policy server 16, and the service execution device 18 search for information using a key filter and a key. By using identifiers via the hash table, the complexity associated with managing identifiers can be reduced, and the cluster nodes holding information can be distributed appropriately.
Furthermore, in the information / service providing system 1, the client PC 2, the data access device 3, the profile specification management device 12, the external profile management device 14, the policy server 16, and the service execution device 18 use the key hash table to When changing the node, it is only necessary to change the key hash table, and the data change can be minimized.

[Data access server 5]
With the spread of mobile terminals such as mobile phones, the number of users in the mobile environment is increasing, so information and services are effectively provided to users connected to a fixed network using a PC or the like. In addition to the need, there is a need to effectively provide information and services to users connected to mobile networks.
A usage pattern that is specific to the usage pattern of the mobile network and is not found in the fixed network is that groups of users are generated each time at various destinations.
In other words, it is important to provide information and services to a dynamically generated user group (“mobile community” or “community”) based on a common purpose, interest, and impression at a specific location. It has become.

In addition to receiving the information provided to the community unilaterally, the information is sent to other users participating in the community within the community, and information is exchanged between users participating in the community. There is a demand for sharing.
There is a need for a system that can efficiently provide and share information and services in units of such mobile communities.
The data access server 5 described below cooperates with other components of the information / service providing system 1 to efficiently provide information / service and share information in units of mobile communities. It is devised to be able to.

[Outline of control for information / service provision and information sharing]
FIG. 34 is a chart showing attributes used for control for providing information and services to the community and for sharing information. FIG. 34A shows a case where a company or a user who does not participate in the community The provision attribute used for the control to provide information / service to the members of the community, and (B) is dynamically generated with the offer of provision of information / service by the provider A participation attribute for controlling what kind of user is allowed to participate in the community is shown. (C) shows a sharing attribute for information sharing among members of the community.
First, an outline of control for providing information and services and sharing information by the data access server 5 will be described.

[(1) Control for providing information and services from outside the community]
FIG. 35 is a diagram illustrating the provision of information / services from outside the community.
FIG. 36 is a diagram illustrating participation in a dynamically created community.
FIG. 37 is a diagram illustrating information sharing in a community.
As shown in FIG. 35, the data access server 5 is set for each member when a company or user not participating in the community becomes an information / service provider and provides information / service to members of the community. Control for providing information and services is performed using the provided attribute (FIG. 34A).
34A and 34C, the provided attribute and the shared attribute are, as shown in FIGS. 35 and 37, for each user, as an attribute of the community member information shown in FIG. It is set when participating and is stored in the community member information DB 316 (FIG. 22).

As shown in FIG. 34 (A), a user whose “Sneak-in” is set as the provided attribute is information / services from all users regardless of whether he / she participates in the community. Will not receive any of the above.
In addition, users with “Community-only” as the provided attribute receive information and services provided by users who participate in the community, but information and services provided by users who do not participate in the community. Will not be provided.

In addition, a user who is set to “Buddy-only” as a provided attribute receives information and services provided by the user included in the user's buddy list, but is not included in the buddy list. Information and services are not provided.
A user's buddy list may include both users who belong to the same community and users who do not belong to the same community. Further, reverse lookup buddy list information (FIG. 10) is used in order to quickly and efficiently check whether another user is included in the user's buddy list.
In addition, information / services by all users, regardless of whether or not users with “Public” as the provided attribute belong to the same community and are included in the buddy list Receive the offer.

[(2) Control for participation in a dynamically created community]
As described with reference to FIG. 4C, a community can be dynamically derived from another community in accordance with an offer of information / service provided by a provider.
As shown in FIG. 36, the data access server 5 uses the participation attribute shown in FIG. 34 (B) to derive dynamically according to the offer of the provision of information / service, etc. Control what users are allowed to participate in the community where the service is provided.
As shown in FIG. 36, the participation attributes shown in FIG. 34B are set for each community as attributes of community profile information (FIG. 7) when the community is created, and the community profile information DB 308 (FIG. 22).

As shown in FIG. 34 (B), in the community in which “Private session” is set as the participation attribute, the community created for the provision of the information / service at the start of the provision of the information / service Information and services are provided only to users who belonged to as members.
That is, in a community in which “Private session” is set as a participation attribute, other users cannot participate midway after the start of providing information and services.
In a community for which “Community-only session” is set as a participation attribute, all users who belong to the community for which provision of information / service provision has been made participate in this community. can do.

In communities where “Buddy-only session” is set as a participation attribute, users who belonged to the community created for the provision of information and services at the start of the provision of information and services Only users who are included in this buddy list can join this community. Here, reverse buddy list information (FIG. 10) is used in order to quickly and efficiently check whether a user who has requested participation in the community is included in the buddy list of each member of the community.
In a community for which “Public session” is set as a participation attribute, whether or not it belongs to the community for which provision of information / service provision has been made, and the provision of information / service provision is made. All users can participate in this community regardless of whether they are included in the buddy list of users who belong to the community as members.

[(3) Control for information sharing in the community]
As shown in FIG. 37, when a user belonging to a certain community performs an operation for sharing information with other users, the data access server 5 is stored as an attribute of the community member information of this community. Control for information sharing is performed using attributes (FIG. 34C).
As shown in FIG. 34C, a user with “Sneak-in” set as a sharing attribute cannot share any information with other users.
In addition, a user whose community attribute is set to “Community-only” can share information with all other users participating in the community.

In addition, a user with “Buddy-only” set as a sharing attribute can share information with users included in that user's buddy list, and can be shared with users who are not included in the buddy list. Information sharing is not possible. Here, reverse buddy list information (FIG. 10) is used in order to quickly and efficiently check whether a user who has requested information sharing is included in each user's buddy list.
In addition, a user with “Public” set as a shared attribute can share information with all users in the same manner as a user with “Community-only” set.

[Data Access Server Program 50]
FIG. 38 is a diagram showing a configuration of a data access server program 50 executed in the data access server 5 shown in FIG.
As shown in FIG. 38, the request reception unit 500, the information acquisition unit 502, the target list management unit 504, the access control unit 506, the information / service provision unit 508, the session control unit 510, the community management unit 512, and the information sharing processing unit 514 And a communication control unit 520.
The data access server program 50 cooperates with each component of the information / service providing system 1 by these components, and (1) the control for providing information / service from outside the community, (2 ) Control for participation in a dynamically created community, and (3) Control for information sharing in the community.

In the data access server program 50, the communication control unit 520 performs communication control for performing communication with other nodes via the network 100.
The request receiving unit 500 accepts a request for providing information / service and a request for sharing information from nodes such as the PC 2 and the enterprise server 102 (FIG. 1) of the information / service providing system 1.
The information acquisition unit 502 accesses the profile specification management device 12 (FIG. 1), the data access device 3, and the policy server 16, and (1) controls for providing information and services from outside the community, (2) dynamic And (3) information necessary for control for information sharing in the community (user profile information, community profile information, community member information, and reverse buddy list information) FIG. 6, FIG. 7, FIG. 9, FIG. 10) are acquired.

When the information / service is provided from outside the community, the access control unit 506 provides each user's provided attribute (FIG. 34A) included in the acquired community member information and the user profile of each user. Using a buddy list included in the information, a user who is a target of provision of this information / service is selected.
In addition, when an operation for sharing information in the community is performed on the PC 2 or the like, the access control unit 506 shares each user's shared attribute (FIG. 34 (C)) included in the acquired community member information. And using the reverse lookup buddy list information of the user who requested information sharing, the user who is the target of this information sharing is selected.
That is, the access control unit 506 is a user who provides a service from outside the community according to FIGS. 34A and 34C when a service from outside the community is provided and when information sharing is requested. And, a user who is a target of information sharing is selected, and control for accessing the PC 2 or the like used by these users is performed.

  The target list management unit 504 creates and manages a list (target list) that is selected by the access control unit 506 and indicates users to be provided for information / service or information sharing.

The information / service providing unit 508 provides information and services in cooperation with the service execution device 18 and the like to the user's PC 2 and the like.
When a community for providing information and services is derived, the session control unit 510 controls what kind of users are allowed to participate in this community according to FIG.
The community management unit 512 manages the dynamically created community in accordance with the provision of information / service provision and the like, and extinguishes the derived community after the provision of the information / service is terminated. Perform the process.
When information sharing is requested, the information sharing processing unit 514 transmits information to be shared to users who are targets of information sharing.

[Operation of Data Access Server Program 50]
The operation of the data access server program 50 shown in FIG. 38 will be described below.

[(1) Provision of information and services from outside the community]
The provision of information and services from outside the community will be described below.
FIG. 39 is a flowchart showing processing (S52) for providing information / service from outside the community shown in FIG.
As shown in FIG. 39, in step 520 (S520), the request receiving unit 500 (FIG. 38) of the data access server program 50 receives a request for providing information / service from the PC 2 or the company server 102.
In step 522 (S522), the target list management unit 504 initializes the target member list.

In step 524 (S524), the information acquisition unit 502 acquires profile specification information related to community member information from the profile specification management device 12, and based on this information, from the data access device 3, information and service provision targets are obtained. Get community member information for the community being played.
In step 526 (S526), the target list management unit 504 determines whether or not the processing has been completed for all the members of the community.
The data access server program 50 proceeds to the process of S534 when the process for all the members of the community is completed, and proceeds to the process of S528 otherwise.

In step 534 (S534), the information / service providing unit 508 uses the list of users to be provided with the information / service created by the target list management unit 504, and the service execution device 18 (FIG. 1) or the like. In cooperation with the service provider, the information / service is provided to the PC 2 of the user who is the target of the information / service provision.
In steps 528 and 530 (S528 and S530), the access control unit 506 sets the user-provided attribute (FIG. 34A) that has not been processed so far as the processing target, and from the data access device 3, The user profile information of the user is acquired, and it is determined whether or not information / service can be provided.
The data access server program 50 returns to the process of S526 when the information / service cannot be provided to the user, and otherwise proceeds to the process of S532.
In step 532 (S532), the target list management unit 504 adds a user who is a target of information / service provision to the target member list.

Processing for providing information and services from outside the community will be further described.
FIG. 40 is a sequence diagram showing a control process (S40) for providing information / service from outside the community shown in FIG.
As shown in FIG. 40, in step 400 (S400), execution of provision of information / service is requested from PC2 of a member who does not belong to the community.
In step 402 (S402), the data access server 5 searches the profile specification management device 12 for profile specification information related to community member information.
In step 404 (S404), the profile specification management device 12 returns profile specification information (FIG. 12) regarding the community member information to the data access server 5.

In step 406 (S406), the data access server 5 designates the path of the community member information corresponding to the community to be provided with the information / service to the data access device 3.
In step 408 (S408), the data access device 3 inquires of the policy server 16 whether or not the user (PC2 or the like) who has requested execution of information / service provision can access the community member information.
In step 410 (S410), the policy server 16 responds (permits) to the data access device 3 whether or not access to the community member information is permitted.

In step 412 (S412), the data access device 3 searches for community member information (FIG. 9) of the community for which information / service is provided.
In step 414 (S414), the data access device 3 transmits community member information to the data access server 5.

Hereinafter, the processing in steps 416 (S416) to 428 (S428) is performed for all members participating in the community to be provided with information and services.
In step 416 (S416), the data access server 5 searches the profile specification management apparatus 12 for profile specification information related to user profile information.
In step 418 (S418), the profile specification management apparatus 12 returns profile specification information related to the user profile information to the data access server 5.

In step 420 (S420), the data access server 5 specifies the path of the user profile information of the user included in the community member information to the data access device 3.
In step 422 (S422), the data access device 3 inquires of the policy server 16 whether the user (PC2 or the like) who has requested execution of the provision of information / service can access the user profile information.
In step 424 (S424), the policy server 16 responds (permits) whether or not access to the user profile information is permitted.
In step 426 (S426), the data access device 3 searches for user profile information (FIG. 6) of community members.
In step 427 (S427), the data access device 3 transmits user profile information to the data access server 5.
In step 428 (S428), the data access server 5 uses the buddy list included in the user participation attribute and the user profile information to determine whether the information / service can be provided, and creates a target member list.

In step 430 (S430), the data access server 5 requests the service execution apparatus 18 to execute the service requested to be provided from the PC 2 or to provide information.
In step 432 (S432), the service execution device 18 returns the requested information or service provision result to the data access server 5.
In step 434 (S434), the data access server 5 returns the information or service provision result to the PC 2.

[(2) Control for participation in a dynamically created community]
Hereinafter, control for participation in a dynamically created community will be described.
FIG. 41 is a flowchart showing a control process (S54) for participation in a dynamically created community.
FIG. 42 is a flowchart showing the service session control process (S56) shown in FIG.
As shown in FIG. 41, in step 540 (S540), the PC 2 and the company server 102 notify the user and the data access server 5 of information / service provision.
In step 542 (S542), the community management unit 512 of the data access server program 50 (FIG. 38) receives a response from the user for participation in providing information and services, and creates a community for providing information and services. To do.
In step 544 (S544), the information / service providing unit 508 starts providing information / service in cooperation with the service execution device 18.

In step 56 (S56), the session control unit 510 performs service session control.
As shown in FIG. 42, in step 560 (S560), the session control unit 510 determines whether or not a request to join a community for providing information and services has been received from the user's PC2.
The data access server program 50 proceeds to the process of S562 when receiving a community participation request for providing information and services, and proceeds to the process of S546 (FIG. 41) otherwise.
In step 562 (S562), the information acquisition unit 502 displays the community profile information (FIG. 7) and community member information (FIG. 9) of the community created for providing information and services, and the reverse of the user who requested participation. Pull buddy list information (FIG. 10) is acquired.

In Steps 564 and 566 (S564 and S566), the session control unit 510 sends information and information to the user who requested participation based on the information acquired by the processing of S562 and the participation attribute (FIG. 34B). Determine whether to allow participation in the community for service provision.
The data access server program 50 proceeds to the process of S568 when allowing the user who requested the participation to participate in the community, and proceeds to the process of S546 (FIG. 41) otherwise.
In step 568 (S568), the session control unit 510 performs processing for providing information / service to the user who has requested participation.

In step 546 (S546), the community management unit 512 determines whether the provision of information / service has ended.
The data access server program 50 proceeds to the process of S548 when the provision of information / service is completed, and returns to the process of S56 otherwise.
In step 548 (S548), the community management unit 512 deletes the community created for providing information and services.

Controls for participation in dynamically created communities are further described.
FIG. 43 is a communication sequence diagram illustrating a control process (S46) for participation in a dynamically created community.
As shown in FIG. 43, in step 460 (S460), a request to participate in the community for providing information and services is issued from the PC 2 or the like to the data access server 5.
In step 462 (S462), the data access server 5 searches the profile specification management apparatus 12 for profile specification information related to community profile information, community member information, and reverse lookup buddy list information.
In step 464 (S464), the profile specification management device 12 returns the profile specification information related to the community profile information, community member information, and reverse lookup buddy list information found as a result of the search.

In step 466 (S466), the data access server 5 provides the data access server 3 with the community profile information and community member information path for providing information and services, and the reverse lookup buddy of the user who requested participation. Specify the list information path.
In step 468 (S468), the data access device 3 accesses the community profile information and community member information such as the PC 2 that has issued a request for participation in the community for providing information and services to the policy server 16. Inquire about availability.
In step 470 (S470), the policy server 16 responds (permits) whether or not access to the community profile information and community member information is possible.

In step 472 (S472), the data access device 3 searches the community profile information (FIG. 7), community member information (FIG. 9), and reverse lookup buddy list information (FIG. 10).
In step 473 (S473), the data access device 3 transmits community profile information, community member information, and reverse lookup buddy list information to the data access server 5.
In step 474 (S474), the data access server 5 determines whether or not the user who has requested participation is allowed to participate in the community for providing information and services based on these pieces of information.
In step 475 (S475), the data access server 5 requests the service execution apparatus 18 to execute provision of information / service.

In step 476 (S476), the service execution device 18 responds to the data access server 5 with the execution result of the provision of information / service.
In step 478 (S478), when the user who has requested participation in the community can participate, the data access server 5 sends a response indicating that the user can participate and the execution result of the information / service provision to the PC 2. Output.
In addition, when the user who has requested participation in the community cannot participate, the data access server 5 outputs a response indicating that participation is not possible to the PC 2.

[(3) Control for information sharing in the community]
Hereinafter, control for information sharing in the community will be described.
FIG. 44 is a flowchart showing the control process (S58) for information sharing.
As shown in FIG. 44, in step 580 (S580), the request receiving unit 500 receives an information sharing request from the PC2.
In step 582 (S582), the information acquisition unit 502 acquires the reverse lookup buddy list information (FIG. 10) of the user who has issued the information sharing request.

In step 584 (S584), the target list management unit 504 initializes the target member list.
In step 586 (S586), the information acquisition unit 502 acquires profile specification information related to community member information from the profile specification management device 12, and based on this information, from the data access device 3, the information of the community requested to share information is acquired. Get community member information.
In step 588 (S588), the target list management unit 504 determines whether or not the processing has been completed for all the members of the community.
The data access server program 50 proceeds to the process of S596 when the process for all the members of the community is completed, and proceeds to the process of S590 otherwise.

In step 596 (S596), the information sharing processing unit 514 cooperates with the service execution device 18 (FIG. 1) using the list of users to be information sharing created by the target list management unit 504. Thus, information to be shared is provided to users included in the target list.
In steps 590 and 592 (S590 and S592), the access control unit 506 sets the sharing attribute of the user that has not been processed so far (FIG. 34C) as the processing target and requests the information sharing. The reverse lookup buddy list information is used to determine whether information can be shared.
The data access server program 50 returns to the process of S588 when information cannot be shared with the user, and proceeds to the process of S594 otherwise.
In step 594 (S594), the target list management unit 504 adds a user who is a target of information sharing to the target member list.

The control for information sharing will be further described.
FIG. 45 is a communication sequence diagram showing a control process (S60) for information sharing.
As shown in FIG. 45, in step 600 (S600), execution of information sharing is requested from the community member PC2 or the like.
In step 602 (S602), the data access server 5 searches the profile specification management apparatus 12 for profile specification information related to reverse lookup buddy list information.

In step 604 (S604), the profile specification management device 12 returns profile specification information (FIG. 12) regarding the reverse lookup buddy list information to the data access server 5.
In step 606 (S606), the data access server 5 designates the reverse buddy list information path of the user who has issued the information sharing request to the data access device 3.
In step 608 (S608), the data access device 3 inquires of the policy server 16 whether or not the user (PC2 or the like) who has requested execution of information sharing can access the reverse lookup buddy list information.

In step 610 (S610), the policy server 16 responds (permits) to the data access device 3 whether or not the reverse lookup buddy list information is accessible.
In step 612 (S612), the data access device 3 searches the reverse lookup buddy list information (FIG. 10) of the user who has requested execution of information sharing.
In step 614 (S614), the data access device 3 transmits reverse lookup buddy list information to the data access server 5.

In step 616 (S616), the data access server 5 searches the profile specification management device 12 for profile specification information related to community member information.
In step 618 (S618), the profile specification management device 12 returns profile specification information related to community member information to the data access server 5.
In step 620 (S620), the data access server 5 designates the path of the community member information of the community whose information sharing is requested to the data access device 3.

In step 622 (S622), the data access device 3 inquires of the policy server 16 whether or not the user (PC2 or the like) who has requested execution of information sharing can access the community member information.
In step 624 (S624), the policy server 16 responds (permits) whether or not access to the community member information is permitted.
In step 626 (S626), the data access device 3 searches for community member information (FIG. 9).
In step 627 (S 627), the data access device 3 transmits community member information to the data access server 5.

Hereinafter, the process of step 628 (S628) is performed for all members participating in the community that is the target of information sharing.
In step 628 (S628), the data access server 5 determines whether or not information sharing is possible using the user's sharing attribute and the reverse lookup buddy list information of the user who requested execution of information sharing, and creates a target member list. To do.
In step 630 (S630), the data access server 5 requests the service execution apparatus 18 to share information requested from the PC 2.
In step 632 (S 632), the service execution apparatus 18 returns the requested information sharing result to the data access server 5.
In step 634 (S634), the data access server 5 returns the information sharing result to the PC 2.

According to the processing of the data access server program 50 described above, it is possible to provide information and services between communities composed only of users who comply with certain rules. Can be protected from.
In addition, it is troublesome for a community participant to create the information necessary for access control by himself / herself, which is troublesome work. However, according to the method according to the present invention, Access control can be performed using attribute information (information shown in FIGS. 34A to 34C) and a buddy list (or reverse lookup buddy list information) included in the user profile information of each participant.
Therefore, the method according to the present invention not only facilitates the setting and management of the privacy protection of the community participant, but also can provide the community participant with a filter function for selecting the information / service provider. .

Explanation of symbols

1 ... Community information search system,
12 ... Profile specification information management device,
14 ... External profile information management device,
15 ... External profile information storage device,
16: Policy server,
18 ... Service execution device,
2 ... Client PC,
110 .. Cluster node body,
112 ... CPU,
114 ... memory,
118... Recording device,
120... Recording medium,
122... Communication device,
DESCRIPTION OF SYMBOLS 3 ... Data access apparatus 30 ... Profile information operation program 300 ... Communication processing part 302 ... Profile specification information cache DB
304 ... Profile information cache DB
306 ... Profile information DB
308 ... Community profile information DB,
310 ... community list information DB,
312 ... Reverse lookup buddy list information DB,
316 ... Community member information DB,
32 ... Profile information search part,
320 ... UI unit,
322 ... request interpreter,
324 ... Profile specification information search unit,
326... Data access device specifying unit,
328 ... Key filter value calculation unit,
330 ... Data access device ID acquisition unit,
332 ... Data access device ID determination unit,
334 ... access control unit,
336 ... service execution control unit,
338: Profile information search unit,
340... Cluster node identification unit,
342... Data source reading unit,
344: Profile information search unit,
346: Profile information storage unit,
36: Profile information storage unit,
360 ... Prerequisite checking part,
362 ... Profile information storage unit,
38 ... Profile information deletion part,
380 ... Precondition check part,
382 ... Profile information deletion unit,
104 ... management PC,
40: Profile specification information confirmation program,
400: Profile specification information confirmation unit,
42 ... Profile specification information operation program,
420 ... request interpreter,
422 ... Profile specification information search unit,
424 ... Profile specification information storage unit,
426: Profile specification information update unit,
428 ... Profile specification information deletion unit,
430 ... Profile specification information DB,
44 ... Profile information search program,
440 ... Profile information search unit,
46 ... Profile specification information operation program,
5 ... Data access server,
50: Data access server program,
500 ... request receiving unit,
502 ... Information acquisition unit,
504 ... Target list management unit,
506: Access control unit,
508 ... Information and service provision department,
510... Session control unit,
512 ... community management department,
514 ... Information sharing processing unit,
520 ... Communication control unit,
8: Identifier management device,

  The present invention can be used for providing information and services via a network.

Claims (16)

Information / service that provides information and / or service (hereinafter referred to as “information / service”) as a provider to a community in which one or more users each participate as a provider. Providing system,
User profile information storage means (306) for storing user profile information including at least identifiers of a plurality of users;
Community member information in which each of the community identifiers is associated with at least an identifier of zero or more users belonging to the community, and a mode in which each user belonging to the community receives the provided information / service. Community member information storage means (316) for storing
Based on the stored user profile information and the stored community member information, information provided by the provider in a manner included in the stored community member information for each user participating in the community. An information / service providing system comprising providing means (50) for providing a service. The manner in which the user receives information / service provided is as follows:
A first mode in which no information / service is provided;
A second mode of not receiving information / service by a provider who does not participate in the community;
And at least a third mode for receiving all information and services,
The information / service providing system according to claim 1, wherein the providing unit provides the information / service only to a user whose third mode is stored in the community member information. The stored user profile information is:
A buddy list in which each of the user identifiers is associated with a list including zero or more user identifiers.
Further including
The manner in which the user receives information / service provided is as follows:
A fourth mode of receiving provision of information / service only when a user included in the user's buddy list is a provider;
The providing means provides information and services,
The third aspect provides for a user stored in the community member information,
The information / service provision system according to claim 2, wherein the fourth aspect provides the provider only to the user included in the buddy list of the user among the users stored in the community member information. . Reverse lookup buddy list information storage means (312) associating each of the user identifiers with a list of zero or more user identifiers including the user identifiers in its own buddy list
Further comprising
The providing means provides information and services,
The third aspect provides for a user stored in the community member information,
The information / service provision system according to claim 2, wherein the fourth aspect provides only to users included in the reverse buddy list information of the provider among users stored in the community member information. In response to an offer to provide information and / or services (hereinafter referred to as “information / services”) made to a first community in which one or more users each participate, An information / service providing system for providing information / service to a user who wishes to provide,
Community profile information storage means (308) that associates at least the identifier of the second community that is dynamically created in response to the offer of provision of the information / service with a predetermined information / service provision mode;
Community member information storage means (316) for storing community member information in which each identifier of the community is associated with at least an identifier of zero or more users belonging to the community;
Based on the stored community profile information and the stored community member information, the participation is provided according to the predetermined information / service provision mode for a user who requests participation in the second community. An information / service providing system comprising: providing means (50) for controlling whether or not a user who has requested the user participates and providing information / service. The predetermined information / service provision mode is as follows:
A first mode of providing information / service only to a user who wishes to provide information / service in response to the offer when providing the information / service;
A second mode in which only a user who participates in the first community is allowed to participate in the second community and provides information and services;
A third mode of providing information and services to an arbitrary user, and
The information / service providing system according to claim 5, wherein the providing unit provides the information / service according to any one of the first to third aspects. Reverse lookup buddy list information storage means (312) associating each of the user identifiers with a list of zero or more user identifiers including the user identifiers in its own buddy list
Further comprising
The predetermined information / service provision mode is as follows:
When the offer of provision of the information / service is made, the user included in the buddy list of the user who wishes to provide the information / service according to the offer is allowed to participate in the second community. A fourth aspect of providing a service,
The providing means provides information and services,
The information / service providing system according to claim 6, wherein the providing means provides information / service according to any one of the first to fourth aspects. An information sharing system for sharing information among users in a community in which one or more users each participate,
User profile information storage means (306) for storing user profile information including at least identifiers of a plurality of users;
A community that stores community member information in which each identifier of the community is associated with at least an identifier of zero or more users belonging to the community, and a mode in which each user belonging to the community shares the information Member information storage means (316);
Sharing means for sharing information in a manner included in the stored community member information among users participating in the community based on the stored user profile information and the stored community member information (50) An information sharing system comprising: The mode when the user shares information is as follows:
A first mode in which no information sharing is performed;
A second mode for sharing information only with users who participate in the community;
And at least a third mode for sharing information with all users,
The sharing means provides information and services,
The second aspect allows information to be shared only among users stored in the community member information,
The information sharing system according to claim 8, wherein the third mode causes the user information stored in the community member information to be shared among all users. Reverse lookup buddy list information storage means (312) associating each of the user identifiers with a list of zero or more user identifiers including the user identifiers in its own buddy list
Further comprising
The mode when the user shares information is as follows:
A fourth mode of sharing information only with users included in the user's buddy list;
The sharing means provides information and services,
The second aspect allows information to be shared only among users stored in the community member information,
In the third aspect, the user information stored in the community member information is shared among all users,
10. The information sharing system according to claim 9, wherein the fourth mode allows information to be shared only with a user stored in the community member information among users who include the user in reverse lookup buddy list information. Information / service that provides information and / or service (hereinafter referred to as “information / service”) as a provider to a community in which one or more users each participate as a provider. Providing method,
A user profile information storage step (306) for storing user profile information including at least identifiers of a plurality of users;
Community member information in which each of the community identifiers is associated with at least an identifier of zero or more users belonging to the community, and a mode in which each user belonging to the community receives the provided information / service. Community member information storage step (316) for storing
Based on the stored user profile information and the stored community member information, information provided by the provider in a manner included in the stored community member information for each user participating in the community. An information / service providing method for causing a computer to execute the providing step (50) of providing a service. In response to an offer to provide information and / or services (hereinafter referred to as “information / services”) made to a first community in which one or more users each participate, An information / service providing method for providing information / service to a user who wishes to provide,
A community profile information storage step (308) in which at least the identifier of the second community that is dynamically created in response to the offer of provision of the information / service is associated with at least a predetermined information / service provision mode;
A community member information storage step (316) for storing community member information in which each of the community identifiers is associated with at least an identifier of zero or more users belonging to the community;
Based on the stored community profile information and the stored community member information, the participation is provided according to the predetermined information / service provision mode for a user who requests participation in the second community. An information / service providing method for causing a computer to execute a providing step (50) for providing information / service by controlling whether or not a user who has requested the user participates. An information sharing method for sharing information among users in a community in which one or more users each participate,
A user profile information storage step (306) for storing user profile information including at least identifiers of a plurality of users;
A community that stores community member information in which each identifier of the community is associated with at least an identifier of zero or more users belonging to the community, and a mode in which each user belonging to the community shares the information Member information storage step (316);
A sharing step of sharing information in a manner included in the stored community member information among users participating in the community based on the stored user profile information and the stored community member information (50) An information sharing method for causing a computer to execute and. Information / service that provides information and / or service (hereinafter referred to as “information / service”) as a provider to a community in which one or more users each participate as a provider. Provided program,
A user profile information storage step (306) for storing user profile information including at least identifiers of a plurality of users;
Community member information in which each of the community identifiers is associated with at least an identifier of zero or more users belonging to the community, and a mode in which each user belonging to the community receives the provided information / service. Community member information storage step (316) for storing
Based on the stored user profile information and the stored community member information, information provided by the provider in a manner included in the stored community member information for each user participating in the community. An information / service providing program that causes a computer to execute the providing step (50) of providing a service. In response to an offer to provide information and / or services (hereinafter referred to as “information / services”) made to a first community in which one or more users each participate, An information / service providing program that provides information / services to users who wish to provide,
A community profile information storage step (308) in which at least the identifier of the second community that is dynamically created in response to the offer of provision of the information / service is associated with at least a predetermined information / service provision mode;
A community member information storage step (316) for storing community member information in which each of the community identifiers is associated with at least an identifier of zero or more users belonging to the community;
Based on the stored community profile information and the stored community member information, the participation is provided according to the predetermined information / service provision mode for a user who requests participation in the second community. An information / service providing program that controls whether or not the user who requested the information can participate and provides the information / service to the computer. An information sharing program for sharing information among users in a community where one or more users each participate,
A user profile information storage step (306) for storing user profile information including at least identifiers of a plurality of users;
A community that stores community member information in which each identifier of the community is associated with at least an identifier of zero or more users belonging to the community, and a mode in which each user belonging to the community shares the information Member information storage step (316);
A sharing step of sharing information in a manner included in the stored community member information among users participating in the community based on the stored user profile information and the stored community member information (50) An information sharing program for causing a computer to execute and.

Images