JP2015207136A - Friend management system for sns and friend management method using the same system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a friend management system of an SNS for enabling a user to extinguish a friendship in an SNS without performing any operation following the connection of a real society, and to reduce a stress by saving a workload related to the management of friends.SOLUTION: A friend management system of an SNS is used for an SNS having a personal page for enabling each user to display his or her own situation and a message page for enabling the user to send and receive a messages to and from the other users. The system includes: a browsing information acquisition part for enabling friend users to confirm the presence/absence of the browsing of their mutual personal pages; a message information acquisition part for enabling the users to confirm the presence/absence of utterance in their mutual message pages; a period management part for storing the information of a preliminarily set setting period; and a friend management part for moving the information of the friend users from a friend category to an other person category on the basis of those information.

Description

  The present invention relates to an SNS friend management system for managing other users associated with a user in SNS, so-called “friends”, and a friend management method using the same.

  In a real society, the relationship between people is determined by the “edge”. In other words, if there is a relationship between people, they will meet, and if there is no relationship, they will not meet. Also, if the edge continues, the relationship continues, and if the edge breaks, the relationship disappears. In this way, people repeat encounters and separations, and this is the providence of nature. This “margin” is often determined by mutual intentions, and the relationship will continue if there is an intention to continue the relationship with each other, and the relationship will disappear if there is no intention in each other.

  With the advancement of IT technology, a huge amount of data can be stored and stored in a server. In addition, due to the general spread of SNS, the number of users is still increasing. Under such circumstances, a friend function is attached to the SNS so that the user can easily interact with other acquaintance users. By having the friend function in this way, the user can know the current state of his / her acquaintance and exchange messages.

  However, since the server can accumulate a large amount of data as described above, the number of friends is basically not limited in the SNS. Therefore, the number of users as friends in the SNS often continues to increase. This leads to the user who wants to end the relationship and the user who is not interested continue to be associated with himself as a friend. Continuing exchanges with such a related user in the SNS causes a stress called SNS fatigue.

  In many cases, the SNS has a function of deleting a friend in order to end the relationship as a friend in the SNS, but the user needs to perform this act of deleting the friend himself. Deletion from a friend user with such a revised intention is a situation that cannot be easily performed in consideration of a relationship with the user to be deleted (for example, a relationship in the real world). That is, there is a stress that the friend cannot be deleted even though the friend is desired to be deleted.

  Some friendships will naturally end in the original “edge” mentioned above. Nevertheless, in SNS, this is stored for a long time as other user information as friends. This is contrary to “margin” and is considered to be affecting the user as stress.

  Within SNS, various users are welcomed as friends, and the relationship is established by starting from seeing what the friends are up to and sending messages individually. Considering the original “margin”, other users who do not see current status or exchange messages should not be friends. However, the current SNS system has only been devised to increase the number of friends (see, for example, Patent Document 1), and contrivances have been made to relieve stress in such a way that friends are deleted naturally. Not.

