JP7520308B2 - Server device, mobile terminal, event management method and program - Google Patents

Description

The present invention relates to a server device, a mobile terminal, an event management method, and a program for communicating with friends using a social networking service.

Social networking services (hereinafter referred to as "SNS") are widely used as web services whose main purpose is communication between participants. This type of SNS allows friends to share their thoughts about television programs, etc.

In addition, when it comes to television programs, there is an indicator called the viewership rating, but it is not instantaneous and it is not possible to know the viewership rating of a television program that is currently being broadcast.

In addition to the above, there are application programs for mobile devices such as smartphones that handle opinions and word-of-mouth information about currently broadcast television programs or television programs that have been broadcast in the past. (For example, non-patent literature 1, 2)

URL “http://ja-jp.facebook.com/tuneTV?sk=app_212157885497998” (confirmed on September 13, 2012)” URL “http://wiz-tv.com/” (confirmed on September 13, 2012)”

When using the above SNS to share thoughts about TV programs among friends, the content tends to be a disjointed list of each person's thoughts.

In addition, all of the technologies mentioned in the above non-patent documents provide information common to all users of the application program, and these users are an unspecified number of people regardless of age, sex, occupation, hobbies, preferences, etc. Therefore, opinions about programs exchanged there are treated as merely general opinions and do not become familiar information that is tailored to the individual sensibilities of each user.

The present invention has been made in consideration of the above-mentioned circumstances, and its purpose is to provide a server device, a mobile terminal, an event management method, and a program that enable users to share their impressions of events such as television programs in real time in accordance with their emotions.

One aspect of the present invention is a server device that includes an event designation means for accepting designation of an event to be viewed, a display means for displaying a plurality of options for the designated event in a selectable manner on a mobile device accessed via a network, a counting means for acquiring a counting result of options selected for the designated event by other users related to the user of the mobile device, including the option selected by the user of the mobile device, and a transmission means for transmitting display data for displaying the acquired counting result on the mobile device of the user.

The present invention makes it possible for users to share their thoughts about events in real time in accordance with their emotions.

1 is a block diagram illustrating a system environment of a television broadcast review sharing service according to an embodiment of the present invention. 10 is a flowchart showing the processing contents between the mobile terminal and the emo graph server according to the embodiment. 11 is a flowchart showing the processing executed by the emo graph server according to the embodiment up to login when accessed from a mobile terminal. 11 is a flowchart showing the processing content executed by the emo graph server according to the embodiment after a mobile terminal logs in. 11A to 11C are diagrams illustrating examples of screens displayed on the mobile terminal before logging in to the emo graph server according to the embodiment. 11A to 11C are diagrams illustrating examples of screens displayed on the mobile terminal before logging in to the emo graph server according to the embodiment. 11A to 11C are diagrams illustrating examples of screens displayed on the mobile terminal before logging in to the emo graph server according to the embodiment. 11A to 11C are diagrams illustrating examples of screens displayed on the mobile terminal before logging in to the emo graph server according to the embodiment. 11A to 11C are diagrams illustrating examples of screens displayed on the mobile terminal before logging in to the emo graph server according to the embodiment. 11A to 11C are diagrams illustrating examples of screens displayed on the mobile terminal before logging in to the emo graph server according to the embodiment. 11A to 11C are diagrams illustrating examples of screens displayed on the mobile terminal before logging in to the emo graph server according to the embodiment. 11A to 11C are diagrams illustrating examples of screens displayed on the mobile terminal before logging in to the emo graph server according to the embodiment. 11A to 11C are diagrams illustrating examples of screens displayed on the mobile terminal before logging in to the emo graph server according to the embodiment. 2 is a diagram showing the configuration of a database (DB) for television programs in the emograph server according to the embodiment. FIG. 2 is a diagram showing the configuration of a database (DB) in the case where a video site of the emo graph server according to the embodiment is targeted. 13 is a diagram showing the configuration of a database (DB) for a news site of the emo graph server according to the embodiment. FIG. 13 is a diagram showing a change in the ratio of the number of emo transmissions of the emo graph server according to the embodiment. 13 is a diagram showing a change in the number of emo (laugh) transmissions related to the emo graph server according to the embodiment. 13A and 13B are diagrams illustrating examples of screens displayed on the mobile terminal after logging in to the emograph server according to the embodiment. 13A and 13B are diagrams illustrating examples of screens displayed on the mobile terminal after logging in to the emograph server according to the embodiment. 13A and 13B are diagrams illustrating examples of screens displayed on the mobile terminal after logging in to the emograph server according to the embodiment. 13A and 13B are diagrams illustrating examples of screens displayed on the mobile terminal after logging in to the emograph server according to the embodiment. 13A and 13B are diagrams illustrating examples of screens displayed on the mobile terminal after logging in to the emograph server according to the embodiment.

