JP2014219853A - Social service server - Google Patents

Abstract

It is possible to efficiently catch up on topics developed on the timeline in a short time by optimizing the display on the timeline of the feed resulting from past activities from the timeline reference time. An SNS server is provided. Means for generating a timeline retroactive from the time of login based on a social graph of a user triggered by reference of the timeline by one user, and the generated timeline is optimized based on a predetermined requirement The SNS server has a unit for converting the feed group for generating the timeline generated when referring to the timeline of the one user into a plurality of sections, and the same category is included in each section. If there are multiple feeds, they are combined into one feed. [Selection] Figure 7

Description

The present invention relates to a server that realizes display optimization of what is generally called a “timeline” in which feeds are displayed sequentially in time series in social network services and other social services.

Conventionally, a communication service called a social network service (hereinafter referred to as “SNS”) that promotes and supports a connection between people is known. SNS offers services such as a function to publish your profile and photos to members, a diary function that allows you to limit the scope of disclosure to specific friends, and a community function that allows you to decide themes such as hobbies and regions and interact on the bulletin board etc. Features that can be used in As one of such SNSs, a website disclosed in Non-Patent Document 1 is known.

Specific contents of services available to members in the service include, for example, the following. First, users post (post) themselves, such as “diaries”, “tweets”, “calendars (plans)”, “photos”, and “videos”, and view posts from other users who have relationships Content that can be. The framework of the menu for posting such content is determined in advance, and the display mode (display area) is also typical. When one user posts an event he / she experienced as a diary, for example, when a trigger that refers to the timeline occurs, such as another user logging in to the service with a predetermined relationship with that user, A display indicating that the diary has been posted on the top page, that is, a feed is displayed with a link, and another user can view the contents of the diary of one user by opening the link.

Another content is a community function. In this case, information can be exchanged by a user posting on a bulletin board page according to a specific theme, or by browsing a post of another user. Posts to these community features are also displayed on the user's top page and other frequently viewed pages where the feed with the link is displayed, and the user can view the content of the post by opening the link, and can also post by himself it can. Alternatively, event guidance in a community may be distributed in the form of a feed to users belonging to the community.

Furthermore, in addition to the content actively posted by the user as described above, due to the behavior in the service of each user in an application such as a game (hereinafter sometimes referred to as “activity”), The feed is distributed to other users having a predetermined relationship.

Here, a feed distributed due to various factors as described above is generated when a user logs in or reloaded, and is displayed to the user. As a display method of the feed, different fields may be displayed for each of the various triggers, or may be displayed separately by switching the tags, or may be displayed in one order regardless of the types of the various triggers. As the rank, in general, many items are displayed in a chronological order based on when a post is made or when a comment on the post is posted by another user. A group of feeds displayed based on such a time series may be referred to as a “timeline”.

By the way, conventionally, in the invitation to browse to the content by the feed display, the feed is basically configured as text information with a link. It was also a device for realizing convenience as a service while considering restrictions on communication line speed and terminal processing speed.
However, at present, communication lines have been enriched and terminal performance has been improved as compared to the early days of SNS. Along with this, not only the conventional text information with a link but also the number of images displayed with image data and moving image thumbnails are increasing.

Another change is the diversification of terminals used. Conventionally, most users use services using personal computers and feature phones. In recent years, however, terminals in the form of smartphones and tablets have emerged, and the number of users who use services has rapidly increased.
A characteristic of such a new type of terminal is that the display screen is small due to its compact size. When displaying feeds with image data or video thumbnails as described above on such a small display screen, the number of feeds that can be displayed per screen is smaller than before, and the user can check past feeds. Has the problem that scrolling operations must be repeated.

Such a problem becomes conspicuous in a seasonal event such as Christmas or an event peculiar to each user such as a birthday. That is, when an activity related to an event is performed by another user having a relationship, the timeline of one user is filled with a feed related to the event.

Or even if it is not such an event, the same problem will arise depending on how other users act in the service. In other words, when other users perform activities at one time, for example, the login frequency is not so high, but when logging in, it is possible to write comments on other users' posts (posts) collectively or “favorite” When a flag is set or a timeline that is purely in time series is formed, a feed resulting from the activity of the other user is continuous on the timeline of one user.

Furthermore, the number of feeds generated within a given period has increased as services have matured, such as the number of users who use SNS increases relatively and more relationships with each other are built. ing. Under such circumstances, the timeline of one user is overcrowded, and as a result, a situation in which a feed related to information that the one user wants to see is lost without being recognized.
For these reasons, it has been required to perform filtering on the feeds that constitute the timeline.

