JP2013015980A - Sns (social networking service) server for controlling content browsing and feed distribution corresponding to inter-user relevancy and disclosure range set by content owner - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an SNS (Social Networking Service) server for lowering the hurdle of relevancy construction between one user and the other user in an SNS, and for optimizing the disclosure range setting of content and feed reception/distribution setting in the SNS based on unilateral relevancy.SOLUTION: Inter-user relevancy information recorded in an SNS server 10 includes information relating to unilateral relevancy to be formed by one user with respect to the other user. Top page information generation means is configured to generate top page information including a feed to be extracted on the basis of disclosure range information set by the other user for each activity and each content and the inter-user relevancy information among feeds recorded in a feed storage means. Also, content page information generation means is configured to generate content page information on the basis of the content disclosure range information set for each content on the basis of an instruction from the other user.

Description

The present invention relates to a server that controls content browsing and feed distribution according to a relationship between users and a disclosure range set by a content owner in an SNS (Social Networking Service).

Conventionally, a community-type service called a social networking service (hereinafter referred to as “SNS”) that promotes and supports connections between people is known. In SNS, the function of publishing one's profile and photos to members, the diary function that limits the scope of disclosure to specific friends only, or the ability to publish daily events without limitation, bulletin board with a theme such as hobbies and regions The feature is that services such as community functions that can be exchanged on the Internet can be used on the Internet. As one of such SNSs, a website disclosed in Non-Patent Document 1 is known.

Specific contents of services that members can use in this service, such as “Diary”, “Voice”, “Calendar (plan)”, “Photo”, “Video”, etc. One that can view member posts.

For example, in “Diary” content, one member can post a text with an event he / she experienced, or a text with other data such as an image, and when posted, the member has a specific relationship with the member. The feed is displayed with a link on the top page of another member who has. The other member can view the contents of one member's diary by opening the link.

Or, in a “voice” content, when a member posts a casual event in a short sentence without hesitation, it becomes another “voice (= tweet)” that has a specific relationship with the member. Displayed as a feed on the member's top page. Similarly, in other contents (such as “photos” and “moving pictures”), when a new post is made, a feed to that effect is displayed on the top page of another member having a specific relationship with a link.

Here, when posting each content, the user can appropriately set the disclosure range. In the case of the website disclosed in Non-Patent Document 1, other users to be disclosed, such as “open to the whole”, “open to friends of friends”, “open to friends”, “open to specific friends” Can be set for each content.

The above-mentioned “specific relationship” in SNS is usually a bilateral relationship. That is, when one user desires to establish a specific relationship with another user, the one user applies to the other user for the purpose of establishing a specific relationship. Only when another user accepts the application, a specific relationship is established between them.

However, the process of establishing such a “specific relationship” often hinders the user's active communication. That is, there is a psychological obstacle to making such an application for a user who is not necessarily social or active. Even if the acquaintance in the real world is still small, it is not only the user who can always perform the act of applying without hesitation when becoming acquainted through the service.

In SNS, the occurrence of new communication itself leads to the provision of benefits to users, and more users gather, increasing the commercial value.

In this sense, as a technique for generating a relationship with another user, it is conceivable that the method is based on a unilateral relationship instead of the above-described bidirectional relationship. In some cases, communication services that build specific relationships by unilateral relationships are actually provided. In such a service, when one user is interested in another user and desires to establish a specific relationship, a setting of “follow” is performed. Thereby, the entry of the other user is displayed on the main page of the user as a feed.

However, in a communication service that builds a relationship based on such a unilateral relationship, a content contributor cannot set a disclosure range for each content. Although it is possible to respond personally by blocking for each individual user, there is a problem that it is not possible to perform public management on an individual content basis.

The disclosure or feed setting in consideration of unilateral relationship in SNS is mentioned in Patent Document 1. However, it is only about the stage before the establishment of the two-way relationship, and is merely a transitional configuration. Moreover, it only mentions the management regarding the relationship between two users, and does not mention the relationship between three users.

Furthermore, regarding the disclosure range setting of the posted content, the service disclosed in Non-Patent Document 1 discloses the setting of the disclosure target based on the bidirectional relationship, and in Patent Document 2, the friendship relationship is set. A configuration in which a friend level is set for other members and data corresponding to the set friend level is disclosed is disclosed. However, these are all the setting of the disclosure range based on the bilateral relationship, and there is no mention of the setting of the disclosure range in the SNS introducing the unilateral relationship, and further the setting of the feed reception / delivery.

