JP2007328538A - Access history providing device, method, and program - Google Patents

Access history providing device, method, and program Download PDF

Info

Publication number
JP2007328538A
JP2007328538A JP2006158963A JP2006158963A JP2007328538A JP 2007328538 A JP2007328538 A JP 2007328538A JP 2006158963 A JP2006158963 A JP 2006158963A JP 2006158963 A JP2006158963 A JP 2006158963A JP 2007328538 A JP2007328538 A JP 2007328538A
Authority
JP
Japan
Prior art keywords
user
information
relationship
history
site
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
JP2006158963A
Other languages
Japanese (ja)
Inventor
Mika Sugimoto
美香 杉本
Original Assignee
Fujifilm Corp
富士フイルム株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujifilm Corp, 富士フイルム株式会社 filed Critical Fujifilm Corp
Priority to JP2006158963A priority Critical patent/JP2007328538A/en
Publication of JP2007328538A publication Critical patent/JP2007328538A/en
Application status is Pending legal-status Critical

Links

Images

Abstract

A user who manages a site on an SNS can immediately know whether a user who has accessed the site has a certain relationship with the user.
An SNS server 100 identifies a relationship between a user A and a user B based on a friend management table 51 and a community management table 53 of both. Based on the user ID of the user A sent from the client 200a of the user A, the SNS server 100 stores “date and time” / “visitor” corresponding to the user ID of the user A stored in the footstep management table 52. After configuring the items of “user ID”, “relation”, and “access source” in the order of the access date and time, the Web page (additional page) is configured, and the additional page is transmitted to the client 200a.
[Selection] Figure 9

Description

  The present invention relates to a technique for providing information related to an access history to a site managed by a user in a social network service.

  In recent years, a service called a social network service (SNS) has become widespread. The SNS is a website opened for the purpose of expanding new friendships by introducing friends to each other. The SNS forms a group called a community where users with the same interests and interests gather, and on the community website, community members exchange information on common topics and share information.