Various methods have been proposed for feed filtering. For example, Patent Literature 1 discloses a method for analyzing information novelty and a system for personalizing and filtering information for the user by identifying the novelty of the story in the context of the story that the user has already confirmed. This is understood to be a configuration that customizes the news feed individually based on information that has already been confirmed by the user, such as reading, but with this configuration alone, the phenomenon described above, that is, the activity of the same type or the same user within a predetermined time It is not possible to present a solution to the problem of concentrated feeds due to, and it does not contribute to catching up timeline topics quickly and efficiently.

Further, in Patent Document 2, a dynamic list component filter is set based on the viewing user's preference or the like, or only the highest weighted activity of the subordinate user is displayed according to the affinity calculation for the viewing user. A configuration for performing feed filtering in the form of. However, these also only set the filter according to the interest of the viewing user or the familiarity with other users, and if it depends uniformly on such filtering, other users with low plain relationship or new Therefore, it is difficult to display a feed based on posts of other users who have established a relationship with the user, and the expansion of the user's social graph is unnecessarily suppressed, and an increase in value as a service medium cannot be expected.

JP2005-251203 Japanese Patent No. 4866463

“Social Networking Service [mixi]” [Search April 21, 2013], Internet <URL: http://mixi.jp/>

Accordingly, an object of the present invention is to provide an SNS server that can efficiently catch up topics developed on the timeline in a short time by optimizing the display on the timeline of the feed. . In particular, it is an object to provide an SNS server capable of correcting an irregular timeline formation by focusing on a short period of feeds caused by the activity of the same type or the same user, which is caused by a change in the approximate communication environment or terminal status. To do.

In order to solve the above problems, the present invention has the following configuration.
(1) The SNS server according to the first invention is configured to generate a timeline that goes back from the timeline reference time point based on a social graph of the user, triggered by reference to the timeline by one user, SNS server having means for optimizing the generated timeline based on a predetermined requirement, wherein the predetermined requirement includes a plurality of feed groups for generating a timeline generated when referring to the timeline of the one user. It is divided into sections, and when feeds of the same category exist in each section, they are aggregated into one feed (claim 1).

(2) The SNS server according to a second aspect of the present invention is a means for generating a timeline that goes back from the timeline reference time point based on a social graph of the user, triggered by reference to the timeline by one user, SNS server having means for optimizing the generated timeline based on a predetermined requirement, wherein the predetermined requirement includes a plurality of feed groups for generating a timeline generated when referring to the timeline of the one user. It is divided into sections, and when feeds of the same creative exist in each section, they are aggregated into one feed (claim 2).

(3) The SNS server according to the third invention is a means for generating a timeline retroactively from the timeline reference time point based on a social graph of the user, triggered by reference of the timeline by one user, SNS server having means for optimizing the generated timeline based on a predetermined requirement, wherein the predetermined requirement includes a plurality of feed groups for generating a timeline generated when referring to the timeline of the one user. When there is a feed that is divided into sections and the position information associated with the post due to the feed that exists in each section is close, the feeds are aggregated into one feed (claim 3).

(4) The SNS server according to the fourth invention is a means for generating a timeline retroactively from the timeline reference time point based on a social graph of the user, triggered by reference of the timeline by one user, SNS server having means for optimizing the generated timeline based on a predetermined requirement, wherein the predetermined requirement includes a plurality of feed groups for generating a timeline generated when referring to the timeline of the one user. When there is a feed that is divided into sections and the same post theme is attributed to a feed that exists in each section, the feeds are aggregated into one feed (claim 4).

Note that the aggregation into the one feed in these inventions is characterized in that the aggregation is performed based on the familiarity between the user who made the posting due to the plurality of feeds to be aggregated and the one user. (Claim 5) In addition, it can be performed based on the correlation between the theme of the post caused by the plurality of feeds to be aggregated and the interest of the one user (Claim 6). . Or it can also be characterized by performing based on evaluation of other users to a post which a plurality of feeds which are the aggregation object concerned originates (claim 7). Or it can also be characterized by performing based on the low frequency of posting by a user who has made a posting due to a plurality of feeds to be aggregated (claim 8).

(5) An SNS server according to another invention is generated by means for generating a timeline retroactively from the log-in time based on a user's social graph based on a user's social graph as a trigger. And a means for optimizing the timeline based on a predetermined requirement, wherein the predetermined requirement divides a feed group that generates a timeline generated when referring to the timeline of the one user into a plurality of sections. The feed in each section is filtered based on the intimacy between the user who divided and posted the post attributed to the feed existing in each section (claim 9). ).