JP 2009-245220 A JP 2008-146246 A

"Social networking service [mixi]", [online], [Search April 1, 2011], Internet <URL: http://mixi.jp/>

Therefore, an object of the present invention is to provide an SNS server capable of optimizing the content disclosure range setting and feed receiving / delivery setting in the SNS based on unilateral relationship.

In order to solve the above problems, the present invention has the following configuration.

(1) User information storage means for recording user attribute information for each user, relationship information storage means for recording relation information of one user with other users, and generation based on instructions from the user Content storage means for recording recorded content, activity storage means for recording user activity, feed generation means for generating a feed in response to data entry in the content storage means or the activity storage means, and the generated Feed storage means for recording a feed, top page information generation means for generating top page information based on an instruction from the one user, and a page related to content of another user based on the instruction from the one user Content page information generating means for generating information, In an SNS server that provides an SNS (Social Networking Service) through a network, the relationship information includes at least information on a unilateral relationship formed by one user with respect to another user, and the top page information generation means includes: , Out of feeds recorded in the feed storage means, at least a disclosure range information set for each activity and content based on an instruction from the other user and a feed extracted based on the relationship information The content page information generating unit generates content page information based on content disclosure range information set for each content based on an instruction from the other user. An SNS server (claim 1).

(2) As the above relationship information,
(A) A relationship in which one user defines another user as a member of the group (b) A relationship in which one user forms a unilateral relationship with another user (c) One user in the other (D) A relationship in which only one user forms a unilateral relationship with one user (e) A relationship between one user and another user There is no one-sided relationship formed directly between them, but a one-sided relationship is formed continuously through a third user (f) One-way relationship is not formed, whether directly or indirectly One or more categories of relationships that are not defined for group members can also be recorded (claim 2).

(3) In addition, as the disclosure range information,
(A) Individual user designation (b) Individual group designation (c) User whose user who is the activity sender or content owner forms a unilateral relationship (d) User who is the activity sender or content owner The user (e) who has formed a unilateral relationship through a third party is recorded as one of the categories of all users (claim 3).

(4) Furthermore, the SNS server according to the present invention provides an extraction based on the disclosure range information and the relationship information on the condition that the one user forms a unilateral relationship with another user. Regardless of whether the other user's top page information is generated based on an instruction from the other user, the one user is generated based on his / her own activity with respect to the other user, and the feed storage means And a forced feed distribution means for generating top page information including the feed recorded in the above (claim 4).

According to the invention of (1) above, it is possible to define the content disclosure range and the range in which the feed is distributed while building the relationship based on the unilateral relationship. It can be expected that the psychological resistance to building the relationship is smaller than before. This facilitates building relationships between users and is expected to improve the frequency of use of the service itself, which inevitably increases traffic and increases its advantage as an advertisement placement target.

Further, if the relationship is established based on the unilateral relationship in the SNS, the degree of intimacy is not appropriately expressed only by the relationship between the two users. Therefore, the determination of whether or not feed distribution or content browsing is possible while grasping the relationship between the related user up to the related other user, in other words, the relationship with the other user via a third party. By making it a factor, it becomes possible to control the user's own information desired by the user. Alternatively, regardless of whether or not the relationship is established, other users viewed from the group are grouped, and this and the above-mentioned one-sided relationship are filtered in a superimposed manner, so that more detailed feed distribution and one's own Content disclosure can be controlled.

Furthermore, by making it possible to set the disclosure range in multiple stages according to individual activities or contents, it is possible to refine the control of the disclosure of the contents.

On the other hand, in the unilateral relationship as described above, one user can perform his / her control to receive the feed of the other user who desires, but the opposite, that is, from one user to another It is not supported for feed delivery to users. Therefore, according to the invention described in (4), it is possible to perform feed distribution of the one user on the top page of another user. Thereby, the opportunity for constructing a unilateral relationship with the one user is born from the other user, and it can be expected that the construction of the relationship between the users is promoted.

In the present invention,
(1) “SNS” means a general definition of “community-type membership system service that promotes and supports the connection between people” or the environment on the Web where the service is provided. However, the present invention is not limited to this, and may not be provided as a service by a specific management entity, and may include, for example, a blog having a communication function such as a comment or a trackback.