Hereinafter, an SNS system according to an embodiment of the present invention will be described with reference to the drawings.
In this embodiment, the event to be posted is a currently broadcasting television program, but it is not limited to television programs and may be a video site, a news site, or a real event (e.g., watching a soccer game, a wedding, etc.). In other words, this embodiment may be anything related to social viewing.

Figure 1 shows the system environment of a television broadcast review sharing service according to this embodiment, tentatively called "emograph (emotional graph)." In this figure, SNS servers 2A to 2C of companies A, B, and C, which each provide SNS, are connected to a network 1 such as the Internet, and an emograph server 3, for example provided by company A, that provides the service according to this embodiment is also connected.

Furthermore, mobile terminals 4 and 5, which are client devices used by users in this system, are connected to network 1 via an access point (AP) 6 or base station 7.

The SNS servers 2A to 2C are all server devices operated by various companies to provide existing SNSs, and store account information, including registered members and their friendship relationships, in a database.

The emo graph server 3 is a server device for a television broadcast impression sharing service operated by Company A, similar to the SNS server 2A.

On the other hand, the mobile terminals 4 and 5 on the client side include smartphones, feature phones, etc., and may be mobile phones that run on operating systems such as Android (registered trademark) and iOS (registered trademark), or may be notebook personal computers, mobile computers, tablet computers, etc. In any case, the application program for the television broadcast impression sharing service "Emograph" according to this embodiment is assumed to be installed in advance on the mobile terminals 4 and 5.

The hardware configurations of the electronic circuits of the SNS servers 2A to 2C, the emograph server 3, and the mobile terminals 4 and 5 are very common and well known, so we will omit any further description or explanation.

Next, the operation of the above embodiment will be described.
FIG. 2 is a flowchart showing the processing content between the client-side mobile terminal 5 and the emograph server 3, which is the basic concept of this embodiment.
In particular, FIG. 2 shows a configuration in which each time a mobile terminal 5 on the user (client) side sends an emotion message, the emo graph server (server) 3 tallys up the emotions from the mobile terminal 5 and returns the tally to the user.

That is, the mobile terminal 5 waits to send an emo message (step C01). Then, when it determines that an operation to send an emo message has been performed, it executes an emo message sending process from the mobile terminal 5 to the emo graph server 3 according to the push notification settings at that time (step C02), which will be described later.

The emo graph server 3 is constantly waiting for an emo call from the client side (step S01). When an emo call is received from the mobile terminal 5, the emo graph server 3 executes a preset calculation process, which will be described later, and returns the calculation results to the mobile terminal 5 (step S02).

After sending an emo message to the emo graph server 3, the mobile terminal 5 waits for the tally results to be returned from the emo graph server 3 (step C03). When it is determined that the tally results have been returned from the emo graph server 3, the mobile terminal 5 displays the returned tally results on its screen and, if necessary, performs an appropriate voice notification process, thereby enabling the user to recognize that the emo message was properly processed by the emo graph server 3.

The operation from the state in which the mobile terminal 5 logs in to the emo graph server 3 will be described in more detail below.
FIG. 3 is a flowchart showing the process executed by the emograh server 3 when the emograh server 3 receives access from the mobile terminal 5 via the network 1, up to login.

When the emo graph server 3 is accessed via the network 1 by starting the emo graph application program from a mobile terminal 4 on which the emo graph application program has been installed, the emo graph server 3 first creates a graph reflecting the emotions (emos) registered by all members who are currently participating in the emo graph, regardless of whether they are friends of the user of the mobile terminal 5, (hereinafter and in the drawings, referred to as the "emo graph") along with data on a list image of the television programs currently being broadcast, and transmits this data to the mobile terminal 5 that has accessed the emo graph (step S101).

Figure 5 is a diagram showing an example of a program list image displayed on the screen of mobile terminal 4 at this time. In this figure, the name of the TV program and the broadcast time for each of the seven channels (channels 1 to 8) as of 4:00 p.m. are displayed, along with the emogra- phys of all members at that time.

This emo graph is a bar graph made up of three colors, red, yellow, and blue, which express the members' impressions through color. The length of the bar graph, i.e., the absolute number of members, allows one to understand the tendency of the number of members watching each program, and the degree of color coding of the three colors, combined with the program name, allows one to predict to some extent the content and satisfaction level of the program.