(6) Alternatively, a means for generating a timeline retroactively from the timeline reference time point based on a social graph of the user triggered by reference of the timeline by one user, and the generated timeline as a predetermined requirement SNS server having means for optimizing based on the above, wherein the predetermined requirement divides a feed group for generating a timeline generated when referring to the timeline of the one user into a plurality of sections, It is also possible to use an SNS server characterized by filtering the feeds in each section based on the correlation between the post theme caused by the feed existing in and the one user's interest ( Claim 10).

(7) The SNS server according to yet another invention is generated by means for generating a timeline retroactively from the log-in time based on a social graph of the user, triggered by reference of the timeline by one user. And a means for optimizing the timeline based on a predetermined requirement, wherein the predetermined requirement divides a feed group that generates a timeline generated when referring to the timeline of the one user into a plurality of sections. The feed is divided and the feed in each section is filtered based on the evaluation of other users with respect to the post due to the feed existing in each section (claim 11).

The division into the plurality of sections is performed based on time point information possessed by the post resulting from each feed, and is performed at equal time intervals retroactively from the timeline reference time point. (Claim 12) Besides, it is performed based on time point information possessed by a post originating from each of the feeds, and is performed at a wide time interval as the period going back from the timeline reference time point becomes longer. (Claim 13). Alternatively, the division into the plurality of divisions is performed based on the order of each feed in the generated timeline, and the division into a plurality of divisions is performed for each predetermined number of feeds. In addition to being possible (Claim 14), it is performed based on the order of each feed in the generated timeline, and as the order goes down, many feeds are divided into one section. (Claim 15).

Further, the feed in each of the above inventions may be characterized in that it is accompanied by non-text information such as image display / moving image thumbnail display. Alternatively, a user operation for the feed can be performed in the feed display area without transitioning to another screen or another display, and the display reflecting the user operation on the feed may be performed. (Claim 17)

The SNS server according to the present invention optimizes the display on the timeline of the feed resulting from the past activity from the time of referring to the timeline at the time of login or the like, so that the topics developed on the timeline can be quickly viewed. It becomes possible to catch up efficiently. In particular, it is possible to correct an irregular timeline formation due to the concentration of feeds in a short period due to the activity of the same type or the same user, which is caused by a change in the approximate communication environment or terminal status.

In the present invention,
“Timeline reference” is generated based on the user's operation such as login or reloading, based on the social graph of the user operated by the SNS server, based on other users' posts, etc. Time-series display of feeds, that is, transmission of a signal from a user terminal that triggers generation of a “timeline”. “Login” refers to an operation for identifying the identity and validity from the user ID and password at the start of use of the service and obtaining qualification information necessary for accessing various resources in the service. Usually, a user connects to an SNS server via a network from a terminal (personal computer, mobile phone, smartphone, tablet, etc.) owned by the user and performs a login operation. Login can be one of triggers for generating and displaying by referring to a timeline, but is not limited to this, and for example, a reload operation by a user can be one of triggers for referring to a timeline.

“Social graph” refers to a relationship with other users constructed by each user in the social network service. In general, in social network services, “My Miku”, “Friends”, “Followers”, etc. are called differently depending on the service, but one user can display feeds generated by other users' activities on their pages. Alternatively, a relationship such as permitting other users to view his / her posts is constructed.

“Feed” refers to other users ’web activities such as“ post a diary ”,“ set a “like” flag for other posts ”,“ check in a specific location ”,“ items ” Refers to a document (document) that has been processed to display on the timeline the events that occur due to these and the like. The document usually has a link, and you can follow the link to view details of other users' posts and community events, but not limited to this, a short post itself can be linked. Some posting categories are delivered directly to a single user as feeds.

A "timeline" is a series of these feeds displayed in chronological order (usually going from top to bottom). Each feed that makes up the timeline may display text information, such as a short post ("tweet"), while in the case of a feed with a photo diary or video post, the thumbnail of the photo or video It can also be displayed as a feed with non-text information. Alternatively, such a feed does not involve a transition to another screen via a link, and an advanced input beyond simply setting the “Like!” Flag by the browsing user performing an operation within the display area of the feed. There are cases where an interface capable of performing the operation is provided.

“Optimization” means to reconstruct the timeline so that a topic can be efficiently recognized for a topic developed for one user, specifically filtering and / or multiple Timeline compression by collecting feeds. “SNS server” refers to a server that stores an engine and various databases for providing a social network service via a network. A single node is not a requirement, and a plurality of nodes may cooperate to realize a similar configuration.