Patent Document 1 is an example of an access analysis technique on a Web site. Here, the granularity of Web server access analysis is determined according to the access frequency for each client. Also, the analysis result output method is changed according to the display capability of the client.
JP 2000-31124 A

  In the conventional SNS, there is a “footstep” function for displaying a history of users who have accessed their pages. However, with the conventional foot function, if you are not a familiar person, you will not know what relationship the accessing user has with you unless you check the user's profile. . Also, if a user other than a user who has a certain relationship, such as a user who is registered as a friend or a user who belongs to the same community, visits the page, you will not know how to get to your page. Absent.

  The present invention has been made in view of such problems, and if a user who has accessed his / her site is not in a certain relationship with himself / herself, or if he / she does not have a certain relationship with himself / herself, how is the user? The purpose is to make it possible for a user who manages a site on the SNS to immediately know whether he / she has arrived at his / her page or what kind of profile the user does not have a certain relationship with himself / herself.

  The present invention relates to an access history providing apparatus used in a social network service system that provides a social network service to a user of each terminal via a network.

  The device includes a user information storage unit that stores user identification information and user profile information of each terminal, a relationship storage unit that stores relationship information that defines a relationship between users stored in the user information storage unit, and A history of the first user's access to the second user's site in response to the terminal of the first user being an unspecified user accessing a site managed by a second user being a specific user And the relationship between the first user and the second user according to the relationship information stored in the relationship storage unit in response to the first user accessing the site managed by the second user. A relationship identifying unit that identifies the first user, a history of access to the site of the second user by the first user, and information indicating the relationship between the first user and the second user. A history information creation unit for creating access history information to be performed; a history provision unit for providing access history information created by the history information creation unit to the second user terminal in response to a request from the terminal of the second user; Is provided.

  According to the present invention, access history information indicating the history of access by the first user and the relationship between the first user and the second user is provided to the terminal of the second user.

  By referring to the access history information, the second user can easily know what kind of relationship the user who has accessed his site is with him.

  When the history information creation unit creates access history information that displays icons representing the relationship between the first user and the second user in association with the access history, the second user further communicates with the first user. You can easily know the relationship.

  The history storage unit further stores an access history of a transit site that is a site through which the first user accesses the second user's site, and the history information creation unit is identified by the relationship identification unit based on the relationship information In response to determining that the relationship between the first user and the second user is not a predetermined relationship, access history information for displaying information indicating the type of the transit site of the first user in association with the access history is displayed. Create it.

  If the relationship between the first user and the second user is not in a predetermined relationship (for example, belonging to a common community, having a friend relationship, or having a common friend), the access history information is The site through which the first user has accessed to access the user's site is shown. For this reason, the second user can know how an unknown first user who has no fixed relationship with the user has accessed his / her site.

  The history storage unit further stores the history of the search keyword input on the search page in response to determining that the search page is included in the transit site, and the history information creation unit includes the search page in the transit site. If it is determined that the access site information is displayed, information indicating that the type of the transit site is a search page and information indicating the search keyword input on the search page is displayed in association with the access history.

  In this way, the second user can know what keyword the first user has specified from the search page to find and access the site of the second user.

  In response to determining that the relationship between the first user and the second user specified by the relationship information by the relationship information is not a predetermined relationship, the access history providing unit stores the first user stored in the user information storage unit. Access history information that displays all or part of the profile information in association with the access history may be created.

  In this way, when the first user who has accessed the second user's page is not in a predetermined relationship with himself / herself, the profile of the first user is shown, so the page introducing the profile of the first user is displayed. It is not necessary to make a transition until.

  In addition, a relationship memory | storage part is the relationship information which prescribes | regulates the friend relationship between the users in a social network service, the relationship information which prescribes | regulates the user who has a friend relationship in common, or a user in a social network service. It includes at least one piece of related information that defines information of the community to which it belongs.

  The present invention relates to an access history providing method used in a social network service system for providing a social network service to a user of each terminal via a network.

  The method includes a step of storing user identification information and user profile information of each terminal, a step of storing relationship information defining a relationship between users stored in the user information storage unit, and an unspecified user. Storing a history of the first user's access to the second user's site in response to accessing a site managed by a second user, a particular user, of a certain first user's terminal; Identifying the relationship between the first user and the second user in accordance with the stored relationship information in response to the first user accessing a site managed by the second user, by the first user The access history information for displaying the history of access to the site of the second user in association with the information indicating the relationship between the first user and the second user is created. Comprising the steps of, the steps of providing in response to a request from the terminal of the second user, the access history information created in the terminal of the second user.

  A program for causing a computer to execute this access history providing method is also included in the present invention.

  According to the present invention, access history information indicating the history of access by the first user and the relationship between the first user and the second user is provided to the terminal of the second user.

  By referring to the access history information, the second user can easily know what kind of relationship the user who has accessed his site is with him.