(2) “Feed” is notification information generated based on content generation performed by a SNS user, and the user can know from the feed that other users have generated content. Alternatively, the generated content itself can be displayed as a feed.

(3) “One-sided relationship” means a relationship that allows one user to establish a specific other user in SNS without requiring the consent of the other user. By establishing the unilateral relationship, the one user can receive a feed related to the activity or the like that the specific other user has set to public. In addition, among the content posted by the one user, the content that is actively set as the content disclosure range and is not passively set can be browsed when the specific other user makes a browsing request. it can.

(4) “Content” means a diary, a photo, a video, a tweet, etc. posted by the user in the service. When posting these contents, the user can set the disclosure range for each content. Of course, a predetermined release range (for example, “only open to users who have established a one-sided relationship”) is set as the default release range for the user, and it is configured not to ask for a setting for each posting. You can also. The user attribute information set for each user is also included in the content here.

(5) “Activity” refers to a specific activity on the user's service other than posting the above content. For example, “view other users' content and attach comments” “any application in the service” In addition to activities such as “Download” and “Build unilateral relationship with other users”, “Set a flag indicating that it is favorable to other users' content and activities (for example, the above non-patents) In the SNS described in Document 1, “input of“ like! ”)” Is also included. The setting of such a flag can be used as a simple comment indicating that it is favorable even if the motivation for actively posting character information is not available.

(6) “Group” means category classification of another user viewed from one user, and grouping according to a desired purpose is possible. For example, not only aggressive group settings such as “partners of club activities”, “high school classmates” and “baseball enthusiasts”, but also passive group settings such as “do not deliver their own feed” or “do not receive feeds” Is possible. This can be set to exclude such contact with the user in service because other users who feel it is undesirable to interact with the user as the SNS is used.

It is a figure which shows the example of the SNS environment containing the SNS server and terminal device containing the display order control system of this invention. It is the functional block diagram which described the SNS server 10 from the side of the function. It is a conceptual diagram of the information recorded on user attribute DB121. It is a figure which shows an example of the screenshot of the top page of the user terminal of one user. It is a conceptual diagram of the information transmitted when one user performs the input to construct a unilateral relationship with another specific user. It is a conceptual diagram which shows the recording content of relationship information DB. It is a figure which shows an example of the screen displayed on the display means of a user terminal. It is a conceptual diagram of the information regarding the content currently recorded on content DB123. It is a judgment table regarding the relationship recognition between A and C according to the construction situation of the comprehensive unilateral relationship of A, B, and C3. It is a timing chart which shows transmission / reception of information between each node thru | or a process part when a content is contributed. It is a conceptual diagram which shows the activity information recorded on activity DB124. It is a timing chart which shows transfer of the information between each node or a process part until an activity is recorded and the feed based on this is produced | generated. It is a conceptual diagram which shows the feed recorded on generation | occurrence | production feed DB125. It is a timing chart which shows the movement of transmission / reception of information between each node thru | or a process part when one user requests | requires own top page display. It is a flowchart which shows the flow of feed extraction. It is a timing chart which shows the flow of transmission / reception of the information between a node thru | or a process part when one user makes the content display request of another user. It is a flowchart which shows the flow by which display content information is extracted and produced.

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

FIG. 1 is a diagram illustrating an example of an SNS environment including an SNS server and a terminal device including the display order control system of the present invention. The SNS server 10 and each user terminal 30 can be connected to each other via a network 20 such as the Internet. Here, each user terminal 30 has, for example, a PC 31, a mobile phone 32, and a tablet terminal 33, regardless of the type, and can log in to the SNS server 10 (function to connect to the Internet and Web browser). It only has to have.

The SNS server 10 includes a CPU (Central Processing Unit) 10a, a RAM (Random Access Memory) 10b, a ROM (Read Only Memory) 10c, a storage means 10d such as an HDD, an input / output means 10e such as a display and a keyboard, and other various hardware. It is composed by wear.

The ROM 10b or the storage unit 10d includes an input information processing unit 111, a feed generation unit 112, a feed distribution determination unit 113, a top page information generation unit 114, a content page information generation unit 115, a display control unit 14, a user interface shown in FIG. A program and data for realizing a function such as 13 are stored. The storage unit 10d stores data of each DB (user attribute DB 121, relationship information DB 122, content DB 123, activity DB 124, and generated feed DB 125) described in the DB group 12 shown in FIG. These programs and data are loaded into the RAM 10b as necessary, and the programs are executed by the CPU 10a to perform arithmetic processing.

