JP2009199368A - Group cooperation system, group cooperation method and group cooperation program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To cooperate user's state information and shared information between different SNSs. <P>SOLUTION: A group cooperation system includes: a group server for providing preset different social networking services 100, 200 which are mutually connected via a communication network and; a plurality of user terminals which are mutually connected through the group server. A user group for allowing the user terminals to mutually perform information cooperation through respective social networking services 100, 200 is set. The group server includes a means for determining whether the information cooperation to be performed by the user terminals through the different social networking services 100, 200 is to be allowed or not and repeating the information cooperation, and a means for setting the user group for performing the information cooperation through the different social network services. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to data collaboration technology for user groups formed via a network, and more particularly to a data collaboration technique in a social networking system.

  In recent years, a social networking system (SNS) has been used to activate communication and share information within a company. In SNS, there is a portal function that manages the relationship between end users and can grasp the daily situations of other users who are closely related to the user.

In addition, the currently operated SNS is used as a means for promoting communication between communities set in the SNS.
For this reason, the SNS is used only for members who use a specific SNS to centrally manage the situation of users who are particularly closely related. For example, an SNS in which all employees in a department within a company are registered. By setting, employees in the department can mutually see the status of other employees via the portal page of SNS.

Furthermore, as SNSs become widespread, in order to make use of the portal function, it has become necessary to realize communication with users of other SNSs through SNSs that are normally used.
For example, in actual work, there are many cases where human relations do not close within one department or within the company, such as joint projects with other departments, joint projects with employees of other companies, or when outsourcing work to subcontractors. It is coming.

However, the current SNS does not have a function for realizing communication with a user who uses a different SNS.
For this reason, when a SNS is used in units of a company or a department within a company, in a project performed between companies or departments using different SNSs, the portal function of the SNS currently operated is used. However, it is difficult to apply, and it is necessary to use another method such as newly setting an SNS.

  As a related technique for this, a method is disclosed in which profile information and presence information between groups are matched and approved, and a user group (corresponding to a community) invites another user group. (Patent Document 1).

  Also, a technique for providing profile information of users in the local community to other communities is disclosed as a related technology (Patent Document 2).

JP 2005-284495 A JP 2007-193611 A

  However, the related information disclosed in Patent Documents 1 and 2 is not assumed to be linked between a plurality of different SNSs, and the data structure is a structure that cannot be linked between SNSs. There was an inconvenience.

  For this reason, for example, when performing joint projects with other departments or outsourcing work to other companies, as a system for grasping the situation separately from the SNS that is normally used, another SNS can be constructed, It is necessary to construct a system for sharing information, which may cause inconvenience that it takes man-hours and time to grasp the situation and prepare for information sharing.

  Furthermore, since information cannot be provided to users who can disclose other SNS information, the status of users who are closely related to other departments or other companies can be grasped centrally using the portal function of SNS that is normally used. There is an inconvenience that can not be done.

[Object of invention]
It is an object of the present invention to provide a group linkage system, a group linkage method, and a group linkage program that improve the inconveniences of the above-described conventional example and effectively link situations and information between users of different SNSs. To do.

  In order to achieve the above object, a group cooperation system according to the present invention is connected to a group server that is connected to each other via a communication network and provides different social networking services that are set in advance. A plurality of user terminals, and a group cooperation system for setting user groups in which the user terminals mutually perform information cooperation via the social networking services, wherein the group server includes the user terminal It is configured to determine whether to allow information cooperation performed through different social networking services and to relay the information cooperation, and to set a user group through the different social networking services. Yes.

  In addition, the group cooperation method according to the present invention includes a group server that is mutually connected via a communication network and provides different social networking services that are set in advance, a user terminal that is set in the group server, and the common group A group cooperation method comprising a user terminal set in a server as a user group and linking information between user groups set in different group servers, wherein the group server is set in another group server A communication request receiving step for receiving a communication request sent from a communication permission determining step for determining whether or not to allow the communication request based on a communication permission policy indicating a preset condition for allowing communication; and When communication is permitted, the user terminal that is the communication request is connected to the same user. Is characterized in that a group collaboration allowable setting step of setting as THE group.

  Furthermore, the group cooperation program according to the present invention includes a group server that is connected to each other via a communication network and provides different social networking services that are set in advance, a user terminal that is set in the group server, and the common group It is a group cooperation program for providing user terminals set on a server as user groups and for linking information between user groups set on different group servers, and sent from a user terminal set on another group server A communication request reception function for receiving a communication request, a communication permission determination function for determining whether or not to allow the communication request based on a communication permission policy that indicates a preset condition for allowing communication, and the communication is permitted. If the user terminal of the communication request is It is characterized in that to execute a group linkage allowable setting function of setting as a group in a computer.

  Since the present invention is configured and functions as described above, according to the present invention, a group server that provides different social networking services and a user terminal that is set in the group server and shares information with each other are provided. Storing conditions for allowing mutual communication between the user groups, and providing means for setting and managing user terminals set in the different group servers as the same user group, so that the situation between users of different user groups It is possible to provide a group cooperation system, a group cooperation method, and a group cooperation program that can effectively cooperate with each other and can grasp the status of users of different user groups in a unified manner.

[Embodiment]
Next, the basic configuration content of the embodiment of the present invention will be described.

  As shown in FIG. 1, the group cooperation system of this embodiment includes, for example, an SNS (Social Networking Service) 100 operated by Company A and an SNS 200 operated by Company B, and each SNS belongs to the group cooperation system. It has an X project community 101 and 201 formed by in-house users, and is configured such that data cooperation is performed between the communities 101 and 201.