<First Embodiment>
FIG. 1 is a diagram showing a schematic configuration of a social network service (SNS) system according to a preferred embodiment of the present invention. In this system, when a plurality of clients 200 configured by a personal computer, a mobile phone, a PDA, and the like access the SNS server 100 via a network 50 such as the Internet, information can be exchanged with each other through the mediation of the SNS server 100. .

  The SNS server 100 includes a database 5, a Web server 4, an on-site content management unit 3, a footstep management unit 2, and an access history storage unit 1.

  As shown in FIG. 2, the database 5 includes a user management unit 5a and a community management unit 5b. The user management unit 5 a includes a friend management table 51, a footstep management table 52, a community management table 53, a profile management table 54, a diary management table 55, a message management table 56, and an access count management table 57. The community management unit 5b includes a member management table 58 and a topic management table 59.

  The access history storage unit 1 controls the storage / deletion / update of information in the message management table 56 and the access count management table 57. The footstep management unit 2 controls storage / deletion / update of information in the footstep management table 52. The on-site content management unit 3 controls storage / deletion / update of information in the diary management table 55, the friend management table 51, the community management table 53, and the profile management table 54.

  FIG. 3 shows information accumulated in the footstep management table 52. The footstep management table includes a “visitor user ID” that is an ID of a user who has accessed a site managed by a specific user on the SNS, a “relation” indicating the relationship between the user and the user, “Access source” indicating all or part of the site (routed site) through which the user's site is accessed (accessed site), “access date / time” that is the access start time, and the like are managed for each user who has accessed. .

  In this figure, “0002”, “3214”, “3721”, and the like are stored as visitor user IDs that have accessed the site managed by the user with the user ID “0001”, and the user ID “0002”. It is stored that the user is a “friend” relationship with the user ID “0001”.

  Based on the past access history of the client 200b that has accessed a specific site managed by a specific user, the foot management unit 2 is a “user page” that is a site managed by the user who has accessed the transit site. ”,“ Ranking ”, which is a popular site in the SNS, or“ Other ”, which is a site other than the above, and the“ Access Source ”item in the footstep management table 52 Stores the categorization of the via site.

  Whether a user who has accessed a site managed by a specific user is in a certain relationship with the site's management user (here, as an example, a friendship, a common friend, or belonging to a common community) Whether or not is determined by the information of the friend management table 51, the community management table 53, and the member management table 58.

  As illustrated in FIG. 4, the friend management table 51 stores user IDs of other users who have a friend relationship with a specific user. Here, the user relationship storage unit 23 for the user with the user ID “0001” stores the friend user IDs “0002”, “0324”, and “1307”. The friend relationship prescribed | regulated by the friend management table 51 can be arbitrarily set based on agreement between users like existing SNS.

  As shown in FIG. 5, the community management table 53 is an ID (community ID) that identifies a community to which each user belongs (a virtual space on the network for the purpose of communication between users regarding specific interests and interests). ) Is memorized. Here, it is defined that the user with the user ID “0001” belongs to a plurality of communities specified by community IDs “003493”, “123093”, and the like.

  Users belonging to each community are called members. As shown in FIG. 6, the member management table 58 stores members of each community. Here, for example, it is stipulated that the user IDs “0001” and “0002” belong to the community ID “003493”, and a community to which a plurality of users belong in common I understand.

  The access number management table 57 stores the number of accesses to a site managed by a specific user. However, the number of accesses may also be managed by the management table 52. The number of accesses in the access number management table 57 is updated every time there is an access.

  The message management table 56 stores and manages messages written to the site.

  The diary management table 55 stores and manages a diary (generally called a weblog) written by the specific user himself / herself on a site managed by the specific user.

  The topic management table 59 stores information input by community members on a bulletin board that handles topics of conversation within each community.

  As shown in FIG. 7, the profile management table 54 stores profile information that is information for introducing the user for each user ID that is identification information of each user.

  Hereinafter, the flow of the access history providing process executed by the SNS server 100 will be described with reference to the flowchart of FIG.

  First, it is assumed that a client 200b used by a certain user B (an unspecified user and can change variously) accesses the Web server 4 managed by the SNS server 100 in B1.

  In S <b> 1, when the client 200 b acquires and browses arbitrary content, the SNS server 100 obtains a predetermined number (for example, 10) from the latest URL of the content acquired by the client 200 b by the user B “ The access history is sequentially stored in the access history storage unit 1 as “access history”. When the client 200b accesses the search page and inputs a keyword to obtain a search result, the keyword input on the search page is also included in the access history to the search page and saved.

  If the client 200b of the user B accesses the site of a specific user A managed by the SNS server 100 via some site or directly, the SNS server 100 performs the process of S3.

  That is, in S3, the SNS server 100 accesses the database 5, and stores the friend management table 51 of each of the users A and B and the community management table 53 of each of the users A and B in a volatile memory (not shown). expand.

  Next, in S4, the SNS server 100 specifies the relationship between the user A and the user B based on the friend management table 51 and the community management table 53 of both. That is, if the user IDs stored in the friend management table 51 of the user A and the user B are matched and there is a matching user ID, there is a user who has at least a friend relationship in common with both. It is specified. And if the matching user ID is the user ID of the user A or the user ID of the user B, it is specified that both have a direct friendship relationship.

  The SNS server 100 matches the community IDs stored in the community management table 53 of the user A and the user B, and if there is a matching community ID, the two belong to a common community. Is identified.

  The SNS server 100 specifies the relationship between the two as described above, and the user A and the user B have a certain relationship, that is, have a direct friend relationship or a common friend. Determine whether you have or belong to a common community. When it is determined that the user A and the user B have a certain relationship, the process proceeds to S5. When the user A and the user B do not have a certain relationship, the process proceeds to S6.

  In S5, the footstep management unit 2 sets the access date and time of the user B to the site of the user A in the “date and time” item corresponding to the user ID of the user A in the footstep management table 52, and the user in the “visitor ID” item. The ID of B is stored. These pieces of information correspond to additional information or history information in the existing SNS.

  Furthermore, the footstep management unit 2 stores the relationship between the user A and the user B specified in S4 in the “relation” item corresponding to the user ID of the user A. If there is a direct friend relationship between the two, "friend" is stored, if there is a user who has a friend relationship in common with both, the user ID is stored, and if they belong to a common community, The community ID is stored. It is preferable to identify the community name corresponding to the community ID from the community management table 53 and store it in the “relation” item together with the community ID. Note that no information need be stored in the “access source” item.

  In S6, the footstep management unit 2 acquires the past access history of the user B stored by the access history storage unit 1, and based on this, the user B passes through what site the user A's The arrival of the site is classified into “user page”, “ranking”, and “other”. The footstep management unit 2 stores the classification of the transit site in the “access source” item corresponding to the user ID of the user A in the footstep management table 52. If the transit site is a search page, a keyword (hit keyword) that hits the site of user A on the search page is also stored in the “access source” item.

  Thereafter, when the SNS server 100 determines that the client 200a of the user A has requested browsing of an additional page indicating an access history for the user's site at an arbitrary time (A1) ("Y" in S8). , S9 is performed.

  That is, in S9, based on the user ID of the user A sent from the client 200a of the user A, the “date and time” and “visitor” corresponding to the user ID of the user A stored in the footstep management table 52 are stored. After configuring the items of “user ID”, “relation”, and “access source” in the order of the access date and time, the Web page (additional page) is configured, and the additional page is transmitted to the client 200a. When the client 200a receives the last page, it displays it on a display screen such as a liquid crystal monitor (not shown).

  FIG. 9 shows an example of a footstep page. This page displays “date and time”, “visitor user ID”, “relation”, and “access source” of the latest 10 accesses to the site of user A.

  Here, since it is difficult to understand even if “visitor user ID”, “relation”, and “access source” are displayed as they are, if the user name N1 corresponding to the visitor user ID stored in the profile management table 54 is displayed, Good. In addition, an icon corresponding to the “relation” classification or an icon corresponding to the “access source” may be displayed.

  For example, in FIG. 9, if the “relationship” is “friend”, the “tomodachi” icon I1 is displayed, and if the “affiliation community” is common, the “community” icon I2 and the community name N2 are displayed. If the “access source” is a search page, a “search” icon I3 is displayed. If the “access source” is an access ranking page, a “ranking” icon I4 is displayed. The “search” icon I3 is displayed with the hit keyword (“Cooper” or “ramen” in this case) input on the search page.

  The user A who has viewed the last page as shown in FIG. 9 uses the “tomodachi” icon I1 and the “community” icon I2 to determine what relationship the user who has accessed his site has with him. At a glance you can grasp. Alternatively, even a user who does not have a certain relationship with himself can grasp at a glance what keyword is designated on the search page by the “search” icon I3 and the keyword and arrives at his site. Alternatively, the “ranking” icon I4 can clearly understand that the user B has arrived at his / her site via the access ranking page.