JP 2014-44721 A

  The present invention is based on the above prior art, and can be deleted without any user operation by comparing the friendship in the SNS to the edge of the real world, and other users registered as friends It is an object of the present invention to provide an SNS friend management system and a friend management method using the same, which can reduce the stress by eliminating the work burden associated with managing friends.

  In order to achieve the above object, in the present invention, a personal page for each user to display his / her recent situation, a message page provided for each other user to exchange messages with other users, The other user is classified into a friend user or another user, and is used in an SNS including a main page on which a link to the personal page of the friend user and a link to the message page is displayed, and is displayed on the personal page. A personal page server in which each user uploads data, a user information server that stores the information of the friend user and the other user for each user in a friend category and a different person category, and the friend user When the personal page of the friend user is updated, the update information is not displayed on the main page. Between the update management unit and the friend user, the browsing information acquisition unit for confirming whether or not the user has browsed each other's personal page, and the friend user speaking on the message page. A message information acquisition unit for confirming the presence or absence of information, when information is stored in the friend category of each other as the friend user, or when a personal page is browsed between the friend users, or the message page Based on the information of the period management unit that stores information of a preset period that is set in advance as starting when there is a mutual remark, and the browsing information acquisition unit, the message information acquisition unit, and the period management unit SNS friend management system, comprising: a friend management unit that moves information of the friend user from the friend category to the other person category To provide.

  Preferably, the friend management unit determines that the friend users are not browsing each other's personal pages in the browsing information acquisition unit, or the friend users are speaking to each other in the message information acquisition unit. In the case where it is determined that there is no mutual action, the period of not having reached each other's action exceeds the set period stored in the period management unit. Move information from the friends category to the others category.

  Preferably, the friend management unit determines that the friend users are browsing each other's personal pages in the browsing information acquisition unit, or the friend users speak to each other in the message information acquisition unit. If the period until reaching each other's action exceeds the set period stored in the period management unit, the other friend user at the user information server of each user Is moved from the friend category to the other person category.

  Preferably, the SNS friend management system further includes an update operation unit that automatically updates the personal page within the set period.

  In the present invention, the friend users check each other's personal page, or the friend users talk to each other on the message page, and the mutual communication exists in both directions. A bidirectional confirmation step for confirming whether or not the bidirectional exchange is performed within the set period, and a bidirectional period confirmation step for confirming whether or not the bidirectional exchange is performed, There is provided a friend management method using a friend management system of SNS, comprising a non-bidirectional period confirmation step for confirming whether a set period has elapsed.

  According to this invention, a friend user turns into a stranger user, when it is judged in the friend management part that friend users are not browsing a mutual personal page within a setting period. That is, the friendship in SNS disappears. The same applies when it is determined that the friend users are not speaking to each other on the message page. Furthermore, even if these browsing and speaking actions are performed in both directions between friend users, the same applies if the actions are not performed within the set period. In these cases, since it can be determined that there is no relationship between the friend users, the user automatically becomes another user. This makes it possible to eliminate the friendship in the SNS by comparing it with the edge of the real world without any operation by the user, and to sort out other users registered as friends. It is possible to reduce the stress by eliminating the work burden of managing friends.

  In addition, by providing an update operation unit, it is possible to arouse browsing of personal pages of friend users who want to continue or are interested in the relationship, so if there is a relationship, two-way exchange will be performed This means that you can continue friendships based on relationships.