Further, portal pages 102 and 202 are set in the communities 101 and 201, respectively. As a result, the users AAA and BBB belonging to the respective communities 101 and 201 can browse the portal pages of their participating communities using, for example, a web browser.
The portal page 102 displays the latest writing of the X project and the status of each user BBB in the community 201 of company B, which is the data linkage destination, and the portal page 103 displays the latest writing of the X project and data linkage. The status of each user AAA in the community 101 of company A, which is the destination, is displayed.

Here, each user AAA who is a participant of the community 101 displays the portal page 102 of the community 101, so that the latest writing of the user AAA who is a participant of the X project and the status of the B company user BBB as the data linkage destination Thereby, as shown in FIG. 3, it seems that the user of another SNS is writing and browsing with respect to the community of own SNS.

  In addition, as shown in FIG. 4, the portal pages 102 and 103 of the users participating in the cooperation communities 101 and 201 of the SNSs 100 and 200 are participating in the latest written information of the community and the cooperation community. Other SNS users' diaries and profiles are displayed.

As shown in FIG. 2, the SNS cooperation approval database (DB) 10 which stores the approval information of cooperation between SNSs, and the community database (DB) 20 which stores the information of the community in SNS are provided.
In addition, the SNS cooperation approval setting means 30 for recording the SNS cooperation approval information in the SNS cooperation approval DB 10, the cooperation community setting means 40 for setting the community to be linked, and writing to the portal page of the set community. The community writing browsing means 60 for browsing the written article is connected.

  Further, the community database (DB) 20 includes the cooperative community setting means 40 and the community writing / browsing means 60, community member adding means 50 for setting a member to be added to the community, and other SNS's own SNS. The latest diary providing means 80 for providing the user's diary and the profile information providing means 90 for providing the user's profile information in the own SNS are connected to another SNS.

  Moreover, the said cooperation community setting function 40 displays the community creation function 41 which creates a community in SNS, the community cooperation setting function 42 which sets cooperation with the community of another SNS, and the list of the communities which can be cooperated. It includes a collaborative community list function 43 and a community cooperation setting request processing function 44 which is called from another SNS and performs community cooperation setting.

  Furthermore, the community writing browsing function 60 includes a community writing function 61 for writing an article to its own community, a community writing synchronization function 62 for synchronizing the written article with another SNS community, and a written community. A community browsing function 63 for browsing the article and a community writing request processing function 64 for writing an article to the local community upon receiving a request from another SNS.

  Further, the portal display function 70 includes a community latest writing display function 71 for displaying the latest writing of the community on the portal page of each user, a diary latest writing display function 72 for displaying the latest writing of the diary of friends and community members, And a profile display function 73 for displaying profiles of community members.

  This will be described in detail below.

  The SNS cooperation approval DB 10 of the SNS 100 of company A has an SNS cooperation approval table (FIG. 5) stored in advance. In the SNS cooperation approval table, an SNS ID, an SNS name, and an SNS URL that uniquely identify SNS that can be cooperated are recorded.

  The SNS cooperation approval setting unit 30 displays a SNS cooperation approval setting page set in the SNS cooperation approval DB 10 on an output device (for example, a display) of a user AAA (hereinafter referred to as “user”). And an SNS information request function for transmitting an SNS information request to the input URL, and an SNS information response function for returning an SNS ID and an SNS name in response to the sent SNS information request.

  Further, the SNS cooperation approval setting means 30 includes an input SNS information determination function for determining whether or not the acquired SNS ID and SNS name are equal to the input SNS ID and SNS name, and the input SNS ID and When it is confirmed that the SNS name is the same as the SNS name, an SNS information registration function for registering the SNS ID, SNS name, and URL of the SNS 200 in the SNS cooperation approval table of the SNS cooperation approval DB 10 is provided.

  Accordingly, the SNS 100 registers the SNS ID, the SNS name, and the SNS URL in the SNS cooperation approval table with other SNSs, thereby converting the cooperation between the SNSs into data. be able to.

  The cooperation community setting means 40 displays a community creation page on an output device such as a community creator's display, and receives a community creation page display function for receiving an input as to whether or not to cooperate with a community name and another community. It has a community ID information acquisition function for acquiring community ID information of an existing community from a community table in the community DB 20 storing community information.

  The cooperation community setting means 40 also registers the community ID, the community name input by the community creator, linkage information indicating the presence or absence of cooperation, and the community creator ID as an owner member ID in the community table. Has a registration function.

  The community cooperation setting function 42 includes an approved SNS information acquisition function that acquires cooperation-approved SNS information from the SNS cooperation approval DB 10, and an SNS name list that generates a list of SNS names of the acquired cooperation-approved SNS information. It has a generation function, a community cooperation setting page display function for displaying a community cooperation setting page, and a function for calling a collaborative community list function of another SNS.

Moreover, the community cooperation setting function 42 acquires the community in which the cooperation flag is set to cooperation from the community table of its own SNS and calls the SNS of the caller when the cooperation community list function is called from another SNS. A cooperative community list transmission function for transmitting the community list to the network and a cooperative community list display function for displaying the received cooperative community list on the page.
Furthermore, when it is determined that there is no community of the same SNS, the community cooperation setting function 42 is configured to register a community ID of a different community as a cooperation destination community ID in the cooperation community table, and a community of a cooperation destination community of a different SNS. A function for calling the cooperation setting request processing function 44;

  The collaborative community list function 43 tries to newly collaborate with a collaborated community information acquisition function that acquires information of a collaborated community from a collaborative community table provided in advance, and an SNS to which a community that has already collaborated belongs. The same SNS determination function for determining whether or not there is the same SNS as the SNS to which a given community belongs is provided.