Second Embodiment
FIG. 10 shows a main part of another aspect of the access history providing process executed by the SNS server 100. The process of S21 is executed instead of S7 and S8 of the first embodiment, or is additionally executed after the processes of S7 and S8.

  In S21, the profile information corresponding to the user B ID is acquired from the profile management table 54, and the profile information of the user B is stored in the “access source” item corresponding to the user A ID in the footstep management table 52. To do. That is, when it is determined that the user B does not have a certain relationship with the user A (“N” in S6), the profile information of the user B is stored in the “access source” item.

  Processing steps other than S21 are the same as those in the first embodiment. However, in S9, the profile information stored in the “access source” item corresponding to the user ID of the user A stored in the footstep management table 52 is configured as a part of the display information of the footstep page. . When the client 200a receives this last page, it displays it on the display screen.

  FIG. 11 shows an example of a footstep page. This page displays the user's profile information P that does not have a certain relationship with the user A, in addition to the “date and time”, “visitor user ID”, and “relation” of the latest 10 accesses to the site of the user A .

  The user A who has browsed the information as shown in FIG. 11 uses the “Tomodachi” icon I1 and the “Community” icon I2 to indicate what kind of relationship the user who has accessed his / her site has. At a glance you can grasp. Even if a user who has accessed his / her site is an unknown user who does not have a certain relationship with him / her, the profile information P can immediately know what kind of person the user is, and the user's introduction page There is no need to transition to.