In response to this display of the program list, the emograph server 3 waits for one of the channels to be selected on the mobile terminal 5 (step S102). Then, at the point in time when one of the channels is selected, the emograph server 3 forms image data in which a window encouraging the member to register or log in is superimposed on an image of a "program timeline," which is a list of the member's thoughts on the television programs on the selected channel, and returns this data to the mobile terminal 5 (step S103).

Figure 6 is a diagram showing an example of an image of a program timeline displayed on the screen of the mobile terminal 5 at this time. On this screen, in order to allow friends to share their thoughts about a TV program, a window W11 is displayed with a guide message saying "New registration/login is required to display friends," along with an operation button for "New registration/login," and the screen waits for the operation button to be selected.

When the above operation button is selected, the emo graph server 3 further transmits image data to the mobile terminal 5, which prompts the user to select either "New Registration" or "Login", and when either of these options is selected and operated, it determines whether "New Registration" has been selected, for example (step S104).

Figure 7 is a diagram showing an example of an image displayed on the screen of the mobile terminal 5, prompting the user to select either "New Registration" or "Login." Here, the functions on the "Emograph" are displayed as icons "Friend Display," "Emo," "Check-in," and "Comment," and the "New Registration" or "Login" button is displayed to prompt the user to select one of them.

Here, each of the above functions will be briefly described.
"Friend Display" is a function for displaying friends on other SNS who have been registered in advance by the user of mobile terminal 4 or 5 and who are currently using the "Emograph" application program, for example using the avatars of those friends.
"Emo" is a function that enables users to express their general thoughts about a television program.
"Check-in" is a function for confirming participation, set up to perform the "Comment" function below.
"Comment" is a function that enables a user to express and transmit their thoughts about a television program in text information.

When "New Registration" is operated from the image shown in FIG. 7 on the mobile terminal 5, the emo graph server 3 determines this in step S104 and creates and transmits image data to the mobile terminal 5 that prompts the user to select one SNS from multiple SNSs (step S105).

Figure 8 shows an example of a new registration image displayed on the screen of the mobile terminal 5 at this time. Here, new registration consists of three steps in total, and the screen indicates that the user is currently in the first step. It also displays three operation buttons, "SNS A (provided by company)," "SNS B (provided by company)," and "SNS C (provided by company)," prompting the user to operate one of them.

When, for example, "A.SNS" is selected on the mobile terminal 5, the emo graph server 3 accepts it, accesses the corresponding Company A SNS server 2A using the account of the user of the mobile terminal 5, and acquires the account information of the user of the mobile terminal 5 and the friends registered by that user (step S106).

In this case, if the SNS system allows the user of the mobile device 5 to set priorities for the account information of friends registered by the user of the mobile device 5, the system may determine whether to display the information based on the set priorities.

The above steps S105 and S106 are not limited to being performed for one selected SNS, but can be performed for multiple SNSs.

FIG. 9 shows an example of an image based on data from the emo graph server 3, which is displayed after "A. SNS" is selected from the state shown in FIG. 7.
The "New Registration" process is executed on the mobile terminal 5 side, and along with the fact that this is the second step out of three steps, it displays that registration was made using "A.SNS", the avatar image of the user of the mobile terminal 5 and the handle name in the SNS obtained from the A company SNS server 2A, and that three other friends currently registered in this SNS are also participating in "Emograph", etc. Furthermore, it also displays operation buttons for selecting to link with other "B.SNS" and "C.SNS" to add friends, as well as a button encouraging the user to move to the next step.

Figure 10 shows an example of an image based on data from the emo graph server 3 when the "B.SNS" button is operated on the mobile terminal 5 from the display screen of Figure 9 above. As with Figure 9 above, this shows that this is the second of three steps, and that three more friends have been added using "B.SNS". Here, for "C.SNS," which has not yet been selected, an operation button for selecting to link and add more friends is also displayed, along with a button encouraging the user to move to the next step.

In this way, in response to the processing on the mobile terminal 5 regarding new registration, the emo graph server 3 executes new registration processing for the user of the mobile terminal 5 according to a preset procedure (step S107).

If it is determined in step S104 above that this is not a new registration, i.e., if it is determined that "Login" has been selected on the mobile terminal 5 from the screen shown in FIG. 7 above, the emo graph server 3 creates and transmits image data to the mobile terminal 5 that prompts the user to select one of multiple SNSs (step S108).