Here, since it is generally considered that there is only one community in the SNS in the SNS, in the present invention, as shown in FIG. It is not possible to cooperate with other communities.
Further, the cooperation rule of the present invention enables one community to cooperate with a plurality of communities in other different SNSs.

  The community cooperation setting request processing function 44 has a function of registering the community ID of the calling community as a cooperation destination community ID in the cooperation community table when called from a community of a different SNS.

The community member addition means 50 has a function of displaying a community member addition page.
Here, when called by the administrator, the community member addition means 50 displays a list of members acquired from the SNS member table on the community member addition page, as shown in FIG. The administrator selects a member to be registered through this member list.
Further, when the member himself / herself registers, the community member addition page is displayed in a state where the member himself / herself is selected as a registered member.

Further, as shown in FIG. 14, the community member adding means 50 has a member ID registration function for registering a member ID uniquely determined in the SNS 100 via the community member addition page in the community member table.
As shown in FIG. 15, the community member adding means 50 has a community ID additional registration function for registering the community ID of the added community in the participating community table of the user added as a member.

The community writing function 61 has a community writing page display function for displaying a community writing page set in advance. Thereby, the community writing function 61 receives the subject and content of the written article.

The community writing function 61 has a writing ID acquisition function for acquiring a list of writing IDs of existing writings from a writing table preset in the community DB 20. The write table accepts registration of write ID, write member ID, write member SNS ID, write date and time, subject, and contents. As a result, the registered contents (writing ID, writing member ID, writing member SNS ID, writing date and time, subject, and contents) can be viewed by all members of the community in which writing has been performed.

  The community writing synchronization function 62 includes a linked community presence / absence determination function that determines whether or not a community in which writing has been performed has a linked community, and a linked community table that includes a linked community in which the writing has been performed. A self-community ID column has a cooperative community list generation function that acquires all data in a row that is the ID of a community in which writing has been performed, and generates a list of cooperative communities.

The community write synchronization function 62 also selects from the linked community list one of the communities that have not yet completed synchronous write, and a community write request processing function 64 of the SNS to which the selected community belongs. It has a function to call.
Further, the community write synchronization function 62 has an argument transmission function for transmitting the write ID, write member ID, member SNS ID, write date / time, subject, and contents as arguments to the called community write request processing function 64.

Further, the community write request processing function 64 has an argument registration function for registering a write ID, a write member ID, a member SNS ID, a write date / time, a subject, and contents in a write table of the community in cooperation.
The community write request processing function 64 has a write completion determination function for determining whether writing has been completed for all communities in the linked community list.

  The community browsing function 63 is executed in response to a request for browsing the community writing page by the user, and the community member list acquiring function for acquiring the community member list from the community member table and the member ID of the user who has requested browsing are included in the community member list. It has a browsing user determination function for determining whether or not it is included.

  In addition, the community browsing function 63 displays a writing list acquisition function for acquiring a writing list from a community writing table, a community browsing page, and a writing list when the member ID of the user who has requested browsing is included in the community member list. A browsing page display function is provided.

Further, the community browsing function 63 includes a local SNS ID determination function for determining whether or not the SNS ID of the article selected by the user is the ID of the local SNS, and the SNS ID of the selected article is the local SNS. It has a member name search / acquisition function for retrieving a member name by retrieving a row having a matching write member ID from the member table of its own SNS.
The community browsing function 63 has a function of calling (starting) the SNS profile providing means 90 indicated by the SNS ID when the SNS ID of the selected article is not the SNS ID.

  The profile providing function 90 receives the target member ID and the cooperative community ID, and determines whether or not the target member ID is included in the community member table of the community specified by the cooperative community ID. Judgment function is provided.

Also, the profile providing function 90 determines whether or not the member permits the profile publication to the cooperative community based on the profile table shown in FIG. 21 when the member ID is included in the community member table. It has a function.
Further, the profile providing function 90 has a profile transmission function for transmitting profile information including a member name to the calling SNS when profile publication is permitted.
Further, the profile providing means 90 has a function of displaying a function subject, content, and member name for acquiring a member name of the writing member ID.