Schematic configuration diagram of social network service (SNS) system Database conceptual diagram Conceptual explanatory diagram of information in the footstep management table Conceptual explanatory diagram of information in friend management table Conceptual explanatory diagram of information in community management table Conceptual illustration of information in member management table Conceptual illustration of information in profile management table The flowchart which shows the flow of the access history provision process which concerns on 1st Embodiment. The figure which shows an example of the footstep page which concerns on 1st Embodiment. The flowchart which shows the flow of the access history provision process which concerns on 2nd Embodiment. The figure which shows an example of the footsteps page concerning 2nd Embodiment

Explanation of symbols

1: Access history storage unit, 2: Additional management unit, 3: On-site content management unit, 4: Web server, 5: Database, 100: SNS server, 200: Client

Claims (8)

  1. An access history providing device used in a social network service system that provides a social network service via a network to users of each terminal,
    A user information storage unit for storing user identification information and user profile information of each terminal;
    A relationship storage unit that stores relationship information that defines a relationship between users stored in the user information storage unit;
    The first user access to the second user site in response to the terminal of the first user being an unspecified user having accessed a site managed by a second user being a specific user A history storage unit for storing the history of
    When the first user accesses the site managed by the second user, the relationship between the first user and the second user is specified according to the relationship information stored in the relationship storage unit. A relationship identification unit;
    History for creating access history information for displaying the history of access to the site of the second user by the first user and information indicating the relationship between the first user and the second user in association with each other An information creation department;
    In response to a request from the terminal of the second user, a history providing unit that provides the access history information created by the history information creating unit to the terminal of the second user;
    An access history providing apparatus comprising:
  2.   2. The access history provision according to claim 1, wherein the history information creation unit creates access history information that displays an icon representing a relationship between the first user and the second user in association with the access history. apparatus.
  3. The history storage unit further stores an access history of a transit site that is a site through which the first user has accessed to access the second user's site,
    In response to determining that the relationship between the first user specified by the relationship information and the second user is not a predetermined relationship, the history information creation unit passes through the first user. 3. The access history providing apparatus according to claim 1, wherein access history information for displaying information indicating a site type in association with the access history is created.
  4. The history storage unit further stores a history of search keywords input on the search page in response to determining that the search page is included in the transit site,
    In response to determining that the transit site includes a search page, the history information creation unit includes information indicating that the type of the transit site is a search page and a search keyword input on the search page. 4. The access history providing apparatus according to claim 3, wherein access history information to be displayed in association with the access history is created.
  5.   The access history providing unit stores in the user information storage unit in response to determining that the relationship between the first user and the second user specified by the relationship information by the relationship specifying unit is not a predetermined relationship. 5. The access history providing apparatus according to claim 1, wherein the access history providing device generates access history information that displays all or part of the profile information of the first user that is associated with the access history.
  6.   The relationship storage unit includes relationship information that defines friendships between users in the social network service, relationship information that defines users who are in friendship among the users, or users who are common in the social network service. The access history providing device according to claim 1, wherein the access history providing device includes at least one of relation information that defines information of a community to which the user belongs.
  7. An access history providing method used in a social network service system that provides a social network service to a user of each terminal via a network,
    Storing user identification information and user profile information for each terminal;
    Storing relationship information defining a relationship between users stored in the user information storage unit;
    The first user access to the second user site in response to the terminal of the first user being an unspecified user having accessed a site managed by a second user being a specific user Storing the history of
    Identifying the relationship between the first user and the second user in accordance with stored relationship information in response to the first user accessing a site managed by the second user;
    Creating access history information for displaying the history of access to the site of the second user by the first user and information indicating the relationship between the first user and the second user in association with each other. When,
    Providing the created access history information to the second user terminal in response to a request from the second user terminal;
    Access history providing method including.
  8.   A program for causing a computer to execute the access history providing method according to claim 7.