As the SNS server 10, a workstation or a so-called server machine is used. The SNS system 10 may be configured such that each configuration in FIG. 2 is distributed to a plurality of devices.

FIG. 2 is a functional configuration diagram illustrating the SNS server 10 from a functional aspect. The SNS server 10 can be recognized by being classified into the SNS core 11, the DB group 12, the user interface 13, and the display control unit 14 based on the function.

The SNS core 11 is an input information processing unit 111 that processes user content postings and activities and accumulates data in the DB group 12, a feed generation unit 112 that generates a corresponding feed triggered by data accumulation in the DB group, In conjunction with a feed delivery determination unit 113 that determines a feed to be delivered from feeds stored in the generated feed DB 125 (details will be described later) based on a top page browsing instruction from the user terminal 30, A top page information generating unit 114 that generates information based on a top page browsing instruction from the user terminal 30, and a content page information generating unit that generates content information to be displayed based on a browsing instruction for content information of another user from the user terminal 30 115. Each function will be described sequentially in the description of each activity in the service.

The DB group 12 includes a user attribute DB 121 that records user attributes input from the user terminal 30, a relationship information DB 122 that records a user's relationship with other users for each user, and information related to contents such as diaries and videos. It includes a content DB 123 to be recorded, an activity DB 124 that records a user's behavior history within the service, and a generated feed DB 125 that sequentially stores feeds generated in response to the occurrence of each content input or activity, and are mutually related. While being recorded. Each data structure will be described later.

A user of this service accesses the SNS server 10 from the user terminal 30 via the network 20. As the user terminal 30, a PC, a mobile phone, a tablet terminal, a smartphone, or the like can be used as appropriate. The user interface 13 selects a data format corresponding to the type of each user terminal and performs transmission / reception between the user terminal 30 and the SNS server 10. The display control unit 14 controls the display mode according to the terminal type of the user terminal that has made the request for the information on each page for which the browsing request has been made.

Hereinafter, each functional unit and DB will be described while describing examples of actions that each user can perform in the SNS server 10.

When one user uses the SNS server 10 for the first time, user registration is performed. In user registration, user attribute information such as user name (nickname), login ID (for example, unique e-mail address), login password, other place of residence, birthday, birthplace, hobby, self-introduction, etc. To do. You can also edit your own registered information. These pieces of information are stored in the user attribute DB 121. FIG. 3 is a conceptual diagram of information recorded in the user attribute DB 121. Each user is given a user ID as a main key, and attribute information such as the input user name and residence is linked to each user and recorded.

A user who has registered as a user logs in to use the service. On the login screen (not shown), the user performs authentication by inputting the login ID and login password registered from the user terminal 30. Of course, the user terminal does not need to be unique to each login ID, and any user terminal can log in as long as the terminal is in an environment connectable to the network 20. After authentication, a top page display request corresponding to the user ID of the user is made (described later).

The user can arbitrarily search within the service, or can browse the content of other users who are not subject to browsing restrictions via a link given to the received feed.

For example, the user can browse the content and build a relationship with other interested users. That is, a unilateral relationship with the other user can be established. One user inputs from the user terminal 30 to establish a unilateral relationship with another specific user. The input can be performed by clicking the “connect” button shown on the content screen display of a specific other user (see FIG. 4: button 41), but the input method is not limited to this, For example, a desired other user may be selected from a list of other users obtained as a result of performing a search under a predetermined condition. The input information is transmitted to the SNS server 10 via the network 20.

FIG. 5 is a conceptual diagram of information transmitted when one user inputs to establish a unilateral relationship with another specific user. In addition to the check digit 51 for ensuring the validity of the data, the input date 52, the input user ID data 53 of the input user, and the user ID data 54 of the selected user are linked and transmitted.

The input information processing unit 111 processes the information and records it in the relationship information DB 122. FIG. 6 is a conceptual diagram showing the contents recorded in the relationship information DB. The relationship information is roughly divided into two types: (1) information related to one-sided relationships constructed by one user, and (2) information related to a group in which one user distributes other users as having predetermined attributes. The Here, the former will be described. Information on the unilateral relationship constructed by one user is stored for each user ID as shown in the upper part of FIG. When stored, the related user ID, that is, the state of establishment of the unilateral relationship in the “connected” user is confirmed, and if a unilateral relationship (ie, a bilateral relationship) is established, “reciprocal” The flag is established.