The community latest writing display function 71 is executed when a user requests his / her portal page, and a community list acquisition function for acquiring a community list in which the user participates from a participation community table, and selection of a community by the user And a write list acquisition function for acquiring a write list of the community from the write table.
In addition, the community latest writing display function 71 has a writing ID determination function for determining whether or not the SNS ID of the selected writing is the own SNS, and the SNS ID of the own SNS when the selected writing SNS ID is the own SNS. It has a member name search / acquisition function for retrieving a member name by retrieving a row having a matching write member ID from the member table.

  If the selected SNS ID of the writing is not the local SNS, the community latest writing display function 71 calls the SNS profile providing unit 90 indicated by the SNS ID, and the member name of the writing member ID from the profile providing unit 90. Is acquired, and a write member name acquisition / display function for displaying the write date / time, subject, and acquired member name is provided.

  Further, the community latest writing display function 71 includes a writing display determination function for determining whether or not display has been completed for all writings in the acquired writing list, and a list when all displays have not been completed. The function to determine whether or not the SNS ID is the local SNS, and when all the displays are completed, the latest write display is performed for all the communities listed in the community list. It has a latest writing display determination function for determining whether or not it has been received. Here, the community latest writing display function 71 ends the process when it is determined that the latest writing display has been performed for all the communities.

  The diary latest writing display function 72 is executed when the user requests his / her portal page, and acquires a list of communities in which the user participates from the participating community table, and a community of the selected community It has a member list acquisition function for acquiring a member list from the member table and a local SNS ID determination function for determining whether the SNS ID of the SNS to which the member selected by the user belongs is the local SNS or another SNS.

  When the SNS ID of the SNS to which the selected member belongs is another SNS, the diary latest writing display function 72 is selected by the latest diary providing means calling function for calling the latest diary providing means 80 of the SNS indicated by the SNS ID and the user. When the SNS ID of the SNS to which the member belongs is the own SNS, the latest diary is acquired from the diary table (FIG. 24) of the selected member and the acquired latest diary is displayed. I have.

  Next, the latest diary display function 72 displays the latest diary display determination function for determining whether or not the display of the latest diary has been completed for all members of the member list, and the display of the latest diary for all members has been completed The latest diary display completion determination function for determining whether or not the latest diary display has been completed for all the communities in the community list.

  When the latest diary providing function 80 receives a target member ID and a cooperative community ID from another SNS, the community for determining whether or not this member ID is included in the community member table indicated by the cooperative community ID A member ID determination function, and a member latest diary acquisition function that acquires the latest diary of the member indicated by the member ID from the diary table when the received member ID is included in the community member table indicated by the cooperation community ID; And a diary publishing permission judging function for judging whether or not the collaborative community is allowed to publish the diary based on the latest diary publishing range.

  The profile display function 73 is executed when the user requests a portal page, and a participation community table acquisition function for acquiring a list of communities in which the user participates from the participation community table, and community members of the community selected by the user It has a member list acquisition function for acquiring a member list from the table and a local SNS ID determination function for determining whether the SNS ID of the SNS to which the member selected by the user belongs is the local SNS or another SNS.

  The profile display function 73 calls the profile providing function 90 of the SNS indicated by the SNS ID when the SNS ID of the SNS to which the member selected by the user belongs is determined to be another SNS. When the SNS ID of the SNS to which the member selected by the user and the member selected by the user belongs is the own SNS, the profile information is acquired from the profile table (FIG. 21) of the selected member and the acquired profile information is displayed. It has a profile information acquisition display function.

  Further, the profile display function 73 has a profile display determination function for determining whether or not the profile display has been completed for all members of the member list, and the profile display has been completed for all members of the member list. A community profile display completion determination function that determines whether or not profile display has been completed for all communities in the community list.

[Description of Operation of Embodiment]
Next, the overall operation of this embodiment will be described.

  First, whether a communication request sent from a user terminal set in another group server is received (communication request receiving step), and the communication request is allowed based on a preset communication permission policy indicating a condition for allowing communication It is determined whether or not (communication allowance determination step). Next, when the communication is permitted, the communication request source user terminal is set as the same user group (group cooperation permission setting step). Next, when the information shared in each user group is changed, the group server notifies the user terminal set as the same user group of the information change content (information synchronization notification step).

  Here, regarding the communication request reception step, the communication permission determination step, the group cooperation permission setting step, and the information synchronization notification step, the execution contents may be programmed and executed by a computer.

  Next, in performing data linkage from the SNS (here, SNS 100) to another SNS (here, SNS 200), in the SNS linkage approval table of the SNS 100, the SNS ID of the SNS 200 that is the data linkage destination, the SNS name, and the SNS A data registration procedure for registering the URL will be described with reference to the flowchart of FIG.

  First, the SNS cooperation approval setting means 30 displays an SNS cooperation approval setting page for the administrator of the SNS 100 (step S101). The administrator of the SNS 100 inputs the SNS ID, SNS name, and URL of the SNS 200 of company B on the displayed SNS cooperation approval setting page (step S102). Next, an SNS information request is transmitted to the input URL, and the SNS ID and SNS name of the SNS 200 are acquired. The acquired SNS ID and SNS name are equal to the input SNS ID and SNS name. This is confirmed (step S103). Next, the SNS ID, SNS name, and URL of the SNS 200 are registered in the SNS cooperation approval table of the SNS cooperation approval DB 10 (step S104), and the process ends.

  Next, a procedure for creating a community between the SNS 100 of company A and the SNS 200 of company B will be described. A community is created in each SNS by the procedure shown in FIG.

First, the cooperation community setting means 40 displays a community creation page for the community creator (step S111). The community creator inputs the community name and whether or not to cooperate with another community (step S112).
As shown in FIG. 8, the cooperative community setting unit 40 acquires community ID information of an existing community from the community table in the community DB 20 that stores the information of the existing community (step S113).

Next, a new community ID is determined so as not to overlap with the acquired existing community ID (step S114). The community ID may be a numeric value or a character string.
Next, the community ID, the community name input by the community creator, information on presence / absence of cooperation, and the community creator ID are stored in the community table as owner member IDs (step S115).

  Next, a procedure for linking a community 101 created in advance with another community 201 will be described with reference to the flowchart of FIG.

