SNS system and management server
The SNS system maintains user interactions chronologically, addressing the issue of lost connections by recording and displaying histories, enabling effective reconnection and recognition of past relationships.
Patent Information
- Application Number
- JP2023084469
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-23
- Publication Date
- 2024-12-05
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Conventional SNS systems fail to recognize and maintain connections with acquaintances after a period of no contact, leading to a loss of context about how users met, making it difficult to reconnect.
An SNS system with a management server that records and displays events and interactions with other users in chronological order, allowing users to add and view histories of connections, and includes functions for connecting users and exchanging messages, thereby maintaining a record of interactions.
Enables users to recognize and reconnect with acquaintances by preserving the history of interactions, facilitating reconnection and understanding of past relationships.
Smart Images

Figure 2024168072000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an SNS system and techniques related thereto. [Background technology]
[0002] Conventionally, many technologies for providing SNS (Social Networking Service) have been proposed (see, for example, Patent Documents 1 and 2). Specifically, Patent Document 1 discloses a technology for improving the availability of advertising information by improving the quality of posted information and thereby improving access to posted information. Patent Document 2 discloses an SNS system that allows each salesperson to easily use functions similar to marketing automation. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2020-187722 A [Patent Document 2] JP 2020-091869 A Summary of the Invention [Problem to be solved by the invention]
[0004] By the way, if you use the SNS services mentioned above, it is possible to connect with many people (become friends on the SNS). However, while you can get to know many people, after connecting with them (becoming "friends" on the SNS), there are quite a few acquaintances with whom you may not be in contact for a while, and you may never be able to contact them again.
[0005] Therefore, when, after some time has passed, you see a post on an SNS from an acquaintance (friend) with whom you have lost contact, you may not be able to recognize who that acquaintance (friend) was (for example, how you met them). In this regard, since conventional SNS is designed to one-sidedly view posts from acquaintances (friends), simply viewing the posts may not allow you to recognize how you met that acquaintance (friend).
[0006] Therefore, an object of the present invention is to provide an SNS system and related techniques that enable a user to recognize people connected via SNS after the fact. [Means for solving the problem]
[0007] In order to achieve the above object, the present invention provides a social networking service (SNS) the user terminal displays a new history addition screen for allowing the user to add events between the user and the other user as history, and when new history information is input via the new history addition screen, the user terminal transmits the new history information to the management server, and the management server records the new history information received from the user terminal in chronological order in a history history as new history related to the other user for the user, the user terminal transmits a history view request related to the other user for the user to the management server, and in response to the history view request, the management server transmits the history history of the user related to the other user to the user terminal, and the user terminal displays the events of the user between the user and the other user in chronological order based on the history history.
[0008] Here, it is preferable that the functions of the SNS include a chat function capable of sending and receiving messages between the user and the other users, and when an instruction to add a specific message to the history is given on a chat screen with the other user, the user terminal sends a request to add the specific message to the history of the specific message to the management server, and in response to the history addition request, the management server records the specific message in chronological order in the history history as a new history of the user related to the other user.
[0009] Furthermore, it is preferable that the functions of the SNS include a connecting function for connecting a first user with a second user from among multiple users connected to the user, the user terminal sending a connecting request to connect the first user with the second user to the management server, and the management server, in response to the connecting request, recording the fact that the user has connected the first user with the second user in chronological order in the history history as a new history of the user relating to the first user and recording the fact in chronological order in the history history as a new history of the user relating to the second user.
[0010] It is also preferable that the management server records in chronological order in the history history that the user has connected the first user to the second user in response to the connection request as new history for the user of the first user and in chronological order in the history history as new history for the second user of the first user, and records in chronological order in the history history that the user has connected the second user to the first user in response to the connection request as new history for the user of the second user and in chronological order in the history history as new history for the first user of the second user.
[0011] Furthermore, in response to the connection request, it is preferable that the management server creates a chat room in which messages can be sent and received between the user, the first user, and the second user, and adds the second user as a friend of the first user and adds the first user as a friend of the second user.
[0012] The present invention also provides a management server that manages an SNS (Social Networking Service), configured to be capable of network communication with user terminals operated by users registered on the SNS, wherein functions of the SNS include a history function that records events between the user and other users connected to the SNS in chronological order as history, and the management server receives new history information regarding events between the user and the other users from the user terminal, records the new history information in chronological order in the history history as new history for the user regarding the other users, receives a history viewing request for the user regarding the other users from the user terminal, and in response to the history viewing request, transmits the history history of the user regarding the other users to the user terminal. Effect of the Invention
[0013] According to the present invention, a user is provided with a function for recording events with other users with whom they are connected via SNS in chronological order as a history, making it possible for the user to recognize people with whom they are connected via SNS after the fact.
[0014] Incidentally, the above-mentioned Patent Documents 1 and 2 do not disclose any specific configuration for recognizing people connected via an SNS after the fact, as in the SNS system of the present invention. [Brief description of the drawings]
[0015] [Figure 1] 1 is a schematic diagram showing a system configuration of an SNS system according to an embodiment of the present invention. [Diagram 2] A sequence diagram showing the interaction between a user terminal and a management server when adding a new history. [Diagram 3] FIG. 13 is a diagram showing an example of a screen in which the user "Yamada" is selected from the account of the user "Tanaka." [Figure 4]13A and 13B are diagrams showing an example of a new history addition screen before (left) and after (right) input. [Diagram 5] FIG. 13 is a diagram showing an example of a database that records the history of each of the user “Tanaka’s” friends. [Figure 6] FIG. 13 is a diagram showing an example of a history list screen. [Figure 7] FIG. 11 is a sequence diagram showing the interaction between a user terminal and a management server in the connect function. [Figure 8] FIG. 13 is a diagram showing an example of a call screen for a connecting function. [Figure 9] FIG. 13 is a diagram showing an example of a selection screen for selecting a friend (connection) to connect with. [Figure 10] FIG. 13 is a diagram showing an example of a chat room screen in which a person connected by the connecting function sends and receives messages with the connected people. [Figure 11] 13 is a diagram showing an example of a screen when viewing the history of user "Sato" using the account of user "Tanaka." [Figure 12] FIG. 13 is a diagram showing an example of a screen when viewing the history of user "Yamada" using the account of user "Tanaka." [Figure 13] FIG. 13 is a diagram showing an example of a screen when viewing the history of user "Sato" using the account of user "Yamada." [Figure 14] FIG. 13 is a diagram showing a state in which a specific message is selected on the chat room screen. [Figure 15] FIG. 13 shows a screen for adding a specific message selected on the chat room screen to the history. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0016] <1. Embodiment> An SNS system and a management server according to an embodiment of the present invention will be described with reference to Figures 1 to 13. The SNS system of this embodiment is a system for providing a general SNS where registered users can interact with each other.
[0017] In the following, as an example of an SNS system according to the present invention, an SNS system 1 shown in Fig. 1 is illustrated. Also, as an example of a management server 2 according to the present invention, the management server 2 also shown in Fig. 1 is illustrated.
[0018] The SNS of this embodiment has functions such as "tags," "history," "connect," and "chat" in addition to the functions of a general SNS. In this embodiment, users who are connected to each other on the SNS are also called "connections."
[0019] "Tags" is a feature that allows you to leave notes about connected friends that you want to remember. With this feature, you can record your friend's occupation, hobbies, interests, etc. as tags on their profile.
[0020] "History" is a function that records events with people connected on SNS (connected friends). This function allows you to record actions (events) that you tend to forget, such as casual messages in chat rooms or when A introduced B to you, as history. This function will be described in detail later.
[0021] "Connect" is a function that connects (creates connections) between selected users from among multiple users connected on SNS. When a connection is created by "Connect," the interactions and facts leading up to the connection are automatically recorded. This function will be described in detail later.
[0022] "Chat" is a function that allows users who are connected via SNS to exchange messages in chat rooms.
[0023] Next, the system configuration of the SNS system in this embodiment will be described with reference to Fig. 1. As shown in Fig. 1, the SNS system 1 is configured to include a management server 2 that manages the SNS (Social Networking Service) and each user terminal 3 (3A, 3B, 3C, ...) used by each user of the SNS. Note that each user terminal 3A, 3B, 3C, ... has the same configuration. Therefore, in the following description, each user terminal 3A, 3B, 3C, ... may be collectively referred to simply as "user terminal 3" as necessary.
[0024] The management server 2 is configured as a known server computer. Specifically, the management server 2 includes a CPU, RAM, ROM, a communication unit (communication IF), a storage unit, and the like, which are interconnected by a bus.
[0025] The CPU is a central processing unit, and executes each function (various processes) of the SNS in cooperation with the RAM, ROM, etc. In detail, the CPU executes each function (various processes) of the SNS by executing one or more programs that are pre-installed. In this way, the CPU functions as a control unit that comprehensively controls the operation of the management server 2.
[0026] RAM is the main memory that temporarily stores data during CPU calculations. ROM is a read-only memory that stores programs such as BIOS.
[0027] The storage unit is composed of a solid state drive (SSD) or hard disk drive (HDD), and stores the history database DB (see Figure 5) described below.
[0028] The user terminal 3 is configured by a known smartphone, a known tablet terminal, or the like, that is equipped with built-in memory (RAM, ROM, etc.) and an operating system (OS).
[0029] A dedicated application program for using SNS (hereinafter, also simply referred to as an “SNS application”) is installed in the user terminal 3. The SNS application is a program that runs on the OS of the user terminal 3.
[0030] The user terminal 3 is provided with a touch panel display (hereinafter, simply referred to as a touch panel) having a display function and an operation input function. On this touch panel, various operation screens for using the SNS are displayed in conjunction with the execution of the SNS application.
[0031] The user terminal 3 has a network communication function for connecting to the Internet via a mobile phone network or WiFi, whereby the user terminal 3 is connected to the management server 2 via the Internet.
[0032] Next, we will explain the process of adding a new history using "History," a function of SNS, with reference to the sequence diagram in Figure 2. As mentioned above, "History" is a function that records events that a user has had with other users connected via SNS in chronological order as history.
[0033] Here, an example is shown in which "Tanaka" adds an event with his friend "Yamada" as a new history. Note that "Tanaka" is an example of a "user" according to the present invention, and "Yamada" is an example of an "other user" according to the present invention.
[0034] When "Tanaka" selects "Yamada" from among his friends connected via SNS on the user terminal 3, the screen SG1 shown in Fig. 3 is displayed on the display of the user terminal 3. On the screen SG1, a history button and a plus icon are arranged to the right of the history button.
[0035] When "Tanaka" selects (tap) the plus icon on screen SG1, screen SG2 (an example of a new history addition screen) shown in the left diagram of Fig. 4 is displayed on the display of user terminal 3 (step S11 in Fig. 2). As shown in the left diagram of Fig. 4, the "date and time" is automatically recorded on screen SG2. However, the operator can also manually rewrite the "date and time".
[0036] As shown in the right diagram of Fig. 4, when "Tanaka" fills in "Title" and "Details" on screen SG2, selects "Photo", and then selects (tap) the "Add" button (step S12), the user terminal 3 transmits new history information to the management server 2 (step S13). Note that, although an example is given here of selecting "Photo" in addition to "Title" and "Details", selecting "Photo" is not necessarily required.
[0037] The new history information sent to the management server 2 includes text data for "Title" and "Details" and image data for "Photo" (only when "Photo" is selected). The new history information also includes information indicating that it is a history of "Tanaka" related to "Yamada" (for example, the user ID of "Tanaka" and the user ID of "Yamada").
[0038] When the management server 2 receives the new history information from the user terminal 3, the management server 2 records the new history information in chronological order in the history as new history of "Tanaka" related to "Yamada" (step S14).
[0039] Specifically, the management server 2 records a new history in the history history database DB shown in Fig. 5. In more detail, the management server 2 identifies the FRIEND ID of "Yamada" associated with the USER ID of "Tanaka" from the history history database DB, and associates the new history with the identified FRIEND ID of "Yamada" and stores them in chronological order. For example, if two histories (HISTORY 1, HISTORY 2) are already associated and recorded with the identified FRIEND ID of "Yamada", the management server 2 adds the new history as the third HISTORY 3.
[0040] Note that Figure 5 shows a history database DB for each friend associated with "Tanaka," but it is assumed that similar history databases are also recorded for other users ("Yamada" and "Sato").
[0041] Users will be able to check the history of other users they are connected to on social media after the fact, as the history will be recorded.
[0042] In the above example, the history of "Tanaka" related to "Yamada" is registered. In this case, "Tanaka" can check the history related to "Yamada" after the fact. Specifically, when a history viewing operation of "Tanaka" related to "Yamada" is performed on the user terminal 3, the user terminal 3 sends a history viewing request of "Tanaka" related to "Yamada" to the management server 2.
[0043] In response to the history viewing request, the management server 2 extracts all history (history history) relating to “Tanaka” and “Yamada” from the history history database DB and transmits it to the user terminal 3 .
[0044] The user terminal 3 displays on the display a screen SG3 (history list screen) shown in Fig. 6 based on the entire history (history history) of "Tanaka" related to "Yamada". On the screen SG3, events between "Tanaka" and "Yamada" are displayed in chronological order.
[0045] Next, with reference to the sequence diagram in FIG. 7, a process of connecting users who are connected on an SNS using a "connect" function of the SNS will be described. Here, an example is shown of "Yamada" connecting "Sato" and "Tanaka" who are connected on the SNS. Note that "Yamada" is an example of a "user" according to the present invention. Also, "Sato" is an example of a "first user" according to the present invention, and "Tanaka" is an example of a "second user" according to the present invention.
[0046] In addition, the terminal used by "Yamada" is referred to as user terminal 3A, the terminal used by "Sato" is referred to as user terminal 3B, and the terminal used by "Tanaka" is referred to as user terminal 3C.
[0047] When the "Connect" button is selected on the screen SG4 (encounter management book) shown in FIG. 8 on the user terminal 3A (step S21 in FIG. 7), the user terminal 3A transmits a connection start instruction to the management server 2 (step S22).
[0048] In response to the connection start instruction, the management server 2 transmits an instruction to display the screen SG5 (connection selection screen) shown in FIG. 9 to the user terminal 3A (step S23).
[0049] In response to the display instruction, the user terminal 3A displays a screen SG5 (connection selection screen). When the people to be connected ("Sato" and "Tanaka") are selected on the screen SG5, the user terminal 3A transmits connection information to the management server 2 together with a connection request for connecting "Sato" and "Tanaka" (step S25). The connection information includes identification information of the person to be connected (Yamada) and identification information of the people to be connected ("Sato" and "Tanaka").
[0050] In response to the connection request, the management server 2 creates a chat room in which messages can be sent and received between the person who can connect ("Yamada") and the people who want to connect ("Sato" and "Tanaka") (step S26).
[0051] Furthermore, the management server 2 registers the people to be connected ("Sato" and "Tanaka") as a connection, that is, adds "Tanaka" as a friend of "Sato" and also adds "Sato" as a friend of "Tanaka" (step S27).
[0052] In addition, the management server 2 automatically records in the history history database DB that "Yamada" connected "Sato" and "Tanaka" as a new history of "Yamada" (the person who connected) regarding "Sato" (the person who connected), and automatically records in the history history database DB as a new history of "Yamada" (the person who connected) regarding "Tanaka" (the person who connected) (step S28).
[0053] Furthermore, the management server 2 automatically records in the history history database DB that "Yamada" connected "Tanaka" with "Sato" as a new history of "Tanaka" related to "Yamada", and also automatically records in the history history database DB as a new history of "Tanaka" related to "Sato" (step S29).
[0054] Similarly, the management server 2 automatically records in the history history database DB that "Yamada" has connected "Sato" with "Tanaka" as a new history of "Sato" related to "Yamada", and also automatically records in the history history database DB as a new history of "Sato" related to "Tanaka" (step S29).
[0055] Thereafter, the management server 2 notifies the user terminals 3B and 3C of the connection registration (steps S30 and S32). Then, the user terminals 3B and 3C each display a notification screen (not shown) (steps S31 and S33).
[0056] As shown in Figure 11, when "Sato" is selected in "Tanaka's" account, screen SG7 (left diagram in Figure 11) is displayed, which shows part of "Tanaka's" history related to "Sato". When "Show all" is selected at the bottom of the history on screen SG7, screen SG8 (right diagram in Figure 11) is displayed, which shows the entire history. Note that as part of "Tanaka's" history related to "Sato", it is noted that he was connected to "Yamada".
[0057] As shown in Figure 12, when "Yamada" is selected in "Tanaka's" account, screen SG9 (left diagram in Figure 12) is displayed, which displays part of "Tanaka's" history related to "Yamada". When "Show all" is selected at the bottom of the history on screen SG9, screen SG10 (right diagram in Figure 12) is displayed, which displays the entire history. Note that as part of "Tanaka's" history related to "Yamada", it is noted that he was connected to "Sato".
[0058] As shown in Figure 13, when "Sato" is selected in "Yamada's" account, screen SG11 (left diagram in Figure 13) is displayed, which shows part of "Yamada's" history related to "Sato". When "Show all" is selected at the bottom of the history on screen SG11, screen SG12 (right diagram in Figure 13) is displayed, which shows the entire history. Note that the history related to "Yamada" states that "Sato" and "Tanaka" have been connected.
[0059] Although not shown, when "Tanaka" is selected from the "Yamada" account, the screens SG11 and SG12 shown in FIG. 13 are displayed as appropriate.
[0060] According to the above-described embodiment, the system is equipped with a function for recording events that a user ("Tanaka") has with other users ("Yamada") who are connected to the user via the SNS in chronological order as a history, making it possible to recognize (easily identify) people connected to the user via the SNS after the fact.
[0061] Furthermore, according to the above-described embodiment, information entered via screen SG2 (new history addition screen) shown in FIG. 4 is recorded in the history history database DB (see FIG. 5) as an event (history) of the user ("Tanaka") related to another user ("Yamada"). Therefore, the user (Tanaka) can select for himself / herself the event (history) he / she wishes to add to his / her history from among the events with the user (Yamada). Having the history he / she has selected recorded in the history history database makes it easier to recognize (remember) other users.
[0062] In the above embodiment, the "connect" function of the SNS automatically adds the act of connecting and being connected to history, so that the person who connected can recognize after the fact who connected them and who connected them.
[0063] <2. Modifications> The SNS system and management server according to the present invention are not limited to the above-described embodiment, and various modifications and improvements are possible within the scope of the claims.
[0064] For example, in the above embodiment, the case where an SNS is used by accessing the management server 2 using an SNS application (dedicated application) installed on the user terminal 3 has been exemplified, but the present invention is not limited to this. An SNS may be used by accessing the management server 2 using a web browser installed on the user terminal 3.
[0065] In the above embodiment, the case where the user "Yamada" connects two users, "Sato" and "Tanaka", is exemplified, but the present invention is not limited to this. Three or more people may be selected as the connections to be connected on the screen SG5 in FIG. 9, and three or more people may be connected.
[0066] In the above embodiment, a case where a user registers an event related to another user as a new history in the history database DB via the screen SG2 (new history addition screen) shown in Fig. 4 has been exemplified, but the present invention is not limited to this. A message selected by the user on a chat room screen (screen SG13 shown in Fig. 13) for sending and receiving messages with other users may be registered as a new history in the history database.
[0067] Specifically, when a specific message (message circled) in screen SG13 shown in Fig. 14 is pressed and held, the user terminal 3 displays on the display screen SG14 (see Fig. 15) in which an add history button is superimposed on screen SG13. Then, when add history is selected on screen SG14, the user terminal 3 transmits a history addition request for the specific message to the management server 2. In response to the history addition request, the management server 2 records the specific message in chronological order in the history history as a new history related to the user's other users. Note that the date and time of the specific message is recorded as the date and time of the specific message. [Explanation of symbols]
[0068] 1. Social networking system 2 Management Server 3 User terminal SG1~SG14 screen
Claims
1. A social networking service (SNS) system that provides a social networking service, A management server for managing the SNS; A user terminal configured to be capable of network communication with the management server and operated by a user registered in the SNS; Equipped with The functions of the SNS include a history function that records events between the user and other users connected via the SNS in chronological order as history, The user terminal displays a new history addition screen for the user to add an event with the other user as a history; When new history information is input via the new history addition screen, the user terminal transmits the new history information to the management server; The management server records the new history information received from the user terminal in a history history in chronological order as new history of the user regarding the other user; The user terminal transmits a history viewing request for the user regarding the other users to the management server; The management server transmits the history of the user regarding the other users to the user terminal in response to the history viewing request; The SNS system is characterized in that the user terminal displays events between the user and the other users in chronological order based on the history.
2. The SNS function includes a chat function that enables the user to send and receive messages between the user and the other user, When an instruction to add a specific message to a history is given on a chat screen with the other user, the user terminal transmits a request to add the specific message to a history to the management server; The SNS system according to claim 1 , wherein the management server, in response to the history addition request, records the specific message in chronological order in the history history as a new history of the user regarding the other user.
3. The SNS function includes a connecting function for connecting a first user and a second user from among a plurality of users connected to the user, The user terminal transmits a connection request to the management server to connect the first user and the second user; The SNS system described in claim 1, characterized in that the management server records in chronological order in the history history that the user has connected the first user with the second user in response to the connection request as a new history of the user regarding the first user and records in chronological order in the history history as a new history of the user regarding the second user.
4. The management server includes: Recording the fact that the user connected the first user to the second user in response to the connection request in the history history as a new history of the first user related to the user in chronological order and recording the fact that the user connected the first user to the second user in the history history in chronological order as a new history of the first user related to the second user in the history history; The SNS system described in claim 3, characterized in that the fact that the user has connected the second user to the first user in response to the connection request is recorded in chronological order in the history history as new history for the second user regarding the user, and is also recorded in chronological order in the history history as new history for the second user regarding the first user.
5. The SNS system described in claim 3, characterized in that, in response to the connection request, the management server creates a chat room in which messages can be sent and received between the user, the first user, and the second user, and adds the second user as a friend of the first user and adds the first user as a friend of the second user.
6. A management server for managing a social networking service (SNS), The SNS is configured to be capable of network communication with a user terminal operated by a user registered in the SNS, The functions of the SNS include a history function that records events between the user and other users connected via the SNS in chronological order as history, The management server includes: receiving new history information from the user terminal regarding occurrences of the user with the other users; Recording the new history information in a history history in chronological order as new history of the user regarding the other user; receiving a history viewing request from the user terminal for the user regarding the other user; a management server that transmits the history history of the user relating to the other users to the user terminal in response to the history viewing request.
Citation Information
Patent Citations
SNS system, computer program, marketing automation method using SNS, and display method
JP2020091869A
Management server device for SNS system
JP2020187722A