Next, group setting will be described. Users can group other users in the service based on various common terms. As a result of browsing the contents of other users, one user has a common preference (including hobbies such as fishing and handicrafts, and common real-world items such as being a fan of a specific artist) Other users can be selected and registered as a group. The types of groups that can be registered can be set in various ways. For example, “attribute 1 user with a common hobby” “attribute 2 user who does not want to build a one-sided relationship” can be set in either plus or minus groups. Can be formed.

When information related to group settings is transmitted from the user terminal 30, the input information processing unit 111 performs the same processing and stores it in the relationship information DB 122. The lower part of FIG. 6 is a conceptual diagram of the stored information. A group ID, a target user ID, and a group attribute are recorded for each user.

Next, content posting will be described. The user can post various contents to the SNS server 10. For example, FIG. 7 shows an example of a screen displayed on the display means (not shown) of the user terminal 30 of one user. As shown in the upper part (broken line box), You can post various media contents such as “Check” “Diary” “Photo”. In addition, when posting these contents, the range of users permitted to view can be limited. Thereby, the user can disclose information about the self in the system under his / her arbitrary control.

FIG. 8 is a conceptual diagram of information related to the content posted by the user and recorded in the content DB 123. The user can select the type of content to be posted and its disclosure range. The content type can be selected from each menu tag in FIG. For example, in the case of a diary, text data can be directly input in an input field (not shown). Further, if it is image or video data, it is possible to upload what is stored in advance in its own user terminal 30. The scope of disclosure includes (1) individually specifying users to be disclosed, (2) individually specifying groups to be disclosed, (3) users who have established a unilateral relationship, (4) unilaterally via a third party. One of the users having the relationship formed and (5) all users in the service can be selected. When other users access the top page of the user according to these disclosure range settings, the presence or absence of display is controlled for each content based on the relationship with the other user.

A feed to that effect is generated due to the posting of content, but even if the disclosure range is set to “(5) All users in the service”, the feed is distributed to all users. Instead, it is appropriate to configure the feed to be distributed only to other users who have established a predetermined relationship, for example, other users whose relationship has been established bidirectionally. Otherwise, the feed is distributed to all users every time full-access content is posted, which is complicated.

Here, “a user in which a one-sided relationship is formed through a third party” (hereinafter sometimes referred to as “friend of friend” in the figure) will be described in detail with reference to FIG. FIG. 9 is a determination table related to the recognition of the relationship between A and C according to the state of establishment of the unilateral relationship between the A, B, and C members. It is assumed that a unilateral relationship is not directly established between A and C in any direction.

For example, in number 1, A-B establishes a unilateral relationship with each other, and B-C is the same. In such a case, as the relationship between A and C, the relationship can be simulated via B mutually trusted. Therefore, between A and C, the relationship of “friends of friends” is recognized, and contents are released.

For example, in the number 4, an arrow is marked from B to A. This means that B is building a unilateral relationship with A. In this case, since it is a friend C of B who trusts A, it is treated as "friend of friend" for A to C. However, since A has no trust in B, there is nothing for C to A. The relationship is not imitated and it is treated as “others”.

FIG. 10 is a timing chart showing information exchange between each node or processing unit when one user posts content. When the user posts content (for example, “diary”) via the network 20 (step S1001), the content data is transmitted to the input information processing unit (step S1002). The input information processing unit 111 of the SNS core 11 processes the content. Specifically, a process of associating a user ID, a content type, a URL where the content is displayed, and the like is performed. The content data is transmitted to the content DB 123 together with information regarding the disclosure range (step S1004). At the same time, the information is sent to the feed generation unit 112 to generate a feed indicating that the content has been posted (step S1005). When these internal processes are completed, the SNS core 11 transmits information indicating that the content posting has been completed to the user terminal 30 having posted the content again via the network 20 (step S1006). The content DB 123 stores the received content data (step S1007). The feed generation unit generates feed information associated with the content type and the disclosure range (step S1008).