“Category” refers to the classification of feeds according to the type of user activity that causes the feed to be generated, such as “tweet”, “image”, “diary”, community activity, app activity, Broadly divided into advertisements. “Creative” refers to classification of a feed according to a data format such as a user's activity that causes the feed to be generated, and is broadly classified as text only, with an image, with a video. “Aggregation” means that only one feed among a plurality of common feeds is normally displayed, and other feeds are displayed as being aggregated, or nothing is displayed.

“A user operation for the feed can be performed in the feed display area without transitioning to another screen or another display and the user operation is reflected on the feed” is a so-called interactive property. It means that the feed has. The feed having “interactiveness” mentioned here refers to a feed that can provide what the user desires (service) in a complete form in the feed in interactive exchanges with the system. Specifically, a video feed having a play / stop button, a questionnaire feed in which the progress of counting is visible, a game application feed in which a game progresses when a user selects one of a plurality of options, and the like are applicable.

It is a network block diagram which shows the state which the SNS server 20 and the terminal device 10 which concern on one Example of this invention connect via the network 30. FIG. It is a functional block diagram of SNS server 20 concerning one example of the present invention. It is a functional block diagram of the terminal device 10 which concerns on one Example of this invention. It is a flow which shows the flow until a feed is produced | generated and the feed information which comprises a timeline is transmitted to the terminal device 10. FIG. It is an image figure which shows the process in which the event relevant to the said user is extracted from the event in a service. 5 is a flowchart showing a subroutine of step S405 in FIG. It is an image figure which shows a series of flows by which a timeline is produced | generated and reconfigure | reconstructed. It is an image figure which shows a series of flows by which a timeline is produced | generated and reconfigure | reconstructed. It is an image figure which shows a series of flows by which a timeline is produced | generated and reconfigure | reconstructed.

FIG. 1 is a configuration diagram of a network system 1 including an SNS server 20 according to an embodiment of the present invention. The SNS server 20 is connected to the terminal devices 10... 10 of each user via the network 30 and can exchange data. The terminal device 10 is wirelessly connected to the base station and is connected to the network 30 via a network device such as a gateway (note that the base station and the gateway are not shown). The user browses and acquires various contents and information provided by various sites via the network 30, and the user himself / herself transmits information from the terminal device 10. Various sites include services such as those provided by the SNS server 20.

FIG. 2 is a functional block diagram illustrated with blocks indicating functions of the SNS server 20. The function of the SNS server 20 includes: a DB group 210 that records master information related to user attributes and transaction information such as individual activities and contents; an SNS core 220 that appropriately performs processing based on externally input information; and the network 30. And the user interface 230 for optimizing the data format when exchanging information with the various terminal devices 10 and the like.

The DB group 210 includes a user attribute DB 211 that records attribute information such as the name, age, sex, birthplace, and hobbies of SNS users, a relationship DB 212 that records information about relationships between users, and services of each user. Activity DB 213 that records behavior history in the user, for example, setting of flags for other people's content, community participation, etc., content DB 214 that records posts such as diaries, photos, and videos by users, user activities and content, Including a preference DB 215 that records the preference calculated based on the time series transition for each user, and an advertisement information DB 216 that records the advertisement information expressed based on the above-described preference and other indicators. Yes.

The SNS core 220 is based on the input information processing unit 221 that processes the input information from the terminal device 10, the preference determination unit 222 that determines the preference using the occurrence of user activity or content posting as a trigger, and the determined preference. Based on the distribution advertisement selection unit 223 that selects an advertisement to be distributed for each user, the user's login or reload request, the relationship or preference of the user with other users, the presence or absence of participation in the community, and the application / game A feed generation unit 224 that generates a feed to be displayed for each user based on a status such as presence / absence of participation, a feed that is aggregated or thinned out under predetermined requirements, and that is displayed on a timeline A timeline display control unit 225 for controlling the display mode, based on the display request from the user. And a content page information generation section 226 that generates page information.

FIG. 3 is a functional block diagram of the terminal device 10. The terminal device 10 includes a CPU 11 that controls operation of the terminal including control of timeline and other screen display based on data received from the server, a memory 12 that temporarily develops application data, etc., downloaded application programs and distribution A storage unit 13 for storing the content and other information, a transmission / reception unit 14 for controlling connection with other nodes via the network 30, a display unit 15 for displaying a downloaded web page, a keyboard, a numeric keypad, etc. And an input device 16 for performing an active input operation for terminal operation by an operator, such as a touch panel arranged on the screen. Although not shown in the drawings, a sensor for recognizing information (ambient illuminance or given acceleration) other than an active operation with respect to a speaker for sound output or the input device 16 may be provided. The CPU 11 and other elements are electrically connected through a bus.