First, the community creator calls the community cooperation setting function 42 of the community 101 for which cooperation setting is desired, and the community cooperation setting function 42 acquires the SNS information that has been approved for cooperation from the SNS cooperation approval DB 10 of the company A SNS 100 (step S121).
Next, the community cooperation setting function 42 generates a list of SNS names of the acquired cooperation approved SNS information and displays a community cooperation setting page (step S122). The community creator selects an SNS of company B having a community to be linked from among the displayed SNS names (step S123).
Next, the community cooperation setting function 42 of the company A calls the cooperative community list function 43 of the SNS of the company B (step S124). The called B company cooperable community list function 43 acquires all the communities whose cooperation flags are linked from the community table of its own SNS, and sends a list to the A department SNS (step S125).
A company SNS displays the received cooperation community list on a page (step S126). Next, the community creator selects a community to be linked from the list (step S127).

  Next, as shown in FIG. 10, the collaborative community list function 43 of the company A SNS obtains information on the community that the community 101 has already cooperated from the created community community table of the community 101 (step S128). The collaborative community list function 43 determines whether or not the B company SNS 200 to which the community 201 to be newly linked belongs has the same SNS among the SNSs to which the already linked communities belong (step S129). . Here, if there is the same SNS, the process is terminated, and the cooperation with the selected community 201 is not set.

Here, since it is generally considered that there is only one community in the SNS in the SNS, in the present invention, as shown in FIG. 11, a plurality of communities in which one community is in another same SNS as shown in FIG. It is not possible to cooperate with other communities.
Further, the cooperation rule of the present invention enables one community to cooperate with a plurality of communities in other separate SNSs.

Next, the community cooperation setting function 42 registers the community ID of the community 201 as a cooperation destination community ID in the cooperation community table when the B company SNS 200 does not exist in the SNS to which the already cooperated community belongs (step S130). Then, the community cooperation setting request processing function 44 of the community 201 of the company B SNS 200 which is the cooperation destination community is called (step S131).
Next, the community cooperation setting request processing function 44 of the company B SNS 200 registers the community ID of the community 101 of the company A SNS 100 as a cooperation destination community ID in the cooperation community table of the community 201 to be cooperated (step S132).

  Next, the procedure for registering members in the community will be described based on the flowchart of FIG.

  First, the community creator (administrator) or community member calls the community member adding means 50 of the community 101 to which a member is desired to be added after community cooperation, whereby a community member addition page is displayed (step S141).

Here, when the administrator calls, a list of members acquired from the member table of SNS A is displayed as shown in FIG. Here, the administrator selects a member to be registered.
Further, when the member himself / herself registers, the community member addition page is displayed in a state where the member himself / herself is selected as a registered member.

Next, as shown in FIG. 14, the community member adding means 50 registers a member ID uniquely determined in the SNS 100 via the community member adding page in the community member table (step S142).
Next, as shown in FIG. 15, the community member adding means 50 registers the community ID of the added community in the participating community table of the user added as a member (step S143).

  Next, an operation when writing is performed in the community (community writing page) will be described based on the flowchart of FIG.

First, a community member calls a community writing function 61 by making a write request in a community where writing is desired. Thereby, the community writing page is displayed (step S151). Next, community members (hereinafter referred to as “members who write”) input the subject and content of the article to be written (step S152).
Next, a list of existing write IDs is acquired from a write table (FIG. 17) preset in the community DB 20 (step S153). Here, the member who performs writing sets the writing ID of the new writing to be unique (step S154). Write ID, write member ID, write member SNS ID, write date and time, subject, and contents are registered in the write table (step S155).

  As a result, the written contents (write ID, write member ID, write member SNS ID, write date / time, subject, and contents) can be viewed by all members of the written community.

  Next, a procedure for synchronizing writing to the community with the cooperative community (synchronous writing) will be described with reference to the flowchart of FIG.

  When the community write synchronization function 62 is called after completion of writing to the community (step S155), first, the community write synchronization function 62 determines whether or not there is a cooperative community in the community in which writing has been performed. This is performed (step S161). Here, if there is no linked community, the process is terminated.

If there is a linked community in the community in which writing has been performed, all data in the row in which the local community ID column is the ID of the community in which writing has been performed is acquired from the linked community table, and a list of linked communities is generated (step S162).
Next, one of the communities for which synchronous writing has not yet been completed is selected from the linked community list (step S163). If the selected community is the SNS 200, the community write request processing function 64 of the SNS 200 is called (step S164).

  Here, the community write synchronization function 62 passes the write ID, write member ID, member SNS ID, write date / time, subject, and contents as arguments to the community write request processing function 64. The community write request processing function 64 of the called SNS 200 registers the write ID, write member ID, member SNS ID, write date / time, subject, and contents in the write table of the associated community (step S165).

  Next, the community write synchronization function 62 of the caller SNS 100 determines whether writing has been completed for all the communities in the linked community list. If not, the process returns to step S163, and the remaining communities are set. select. On the other hand, if writing has been completed for all the communities in the linked community list, the process ends (step S166).

  Next, the browsing operation for community writing (community writing page) will be described based on the flowchart of FIG.

When the user requests browsing of the community writing page, the community browsing function 63 is called, and a community member list is acquired from the community member table (step S171). Next, it is determined whether or not the member ID of the user who has requested browsing is included in the community member list (step S172). If it is not included, the process ends.
Here, if the member ID of the user who has requested browsing is included in the community member list, the writing list is acquired from the community writing table (step S173). Next, a community browsing page is displayed, and a list of writing is also displayed therein (step S174).