Next, a case where one user performs an activity in the service will be described.
In addition to posting content, the user can perform various activities within the service. For example, a comment is attached to content posted by another user, and a one-sided relationship with another user is established. FIG. 11 is a conceptual diagram showing activity information recorded in the activity DB 124. Depending on the type of activity, it can be managed in association with predetermined content. In other words, in the case of an activity of “attaching a comment”, the activity is recorded with a relationship with the content to which the comment is attached. Each content and activity is assigned an ID, and is stored in association with the ID of the user who performed the activity and the disclosure range designation of the activity. Here, the categories of the disclosure range are basically the same as described in the content posting scene, (1) individual user designation, (2) individual group designation, and (3) the user forms a unilateral relationship. Or (4) a user who has a unilateral relationship with the user through a third party. The present disclosure range setting defines the transmission range of the feed resulting from the activity, and therefore there is no category of “(5) All users”. Note that there may be an activity that is not associated with the content (for example, a fact that a predetermined news article has been checked on the SNS), and in this case, the activity may be recorded without being related to the specific content.

FIG. 12 is a timing chart showing information exchange between each node or processing unit until an activity performed by one user is recorded and a feed based on the activity is generated. When an activity (for example, a comment on another user's diary) is performed from the user terminal 30 (step S1201), the information is transmitted to the input information processing unit 111 of the SNS core 11 via the network 20 (step S1202). ). The input information processing unit 111 processes the received activity information (step S1203). The activity data is sent to the activity DB 124 (step S1204), and at the same time, information indicating that the activity has been received is also sent to the feed generation unit 112 (step S1205). The activity DB 124 stores the received activity information for each original content (step S1206). In addition, the feed generation unit 112 generates a feed in which the user ID and the disclosure range of the received activity data are associated (step S1207), and sends the generated feed DB 125 (step S1208). The generated feed DB 125 stores the generated feed (step S1209).

In addition, as a reaction to the content of other users, it is possible not only to add a comment positively, but also to set a flag indicating that the content is favorable instead of the comment. Even based on a comment posted by another user or a flag indicating favor, a feed is generated in the same manner as shown in FIG.

FIG. 13 is a conceptual diagram showing feeds recorded in the generated feed DB 125. Each feed information is assigned with an individual feed ID, and the generation trigger ID (content ID or activity ID), user ID, type, and disclosure range are associated with each other and recorded. Note that these feeds are usually configured so that when one user establishes a unilateral relationship with another user, the one user receives the feed of the other user. Even if the other user has not established a unilateral relationship, the feed can be distributed to any other user who wants to distribute the feed by adding a compulsory flag when generating the feed. Can do. Of course, only those that have registered to receive the feed that they want to receive should be delivered, but abuse of such actions and continuing to deliver the feed will lower the reputation of the user within the Service. You may be connected and put into a group that doesn't receive a feed.

Next, the flow of processing when one user requests browsing of his / her top page will be described.
FIG. 14 is a timing chart showing the movement of information exchange between each node or processing unit when one user requests his / her top page display.

When a top page request is instructed in the user terminal 30 (step S1401), the request information is transmitted to the input information processing unit of the SNS core 11 via the network 20 (step S1402). The input information processing unit 111 performs initial processing such as confirming the validity of the requested user ID (step S1403), and sends request information to the top page information generation unit 114 together with the user ID that has made the display request (step S1404). ). At the same time, necessary data is read from each DB. That is, the user attribute information of the user to be displayed on the top page is read from the user attribute DB 121 (step S1405), and the relationship information necessary for extracting the feed to be distributed (displayed) is read from the relationship information DB 122. A request (step S1406) is made. Further, the top page information generation unit 114 reads the content data associated with the received user ID to be displayed from the content DB 123. The read relevance information is sent to the feed delivery determination unit 112. A feed to be displayed is extracted from the feed recorded in the feed distribution determination unit 112 generated feed DB 125 in response to the top page display request.