Next, basic user behavior in the service will be described.
(1) Upon receiving provision of a service for registering user attribute information, the user registers his / her attribute information. Various information can be registered as attribute information. For example, name, age, handle name, profile picture, current address, gender, birthday, blood type, birthplace, hobby, occupation, affiliation, etc. can be registered. The user inputs these attribute information from his / her terminal device 10. The input information is stored in the user attribute DB 211 in a form associated with the user ID.

(2) Building relationships with other users Users can build relationships with other users within the service. There are various ways to build the relationship depending on the service, and it may be one-sided feed acceptance (follow), bilateral friend application-accepting feeds from each other by acceptance, and allowing posts to be viewed Also good. In addition, the relationship is not limited to a single layer, but a layer such as “best friend” is provided as a more intimate relationship, so that only the more specific relationship is disclosed and its feed is distributed. An aspect may be sufficient. Such a relationship is stored in the relationship DB 212 in a form associated with the user ID.

(3) Description of activity The user can perform various activities within the service. For example, an application provided in the service can be downloaded and played. Events occurring and actions taken in such games are stored in the activity DB 213 in a form associated with the user ID.

Other examples of activities include posting a comment in the community, posting a comment on the content of another user, and setting a “Like!” Flag. A community can be created not only as a service operator but also as a place where individual users exchange opinions on specific topics. For example, the contents of a community where fans of specific entertainers gather, a community where users who share the same hobbies such as fishing and futsal gather, and the like are not limited. Setting the “Like!” Flag means a positive willingness to the post or comment, although there is no motivation to actively write a comment on a post or comment by another user. It is usually configured to be set with one click. The posting of these comments and the setting of the “Like!” Flag are also stored in the activity DB 213 in a form linked to the user ID of the user who made the posting or setting, and a comment is posted or “Like!” The content is stored in the content DB 214 in association with the content ID of the content for which the flag is set.

(4) Post (post)
The user can write, for example, daily events so as to keep a diary. Or you can post a short sentence as a tweet, even if it's not as big as a diary. In addition to posting pictures and videos together in the diary, you can also link and write URLs of other Web pages you want to talk about. In this way, you can post your concerns, your thoughts, opinions, and things you like in various formats such as text, images, videos, and audio data.

Furthermore, the user can appropriately control the disclosure range for each post. All users of the service can be set to be viewable, or can be set only to friends. Alternatively, the disclosure range can be controlled for each individual friend, and the disclosure level can be set for each individual post. If you want to broaden the relationship but do not want to disclose it indefinitely, you can also set “Open to friends of friends”. By appropriately controlling the disclosure range in this way, it is possible to post about daily events without hesitation, and to increase the possibility of expanding relationships with other users. Thus, the content posted by each user is stored in the content DB 214 together with the setting of the type and the disclosure range.

(5) Accumulation of palatability As described above, user activities and content postings are sequentially stored in association with the corresponding user IDs. However, with these as materials, individual user preference trends and palatability Are also calculated sequentially. For example, when one user posts a diary including “car” as a term, it is processed in the input information processing unit 221, stored in the content DB 214, and the user's preference tendency in the preference determination unit 222. Is recalculated and stored in the preference DB 215 in association with the user ID of the user. This preference information is used in various aspects, and when the advertisement information displayed on the user's top page is selected from the advertisement information DB 216, the affinity information is based on the preference information. A high advertisement is selected and displayed. Alternatively, as will be described later, it is possible to take into account the user's preference information in optimizing the timeline display.

Next, a flow in which a feed is generated after the user refers to the timeline with reference to FIGS. 4 to 6, the feed is reconfigured according to predetermined requirements, and transmitted to the user terminal device 10 will be described. .

FIG. 4 is a flow showing a flow until a feed is generated in response to a user request and feed information constituting a timeline is transmitted to the terminal device 10 operated by the user.

Triggers that cause a series of flows may include user login, reload, and transition from another screen to the user top screen. Of course, a configuration in which feeds generated by other user activities after the user has entered the service once is not subject to aggregation may be considered. In that case, only the user login can be set as a trigger. Or, it can be configured to aggregate the previous feeds even when reloading after a long time by triggering the occurrence of a situation where a predetermined time has passed since the previous timeline reference You can also.