At this time, the login image displayed on the screen of the mobile device 5 is similar to that of the above-mentioned new registration, except that the "New Registration" item in FIG. 8 above is replaced with "Login" and a guide message is displayed encouraging the user to select an SNS when logging in. The three actual operation buttons "A. SNS", "B. SNS", and "C. SNS" are displayed, and the subsequent operations are generally the same as those of the above-mentioned new registration.

Then, when, for example, "A.SNS" is selected on the mobile terminal 5, the emo graph server 3 accepts the selection of "A.SNS" and uses the account of the user of the mobile terminal 5 to access the corresponding Company A SNS server 2A, and acquires the account information of the user of the mobile terminal 5 and the friends registered by that user (step S109).

The above steps S108 and S109 are not limited to being performed for one selected SNS, but can be performed for multiple SNSs.

Figure 11 shows an example of an image based on data from the emo graph server 3 that is displayed after "A.SNS" is selected. Here, the emo graph server 3 executes the "login" process, and displays the avatar image of the user of the mobile device 5 obtained from Company A's SNS server 2A and their handle name within the SNS, indicating that this is the second step of three, and that they have registered using "A.SNS." Additionally, operation buttons for selecting to link with other "B.SNS" and "C.SNS" and add friends, as well as a button encouraging the user to move to the next step, are also displayed.

Following the new registration process in step S107 (Figures 9 and 10) or the login process in step S109 (Figure 11), the emo graph server 3 transmits image data to the mobile terminal 5, prompting the user to select whether or not to enable the push notification function to check friends who are watching the same TV program, and determines the result of the operation on that image (step S111).

Figure 12 is a diagram showing an example of an image displayed on the screen of the mobile device 5 at this time, encouraging the user to set up push notifications. Here, the "notification settings" process is in progress, and the user is informed that this is the third and final step of three steps. A guide message is displayed showing an example of the friend's avatar face and some of the posted comments, and informing the user that by clicking "OK (set)" for push notifications, friends who are watching the same TV program can be seen. In addition, an operation button for "setting push notifications" is also displayed.

By operating this operation button on the mobile terminal 5 side, the emo graph server 3 transmits to the mobile terminal 5 image data for selecting whether or not to make the same setting.
13 is a diagram showing an example of an alert screen for asking whether or not to permit the setting of a push notification, which is displayed on the screen of the mobile terminal 5 at this time. In the diagram, a guide message for confirming whether or not "EMOGRAPH" needs to send a push notification to the user is displayed, along with operation buttons for "OK (permit)" and "not permit."

The emo graph server 3 determines which operation button was operated on the mobile terminal 5 in response to the alert image shown in Figure 13 above.

If "OK (Allow)" is operated here, the emo graph server 3 that received this operation from the mobile device 5 determines this in step S111 above, sets up push notifications for the mobile device 5, and sends image data to the mobile device 5 indicating that push notifications have been set up (step S112), ending the login process shown in FIG. 3 above and moving on to post-login processing.

In addition, if the "Do not allow" operation button is operated on the screen shown in FIG. 13 on the mobile device 5, the emo graph server 3, which receives this operation from the mobile device 5, determines this in step S111 and does not set up push notifications for the mobile device 5. It also sends image data to the mobile device 5 indicating that push notifications are not set up and that friend avatars, etc. will not be displayed (step S113), and ends the login process shown in FIG. 3 above and moves on to post-login processing.

FIG. 4 is a flowchart showing the process executed by the emograph server 3 in response to a call from a logged-in mobile terminal 5 or the like.
The emo graph server 3 waits for any of the following states by repeatedly determining in sequence whether the call from the mobile terminal 5 is related to an emo call (step S201), whether it is a call related to check-in settings (step S205), whether it is a call to send a comment on a TV program (step S207), whether it is a change to push notification settings (step S211), or whether it is a call for logging out (step S213).

When an emo transmission for a television program is made from the mobile device 5 to the emo graph server 3, the emo graph server 3 that receives this judges this in step S201 above, and executes emo transmission processing according to the push notification settings status of the user of the mobile device 5 at that time (step S202).

Figure 14 is a diagram showing the configuration of the database (DB) of the emo graph server 3. For example, the emo graph server 3 stores emotional information such as laughter, crying, and anger, as well as information such as ID, address, age, sex, SNS account, location information, channel, program name, program content, maximum number of instantaneous emotes, program start time, and program end time.

Incidentally, FIG. 15 illustrates an example of the configuration of the database (DB) of the emo graph server 3 when an emo is sent to a video site instead of the above television program.