JP2006158963A 2006-06-07 2006-06-07 Access history providing device, method, and program Pending JP2007328538A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2006158963A JP2007328538A (en) 2006-06-07 2006-06-07 Access history providing device, method, and program

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2006158963A JP2007328538A (en) 2006-06-07 2006-06-07 Access history providing device, method, and program

Publications (1)

Publication Number Publication Date
JP2007328538A true JP2007328538A (en) 2007-12-20

Family

ID=38928967

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2006158963A Pending JP2007328538A (en) 2006-06-07 2006-06-07 Access history providing device, method, and program

Country Status (1)

Country Link
JP (1) JP2007328538A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011097624A3 (en) * 2010-02-08 2011-12-15 Facebook, Inc. Communicating information in a social network system about activities from another domain

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011097624A3 (en) * 2010-02-08 2011-12-15 Facebook, Inc. Communicating information in a social network system about activities from another domain
US10110413B2 (en) 2010-02-08 2018-10-23 Facebook, Inc. Communicating information in a social network system about activities from another domain

Similar Documents

Publication Publication Date Title
CN102474529B (en) Collect the information about the connection in social networking service
US7882039B2 (en) System and method of adaptive personalization of search results for online dating services
US8880583B2 (en) System and method for permitting geographically-pertinent information to be ranked by users according to users&#39; geographic proximity to information and to each other for affecting the ranking of such information
US7987198B2 (en) Indicating recent content publication activity by a user
CN102576368B (en) The framework of relevant answer frame as query suggestion is inputted to user for selecting and presenting
US7895177B2 (en) Enabling searching of user ratings and reviews using user profile location, and social networks
US8001102B2 (en) Integration of instant messaging with internet searching
AU2011243008B2 (en) Social graph that includes web pages outside of a social networking system
JP5383950B2 (en) Personalizing web pages outside social networking systems using content from social networking systems
EP2626798A1 (en) Electronic profile development, storage, use and systems for taking action based thereon
CN102971762B (en) Promote between social network user is mutual
JP3726748B2 (en) Mobile marketing method, system, server, user terminal, analysis terminal, and program
US9104771B2 (en) Providing relevant product reviews to the user to aid in purchasing decision
TWI416344B (en) Computer-implemented method and computer-readable medium for providing access to content
EP2747013A1 (en) System and Method for Analyzing Messages in a Network or Across Networks
JP5941075B2 (en) Search system, method, and computer-readable medium with integrated user judgment including a authority network
US8762302B1 (en) System and method for revealing correlations between data streams
US8140566B2 (en) Open framework for integrating, associating, and interacting with content objects including automatic feed creation
US20110055017A1 (en) System and method for semantic based advertising on social networking platforms
KR20100128321A (en) Advertisement display method, advertisement display system, and advertisement display program
US20190179516A1 (en) Matching Process System and Method
KR20140051222A (en) Client-side modification of search results based on social network data
KR100824091B1 (en) Search system and methods with integration of user annotations from a trust network
US20090319648A1 (en) Branded Advertising Based Dynamic Experience Generator
US20130298084A1 (en) Targeted advertising based on trending of aggregated personalized information streams