It is the schematic which shows an example of the main page of SNS where the friend management system of SNS which concerns on this invention is applied. It is the schematic which shows an example of the personal page of SNS to which the friend management system of SNS which concerns on this invention is applied. It is the schematic which shows an example of the message page of SNS to which the friend management system of SNS which concerns on this invention is applied. It is the schematic of the friend management system of SNS which concerns on this invention. It is a flowchart which shows the friend management method using the friend management system of SNS which concerns on this invention. It is the schematic which shows another example of a main page. It is the schematic which shows an example of a profile page.

  As shown in FIG. 1, a display area 2 for displaying other user information registered as a friend user on the SNS is arranged on the main page 1 of the SNS to which the present invention is applied. In this display area 2, a profile image 3 of a friend user is displayed. The profile image 3 can freely set a photograph, an image, or a so-called avatar for each user. Further, in the display area 2, a link 5 to the personal page 4 (see FIG. 2) and a link 7 to the message page 6 (see FIG. 3) are displayed.

  As shown in FIG. 2, the profile image 3 of the friend user is displayed on the personal page 4, for example, the user name 8 is displayed beside the profile image 3. This user name may be displayed near the profile image 3 in the display area 2. The personal page 4 is a page given to each user, and is for uploading and describing his / her recent situation. For example, a date column 9 and a recent condition description column 10 are arranged, and each date is sequentially updated as one block. Text, a photograph, or a moving image can be put in the recent condition description column 10. Since this personal page 10 displays the current status of the user, a user who cares about the user browses from the link 5 with considerable frequency.

  What is important here is that, in the display area 2, the update information indicating that the personal page 4 of the friend user has been updated is not displayed in the link 5. In other words, the fact that the personal page 4 has been updated is not recognized until the personal page 4 is actually moved from the link 5 to the personal page 4. Information such as text uploaded to the personal page 4 is not displayed as it is on the main page 1, but only the link 5 is displayed. I can't. Thereby, each user views the personal page 4 of only friend users who really want to know the current status.

  On the other hand, other users are classified into friend users or other users, and only the friend users are displayed in the display area 2. Therefore, in the case of a relationship with another user, the user's personal page 4 cannot be viewed and the message page 6 cannot be exchanged.

  As shown in FIG. 3, the message page 6 is a page provided for each friend user in order for the friend users to exchange messages. Here, for example, a balloon 11 is displayed beside the profile image 3, and a text message is displayed in the balloon 11. The user name 8 may be added to the profile image 3 for easy understanding. By placing the profile image 3 of the friend user on the left end and the self on the right end on the message page 6, for example, it is possible to show a sense of realism between the users.

  The present invention is used for the SNS as described above. As a premise, the update of the personal page 4 of the friend user is used for an SNS having a specification that can be confirmed only through the link 5. As is apparent from FIG. 4, the SNS friend management system 12 according to the present invention is formed by a terminal 14 and an application server 15 that are communicably connected via a network communication network 13. A personal page server 16 is arranged in the application server 15. The personal page server 16 is an area where each user uploads data in order to display his / her current status on the personal page 4. Therefore, the user's personal page 4 is sequentially updated by uploading text, photos, and the like to the personal page server 16. The application server 15 is provided with a user information server 17. The user information server 17 stores information on friend users and other users for each user. The friend user information is stored in the friend category 18 in the user information server 17, and the other user information is stored in the other person category 19 in the user information server 17.

  The application server 15 is provided with an update management unit 20. The update management unit 20 is configured to hide the update information on the main page 1 when the friend user updates the personal page 4. That is, as described above, the information on the recent situation uploaded by the friend user to the personal page server 16 is not displayed on the link 5 of the main page 1 and is moved to the personal page 4 via the link 5 to the last. It can be confirmed with. Therefore, if it is desired to know the current state of each other, it is necessary to operate each other's link 5 on each main page 1 to move to and view each other's personal page 4. The application server 15 is also provided with a browsing information acquisition unit 21 for confirming whether or not each of the personal pages 4 has been browsed, that is, when browsing has been performed in both directions.

  Further, the application server 15 is provided with a message information acquisition unit 22. This message information acquisition part 22 confirms the presence or absence of uttering in the message page 6 mutually with the friend user. That is, it is for confirming that there was a statement in both directions.

  Further, the application server 15 is provided with a period management unit 23. The period management unit 23 stores information on a preset setting period. The setting period can be freely determined by the side managing the application server 15. When the information is stored in each other's friend category 18 as a friend user (registered as a friend user), or when the friend users browse each other's personal page 4, or the message page 6 Start when there is a remark in each other. That is, the setting period starts from when the friendship is first established, and is reset when there is a two-way browsing or remark, and the setting period starts again from the beginning.

  A friend management unit 24 is arranged in the application server 15. This friend management part 24 moves the information of a friend user from a friend category to another person category based on the information of the browsing information acquisition part 21, the message information acquisition part 22, and the period management part 23. That is, the friend management part 24 makes a friend user another user, and extinguishes the friend relationship on SNS automatically, without requiring operation of each user.

  The friend management method according to the present invention will be described below. As shown in FIG. 5, first, the friend users check each other's personal page 4, or the friend users speak each other on the message page 6. A bidirectional confirmation process is performed to confirm whether it exists in (Step S1). If each other's personal page 4 is viewed in both directions, or if the message page 6 is spoken in both directions, whether or not the two-way exchange is performed within the set period. A bidirectional period confirmation step for confirmation is performed (step S2). If it is performed within the set period, the friendship on the SNS is maintained (step S3). Note that the set period is a set period until the next bidirectional exchange is reset after being reset when there is a bidirectional exchange.

  On the other hand, when there is no mutual interaction in the interactive confirmation process, that is, when the browsing information acquisition unit 21 determines that the friend users are not browsing each other's personal pages, or message information If the acquisition unit 22 determines that the friend users are not speaking to each other, a non-bidirectional period confirmation process is performed. In this non-bidirectional period confirmation step, it is determined whether or not there is a state where there is no bidirectional exchange between the users for the set period (step S4). If the set period has not elapsed, the bidirectional confirmation process is performed until it elapses. When the set period has elapsed, the information of the other friend user is moved from the friend category 18 to the other person category 19 in the user information server 17 of each user (step S5). As a result, the friendship between the users disappears, and the display area 2 of each other's user is hidden on each other's main page 1.

  On the other hand, when interactive communication is confirmed in the interactive confirmation process, that is, when the browsing information acquisition unit 21 determines that the friend users are viewing each other's personal page 4, or message information acquisition. Even if it is determined that the friend users are talking to each other in the unit 22, if the period until the interactive action exceeds the set period stored in the period management unit 23, The information of the other friend user is moved from the friend category 18 to the other person category 19 in the user information server 17 of each user (step S5). That is, the friendship is terminated.

  In the friend management method of the present invention based on the flowchart as described above, when the friend management unit 24 determines that the friend users are not browsing each other's personal page 4 within the set period, Become. That is, the friendship in SNS disappears. The same applies when it is determined on the message page 6 that the friend users are not speaking to each other. Furthermore, even if these browsing and speaking actions are performed in both directions between friend users, the same applies if the actions are not performed within the set period. In these cases, since it can be determined that there is no “margin” between the friend users, it automatically becomes another user. This makes it possible to eliminate the friendship in the SNS by comparing it with the edge of the real world without any operation by the user, and to sort out other users registered as friends. It is possible to reduce the stress by eliminating the work burden of managing friends.