The user selects an article to be viewed from the writing list (step S175). It is determined whether the SNS ID of the selected article is the ID of its own SNS (step S176).
Here, when the SNS ID of the selected article is the local SNS, the line where the writing member ID matches is searched from the member table of the local SNS, and the member name is acquired (step S177).
On the other hand, if it is not the local SNS, the SNS profile providing means 90 indicated by the SNS ID is called, and the profile providing means 90 acquires the member name of the writing member ID (step S178). Next, the profile providing unit 90 displays the subject, contents, and member name (step S179).

  Thereby, the user can browse the community writing page.

  Next, the operation in which the profile providing function 90 provides the profile information of the own SNS member to another SNS will be described based on the flowchart of FIG.

  First, the profile providing unit 90 receives a member ID and a cooperation community ID that are targets for profile information acquisition (step S181). It is determined whether or not the target member ID is included in the community member table of the community specified by the cooperation community ID (step S182). If no member ID is included, the process ends.

Next, when the member ID is included in the community member table, it is confirmed in the profile table shown in FIG. 21 whether or not the member permits the linked community to disclose the profile (step S183). Here, if the profile publication is not permitted, the process is terminated.
Here, when the profile publication is permitted, the profile information including the member name is provided to the calling SNS (step S184), and the process is terminated.

  Thereby, the user can acquire and browse the profile information of the member who belongs to SNS different from self SNS.

  Next, a procedure for displaying the latest writing information to the community on the user's portal page will be described based on the flowchart of FIG.

First, the user calls the community latest writing display function 71 by requesting his / her portal page (step S191). When the community latest writing function 71 is executed, the user acquires a community list in which the user is participating from the participating community table (step S192).
Next, when the user selects a community from the list, a writing list of the community is acquired from the writing table (step S193).
Here, the number of items to be acquired as a list is determined based on preset contents such as a new one from a new date and time.

Next, in response to the user selecting one write from the acquired list of latest writes, the community latest write display function 71 determines whether or not the SNS ID of the selected write is its own SNS ( Step S194). When the SNS ID is the local SNS, the community latest written display function 71 searches the community member table of the local SNS for a line having the same written member ID, and acquires a member name (step S195).
When the SNS ID is not the local SNS, the community latest writing display function 71 is called by the SNS profile providing unit 90 indicated by the SNS ID, and acquires the member name of the writing member ID from the profile providing unit 90 (step S196). The date / time, subject, and acquired member name are displayed (step S197).

Next, it is determined whether or not the display has been completed for all the writings in the writing list acquired in step S193 (step S198). Here, when not finished, one other writing is selected from the list, and it is determined whether or not the SNS ID is the local SNS (step S194). On the other hand, when the display is completed, it is determined whether or not the latest writing display has been performed for all the communities listed in the community list (step S199). If the display has not been completed, the process is repeated from step S193.
When it is determined that the latest writing display has been performed for all the communities, the process is terminated.

  Next, a procedure for displaying the latest diary of other SNS users participating in the community in which the user is participating in the user portal page will be described based on the flowchart of FIG.

First, when the user requests his / her portal page, the diary latest writing display function 72 is called, and a list of communities in which the user participates is acquired from the participating community table (step S201). Next, a community is selected from the list of acquired communities (step S202). A member list is acquired from the community member table of the selected community (step S203).
Next, the user selects one member from the member list (step S204), and the diary latest writing display function 72 determines whether the SNS ID of the SNS to which the selected member belongs is the own SNS or another SNS. This is performed (step S205).

  If the SNS ID of the SNS to which the selected member belongs is another SNS, the diary latest writing display function 72 calls the SNS latest diary providing means 80 indicated by the SNS ID (step S206). When the SNS ID of the SNS to which the member selected by the user belongs is the own SNS, the diary latest writing display function 72 acquires the latest diary from the selected member diary table (FIG. 24) (step S207). ), And displays the acquired latest diary (step S208). Next, it is determined whether or not the display of the latest diary has been completed for all members in the member list (step S209).

If the latest diary display has not been completed for all members in the member list, the process is repeated from step S204.
When the display of the latest diary is completed, it is confirmed whether the latest diary display is completed for all the communities in the community list (step S210). If not completed, the process is repeated from step S202, and if the latest diary display has been completed for all communities in the community list, the process ends.

  Thereby, the latest diary of the user who participates in the community in which the user is participating in the user's portal page and belongs to another SNS is displayed, and thus the user can browse the latest diary.

  Here, a procedure in which the latest diary providing unit 80 provides the latest diary of the SNS member to another SNS will be described based on the flowchart of FIG.

  First, the latest diary providing unit 80 receives a target member ID and a cooperative community ID from another SNS (step S221). It is determined whether or not this member ID is included in the community member table indicated by the cooperation community ID (step S222). Here, if it is not included, the process is terminated.

If the received member ID is included in the community member table indicated by the cooperative community ID, the latest diary of the member indicated by the member ID is acquired from the diary table (step S223). Next, based on a preset range of the latest diary, it is determined whether or not the collaborative community permits the diary publication (step S224).
Here, if the collaborative community does not permit the diary publication, the process ends. If the collaborative community permits the diary publication, the latest diary is provided to the SNS that has called (step S225), and the process is terminated. To do.

  Next, a procedure for displaying the profile information of users of other SNS participating in the community in which the user is participating on the user's portal page will be described based on the flowchart of FIG.