When a feed generation trigger occurs, for example, when the input information processing unit 221 receives a login instruction from a user (step S401: Yes), the feed generation unit acquires each piece of information related to the login user from the DB group 210 (step S402). . Information to be acquired includes the attribute information of the user, information about the relationship that the user has with other users, information about the activity of the user, information about the content posted by the user, and comments and flags of the user Information regarding the set content and information regarding the preference calculated by the preference determination unit 222 based on the behavior of the user in the service so far are included. These are used as a filter for extracting only events related to the user from all records such as events accumulated in the service, that is, user activity and posting, construction of new relationships, and the like (step S403). ).

FIG. 5 is an image diagram showing a process in which an event related to the user is extracted from events in the service. Only relevant events are extracted based on user attribute, relationship, activity, content, and preference information. Specifically, for example, only event data having a user ID with which the user has a relationship is extracted. Further, in the content filter, when there is a user who adds a comment or sets a flag to a post made by the user, the information is extracted. Alternatively, if there is a record indicating that the user attribute belongs to a predetermined community, if there is an article posted to the community, that fact is extracted. Thus, each filter is not necessarily limited to an AND condition, and events that satisfy the extraction condition are sequentially extracted in each filter.

A feed is generated for the event thus extracted (step S404). If the feed is based on the fact that another user has posted a diary, for example, "○○ has posted the diary" Today is a walk with John "", other user names (or handle names) ) And a short sentence with a link that shows the content of the post. When the diary is accompanied by the pasting of a photo, the thumbnail of the photo is also displayed.

Also, for example, when another user makes a comment on his / her post, the other user name (or handle name) and its activity can be known, such as “▲▲ added a comment to the diary”. Introduced in short text with links.

Or, if another user who is using the same app as your own obtains a certain rare item in the app, another user name (such as “Mr. XX got a rare item”) (Or handle name) and a short sentence with a link that shows the progress of the app. At that time, an image thumbnail of the acquired item may also be displayed.

The feed generated in the feed generation unit 224 is subjected to optimization display control in the timeline display control unit 225 (step S405). The flow will be described with reference to FIGS. FIG. 6 is a flowchart showing the subroutine of step S405 in FIG. The timeline display control unit 225 generates a temporary timeline using the generated feed. That is, the respective feeds are arranged in the order of the reverse order of the time series (a mode that goes back to the past in order from the most recent one) based on the time of occurrence of the event caused by the feed. The left column in FIG. 7 schematically shows a temporary timeline. As shown here, feeds for various categories of events will be arranged out of order. In the figure, “P” represents a post of a photo, “R” represents a post of a diary, and “T” represents a tweet.

The timeline display control unit 225 divides the timeline into a plurality of sections according to time (step S602). The time length of the division can be arbitrarily set, and for example, “6 hours”, “1 day”, or “1 week” may be used. By making the time length of the section wide, the degree of compression of the timeline is further increased. Further, the user may set the time length of the section. Since the amount of feed generated per unit time varies depending on the user, it can be set so that the optimal timeline reconstruction is performed for each user. As shown by the dotted lines in FIG. 7, the timeline is divided into equal intervals.

Next, the timeline display control unit 225 determines the presence / absence of feed of the same category in each section (step S603). In FIG. 7, for example, “R”, that is, three entries in the diary overlap in the uppermost section. In the third section from the top, “P”, that is, two photo submissions overlap. The timeline display control unit 225 aggregates the overlapping feeds in these sections based on the aggregation rule (step S604). Here, an example will be described in which a high familiarity is preferentially displayed based on the familiarity between the user who browses and the user who made the posting due to the feed. The feed based on the three diary posts in the top section is based on other users (A, B, C), and the closeness between the viewing user and each user is (80, 65, 50), respectively. , Only the feed resulting from user A's post is left on the timeline, and the other two feeds are not displayed.

However, as an aggregation rule based on intimacy, not only those with high intimacy can be preferentially displayed, but conversely, those with low intimacy can be preferentially displayed. Such a configuration leads to the promotion of the formation of new relationships and leads to an increase in the value of the service itself as a medium.

Or it is not restricted to aggregation based on familiarity, For example, you may make it aggregate based on the correlation with the content of the posting of a diary, and the user's browsing interest. Further, these aggregation rules may be combined. By configuring in this way, for example, when all three diary posts in the same section are posts from the same user A, priority subordination according to the post content can be determined, and timeline optimization Contribute to. Of course, if there is no dominance due to such an aggregation rule, the newest feed (or the oldest feed) in the same section may be preferentially displayed, or aggregation may not be performed.