Next, it will be described that by using the present invention, separation of users due to “edge” in the real world can be realized even on SNS. Human relationships are roughly divided into the following patterns.
(1) Close friendships (2) Occasionally contactor or rarely contacted but connected with hard bonds (eg local childhood friend)
(3) Relationship between superiors, subordinates and social relations such as social relations (4) Relationship for the moment to be friends for the time being (5) Although they are not close friends, they are disgusted with each other There is no relationship (for example, it is fun to meet and talk but does not actively communicate)
(6) One-sided relationship with favor (7) Relationship with which one wants to quit contact with time (8) Relationship between both sides got worse over time Relationship (9) Bad relationship from the beginning

  First, “(1) close relationship with whom we often communicate” will be described. Since it can be said that there is a relationship between such users, the relationship as a friend user should be maintained also on SNS. Under such circumstances, the browsing of the personal page 4 and the exchange on the message page 6 are frequently performed. Therefore, there is a bidirectional exchange (step S1), and the exchange is also performed within the set period (step S2), so that the friendship is maintained (step S3).

  Next, “(2) Occasionally contacted or rarely negotiated but connected with hard bonds (eg local childhood friend)” will be explained. Since it can be said that the users who are in such a relationship also have an edge, the relationship as a friend user should be maintained also on SNS. However, since there is no frequent browsing of personal page 4 or message exchange under such circumstances (step S1), if there is no bidirectional exchange during the set period (step S4), the friend relationship is deleted. (Step S5). Therefore, an update operation unit 25 is arranged in the application server 15 in the system 12. The update operation unit 25 automatically updates the personal page 4 within a set period. For example, on the user's birthday or any anniversary, an update to notify that is automatically performed. Or when profile information (address, title, hobby, etc.) is changed or when the profile image is changed. In this way, by automatically updating the personal page 4 within the set period, the willingness to browse or send messages is aroused, and if the personality is tied with a solid bond, the individual page 4 is viewed at least within the set period Or exchange messages. As a result, the bidirectional exchange (step S1) is performed within the set period (step S2), and the friendship is maintained (step S3). If there is no two-way exchange within the set period, there is no friendship, but this is not a problem because it can be said to be a natural flow when considering the relationship between the people to be realized by the present invention.

  Next, “(3) Relationship between superiors, subordinates, and social relations such as social relationships” will be described. Users who are in such a relationship may have friendship while the social relationship continues, but when the relationship ends, the relationship is considered to have disappeared, and the relationship is also terminated on SNS Should also be considered good. If one user sends a message, the other user also returns a message with a social decree, so the two-way exchange is probably done within the set period, and the friendship between them is maintained. However, when the social decree relationship is completed, since the exchange is one-way or not at all (step S1), the friendship is ended after the set period (step S4) (step S5). This makes it possible to realize friendships based on edges.

  Next, “(4) Relationship between being able to be friends for now” will be described. Since the users who are in such a relationship lose their bidirectional communication with the passage of time, it is determined that there is no relationship when the time comes, and the friendship should be terminated. Therefore, since bidirectional communication (step S1) is initially performed within the set period (step S2), the friendship is maintained (step S3). However, when there is no longer a bidirectional exchange (step S1), the exchange disappears during the set period (step S4), so that they are deleted from the friend users. As a result, the friendship is maintained as long as there is an edge, and the friendship ends when the edge disappears, so the friendship based on the edge can be realized.

  Next, “(5) Relationships that are not close friends but do not dislike each other (for example, relationships that are fun to meet and talk but do not actively communicate)” will be described. Since users who are in such a relationship will not be able to communicate with each other, it is not necessarily said that there is an edge. In such a case, there is no two-way exchange when contact is lost (step S1), and since there is no exchange during the set period (step S4), they are deleted from the friend users. As a result, the friendship is maintained as long as there is an edge, and the friendship ends when the edge disappears, so the friendship based on the edge can be realized.

  Next, “(6) One-sided relationship with favor” will be described. It cannot be said that users in such a relationship have a relationship. If you take a favored user, you will want to end your friendship. In this case, of course, there is no bidirectional exchange (step S1), and since there is no exchange during the set period (step S4), they are deleted from the friend users. This makes it possible to realize a friendship based on the edge, and since it does not dare to delete the friend, the stress on friend management can be reduced.

  Next, “(7) A relationship in which one wants to quit contacting each other over time” will be described. It can be said that the users who are in such a relationship are in a relationship where there is no longer a bidirectional exchange, as in (3) and (4) above. Therefore, the friendship ends when an appropriate period of time elapses based on the relationship. As for the flow, the friendship ends as in (3) and (4) above.

  Next, “(8) Relationship between both sides that became worse over time” will be described. In this case, as in (7), the friendship is over. Further, in the case of “(9) a bad relationship from the beginning”, it can be considered that the two-way exchange has not passed the set period from the beginning, so the friendship is also terminated.

  If the friendship is further organized from the viewpoint of relationship, when confirming the set period in step S2 or step S4, for example, the number and frequency of two-way exchanges (browsing and utterances), message context, and sentence length The presence / absence of a predetermined keyword may be confirmed at the same time. The set period may be appropriately changed according to these. By providing a plurality of such parameters, it is possible to realize friendships that are compared with edges more accurately.

  Further, in the present system 12, encounters with other users are also determined by the relationship. Other users recorded in the phone book, address book, or address book at the time of SNS start are automatically registered as friend users. That is, the user information is stored in the friend category 18. However, users who are not connected are gradually deleted from the friend users according to the flowchart. And when it becomes a new friend user, it cannot search for another user by search etc. by itself, and only the other user judged by the system 12 becomes a friend user. If the system 12 judges, it will be automatically added as a friend user. Even if a user who does not know at all becomes a friend user, if one of them does not browse or speak, it is determined that there is no connection and is automatically deleted from the friend user. By repeating this, only a user who has a connection with the friend user on the SNS remains. In other words, the system 12 can only be in a friendship relationship with a user who has an “edge”, and the friendship with a user who has no “edge” ends naturally. This is a normal relationship with other people, and if this can be realized, so-called SNS fatigue and stress on the management of friends will not be given to the user.

  In addition, as a friend user who adds that the system 12 has a connection, for example, a user who has many common points in the profile, such as address, age, occupation, birthplace, hobby, date of birth, etc. . As shown in FIG. 4, the profile information is arranged in the application server 15 as the user information storage unit 26. Then, it is the matching control unit 27 disposed in the application server 15 that determines that the users have an edge based on these pieces of information. That is, only other users selected only by the matching control unit 27 are added as friend users.

  On the other hand, the update operation unit 25 has been introduced in the above in order to encourage the browsing of the personal page 4 of the friend user. Distribution may be performed. If the coupon is distributed randomly to the user's personal page 4 and this coupon can be given to another user, the user should browse the personal page 4 to see if the friend user has received the coupon. And if the desired coupon is delivered to the friend user, a message about the transfer of the coupon should be transmitted, and the partner friend user should also reply to this message. This leads to bidirectional exchange, and can contribute to maintaining friendships between users who have ties. Even if this wants a coupon, if it is another friend user who does not want to contact, the user's personal page 4 should not be browsed. With this mechanism, you can organize friendships by relationship.

  As shown in FIG. 6, the main page 1 may be displayed so that only the profile image 3 of the friend user is arranged. At this time, the profile image 3 also serves as a link button, and can move from the image 3 to the profile page 29 of each friend user (see FIG. 7). If there are a plurality of profile images 3 of the friend user on the profile page 29, all of them are displayed (two in the example of FIG. 7), and information such as the place of birth and occupation of the friend user is displayed in the self-introduction column 28. ing. The profile page 29 also displays the link 5 to the personal page and the link 7 to the message page. Thus, by providing the friend user's profile page 29 before browsing the personal page 4, it is possible to confirm in advance what kind of person the user is. Further, browsing the profile page 29 may be counted and used as a parameter for organizing friendships. At this time, if the arrangement of the profile image 3 displayed on the main page 1 is randomly arranged every time, the profile page 29 is referred to until the friend user is searched every time, so as a parameter for measuring the edge depth It can be suitably used. Further, the setting period may be extended by browsing the profile page 29 in both directions.