First, when the user requests a portal page, the profile display function 73 is called, and thereby, a list of communities in which the user participates is acquired from the participating community table (step S231).
Next, the user selects a community from the acquired list (step S232), and acquires a member list from the community member table of the selected community (step S233).

Next, the user selects one member from the acquired member list (step S234), and determines whether the SNS ID of the SNS to which the selected member belongs is the local SNS or another SNS (step S235).
Here, when the SNS ID of the SNS to which the selected member belongs is determined to be another SNS, the SNS profile providing function 90 indicated by the SNS ID is called (step S236).

If the SNS ID of the SNS to which the selected member belongs is the own SNS, profile information is acquired from the profile table (FIG. 21) of the selected member (step S237), and the acquired profile is displayed (step S237). Step S238).
Next, the profile display function 73 confirms whether or not the profile display has been completed for all members in the member list (step S239). If the profile display has not been completed for all members in the member list, the process is repeated from step S234.

  If the profile display is completed for all members in the member list, it is determined whether the profile display is completed for all communities in the community list (step S240). Repeat from S232. If completed, exit.

[Modification]
Here, a modified example of the present embodiment will be described.
As shown in FIG. 27, this modified example is different from the above embodiment in that a linked SNS list system 300 that centrally manages linked SNS information is connected to the SNSs 100 and 200. Here, the same parts as those in the above-described embodiment are denoted by the same reference numerals.

Here, in performing data linkage from the own SNS (here, SNS 100) to another SNS (here, SNS 200), the SNS ID of the SNS 200 that is the data linkage destination, the SNS name, and the SNS are included in the SNS linkage approval table of the SNS 100. A data registration procedure for registering the URL will be described with reference to the flowchart of FIG.
In this case, the administrator of each SNS requests the operator of the linked SNS list system 300 to register information about the SNS in advance.

First, the SNS administrator accesses the linked SNS list system 300 and acquires a list of SNSs that can be linked from the linked SNS list system 300 (step S241). Here, a list of possible SNSs is displayed on the SNS cooperation approval setting page (step S242).
Next, the SNS administrator selects an SNS for which cooperation is desired from the list (step S243). The SNS ID, SNS name, and URL of the SNS 200 are registered in the SNS cooperation approval DB 10 (step S244), and the process ends.

  Thereby, the administrator of the SNS 100 can eliminate the need to input the SNS ID, SNS name, and URL of the SNS 200 of the company B that is the cooperation destination, and can more easily set the cooperation SNS.

As described above, in the present embodiment and the modification, the conventional SNS is used for activating communication between users belonging to one SNS, whereas in the present embodiment, the communication area by the SNS is changed to another. It is possible to manage the situation of other SNS users in a unified manner.

Also,
It is possible to set up a community with a data structure that can link the situation and information with users in other departments and other companies in the SNS within the company and in its own department, and similarly data in SNS of other companies and other departments It is possible to set a community with a data structure that can be linked.

  In addition, by the function to link the data between communities set in each SNS, the writing information of the community of other departments and other companies is synchronized with the community established in the SNS of the own department, and in the SNS of the own department. By browsing the community, information on other departments of the same theme and communities of other companies can also be grasped.

Furthermore, in this embodiment, by using a data structure in which members belonging to the data-linked community are handled as members of the community in the SNS that is normally used, the portal function of the SNS that is normally used is used, It is possible to centrally manage the status of users (employees) in other departments.
In addition, in the present embodiment, information that allows data exchange between a plurality of SNSs is added to the data structure that the SNS has so far, and a procedure for data linkage is provided, so that different SNSs can be exchanged. It is possible to build an environment where communication can be performed smoothly. This allows communication between two or more different SNSs.

Furthermore, since an external system is not constructed other than the SNS, it is possible to reduce the amount of work and costs in operation work such as system construction work and user registration work.
Moreover, the writing and profile of the member of other SNS are displayed on the portal function of SNS, and it can grasp | ascertain the condition of the user of other SNS centrally.

  The present invention can be applied to a scene where communication between different communities is required, such as a joint project between companies or departments, or exchange by a group of a plurality of hobbies.