Here, the emo graph server 3 stores emotional information such as laughter, crying, and anger, as well as information such as ID, address, age, gender, SNS account, location information, video site title, URL, number of plays, current playback position, and total time.

Furthermore, FIG. 16 illustrates an example diagram showing the configuration of the database (DB) of the emo graph server 3 when an emo is sent to a news site instead of the above television program.

Here, the emo graph server 3 stores emotional information such as laughter, crying, and anger, as well as information such as ID, address, age, gender, SNS account, location information, news title, and URL.

The emo graph server 3, which has executed the emo transmission process in step S202, then executes a counting process for the transmitted emo (step S203), and returns the counting result to the mobile terminal 5 (step S204), after which the process proceeds to step S205.

Figure 17 shows the process by which the proportion of emotional messages changes during a television program, for example, from 7:00 to 8:00. Rather than the absolute number of emotional messages, the total is set at 100%, and the changes in the number of messages for each of the three emotions, crying, anger, and laughter, can be visually displayed.

For example, at 7:00, it represents 30% crying, 20% anger, and 50% laughter, and at 7:10, it represents 40% crying, 20% anger, and 40% laughter.

Therefore, the user of the mobile terminal 5 can easily grasp the change in the ratio of emotional calls for one program from 7:00 to 8:00, and can grasp the overall trend of what impressions the user's friends had of the same program.

Figure 18 shows the change in the number of users who expressed the emotion of "laughter" during a television program from 7:00 to 8:00. For example, at 7:10, the number of users who expressed the emotion of "laughter" was 80, whereas at 7:50, 200 users expressed the emotion of "laughter."

Also, 7:50 is the maximum number of emo transmissions. Here, the maximum number of emo transmissions at that time is defined as the instantaneous maximum number of emo transmissions.

For example, when comparing the peak momentary audience rating and the maximum momentary emotional messages, the two are different because the peak momentary audience rating is the percentage of people actually watching the program, whereas the maximum momentary emotional messages is not just information about people watching the program, but also includes the user's emotions regarding that scene.

The results of each of the above Figures 17 and 18 can be tabulated by limiting the target users to friends of the user of the mobile terminal 5, or the results can be output by tabulating users other than friends as well.

Figure 19 is a diagram illustrating an example of a TV program timeline screen displayed on the mobile device 5 after the login process. In comparison with the timeline screen shown in Figure 6 above, this timeline screen is after login, and therefore contains posts only from other users who are registered as friends of the user of the mobile device 5.

At the top of the screen, the name and broadcast time of the selected TV program are displayed, along with a Details button MD for displaying a detailed explanation of that program, and furthermore, based on the content of the emo messages sent at that time, red, yellow, and blue emo message posting trends are displayed according to their width, each with a face symbol.

The majority of the center of the screen displays the most recent posts about TV programs at that time. Furthermore, at the bottom of the screen, there are three buttons for sending emo messages: (from the left) a red button with a smiling face symbol in the center, a yellow button with an angry face symbol in the center, and a blue button with a crying face symbol in the center.

In this embodiment, we have given an example of color-coded emo transmissions using face symbols, but it is also easy to create a system that, for example, displays "red" and "white" buttons and encourages people to vote for one of the two in a singing competition.

When any of these emo sending buttons is operated, this is determined by the emo graph server 3 in step S201 above, and emo sending processing is executed according to the push notification settings.

In other words, the emo graph server 3 performs the process of sending emo information by first confirming that the mobile terminal 5 is currently checked in, and then registering emo information about the sent TV program in association with the account information of the user of the logged-in mobile terminal 5.

As a result of this registration, the emo graph server 3 executes a process of compiling the emo information sent by the user of the mobile terminal 5 for the television program in question, specifically, a process of compiling among those who are registered as friends of the user of the mobile terminal 5, and a process of compiling among all emo graph members who are not registered as friends (step S203).

Then, the emo graph server 3 converts the tally results according to the push notification setting state of the mobile terminal 5 at that time into image data and returns it to the mobile terminal 5 (step S204), and then returns to the processing from step S205 above.

Figure 20 shows an example of a response image from the emo graph server 3 in response to an emo being sent by a user of a mobile terminal 5 that has push notifications set up, while the screen shown in Figure 19 above is displayed, by operating the button with an angry face symbol in a yellow frame in the center of the bottom of the screen.

Here, the display shows that 30% of all friends who sent emo messages had operated the button with an angry face symbol in a yellow frame, just like the user of mobile device 5, along with some avatar images of those friends.