FIG. 15 is a flowchart showing the flow of feed extraction. In the following, description will be given in order with the conceptual diagram of FIG. The display feed extraction process is sequentially performed for each accumulated feed. First, it is determined whether or not a forced flag is attached to the feed (step S1501). As described above with reference to FIG. 13, the compulsory flag refers to a flag that is attached when one user desires to distribute a feed to another user who has established a unilateral relationship. If it is a feed with a compulsory flag (step S1501: Yes), then the user requesting the top page browsing is the feed owner of the feed, that is, the action that generates the feed (content posting, or It is determined whether or not the user who has executed the activity is a user who has established a unilateral relationship (step S1502). The determination is whether the “user ID” item in the relationship DB 122 in FIG. 6 is the user who performed the action of generating the feed, and the “related user ID” item is the user who is making the browsing request. It is done depending on whether or not. If applicable (step S1502: Yes), it is further determined whether the other user has not set a refusal to receive a force flag feed from the one user (step S1503). This forced flag reception refusal setting is performed when the other user sets the reception refusal, for example, the “forced refusal” flag in FIG. 6 is set and associated with the relevant information in the relationship information of the one user. Can be configured to be stored.

If reception refusal is not set (step S1503: Yes), it is further checked whether it is an extraction target. If not applicable (step S1502: No), the process is terminated as the feed does not correspond to the extraction target, and the process proceeds to discrimination of other feeds.

When the compulsory flag is not attached (step S1501: No), the feed distribution determination unit 112 determines whether or not the user requesting to browse the feed is a feed of a user who has established a unilateral relationship. (Step S1504). In the determination, whether the “user ID” item in the relationship DB 122 in FIG. 6 is the user who is making the browsing request, and the “related user ID” item is the user who has performed the action to generate the feed. It is done depending on whether or not. If not applicable (step S1504: No), the process is terminated as the feed does not correspond to the extraction target, and the process proceeds to discrimination of other feeds.

When the forced flag is attached and the user requesting the browsing is a user who has established a unilateral relationship with the feed owner, and the forced flag feed reception refusal is not set (step S1503: Yes), or In the case where the feed flag of the user for which the feed request is not attached and the user requesting the feed has established a one-sided relationship (step S1504: Yes), the browse request is next included in the disclosure range of the feed. It is determined whether or not the user who is doing is included (step S1505). As shown in FIG. 13, this determination is performed based on the “public range” flag of information related to the feed stored in the generated feed DB.
When it corresponds to the disclosure range (step S1505: Yes), the feed is extracted as a display feed (step S1506), and when it is not applicable (step S1505: No), the process is terminated and the other feeds are discriminated. Migrate to

Returning to FIG. 14, the information about the extracted display feed is sent to the top page information generation unit 114 (step S1410), and other information constituting the top page (for example, attribute information of the user who has requested browsing, And the content information of the user who has requested browsing) (step S1411). The display control unit 14 configures display information appropriate for the terminal and transmits it to the user terminal (step S1412). ). The feed extracted at that time is displayed according to the content and time series through predetermined ordering control, for example, as surrounded by a two-dot chain line in FIG. 7 (step S1413).

Next, content display control performed when one user makes a request to display content of another user will be described. FIG. 16 is a timing chart showing a flow of information exchange between nodes or processing units when one user makes a content display request of another user. When one user requests the display of another user's content page (step S1601), the request information is transmitted to the input information processing unit 111 via the network 20 (step S1602). The input information processing unit 111 performs processing of the request information such as confirming the validity of the received display request information (eg, the validity of the requested user ID) (step S1603). Then, the request information is sent to the content page information generation unit (step S1604). On the other hand, a read request for predetermined information is made from the user attribute DB 121 and the relationship information DB 122 (steps S1605 and S1606). Further, a request for reading content data requested from the content DB is made (step S1607). These pieces of information are processed in the content page information generation unit 115, and display content information is extracted and generated (step S1608).

FIG. 17 is a flowchart showing a flow of extracting and generating display content information. Based on the information from the user attribute DB 121 and the relationship information DB 122 that have read the content page information generation unit 115, the content page information generation unit 115 has a relationship (direct one side) as viewed from the content posting user. It is determined whether or not a general relationship or a one-way relationship established via a third party is established (step S1701). If not applicable (step S1701: No), it is next determined whether or not the content is a publicly disclosed content (step S1702). If not, the process is terminated as not being a display target.

On the other hand, if the relationship is established (step S1701: Yes), it is determined whether the disclosure range is satisfied (step S1703). If the disclosure range is satisfied (step S1703: YES), it is generated as display content (step S1704), and if not, the process ends.

When the display content information is generated, the information is transmitted to the user terminal 30 via the network 20 (step S1609), and the content information is displayed on the display means of the user terminal 30 (step S1610).