Returning to FIG. 4, the timeline thus reconfigured is transmitted to the terminal device 10 of the user who requested it via the network 30 and displayed on the display unit 15.

The timeline reconstruction means is not limited to the above-described method.
(1) When there are feeds of the same creative in each category, for example, when there are feeds with a plurality of photos in any category, they can be configured to be aggregated. As a result, feeds having the same appearance do not continue, so even a terminal device with a relatively small screen can be browsed without stress, the frequency of stay of the user increases, and the value as a service medium Will improve.

(2) Alternatively, as a target to be aggregated, a feed whose position information associated with a post resulting from the feed is close may be the aggregate target. For example, when a plurality of users are checking in at a festival in the same region, check-in information from the neighborhood is not necessarily the same location information, but continues on the timeline. It is possible to thin out similar feeds by aggregating such feeds, and even a terminal device with a relatively small screen can be browsed without stress, the frequency of stay of the user is increased, and the service medium Value is improved. In addition, for the determination of the neighborhood, for example, when the straight line distance that can be obtained from the latitude and longitude information of each checked-in point is equal to or less than a predetermined threshold value, it may be aggregated, or the regional mesh to which the obtained latitude and longitude information belongs is different You may judge by.

(3) Alternatively, the feeds to be aggregated may be those that have the same theme as the topic of the post that originates. For example, when there are posts by a plurality of users who have checked or commented on news on a specific Web, it can be aggregated on condition that the URLs of the news on the Web match. It is possible to thin out similar feeds by aggregating such feeds, and even a terminal device with a relatively small screen can be browsed without stress, the frequency of stay of the user is increased, and the service medium Value is improved.

(4) The feed is aggregated based on the level of evaluation by other users on the post resulting from each feed at the time of the trigger occurrence, for example, the number of “Like!” Flags and the number of comments. You may do it. As a result, posts that are judged to be more useful by other users will be preferentially displayed on the timeline, so the service stay time of the viewer is expected to be longer, Value is improved.

(5) Furthermore, regardless of the difference in category or creative, there is also a configuration in which feeds within the same category are aggregated based on the closeness with the browsing user, the correlation with the browsing user's interest, or the evaluation by other users. Conceivable. As a result, even when events are concentrated in a short period of time, the browsing user can check the feed related to the event with the highest interest level for the browsing user without missing it.

(6) Or the structure which aggregates based on the frequency of the post of the user who performed the post which the said feed originated can also be considered. As a result, it is possible to check on the timeline without getting a post from another user who does not post frequently.

(7) Further, the method of dividing the section is not limited to the equal time interval, and for example, as shown in FIG. 8, the section closer to the present may be shorter and the period may be set longer as going back to the past. With such a configuration, feeds are displayed closely for recent hot topics, while past topics are displayed in a thinned-out state to some extent, making it a timeline that makes it easy for viewers to check feeds. , The usability of the user is improved, and the media value of the service is improved.

(8) Also, as shown in FIG. 9, regardless of the category or creative, the feeds in the same category are aggregated for each user when the user who performed the event that caused it matches. You can also For example, in FIG. 9, in the uppermost section, user B makes a comment on his / her own diary posting and the viewing user's post. In this case, only the diary feed is left as the activity of B. Such a configuration is particularly useful when a user who performs posting, commenting, and flag setting collectively in one's social graph is present when the service is not used frequently but is used once. This is because such users often make comments and flag settings for the same user's posts in a short period of time, so the user's timeline with comments and flag settings will be filled with the user's activities in the short term. Because.

(9) In the above-described embodiment, time is used as a reference for dividing a section. However, the present invention is not limited to this. For example, the section may be divided every predetermined number of feeds.

In this way, by optimizing the timeline display, it is possible to efficiently access information that is more useful or more interesting to the user. As a result, usability for the user is improved, and more information is exchanged, so that the value as a service medium is improved.

1 network system 10 terminal device 20 SNS server 210 DB group 211 user attribute DB
212 Relationship DB
213 Activity DB
214 Content DB
215 Preference DB
216 Advertising information DB
220 SNS Core 221 Input Information Processing Unit 222 Preference Determination Unit 223 Delivery Advertisement Selection Unit 224 Feed Generation Unit 225 Timeline Display Control Unit 226 Content Page Information Generation Unit 230 User Interface 30 Network

Claims (17)