In a system where posts are made from a mobile terminal 5, the emo graph server 3 can identify the current location of the mobile terminal 5 from information about base stations and access points, so content sent from emotes in a specific area can be tabulated in association with the area and reflected in the tabulation results.

If the user of the mobile device 5 has not set up push notifications, as shown in the upper part of the screen in Figure 19 above, an image will be displayed on the mobile device 5 that shows the posting trends of emo messages in red, yellow, and blue, each with a face symbol, according to its width, taking into account emo messages from the mobile device 5, and also includes a guide message informing users that they can display their friends' avatars by setting up push notifications.

When the user of the mobile terminal 5 operates the details button MD at the top of the screen shown in Figure 19 above, the emo graph server 3 that receives the transmission first determines whether or not the user of the mobile terminal 5 has set up push notifications at that time.

If it is determined that push notification is set, the emo graph server 3 creates image data that shows an enlarged view of the posting tendency of red, yellow, and blue emo messages sent at that time for the TV program, each with a face symbol, and images of friends' avatars, and sends this data back to the mobile terminal 5.

Figure 21 shows an example of an image displayed on the screen of the mobile terminal 5 at this time. In this figure, the range showing the posting tendencies of friends who have sent emo messages is displayed in a significantly enlarged manner compared to the image shown in Figure 19 above, and at least a portion of the avatar image of the friend who sent the emo message is displayed in each of the red, yellow, and blue areas. By selecting any one of these friend avatar images and performing a touch operation, it is possible to find out about other TV programs that the friend has recently checked in on.

Figure 22 is a diagram showing an example of an image that is displayed on the mobile device 5 when the avatar image of friend A11 is touched in the blue area containing the crying face symbol on the screen of Figure 21 above. At this time, the emograph server 3 searches for other TV programs that the friend selected by touch operation has recently checked in to, using the account information of the friend, and converts the search device into image data and returns it to the mobile device 5, making it possible to display the image on the mobile device 5 as shown in Figure 22 above.

As for the selection of such friend avatar images, if the system allows the setting of priorities for friends as described above, the display form of the avatar image may be changed according to the set priority, or the progress from selection to the next display state may be changed.

In addition, if the push notification is not set, the emo graph server 3 may display updated content of emo posting trends in red, yellow, and blue, each with a face symbol, as shown in the upper part of the image in Figure 19, instead of the display in Figures 21 and 22, and may also send back to the mobile device 5 image data superimposed with a guide message indicating that by setting up push notification, avatar images of friends can be displayed.

If it is determined in step S207 that a comment on a television program has been sent from the mobile terminal 5, the emograph server 3 that has received this executes a comment sending process for the television program according to the push notification setting status of the user of the mobile terminal 5 at that time (step S208).

Then, based on the transmitted comment information, an update process is performed on the comments for the TV program (step S209), and the update result is sent back to the mobile terminal 5 (step S210), after which the process proceeds to step S211.

Figure 23 shows an example of the display screen when the Details button MD at the top of the screen described in Figure 19 above is operated to display an image explaining the details of the TV program, and the "Comments" button in the same image is provisionally selected.

In this case, text input becomes possible when an operation is performed within the actual comment input box CI at the bottom of the screen, allowing the user to create and transmit (post) any comment.

The comment information sent in this way is added to the comments from other users who are registered as friends on the emo graph server 3 as described above, and the updated content is sent back to the mobile device 5 and displayed.

As described above in detail, this embodiment makes it possible for users to share their thoughts about events such as television programs in real time with friends, in line with their emotions.

In addition, in the above embodiment, for each television program, a graph image with a color code corresponding to the emotional options, along with a symbol showing a simple facial expression, is displayed as the tally result. This makes it very easy to visually understand the impressions of friends who are watching the television program, and allows users to more easily participate by posting their own impressions, etc.

In addition, in the above embodiment, when displaying friends' impressions, comments, etc., the avatar images of the friends obtained from each SNS server are also displayed, so that it is possible to provide an image that makes it extremely easy to understand which friend is currently watching which TV program and what their impressions are. This enhances the sense of unity with friends and allows for a closer feeling of intimacy even when watching the same TV program in remote locations.

As explained in part in the above embodiment, the user of the mobile terminal 5 may arbitrarily set priority information regarding the account information of friends registered in each SNS server 2A to 2C, and depending on the priority, for example, the friends whose avatar images are displayed or the friends whose posted comments are displayed may be selected, or the display format may be changed.