As described above, according to the SNS server of the present invention, it is possible to define the content disclosure range and the range in which the feed is distributed while building the relationship based on the unilateral relationship. It can be expected that psychological resistance to building a specific relationship with the user is smaller than before. This facilitates building relationships between users and is expected to improve the frequency of use of the service itself, which inevitably increases traffic and increases its advantage as an advertisement placement target.

Further, if the relationship is established based on the unilateral relationship in the SNS, the degree of intimacy is not appropriately expressed only by the relationship between the two users. Therefore, the determination of whether or not feed distribution or content browsing is possible while grasping the relationship between the related user up to the related other user, in other words, the relationship with the other user via a third party. By making it a factor, it becomes possible to control the user's own information desired by the user. Alternatively, regardless of whether or not the relationship is established, other users viewed from the group are grouped, and this and the above-mentioned one-sided relationship are filtered in a superimposed manner, so that more detailed feed distribution and one's own Content disclosure can be controlled.

Furthermore, by making it possible to set the disclosure range in multiple stages according to individual activities or contents, it is possible to refine the control of the disclosure of the contents.

On the other hand, in the unilateral relationship as described above, one user can perform his / her control to receive the feed of the other user who desires, but the opposite, that is, from one user to another It is not supported for feed delivery to users. Therefore, it is possible to perform feed distribution of the one user on the top page of another user. Thereby, the opportunity for constructing a unilateral relationship with the one user is born from the other user, and it can be expected that the construction of the relationship between the users is promoted.

1 SNS environment 10 SNS server 10a CPU
10b RAM
10c ROM
10d storage unit 10e input / output unit 11 SNS core 111 input information processing unit 112 feed generation unit 113 feed delivery determination unit 114 top page information generation unit 115 content page information generation unit 12 DB group 121 user attribute DB
122 Relationship information DB
123 Content DB
124 Activity DB
125 generation feed DB
13 User interface 14 Display control unit 20 Network 30 User terminal (31 PC, 32 mobile phone, 33 tablet terminal)

Claims (5)

* Main claim (server)
User information storage means for recording user attribute information for each user;
Relationship information storage means for recording relationship information of one user with other users;
Content storage means for recording content generated based on an instruction from a user;
Activity storage means for recording user activity;
A feed generation unit that generates a feed in response to a data entry in the content storage unit or the activity storage unit;
Feed storage means for recording the generated feed;
Top page information generating means for generating top page information based on an instruction from the one user;
Content page information generating means for generating page information related to content of other users based on an instruction from the one user;
In an SNS server that provides SNS (Social Networking Service) through a network,
The relationship information includes at least information on a unilateral relationship that one user forms with respect to another user,
The top page information generation means is based on the disclosure range information set for each activity and each content based on an instruction from the other user, and the relationship information among the feeds recorded in the feed storage means. To generate top page information that includes at least the feed extracted
The SNS server, wherein the content page information generation unit generates content page information based on content disclosure range information set for each content based on an instruction from the other user.
* Implementation of relationship information
(A) A relationship in which one user defines another user as a member of the group (b) A relationship in which one user forms a unilateral relationship with another user (c) One user in the other (D) A relationship in which only one user forms a unilateral relationship with one user (e) A relationship between one user and another user There is no one-sided relationship formed directly between them, but a one-sided relationship is formed continuously through a third user (f) One-way relationship is not formed, whether directly or indirectly The SNS server according to claim 1, wherein the SNS server is recorded as one or a plurality of categories of relationships that are not defined by group members.
* Specification of the scope of disclosure
(A) Individual user designation (b) Individual group designation (c) User whose user who is the activity sender or content owner forms a unilateral relationship (d) User who is the activity sender or content owner The user (e) who has formed a unilateral relationship via a third party from (1) is recorded as any one of the categories of all users, according to claim 1 or 2, SNS server. * Push-type feed delivery On the condition that the one user forms a one-sided relationship with another user, the instruction from the other user can be used regardless of the extraction based on the relationship information. When the top page information of the other user is generated based on the top page information including the feed generated by the one user based on his / her own activity and recorded in the feed storage means. The SNS server according to any one of claims 1 to 3, further comprising forced feed distribution means for performing feed distribution so as to generate. * Push-type feed distribution refusal means When generating the top page information of the other user, the push-type feed distribution refusal means further includes a forced feed reception refusal means that does not display a feed to be distributed by the forced feed distribution means. The SNS server according to claim 4.

Images