Means for generating a timeline retroactively from the timeline reference time point based on a social graph of the user triggered by a reference of the timeline by one user;
A SNS server having means for optimizing the generated timeline based on predetermined requirements,
When the predetermined requirement is that a feed group that generates a timeline generated when referring to the timeline of the one user is divided into a plurality of sections, and feeds of the same category exist in each section, they are aggregated into one feed An SNS server, characterized in that Means for generating a timeline retroactively from the timeline reference time point based on a social graph of the user triggered by a reference of the timeline by one user;
A SNS server having means for optimizing the generated timeline based on predetermined requirements,
When the predetermined requirement divides a feed group that generates a timeline generated when referring to the timeline of the one user into a plurality of divisions, and there is a feed of the same creative in each division, it is aggregated into one feed An SNS server, characterized in that Means for generating a timeline retroactively from the timeline reference time point based on a social graph of the user triggered by a reference of the timeline by one user;
A SNS server having means for optimizing the generated timeline based on predetermined requirements,
The predetermined requirement is that the feed group that generates the timeline generated when referring to the timeline of the one user is divided into a plurality of divisions, and the positional information associated with the post due to the feed existing in each division is close An SNS server characterized in that if a feed exists, the feed is aggregated into one feed. Means for generating a timeline retroactively from the timeline reference time point based on a social graph of the user triggered by a reference of the timeline by one user;
A SNS server having means for optimizing the generated timeline based on predetermined requirements,
The predetermined requirement is that a feed group that generates a timeline generated when referring to the timeline of the one user is divided into a plurality of sections, and a feed having the same post theme due to a feed existing in each section An SNS server, wherein the SNS server is aggregated into a single feed when there exists. The aggregation to the one feed is performed based on a closeness of a user who has made a post due to a plurality of feeds to be aggregated and the one user. 4. The SNS server according to any one of 4. The aggregation to the one feed is performed based on a correlation between a theme of a post caused by a plurality of feeds to be aggregated and an interest of the one user. 4. The SNS server according to any one of 4. 5. The aggregation according to claim 1, wherein the aggregation into the one feed is performed based on an evaluation of another user with respect to a post caused by a plurality of feeds to be aggregated. SNS server. The aggregation to the one feed is performed based on a low frequency of posting by a user who has made a posting due to a plurality of feeds to be aggregated. 5. The SNS server according to any one of the above. Means for generating a timeline retroactively from the timeline reference time point based on a social graph of the user triggered by a reference of the timeline by one user;
A SNS server having means for optimizing the generated timeline based on predetermined requirements,
The predetermined requirement is that the group of feeds that generate a timeline generated when referring to the timeline of the one user is divided into a plurality of sections, and the user who has made a post due to a feed existing in each section and the one A SNS server, wherein the feed in each section is filtered based on the familiarity with the user. Means for generating a timeline retroactively from the timeline reference time point based on a social graph of the user triggered by a reference of the timeline by one user;
A SNS server having means for optimizing the generated timeline based on predetermined requirements,
The predetermined requirement divides a feed group that generates a timeline generated when referring to the timeline of the one user into a plurality of divisions, and the post theme and the one user due to a feed existing in each division An SNS server that filters the feeds in each section based on the correlation with the interest of the SNS. Means for generating a timeline retroactively from the time of login based on a social graph of the user triggered by reference of the timeline by one user;
A SNS server having means for optimizing the generated timeline based on predetermined requirements,
The predetermined requirement divides a feed group that generates a timeline generated when referring to the timeline of the one user into a plurality of divisions, and evaluates other users with respect to a post due to a feed existing in each division. An SNS server that filters the feeds in each section based on the SNS server. The division into a plurality of sections is performed based on time point information possessed by a post originating from each of the feeds, and is performed at equal time intervals retroactively from the time line reference time point. The SNS server according to claim 1. The division into a plurality of sections is performed based on point-in-time information of a post attributed to each of the feeds, and is performed at a wide time interval as the period going back from the timeline reference point becomes longer. The SNS server according to any one of claims 1 to 8. The division into a plurality of divisions is performed based on the order of each feed in the generated timeline, and is divided into a plurality of divisions every predetermined number of feeds. The SNS server according to claim 1. The division into a plurality of sections is performed based on the order of each feed in the generated timeline, and as the order decreases, many feeds are divided into one section, The SNS server according to any one of claims 1 to 8. The SNS server according to any one of claims 1 to 12, wherein the feed is accompanied by non-text information such as an image display / moving image thumbnail display. The feed is capable of performing a user operation on the feed within the feed display area without transitioning to another screen or another display, and performing a display reflecting the user operation on the feed. The SNS server according to any one of claims 1 to 16.

Images