This ensures that information from friends that the user considers to be closer is reflected in the displayed image, making the image information displayed on the mobile device 5 even more interesting.

Although not explained in the above embodiment, for example, if another friend sends an emo message while the image shown in FIG. 15 is being displayed, it is possible to adopt a display format that takes advantage of the results of that message and causes the avatar image of the friend who sent the new emo message to appear in the displayed image, thereby further emphasizing the sense of reality of sharing the same program in real time.

Furthermore, in the above embodiment, the present invention has been described as being applied to an SNS system in which thoughts about a television program currently being broadcast are posted, but the present invention is not limited to this, and various systems can be constructed depending on the settings of the event to be posted, such as a system that displays "red" and "white" buttons on the screen and encourages users to vote for one of the teams in a competitive music program, a system in which users post about and support baseball teams during a game, or a small-scale system in which some kind of voting is done at a drinking party with friends.

In addition, the present invention is not limited to the above-described embodiment, and various modifications can be made in the implementation stage without departing from the gist of the invention. Furthermore, the functions performed in the above-described embodiment may be implemented in appropriate combinations as much as possible. The above-described embodiment includes various steps, and various inventions can be extracted by appropriate combinations of the multiple components disclosed. For example, if the effect can be obtained even if some components are deleted from all the components shown in the embodiment, then the configuration from which these components are deleted can be extracted as an invention.

The inventions described in the claims of the original application of this application are set forth below.
[1]
An event designation means for accepting designation of an event to be viewed from a user of the mobile terminal;
a registration means for registering options selected by a user of the mobile terminal and options selected by other users related to the user of the mobile terminal during the event;
a counting means for registering the options by the registration means and acquiring a counting result of options selected by the user of the mobile device and options selected by other users related to the user of the mobile device for the specified event;
a transmission means for transmitting display data for displaying the acquired tally result on a mobile terminal of the user;
A server device comprising:
[2]
The server device according to [1], wherein the account information of the user of the mobile terminal and the account information of the other user are obtained from a server device that provides a service specified by the user of the mobile terminal.
[3]
The server device according to [1] or [2], wherein the tabulation result includes a graph image color-coded according to the selected option.
[4]
The server device according to any one of [1] to [3], wherein the aggregation result includes at least a portion of the avatar images of the other users.
[5]
The server device according to [4], wherein at least a portion of the avatar images of the other users included in the tallying result is determined based on priority information of the other users.
[6]
A server device described in any one of [1] to [5], wherein the account information of the other user is associated with information indicating the options selected by the other user and information about the event that the other user is interested in watching.
[7]
The server device according to any one of [1] to [6], further comprising a notification means for notifying the other users of information about the other users who are viewing the accepted event to be viewed.
[8]
The server device described in [7] further comprises means for displaying on the mobile terminal display information indicating that information of other users who are viewing the accepted event to be viewed can be displayed if the notification means is not set to executable.
[9]
The server device according to any one of [1] to [8], wherein the tallying results are tallied after logging in to the server device.
[10]
The server device according to any one of [1] to [9], wherein the display data is data that displays, for each event, the percentage of options selected by all users who selected the option.
[11]
A server device described in any of [2] to [10], which performs registration processing for the user of the mobile terminal using account information of the user of the mobile terminal obtained from a server device that provides a service specified by the user of the mobile terminal from among a plurality of services.
[12]
The server device according to any one of [1] to [11], wherein the other user is a friend in a service designated by the user.
[13]
The server device according to any one of [1] to [12], further comprising a server selection display means for displaying on the user's mobile terminal a selection as to whether or not to obtain information about the other user from a server device that provides a service specified by the user.
[14]
Accepting designation of an event to be viewed from a user of the mobile device;
acquiring a compilation result of options selected by the user of the mobile device and options selected by other users related to the user of the mobile device for the specified event;
Transmitting display data for displaying the acquired tally results on the mobile terminal;
An event management method in a server device.
[15]
The server device
Accepting designation of an event to be viewed from a user of the mobile terminal;
acquiring a compilation result of options selected by the user of the mobile device and options selected by other users related to the user of the mobile device for the specified event;
A program that causes the mobile terminal to transmit display data for displaying the acquired tally results.

1...network, 2A to 2C...(Company A to Company C) SNS servers, 3...emo graph server, 4, 5...mobile terminals, 6...access point (AP), 7...base station.

Claims (16)