It is a schematic block diagram which shows one implementation mobile of the group cooperation system by this invention. It is a block diagram which shows an example of the SNS community cooperation program in the group cooperation system disclosed in FIG. It is explanatory drawing which shows an example of the input page in the group cooperation system disclosed in FIG. It is explanatory drawing which shows an example of the portal page in the group cooperation system disclosed in FIG. It is explanatory drawing which shows an example of the SNS cooperation approval table in the group cooperation system disclosed in FIG. It is a flowchart which shows the operation | movement which registers the information of the data cooperation destination SNS in the group cooperation system disclosed in FIG. It is a flowchart which shows the operation | movement which creates the community in the group cooperation system disclosed in FIG. It is explanatory drawing which shows an example of the community table in the group cooperation system disclosed in FIG. 2 is a flowchart illustrating an operation in which a community in the group cooperation system disclosed in FIG. 1 cooperates with another community 201. It is explanatory drawing which shows an example of the cooperation community table in the group cooperation system disclosed in FIG. It is explanatory drawing which shows the cooperation rule of the community in the group cooperation system disclosed in FIG. It is a flowchart which shows the operation | movement which registers a member in the community in the group cooperation system disclosed in FIG. It is explanatory drawing which shows an example of the member table of SNS in the group cooperation system disclosed in FIG. It is explanatory drawing which shows an example of the member table of the community in the group cooperation system disclosed in FIG. It is explanatory drawing which shows an example of the member table of the participating community in the group cooperation system disclosed in FIG. It is a flowchart which shows the operation | movement by which writing is performed in the community writing page in the group cooperation system disclosed in FIG. Write table preset in the community DB 20 It is a flowchart which shows the operation | movement which synchronizes writing to the community with respect to a cooperation community in the group cooperation system disclosed in FIG. It is a flowchart which shows the browsing operation | movement with respect to the community writing page in the group cooperation system disclosed in FIG. It is a flowchart which shows the operation | movement which provides the other SNS with the profile information of the own SNS member in the group cooperation system disclosed in FIG. It is explanatory drawing which shows an example of the profile table in the group cooperation system disclosed in FIG. It is a flowchart which shows the operation | movement which displays the latest writing information to a community on the user's portal page in the group cooperation system disclosed in FIG. It is a flowchart which shows the operation | movement which displays the newest diary of the other SNS user who has participated in the user community in the group cooperation system disclosed in FIG. It is explanatory drawing which shows an example of the user's diary table in the group cooperation system disclosed in FIG. It is a flowchart which shows the operation | movement which provides the other SNS member with the newest diary of the SNS member in the group cooperation system disclosed in FIG. It is a flowchart which shows the operation | movement which displays the user's profile information in the group cooperation system disclosed in FIG. It is a schematic block diagram which shows one Embodiment of the group cooperation system by this invention. It is a flowchart which shows the operation | movement which registers the information of the data cooperation destination SNS in the group cooperation system disclosed in FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 SNS cooperation approval database 20 Community database 30 SNS cooperation approval setting means 40 Cooperation community setting means 41 Community creation function 42 Community cooperation setting function 43 Linkable community list function 44 Community cooperation setting request processing function 50 Community member addition means 60 Community write view Means 61 Community writing function 62 Community writing synchronization function 63 Community browsing function 64 Community writing request processing function 70 Portal display means 71 Community latest writing display function 72 Diary latest writing display function 73 Profile display function 80 Latest diary providing means 90 Profile providing means 100 SNS of company A
101, 201 Community 200 SNS of company B
102 User AAA portal page 202 User BBB portal page

Claims (11)

A plurality of group servers connected to each other via a communication network and providing different social networking services set in advance, and a plurality of user terminals connected via the group servers, A group cooperation system for setting user groups for mutual information cooperation through social networking services,
The group server determines whether or not the user terminal allows information cooperation performed through the different social networking services and relays the information cooperation; and a user group via the different social networking services. A group cooperation system comprising a setting unit. In the group cooperation system according to claim 1,
Each of the group servers includes an information cooperation condition storage unit that stores a preset information cooperation policy indicating the information cooperation permission condition, and whether or not to allow the information cooperation by functioning based on the information cooperation policy. A group linkage system comprising an information linkage control means for controlling. In the group cooperation system according to claim 1,
The group server notifies the user information preset in each user terminal that uses the social networking service of the group server to the user group that uses the other social networking service and the user information notification that notifies each user terminal. A group collaboration system characterized by having functions. In the group cooperation system according to claim 2,
Each of the group servers is provided with an information synchronization notification means for notifying the user terminal of the set user group of the information change contents when the information linked in each user group is changed. Group linkage system. In the group cooperation system according to claim 4,
Each group server includes a shared information page storage unit that sets and stores a shared information page corresponding to each set user group, and each user terminal of each user group browses the shared information page A group cooperation system comprising shared information writing means for writing together. In the group cooperation system according to claim 3,
Each group server is a group terminal storage means for storing terminal specifying information for specifying user terminals of the set user group, and information performed between user groups set through the different social networking services A group cooperation system comprising an inter-group relay control means for performing relay control as to whether or not cooperation is permitted based on the terminal identification information. In the group cooperation system of the said Claim 5, 6,
A group linkage system comprising a linkage server device connected to the plurality of different group servers and configured to relay information linkage performed between the group servers. A group server that provides different social networking services that are mutually connected via a communication network and that is set in advance, a user terminal that is set in the group server, and a user terminal that is set in the common group server as a user group A group linkage method for linking information between user groups set in different group servers,
The group server accepts the communication request based on a communication request receiving step for receiving a communication request sent from a user terminal set in another group server, and a communication permission policy indicating a preset condition for allowing communication. A communication permission determination step for determining whether or not to perform, and a group cooperation permission setting step for setting the user terminal as the communication request as the same user group when the communication is permitted. Group linkage method. In the group cooperation method according to claim 8,
The group server performs an information synchronization notification step of notifying the user terminal set as the same user group of the information change contents when the information shared in each user group is changed, the group cooperation permission setting step A group cooperation method characterized by being provided after. A group server that provides different social networking services that are mutually connected via a communication network and that is set in advance, a user terminal that is set in the group server, and a user terminal that is set in the common group server as a user group A group linkage program for linking information between user groups set in different group servers,
The group server accepts the communication request based on a communication request receiving function for receiving a communication request sent from a user terminal set in another group server and a communication permission policy indicating a preset condition for allowing communication. Causing a computer to execute a communication permission determination function for determining whether or not to perform, and a group cooperation permission setting function for setting the user terminal that is the communication request as the same user group when the communication is permitted A group collaboration program characterized by In the group cooperation program according to claim 10,
The group server causes the computer to execute an information synchronization notification function for notifying the user terminal set as the same user group of the information change content when the information shared in each user group is changed. A group collaboration program characterized by

Images