1: Main page, 2: Display area, 3: Profile image, 4: Personal page, 5: Link to personal page, 6: Message page, 7: Link to message page, 8: User name, 9: Date column 10: Current status description column, 11: Balloon, 12: SNS friend management system, 13: Network communication network, 14: Terminal, 15: Application server, 16: Personal page server, 17: User information server, 18: Friend category , 19: Others category, 20: Update management unit, 21: Browse information acquisition unit, 22: Message information acquisition unit, 23: Period management unit, 24: Friend management unit, 25: Update operation unit, 26: User information storage unit 27: Matching control unit 28: Self-introduction column 29: Profile page

Claims (5)

A personal page for each user to display their current status,
A message page provided for each other user to exchange messages with other users;
The other user is classified into a friend user or another user, and is used for an SNS including a main page on which a link to the personal page of the friend user and a link to the message page are displayed.
A personal page server where each user uploads data for display on the personal page;
A user information server for storing the information of the friend user and the other person's user for each user, divided into a friend category and a different person category,
When the friend user updates the personal page of the friend user, an update management unit that hides the update information on the main page;
A browsing information acquisition unit for confirming the presence or absence of browsing each other's personal pages with the friend user;
A message information acquisition unit for confirming whether or not he / she is speaking on the message page with the friend user;
When information is stored in the friend category of each other as the friend user, when each friend's personal page is browsed by the friend users, or when each other speaks on the message page A period management unit in which information of a preset period is stored;
SNS comprising: a browsing information acquisition unit, a message information acquisition unit, and a friend management unit that moves information of the friend user from the friend category to the other person category based on information of the period management unit Friends management system.   The friend management unit determines that the friend users are not browsing each other's personal pages in the browsing information acquisition unit, or determines that the friend users are not speaking to each other in the message information acquisition unit In the case where the period of not reaching each other's action exceeds the set period stored in the period management unit, the information on the friend user of the other party is stored in the user information server of each user. The SNS friend management system according to claim 1, wherein the friend category is moved to the other person category.   The friend management unit determines that the friend users are browsing each other's personal pages in the browsing information acquisition unit, or determines that the friend users are speaking to each other in the message information acquisition unit If the period until reaching each other's action exceeds the set period stored in the period management unit, the information on the friend user of the other party is displayed on the user information server of each user. The SNS friend management system according to claim 1 or 2, wherein the friend category is moved to the other person category.   The SNS friend management system according to any one of claims 1 to 3, further comprising an update operation unit that automatically updates the personal page within the set period. Check whether the friend users are viewing each other's personal pages, or whether the friend users are speaking each other on the message page, and confirm whether each other's interaction exists in both directions An interactive confirmation process,
A bidirectional period confirmation step of confirming whether or not the bidirectional exchange is performed within the set period;
The SNS according to any one of claims 1 to 4, further comprising a non-bidirectional period confirmation step of confirming whether or not the set period has elapsed when there is no bidirectional exchange. Friend management method using a friend management system.

Images