An event designation means for accepting designation of an event to be viewed from a user of the mobile terminal;
A means for receiving a selection of an SNS from a user of the mobile terminal;
a counting means for acquiring a count result of the emo information selected by the user of the mobile device and emo information selected by other users related to the user of the mobile device in response to receiving emo information from the mobile device that indicates an emotion of the user toward the event selected by the user of the mobile device while the event is being held;
a transmission means for transmitting display data for displaying the acquired tally result on a mobile terminal of the user;
a notification means for notifying the other users of information about the other users who are viewing the received viewing event, the notification means being configurable by the user;
A means for switching the function of the notification means between an executable state and an inexecutable state;
Equipped with
The other user is a user who uses the selected SNS,
A server device, wherein, when the notification means is set to be executable, information indicating the other users is displayed on the user's mobile terminal using images visually associated with each emo information in the aggregation result, and when the notification means is not set to be executable, the information indicating the other users is not displayed on the user's mobile terminal . The emotion information indicates one of a plurality of emotions.
The server device according to claim 1 . the display data includes image data representing, for each of the plurality of emotions, a percentage of users who selected each emotion out of a total number of the user of the mobile device and the other users;
The server device according to claim 2. The mobile terminal further includes a registration unit for registering emo information selected by the user of the mobile terminal and emo information selected by the other user.
The server device according to any one of claims 1 to 3. The server device according to claim 4, wherein the tallying result includes a graph image generated based on the emo information registered by the registration means. The server device according to any one of claims 1 to 5, wherein the aggregation result includes at least a portion of the avatar image of the other user. The server device according to claim 6, wherein at least some of the avatar images of the other users included in the tallying results are determined based on priority information of the other users. a storage means for storing emotion information corresponding to an emotion indicated by emotion information selected by the user of the mobile terminal in association with account information of the user of the mobile terminal;
The server device according to any one of claims 1 to 7. The emotion information is stored in association with event identification information that identifies the event.
The server device according to claim 8. the tallying means tallying up emotion information indicating emotions of the other users in association with an area in which the user of the mobile device is located;
The server device according to any one of claims 1 to 9. The server device according to claim 1, further comprising: a means for displaying on the mobile terminal , when the notification means is not set to be executable, display information indicating that information of the other users who are viewing the accepted event to be viewed can be displayed. The server device according to claim 1 , wherein the tallying result is tallied after logging in to the server device. The server device according to claim 1 , wherein the other users are friends in a service designated by the user. The server device according to any one of claims 1 to 13, further comprising a server selection display means for displaying on the user's mobile terminal a selection as to whether or not to obtain information regarding the other user from a server device that provides a service specified by the user. receiving a designation of an event to be viewed from a user of the mobile terminal;
receiving a selection of an SNS from a user of the mobile terminal;
acquiring, in response to receiving, from the mobile device, emo information indicating an emotion of the user regarding the event selected by the user of the mobile device while the event is being held, a compilation result of the emo information selected by the user of the mobile device and emo information indicating an emotion of the user regarding the event selected by another user related to the user of the mobile device ;
transmitting display data for displaying the acquired tally results on the mobile terminal;
notifying the other users of information about the other users who are viewing the accepted event to be viewed, by a notification means that can be set by the user;
as well as,
A step of switching the function of the notification means to an executable state or an inexecutable state;
Including,
The other user is a user who uses the selected SNS,
When the notification means is set to be executable, information indicating the other users is displayed on the user's mobile terminal by an image visually associated with each piece of emo information in the tallying result, and when the notification means is not set to be executable, the information indicating the other users is not displayed on the user's mobile terminal .
An event management method in a server device. The server device
A process of receiving designation of an event to be viewed from a user of the mobile terminal;
A process of accepting a selection of an SNS from a user of the mobile device;
a process of acquiring a compilation result of the emo information selected by the user of the mobile device and emo information indicating the emotions of other users related to the user of the mobile device regarding the event in response to receiving, from the mobile device, emo information indicating the emotions of the user regarding the event selected by the user of the mobile device while the event is being held ;
A process of transmitting display data for displaying the acquired tally results on the mobile terminal ;
notifying the other users of information about the other users who are viewing the accepted event to be viewed, by a notification means that can be set by the user;
as well as,
A process for switching the function of the notification means between an executable state and an inexecutable state.
Run the command,
The other user is a user who uses the selected SNS,
When the notification means is set to be executable, information indicating the other users is displayed on the user's mobile terminal by an image visually associated with each piece of emo information in the tallying result, and when the notification means is not set to be executable, the information indicating the other users is not displayed on the user's mobile terminal.
program.