JP5718968B2 - Message transmission method, message reception method, management server, and message exchange system - Google Patents

Description

  The present invention relates to a message transmission method and a message reception method in a message exchange system capable of exchanging messages between terminals, and a management server and a message exchange system.

  In recent years, many services for communicating with a specific person have become widespread in a virtual space formed by a telecommunication network such as the Internet. These services are generally called social network services, or SNS for short. In the SNS, there are a plurality of specific persons who want to communicate, and in the case of a large number, the scale is several hundred.

  In order to use the conventional SNS, first, personal information for specifying a user who uses the SNS is registered (account registration) in the server on the service side. In the following, a user who uses SNS is simply expressed as a user. Thereafter, the user searches for personal information of an acquaintance who has been registered in the same manner in the past, and applies to the acquaintance for communication (applicant application). When an acquaintance who has applied for a friend approves the application for the friend, the person and the acquaintance are in a communicative relationship.

(Register)
More specifically, the user registers personal information predetermined by the service side in the server on the service side. This personal information includes a password for using the SNS. The server on the service side gives an account to a user who has registered predetermined personal information. The account name is generally a user's e-mail address, nickname, character string issued by the service side, or the like. When using the SNS, the user transmits the account name and password to the service server, and the service server authenticates the user if the received account name and password are registered (personal authentication). To do. That is, the user illuminates the service side that the user is registered in the SNS by transmitting the correct account name and password. In the following, the account name and password are collectively expressed as login information.

  In Patent Document 1, by using a two-dimensional bar code such as a QR code (registered trademark), an address for accessing registered information once registered without performing key input from the portable terminal is disclosed. The technology is recorded so that the registered information can be accessed smoothly from outside. However, even if such a personal authentication method is adopted, each individual is still authenticated by the server by inputting personal information.

(personal information)
The personal information to be registered and the range of personal information to be disclosed differ depending on each SNS. In addition, there is a service in which personal information to be disclosed can be set based on a user's judgment. For example, when the user is reluctant to publish by the real name, the nickname may be disclosed instead of the real name. In addition, it may be difficult to specify an individual who wants to be a friend only with a real name or a nickname. Therefore, in addition to real names or nicknames, information related to individuals such as age, gender, birthplace, or school may be disclosed.

(Fellow search and application)
In order to search for a partner to communicate with in the SNS, the user generally uses a search system provided in the SNS. The user selects a partner who wants to communicate from acquaintances that match the search contents, and makes a friend application to the partner. At this time, there is a possibility that the other party to whom the user applied for a friend is another person having the same name as the person desired by the user. Moreover, there is a possibility that a partner who has applied for a friend may not want to communicate with a user who has applied for a friend. In these cases, a partner who has applied for a friend can reject the friend application.

(Invite)
In SNS, a partner who wants to communicate may not participate in SNS. In that case, the user can prompt the other party to participate in the SNS. This is called an invitation. The other party who receives the invitation becomes an SNS user by performing registration with the SNS by the above method. SNS users can be friends by the above method. As a means for inviting a partner who wants to communicate to SNS, an e-mail or the like is generally used. Moreover, as a method for inviting a large number of friends easily, a method for inviting a plurality of opponents at once according to the contents of an address book registered in a terminal such as a smartphone can be considered.

(communication)
In order to use the SNS, the user is requested to log in from the server on the service side. That is, the individual who intends to use the SNS enters the account name and password (login information) at the time of account registration on the SNS input screen (login screen). The server on the service side compares the managed information with the input login information, and authenticates the individual as a user if the login information is correct. In this way, the user can use the SNS. A user who feels troublesome to log in each time the SNS is used can also store login information in the terminal for a certain period. According to this method, when an application for using SNS is activated, the user account is automatically in a login state. Therefore, the user does not have to log in every time the SNS is used.

JP 2009-98702 A (published May 7, 2009)

  However, the conventional SNS as described above is required to have high IT literacy for each user who uses the SNS, and has a side that is not a service that anyone can easily use. Specifically, a user who uses the SNS is required to perform operations such as (i) registering an account in the SNS, (ii) managing login information, and (iii) inputting login information at the time of login work. . If the login information is mismanaged and the login information is lost, the user cannot log in to the SNS. Moreover, when login information leaks for some reason, there is a possibility that SNS may be abused because a third party has become a user. Therefore, in the conventional SNS, it is desirable that the user understands the importance of the login information and has IT literacy enough to manage the login information safely.

  Further, in a conventional SNS, on the assumption that it is registered in the SNS, a search method for searching for a partner with whom communication is desired based on publicly disclosed personal information is common. Therefore, a user who wants to find it more easily from other users needs to disclose more personal information on the SNS. However, in this search method, the user's account name and the user's personal information may be set so that they can be viewed by a third party not intended by the user. And since the malicious third party browsed the user's personal information, the user may be involved in crimes such as fraud.

  Moreover, in the conventional SNS, it may be set so that the message currently exchanged in SNS can be browsed even if it is not an approved friend. Therefore, when a user issues an inadvertent message, the message is exposed to eyes other than those intended by the user, and may receive intensive criticism or slander. The phenomenon of being intensively criticized and slandered by an inadvertent message is widely known as “flaming”.

  By intentionally limiting the extent to which the user publishes personal information and messages, or making it private, the possibility of getting involved in the crimes described above and the possibility of being on fire are reduced. However, in order to appropriately set the range for publishing personal information and messages according to the manner in which the user uses SNS, the user may have higher IT literacy than that for safely managing login information. Required.

  As described above, the conventional SNS requests the user for IT literacy to the extent that login information can be safely managed. Moreover, in order to use SNS safely without being involved in a crime or being inflamed, a conventional SNS requires a higher level of IT literacy. It is practically difficult to obtain such high IT literacy from users, children, elderly people, etc., who have little experience using terminals. That is, the conventional SNS has a problem that it is not suitable for use by users who do not have high IT literacy.

  Conventionally, there are household electrical appliances that can be operated by voice, and there are household electrical appliances that recognize a user's voice and respond to it by voice. For users, such home appliances are regarded as a subject of communication as a member of a family, and in the future, users' needs to communicate with such home appliances on SNS are expected. However, since the conventional SNS is intended for people, it is not assumed that it is intended for home appliances, so it cannot satisfy such user needs.

  The present invention has been made in view of the above problems, and an object thereof is to realize a message exchange system that can be used easily and safely even by a user who does not have high IT literacy.

In order to solve the above problems, a message transmission method according to the present invention provides:
A message transmission method in which a terminal transmits a message to a management server of a message exchange system,
In the management server, the terminal confirms whether or not the terminal is a terminal registered in a specific group in the message exchange system. A terminal confirmation step that permits transmission of the message to the management server;
An input step for allowing the user to input the message in the terminal;
In the terminal, a transmission step of transmitting the input message to the management server;
The management server includes a receiving step for receiving the transmitted message.

In order to solve the above problem, a message receiving method according to the present invention provides:
A message receiving method in which a terminal accesses a management server of a message exchange system and receives a message,
In the management server, a terminal confirmation step for confirming whether or not the terminal is a terminal registered in a specific group in the message exchange system;
In the management server, when it is confirmed that the terminal is a terminal registered in a specific group in the message exchange system, a transmission step of transmitting a message to the terminal;
A receiving step for receiving the message at the terminal;
A message receiving method comprising: a display step for displaying the received message in the terminal.

In order to solve the above problem, the management server according to the present invention provides:
A management server that receives messages from a terminal,
The terminal confirms whether or not the terminal is a terminal registered in a specific group in the message exchange system, and if the terminal is confirmed to be a registered terminal, the message from the terminal to the management server A device verification means that allows transmission of
Receiving means for receiving the message transmitted from the terminal.

In order to solve the above problems, another management server according to the present invention
A management server that sends messages to the terminal,
Terminal confirmation means for confirming whether the terminal is a terminal registered in a specific group in the message exchange system;
When the terminal is confirmed to be a terminal registered in a specific group in the message exchange system, it is characterized by comprising transmission means for transmitting a message to the terminal.

In order to solve the above problems, the message exchange system according to the present invention provides:
A message exchange system comprising a terminal and a management server, wherein the terminal transmits a message to the management server,
The management server
Check if the terminal is a terminal registered in a specific group in the message exchange system, and if it can be confirmed that the terminal is a registered terminal, the terminal from the terminal to the management server A device verification means that allows sending messages;
Receiving means for receiving the message transmitted from the terminal,
The terminal
Input means for allowing the user to input the message;
And a transmission means for transmitting the inputted message to the management server.

In order to solve the above problem, another message exchange system according to the present invention provides:
A message exchange system comprising a terminal and a management server, wherein the terminal accesses the management server and receives a message,
The management server
Terminal confirmation means for confirming whether or not the terminal is a terminal registered in a specific group in the message exchange system;
A transmission means for transmitting a message to the terminal when the terminal is confirmed to be a terminal registered in the specific group in the message exchange system;
The terminal
Receiving means for receiving the message;
And a display means for displaying the received message.

  According to one embodiment of the present invention, a message exchange system that can be used easily and safely even by a user who does not have high IT literacy can be realized.

It is a figure which shows the structure of the SNS system which concerns on one Embodiment of this invention. It is a figure which shows the concept of the group comprised in the SNS system which concerns on one Embodiment of this invention. It is a figure which shows an example of the group management table for managing the group in the SNS system which concerns on one Embodiment of this invention. It is a figure showing an example of the terminal management table for managing the terminal registered into the group in the SNS system which concerns on one Embodiment of this invention. It is a figure showing an example of the avatar management table for managing the avatar which can use the terminal registered into the group in the SNS system concerning one embodiment of the present invention. It is a figure which shows an example of the administrator terminal management table which manages which terminal is an administrator terminal in each group in the SNS system which concerns on one Embodiment of this invention. It is a figure which shows an example of the group management table which also contains the terminal number of an administrator terminal. It is a figure which shows an example of the message management table for managing the message which each terminal registered into the SNS system which concerns on one Embodiment of this invention transmitted. In one Embodiment of this invention, it is a figure which shows an example of the flow of a process in the SNS system at the time of registering a new terminal in a group. (A) is a figure which shows the screen displayed on an administrator terminal when starting terminal registration, (b) is the screen displayed on an administrator terminal when selecting the kind of terminal to register. FIG. 10C is a diagram showing a screen displayed on the administrator terminal when selecting the registration method of the mobile terminal, and FIG. 10D is a web for registering the terminal in the group. It is a figure which shows the screen containing QR code in which the link to a page was described. (A) is a figure showing the text of the email transmitted from the administrator terminal to the mobile terminal, (b) is a screen displayed on the mobile terminal when encouraging registration to the group, (c) ) Is a screen displayed on the mobile terminal when the application is manually installed, and (d) is a diagram showing a screen displayed on the mobile terminal when applying for formal registration of the mobile terminal. (A) is the flowchart which shows the flow of a process at the time of installing the application for utilizing an SNS system in the portable terminal newly registered into an SNS system in one embodiment which concerns on this invention, ( b) is a flowchart showing a flow of processing when a terminal number of a mobile terminal is distributed to a mobile terminal newly registered in the SNS system in one embodiment according to the present invention. In one Embodiment of this invention, it is a figure which shows an example of the other flow of the process in the SNS system at the time of registering a new terminal in a group. In one Embodiment which concerns on this invention, it is a figure which shows an example of the flow of a process in the SNS system at the time of registering a television to a group. (A) is a screen for applying for registration to the SNS system displayed on the television, and (b) is a diagram showing a screen including a QR code. (A) is a figure which shows the screen displayed on an administrator terminal when starting terminal registration, (b) shows the screen displayed on an administrator terminal when selecting the registration method of a television. (C) is a diagram showing a screen displayed on the administrator terminal when applying for a formal registration of a TV, and (d) is for notifying that the registration of the TV is completed. It is a figure which shows a screen. In one Embodiment which concerns on this invention, it is a figure which shows an example of the flow of a process in the SNS system at the time of registering a robot cleaner in a group. In one Embodiment which concerns on this invention, it is a flowchart which shows the flow of a process in an SNS system when an administrator terminal acquires a message input screen. In one Embodiment which concerns on this invention, it is a flowchart which shows the flow of a process in a SNS system at the time of performing avatar change, message input, message transmission, and message display. In one Embodiment which concerns on this invention, it is a flowchart which shows the flow of a series of processes in a SNS system when a service server acquires the information for messages. (A) is a figure which shows the screen containing the newest message, (b) is a figure which shows a message input screen. It is a figure which shows the screen for selecting an avatar displayed on an administrator terminal. In one Embodiment which concerns on this invention, it is a flowchart which shows the flow of a process in a SNS system when a television acquires a message input screen. (A) is a figure which shows a mode that the screen containing the newest message and the television screen are displayed simultaneously, (b) shows a mode that the avatar selection screen and the television program are displayed simultaneously. (C) is a figure which shows a mode that the message input screen and the television program are displayed simultaneously.

Embodiment 1
The SNS (social network service) system 10 according to the present embodiment is a message exchange system for sharing messages and the like for communication in units of groups in which a plurality of terminals are registered.

  The SNS system 10 is greatly different from the conventional SNS system in that each terminal is registered in a group in the SNS system 10 instead of a user. Specifically, terminal identification information (terminal number) given uniquely to a terminal used by a user when using the SNS system 10 is registered in a group in the SNS system 10. On the other hand, in the conventional SNS system, each user registers personal information in the SNS system in order to use the SNS system, and acquires an account for each user. In the SNS system 10, an account for each user does not exist in principle (except for a group manager).

  The group in the SNS system 10 is a specific group in which the terminal is registered, and is a group for permitting at least one of message posting and browsing to the registered terminal. A user who uses the SNS system 10 can transmit a message using any terminal registered in the group. This message is transmitted only to other terminals registered in the group to which the terminal belongs. In other words, the SNS system 10 does not transmit the message transmitted by the terminal to the outside of the group. In addition, the SNS system 10 does not transmit a message transmitted from the outside of the group to each terminal belonging to the group.

  Thus, the SNS system 10 is an SNS system having a very closed personality in units of groups. As an aspect of using the SNS system 10, for example, a domestic message board system used in a family, a bulletin board system that shares information among members belonging to the same circle, and the like can be cited. However, these are not limited.

(Outline of SNS system 10)
An outline of the SNS system 10 will be described below with reference to FIGS. FIG. 1 is a diagram illustrating a configuration of the SNS system 10. As shown in FIG. 1, the SNS system 10 includes a service server 11, a group management server 12, a terminal management server 13, an avatar management server 14, a message management server 15, an administrator terminal management server 16, an administrator terminal 21, and a portable terminal. 22, a portable terminal 23, a television 24, and a robot cleaner 25. Hereinafter, a group named “Satoya” configured on the SNS system 10 will be described as a main example.

  As shown in FIG. 1, in the group “Satoya” in the SNS system 10, five terminals of a mobile terminal 21, a mobile terminal 22, a mobile terminal 23, a television 24, and a robot cleaner 25 are registered as terminals. Yes. These terminals are connected to the SNS system 10 via the Internet 31, as shown in FIG.

  FIG. 2 is a diagram illustrating the concept of groups configured in the SNS system 10. A group in the SNS system 10 includes a terminal group and an avatar group. The terminal group represents a group of terminals registered in the SNS system 10 as the group “Satoya”. The SNS system 10 identifies each terminal registered in the group by a terminal number (here, D7001 to D7005). The terminal number here is an identification number that is unique to each terminal and uniquely assigned to each terminal. Hereinafter, an example in which a terminal number is used as information for identifying each terminal will be described. However, in the SNS system 10, information used to identify each terminal is not limited to the terminal number. If each terminal can be identified, information such as a character string other than the number may be used as the terminal identification information.

  The terminal number is preferably a serial number prepared at the time of shipment to the terminal. However, the present invention is not limited to this, and as will be described in detail later, individual terminal numbers can be provided later to each terminal after shipment.

  The avatar group represents a group of avatars displayed on the display unit of the terminal together with the message. An avatar is information (symbol information) that symbolically represents a sender of a message, and is mainly an image reminiscent of the sender. The avatar is transmitted to each terminal together with the message, so that it can be easily determined which user the message is transmitted from.

  In the example illustrated in FIG. 2, the message transmitted from the mobile terminal 21 having the terminal number D7001 is displayed together with the avatar having the avatar number A7001 associated with the terminal number D7001. Similarly, the message transmitted from the portable terminal 22 having the terminal number D7002 is displayed together with the avatar having the avatar number A7002 associated with the terminal number D7002, and transmitted from the portable terminal 23 having the terminal number D7003. The message is displayed together with the avatar of the avatar number A7003 linked to the terminal number D7003. Details of processing for associating a message, a terminal number, and an avatar number will be described later.

  A user who uses the SNS system 10 using the mobile terminals 21 to 23 is basically a user specific to each mobile terminal. This is because the mobile terminal is a terminal that has a strong tendency to be used exclusively by individuals. Therefore, in many cases, a user who uses the SNS system 10 using a mobile terminal is exclusively the owner of each mobile terminal. That is, in many cases, the user 1 uses the mobile terminal 21, the user 2 uses the mobile terminal 22, and the user 3 uses the mobile terminal 23.

  On the other hand, the television 24 is a terminal shared by all family members. In other words, all family members may use the SNS system 10 using the television 24. Taking FIG. 2 as an example, the television 24 may be used by three users 1, 2, and 3. In this case, the avatar number associated with the terminal number D7004 representing the television 24 is preferably changed as appropriate according to the user who transmitted the message. In order to realize the usage pattern as described above, the correspondence relationship between the terminal number and the avatar number in the SNS system 10 is configured to be appropriately changeable.

(Registering home appliances)
Moreover, the terminal registered in the group of the SNS system 10 is not limited to a portable terminal such as a smartphone or an information display terminal such as a television, and may be a home appliance. Household appliances registered in the group are anthropomorphized within the group. The household appliances that can be registered in the group in this embodiment are household appliances that can be operated by voice, or household appliances that can communicate with the user.

  These home appliances often include sensors that can monitor room temperature, humidity, and the like. The household electrical appliance registered in the group of the SNS system 10 supplies the environmental information acquired from each sensor to the external server, and the external server is as if the household electrical appliance is transmitting a message according to the acquired environmental information. May be configured to send a message. The bot 4 described in the member group in FIG. 2 acquires environmental information from the home appliance, and transmits a message corresponding to the environmental information as if it was transmitted from the anthropomorphized home appliance.

  When such home appliances can be registered in the SNS system 10, the SNS system 10 can provide a new usage mode of home appliances as described below.

  (I) When the user wants to keep the room in a comfortable state when returning home, the user may send a message to that effect to the SNS system 10. The household electrical appliances in the group that have received the message can control the air conditioning of the room so that the room is in a comfortable state when returning home.

  (Ii) When the whole family is out, only pets are left in the house. In such a situation, even if the room temperature rises as the temperature rises, the pet cannot turn on the air conditioner by himself or contact his family. In such a case, the household appliances in the group can notify each terminal of the family through the SNS system 10 that the room temperature has become high. In response to the notification from the home appliance, the family can negotiate with the SNS system 10 on a response method. Alternatively, the air conditioner can be turned on by controlling the home appliance through the SNS system 10. Furthermore, through the SNS system 10, it is possible to grasp what kind of response the family has taken.

  However, in the conventional SNS system, there is no method for registering home appliances in the SNS system. In the first place, it is not supposed to register home appliances at all. For this reason, it is difficult to realize the specifications specific to this embodiment described above. In the SNS system 10, since home appliances can be registered in the SNS system, the above-described use mode can be realized.

  In the present embodiment, the robot cleaner 25 will be described as an example of an anthropomorphized home appliance. However, the home appliance is not limited to this, and may be various products existing in the home such as an air conditioner, a refrigerator, or a washing machine.

(Configuration of SNS system 10)
The configuration of the SNS system 10 will be described with reference to FIG. 1 and FIGS.

(Service server 11)
The service server 11 is a server that manages and operates the entire SNS system 10. As shown in FIG. 1, each terminal using the SNS system 10 is connected to the service server 11 via the Internet 31. That is, the service server 11 is a server serving as a window in the SNS system 10. For example, a screen displayed by each terminal is created and transmitted to each terminal.

(Group management server 12)
The group management server 12 is a server that manages a group as a unit when a message is shared in the SNS system 10. FIG. 3 is a diagram illustrating an example of a group management table for managing groups in the SNS system 10. The group management table is stored in a storage unit provided in the group management server 12.

  A plurality of groups are created in the SNS system 10. As shown in FIG. 3, the group management table includes a group number for identifying the group, a group name, a group manager, and a terminal number of a terminal registered in the group for each group. Stored in association.

  Specifically, in the group whose group number is G1234567, the group name is Sato family, the group manager is Ichiro Sato, and the registered unique terminal numbers are D7001, D7002, D7003, D7004 and D7005. is there. In the group whose group number is G1234568, the group name is Saito, the group manager is Jiro Saito, and the registered unique terminal numbers are D8001, D8002, and D8003. In a group whose group number is G12334569, the group name is a golf circle, the group manager is Ichiro Sato, and the registered unique terminal numbers are D9001, D9002, D9003, D9004, and D7001.

  In the present embodiment, an upper limit may be set for the number of terminals that can be registered in each group. This can be realized by setting an upper limit on the number of terminal numbers that can be associated with individual group numbers in the group management table. In the present embodiment, the same terminal can be registered in a plurality of different groups. This can be realized by registering one terminal number in association with a plurality of different group numbers in the group management table.

(Terminal management server 13)
The terminal management server 13 is a server that manages all terminals registered in the group for each group. FIG. 4 is a diagram illustrating an example of a terminal management table for managing terminals registered in a group in the SNS system 10. The terminal management table is stored in a storage unit (not shown) provided in the terminal management server 13. FIG. 3 shows a terminal management table for each terminal registered in the group whose group number is “G123456”.

  In the terminal management table, for each terminal registered in the group, the terminal number of the terminal, the name of the terminal, the date and time when the terminal last accessed the SNS system 10, and the terminal transmitted a message last. The avatar number of the avatar used at the time is stored.

(Avatar management server 14)
The avatar management server 14 is a server that manages an avatar that can be used by each terminal registered in the group for each group. FIG. 5 is a diagram illustrating an example of an avatar management table for managing avatars that can be used by terminals registered in a group in the SNS system 10. The avatar management table is stored in a storage unit (not shown) provided in the avatar management server 14. FIG. 5 shows a terminal management table for managing avatars that can be used by each terminal registered in the group whose group number is “G123456”.

  In the avatar management table, the avatar number unique to the avatar, the name of the avatar, and the file name of the avatar image are stored for each avatar. The data of the avatar image itself is separately stored in the storage unit of the avatar management server 14.

(Administrator terminal management server 16)
The administrator terminal management server 16 is a server that manages which terminal is the administrator terminal in each group in the SNS system 10. FIG. 6 is a diagram illustrating an example of an administrator terminal management table for managing which terminal is the administrator terminal in each group in the SNS system 10. The administrator terminal management table is stored in a storage unit (not shown) provided in the administrator terminal management.

  A plurality of groups are created in the SNS system 10. As shown in FIG. 6, the manager terminal table stores, for each group, a group number for identifying the group and a terminal number of the manager terminal in association with each other.

  In this embodiment, a plurality of administrator terminals can be registered for each group. This can be realized by registering terminal numbers of a plurality of administrator terminals in individual group numbers in the administrator terminal management table.

  In the SNS system 10, the group management server 12 and the administrator terminal management server 16 may be integrated. That is, the group management server 12 may have the function of the administrator terminal management server 16. In this case, the group is managed using the group management table that further includes the terminal number of the administrator terminal. FIG. 7 is a diagram showing an example of a group management table that further includes the terminal number of the administrator terminal. The terminal management table in FIG. 7 is a table in which the terminal management table shown in FIG. 3 and the administrator terminal management table shown in FIG. 6 are integrated.

  In the following description, it is assumed that the group management server 12 has the function of the administrator terminal management server 16. Therefore, the group management server 12 uses the group management table in the format shown in FIG. 7 to confirm whether the terminal that has accessed the SNS system 10 is an administrator terminal.

(Message management server 15)
The message management server 15 manages a message transmitted by each terminal registered in the SNS system 10. FIG. 8 is a diagram illustrating an example of a message management table for managing messages transmitted from each terminal registered in the SNS system 10. The message management table is stored in a storage unit (not shown) of the message management server 15.

  Information related to messages transmitted from each terminal in the SNS system 10 is managed in a message management table for each message. In the example of FIG. 8, the message management table identifies, for each message, a message number for identifying the message, a group number of a group to which the terminal that has transmitted the message belongs, and an avatar that is specified when the message is transmitted. The avatar number to be transmitted, the terminal number of the terminal that transmitted the message, the transmission time of the message, and the content of the message (at least one of text, image, and voice) are stored in association with each other.

  Each time each terminal sends a new message, information about the message is newly accumulated in the message management table. How the message is delivered to the terminal that is the destination of the message using the message management table will be described in detail later.

(Group construction)
In the SNS system 10, a user who has registered as a user in the SNS system 10 can construct the above-described group. Hereinafter, a procedure when the user constructs a group in the SNS system 10 will be described.

  First, a user who wants to create a group registers as a user in the SNS system 10. The user registration here is the same as the procedure for newly registering a user or creating an account in the conventional service. That is, the user registration is performed by applying to the SNS system 10 for an identifier (account) and a password for identifying the user, and further registering the personal information of the user. Note that user registration using an account already used in another service may be performed. A user who has registered as a user in the SNS system 10 is given special authority to construct a group. Below, the user who constructs a group is described as a representative.

  The representative logs in to the SNS system 10 using the administrator terminal 21 and applies to the SNS system 10 for construction of a new group. At that time, the representative inputs information about the group such as a group name. Further, the administrator terminal 21 provides the terminal number of the administrator terminal 21 to the SNS system 10. This creates a group. At that time, the representative administrator terminal 21 is automatically registered in the constructed group. That is, the terminal number of the administrator terminal 21 is associated with the group number of the constructed group and stored in the group management table. From now on, the representative is also the manager of the group.

  When the group construction is completed, the group number of the constructed group is provided from the SNS system 10 to the administrator terminal 21. Therefore, the administrator terminal 21 holds both the terminal number of the administrator terminal 21 and the group number of the group number.

(Registration process of portable terminal 22)
After constructing the group, the user of the manager terminal 21 starts the operation of registering another terminal in the group. Hereinafter, an example of a processing flow in the SNS system 10 when a terminal is registered in a group will be described with reference to FIG. FIG. 9 is a diagram illustrating an example of a process flow in the SNS system 10 when a new terminal is registered in a group in the embodiment of the present invention. Below, the procedure at the time of registering the portable terminal 22 to the group G1 is demonstrated.

(Registration application)
First, the administrator terminal 21 displays the screen shown in FIG. FIG. 10A is a diagram illustrating a screen displayed on the administrator terminal 21 when terminal registration is started. This screen includes an item K1 labeled “Register device”.

  Note that the user of the administrator terminal 21 can register a new avatar in the SNS system 10 through the screen of FIG. This avatar is registered in the SNS system 10 as a group avatar constructed by the representative.

  The user of the administrator terminal 21 selects the item K1. Then, the administrator terminal 21 displays a screen shown in FIG. FIG. 10B is a diagram illustrating a screen displayed on the administrator terminal 21 when the type of terminal to be registered is selected. This screen includes an item K2 labeled “Invite members” and an item K3 labeled “Register shared terminal”. If the item K2 is selected, a process of registering a terminal such as a portable terminal that is exclusively used by one user is started. On the other hand, if the item K3 is selected, a process of registering a terminal such as a television that is shared and used by a plurality of users is started.

  In the present embodiment, the user of the administrator terminal 21 selects the item K2 in order to register the mobile terminal 22 in the group G1. Thereby, the administrator terminal 21 applies to the service server 11 to register a new terminal in the group G1 (step S1). At that time, the administrator terminal 21 transmits the terminal number of the administrator terminal 21 and the group number of the group G1 to the service server 11.

  When receiving the terminal number and the group number, the service server 11 requests the group management server 12 to confirm whether these numbers have been registered (step S2). At that time, the service server 11 transmits the terminal number of the administrator terminal 21 and the group number of the group G1 to the group management server 12.

(Confirm device)
The group management server 12 searches the group management table using the received terminal number and group number. Thereby, it is confirmed whether or not the administrator terminal 21 is a terminal registered in the group G1. If it can be confirmed, the fact is returned to the service server 11 (step S3). Further, the group management server 12 changes the state of the group management table to a new terminal registration waiting state for the group G1.

  If the group management server 12 cannot confirm that the manager terminal 21 is the manager terminal of the group G1, the group management server 12 returns a message to that effect to the service server 11. In response to this reply, the service server 11 transmits an error message to the administrator terminal 21. As a result, the process shown in FIG. 9 ends abnormally.

(Selection of registration method)
When the service server 11 receives a reply from the group management server 12 that the confirmation has been made, the service server 11 transmits a screen for selecting a new terminal registration method to the administrator terminal 21 (step S4). The administrator terminal 21 displays the received screen. Thereby, the screen shown in FIG. 10C is displayed. FIG. 10C is a diagram illustrating a screen displayed on the administrator terminal 21 when the registration method of the mobile terminal 22 is selected. This screen includes an item K4 labeled "Display QR code" and an item K5 labeled "Send by mail".

  In the present embodiment, the user of the administrator terminal 21 selects the item K4. Thereby, the administrator terminal 21 requests the service server 11 to provide a screen including the QR code (step S5).

  Upon receiving this request, the service server 11 creates a QR code in which a link to a web page for registering a terminal in the group G1 is described. In this link, the group number of the group G1 is obfuscated by a technique such as hashing, and is included as a query. Note that the service server 11 may create some two-dimensional code other than the QR code instead.

  The service server 11 transmits a screen including this QR code to the administrator terminal 21 (step S6). The administrator terminal 21 displays the received screen. Thereby, the screen shown in FIG. 10D is displayed. FIG. 10D is a diagram showing a screen including a QR code in which a link to a web page for registering a terminal in group G1 is described. This screen includes a QR code C1.

  If the administrator terminal 21 has sufficient resources, it makes a request for step S5 after applying for step S1 and before receiving the screen shown in FIG. 10C from the service server 11. May be. Thereby, the administrator terminal 21 receives the screen including the QR code before the user of the administrator terminal selects the item K4. Therefore, a screen including a QR code can be displayed immediately after the user of the administrator terminal selects the item K4.

(Tentative registration of mobile terminal 22)
The administrator terminal 21 provides a link of a web page for registering the terminal to the group G1 to the mobile terminal 22 through the QR code C1 (step S7). The procedure is as follows. The user of the mobile terminal 22 uses the camera function of the mobile terminal 22 to photograph the QR code C1 displayed on the screen of the administrator terminal 21. Thereby, the portable terminal 22 acquires an image of the QR code C1. The portable terminal 22 obtains a web page link for registering the terminal in the group G1 by analyzing the image.

  The information (link) included in the QR code is preferably encrypted or obfuscated. In this case, the mobile terminal 22 acquires the link by decrypting the encrypted information or the obfuscated information acquired from the QR code. If the information included in the QR code is encrypted or obfuscated, even if the information leaks from the mobile terminal 22, the link is not specified, so a malicious other person registers another terminal in the group G1. It is possible to prevent applying for this.

  In the present embodiment, the mobile terminal 22 requires a dedicated application in order to use the SNS system 10. By executing this application, it is possible to apply to the SNS system 10 for registration to the group, or to send a message after the registration is completed. In the following description, it is assumed that this application has been installed in the mobile terminal 22.

  The portable terminal 22 requests the service server 11 for a screen for registering the portable terminal 22 in the group G1 by accessing the acquired link (step S8). At that time, the mobile terminal 22 transmits the terminal number of the mobile terminal 22 and the group number of the group G1 to the service server 11. The portable terminal 22 waits for a response from the service server 11 after accessing the link.

  Upon reception of the terminal number of the portable terminal 22 and the group number of the group G1, the service server 11 is in a state of waiting for registration of a new terminal to the group G1 with respect to the group management server 12 in the state of the group management table. An inquiry is made as to whether or not there is (step S9). At that time, the service server 11 transmits the terminal number of the portable terminal 22 and the group number of the group G1 to the group management server 12.

  Upon receiving this inquiry, the group management server 12 refers to the group management table to check whether the state of the group management table is a waiting state for accepting registration of a new terminal in the group G1. If it can be confirmed, a message to that effect is returned to the service server 11 (step S10). Furthermore, the state of the group management table is changed to a waiting state for registration of the portable terminal 22 to the group G1.

  If the group management table 12 cannot confirm that the state of the group management table is a waiting state for accepting registration of a new terminal in the group G1, the group management server 12 returns a message to that effect to the service server 11. The group management table is returned to the normal state. In response to this reply, the service server 11 transmits an error message to the mobile terminal 22 (step S11). As a result, the process shown in FIG. 9 ends abnormally. Note that the service server 11 may also send an error message to the administrator terminal 21. As a result, it is possible to alert the user of the administrator terminal 21 that a suspicious portable terminal has attempted registration with the group G1.

  When receiving a reply from the group management server 12 indicating that the confirmation has been made, the service server 11 transmits a screen for prompting registration to the group G1 to the portable terminal 22 (step S11). The portable terminal 22 displays the received screen. As a result, the screen shown in FIG. 11B is displayed. FIG. 11B is a screen displayed on the portable terminal 22 when prompting registration to the group. This screen includes an item K11 labeled “Install Application” and an item K12 labeled “Apply for Registration”. In the example of FIG. 9, the user of the mobile terminal 22 selects the item K12.

  In response to this selection, the mobile terminal 22 requests the service server 11 for a screen for applying for registration of the mobile terminal 22 in the group G1 (step S12). At that time, the mobile terminal 22 transmits the terminal number of the mobile terminal 22 and the group number of the group G1 to the service server 11.

  Upon receiving this request, the service server 11 requests the group management server 12 to temporarily register the portable terminal 22 in the group G1 (step S13). At that time, the service server 11 transmits the terminal number of the portable terminal 22 and the group number of the group G1 to the group management server 12.

  Upon receiving this request, the group management server 12 confirms whether or not the state of the group management table is waiting for registration of the portable terminal 22 in the group G1. If it can be confirmed, the portable terminal 22 is provisionally registered in the group G1. In addition, the state of the group management table is changed to a name input waiting state of the mobile terminal 22. Furthermore, the fact that the temporary registration is completed is returned to the service server 11 (step S14).

  If the group management server 12 cannot confirm that the state of the group management table is the state of waiting for registration of the mobile terminal 22 in the group G1, the group management server 12 replies to that effect to the service server 11. The group management table is returned to the normal state. In response to this reply, the service server 11 transmits an error message to the portable terminal 22 (step S15). As a result, the process shown in FIG. 9 ends abnormally. Note that the service server 11 may also send an error message to the administrator terminal 21. As a result, it is possible to alert the user of the administrator terminal 21 that a suspicious portable terminal has attempted registration with the group G1.

(Formal registration of mobile terminal 22)
Upon receiving a reply that the temporary registration of the mobile terminal 22 has been completed, the service server 11 transmits a screen for applying for formal registration of the mobile terminal 22 to the group G1 to the mobile terminal 22 (step S15). The portable terminal 22 displays the received screen. Thereby, the screen shown in FIG. 11D is displayed. FIG. 11D is a diagram showing a screen displayed on the mobile terminal 22 when applying for formal registration of the mobile terminal 22. This screen includes an item K14 labeled "Register". An input field for inputting a terminal name is also included.

  The user of the mobile terminal 22 inputs the terminal name of the mobile terminal 22 and further selects the item K14. Upon receiving this selection, the mobile terminal 22 requests the service server 11 to officially register the mobile terminal 22 in the group G1 (step S16). The mobile terminal 22 transmits the input name of the mobile terminal 22, the terminal number of the mobile terminal 22, and the group number of the group G <b> 1 to the service server 11.

  Upon receiving this request, the service server 11 requests the group management server 12 to formally register the mobile terminal 22 in the group G1 (step S17). At that time, the service server 11 transmits the terminal name of the mobile terminal 22, the terminal number of the mobile terminal 22, and the group number of the group G1 to the group management server 12.

  Upon receiving this request, the group management server 12 confirms whether or not the state of the group management table is waiting for the name input of the portable terminal 22. If it can be confirmed, the mobile terminal 22 is registered in the group G1. At that time, in the group management table, the terminal number of the portable terminal 22 is stored in association with the group number of the group G1.

  If the group management server 12 cannot confirm that the state of the group management table is the name input waiting state of the mobile terminal 22, the group management server 12 replies to the service server 11. The group management table is returned to the normal state. In response to this reply, the service server 11 transmits an error message to the mobile terminal 22. As a result, the process shown in FIG. 9 ends abnormally.

  After registering the mobile terminal 22 in the group management table, the group management server 12 next requests the terminal management server 13 to register the mobile terminal 22 in the terminal management table that manages the terminals registered in the group G1. (Step S18). At that time, the group management server 12 transmits the terminal name of the mobile terminal 22, the terminal number of the mobile terminal 22, and the group number of the group G1 to the terminal management server 13.

  Upon receiving this request, the terminal management server 13 registers the mobile terminal 22 in the terminal management table for the group G1. Specifically, the terminal number and the terminal name of the mobile terminal 22 are added to the terminal management table for the group G1. When registration is completed, the terminal management server 13 notifies the group management server 12 to that effect (step S19).

  Upon receiving this notification, the group management server 12 notifies the service server 11 that the formal registration of the portable terminal 22 to the group G1 has been completed (step S20). Upon receiving this notification, the service server 11 transmits a screen for notifying that the registration of the mobile terminal 22 is completed to the mobile terminal 22 (step S21). The portable terminal 22 receives and displays the screen. Thereby, the screen shown in FIG. 11E is displayed. FIG. 11E is a diagram showing a screen for notifying that registration of the mobile terminal 22 is completed. By visually recognizing this screen, the user of the mobile terminal 22 knows that the mobile terminal 22 is officially registered in the group G1.

  After being registered in the group G1, the portable terminal 22 keeps holding the terminal number of the portable terminal 22 and the group number of the group G1 in a storage unit (not shown). The portable terminal 22 can transmit a message to other terminals (such as the administrator terminal 21) belonging to the group G1 by using the terminal number of the portable terminal 22 and the group number of the group G1. Details of the message transmission procedure will be described later.

(Automatic application installation)
After reading the QR code from the administrator terminal 21, the mobile terminal 22 may determine whether an application for using the SNS system 10 has been installed in the mobile terminal 22. And when it determines with the application not being installed in the portable terminal 22, you may install an application automatically. At this time, the process shown in FIG. 12A is executed at the timing shown in the frame W1 in FIG.

  FIG. 12A is a flowchart illustrating a processing flow when an application for using the SNS system 10 is installed in the mobile terminal 22 newly registered in the SNS system 10. As shown in this figure, the portable terminal 22 requests an application distribution server 17a (not shown) to install an application (step S31). In response to this request, the application distribution server 17a transmits data for installing the application to the portable terminal 22 (step S32). The portable terminal 22 installs an application using the received data.

  As described above, the mobile terminal 22 automatically installs the application, thereby eliminating the need for the user to manually install the application on the mobile terminal 22.

  The application can also be installed manually. The procedure is as follows. When the screen of FIG. 11B is displayed, the user of the portable terminal 22 selects the item K11. Thereby, the portable terminal 22 displays the screen shown in FIG. FIG. 11C is a screen displayed on the mobile terminal 22 when the application is manually installed. This screen includes an item K13 labeled "Install".

  The user of the portable terminal 22 selects item K13. Thereby, the portable terminal 22 acquires application installation data from the application distribution server 17a, and installs the application using the acquired data.

(Distribution of terminal numbers)
At the time of starting the registration process of the mobile terminal 22, the terminal number of the mobile terminal 22 does not necessarily have to be prepared in the mobile terminal 22 in advance. In this case, after reading the QR code from the administrator terminal 21, the mobile terminal 22 determines whether or not the terminal number of the mobile terminal 22 is prepared in the mobile terminal 22. And when it determines with the terminal number of the portable terminal 22 not being previously prepared in the portable terminal 22, a terminal number is automatically acquired from the outside. At this time, the process shown in FIG. 12B is executed at the timing indicated by the frame W1 in FIG.

  FIG. 12B is a flowchart showing a flow of processing when distributing the terminal number of the mobile terminal 22 to the mobile terminal 22 newly registered in the SNS system 10. The portable terminal 22 requests the terminal identification information distribution server 17b (not shown) to distribute the terminal number of the portable terminal 22 (step S41). In response to this request, the terminal identification information server 17b generates a terminal number to be assigned to the mobile terminal 22 and transmits it to the mobile terminal 22 (step S42). At that time, the terminal identification information distribution server 17 b generates a terminal number different from any terminal registered in any group in the SNS system 10.

  For example, the terminal identification information distribution server 17b has terminal numbers of all terminals registered in the SNS system 10, and may generate a new terminal number that is different from any of those terminal numbers. Or, the most recently generated terminal number is stored, and when generating the terminal number next time, by adding a certain numerical value to the stored number, the terminal number that has never been generated in the past You may make it produce | generate. In that case, it is preferable that the numerical value to be added is a prime number having a large number of digits.

  The terminal identification information distribution server 17b desirably generates a number that cannot be easily imagined as the terminal number. For example, instead of a decimal number consisting only of numbers, a terminal number of 36 numbers that can take any of 10 numbers from 0 to 9 and 26 alphabets from A to Z in each digit is generated. do it. With such a terminal number, it is difficult to find out the actual terminal number even if a technique for searching for a terminal number for a specific terminal is used by randomly generating a number using numbers. . Therefore, the degree of security can be increased.

  Further, the terminal identification information distribution server 17b may generate the terminal identification information using information such as a character string other than the number instead of the terminal number as long as each terminal can be identified.

  The portable terminal 22 stores the received terminal number in a storage unit (not shown). Thereby, the mobile terminal 22 is in a state where the terminal number of the mobile terminal 22 is prepared.

  As described above, even if the terminal number of the mobile terminal 22 is not prepared in advance in the mobile terminal 22, the mobile terminal 22 can be registered in a group. Therefore, the trouble of preparing the terminal number of the portable terminal 22 in the portable terminal 22 in advance can be eliminated. Moreover, the versatility of the SNS system 10 can be further improved.

  The terminal number of the mobile terminal 22 may be distributed to the mobile terminal 22 by the application distribution server 17a instead of the terminal identification information distribution server 17b. That is, the application distribution server 17a may have the function of the terminal identification information distribution server 17b. In this case, the application distribution server 17 a generates a terminal number of the mobile terminal 22 and transmits installation data including the terminal number to the mobile terminal 22. In the portable terminal 22, by installing the application, the terminal number of the portable terminal 22 is automatically saved in the storage unit.

  When the terminal number is distributed to the portable terminal 22 by this method, the terminal number stored in the storage unit is automatically deleted after the application is uninstalled from the portable terminal 22. Therefore, when an application is newly installed, a terminal number different from the previous one is received from the application distribution server 17a and stored in the storage unit.

  Further, in the SNS system 10, a server other than the application distribution server 17a may have the function of the terminal identification information distribution server 17b. For example, since each terminal always accesses the service server 11 first, if the service server 11 also has the function of the terminal identification information distribution server 17b, the processing load on the SNS 10 can be further reduced. Alternatively, for example, if the terminal management server 13 has the function of the terminal identification information distribution server 17b, the administrator of the SNS 10 can easily manage each server.

(Use of e-mail)
The link of the web page for registering the terminal in the group G1 is not limited to the QR code, and can be provided from the administrator terminal 21 to the portable terminal 22 using an electronic mail. The procedure at that time will be described below with reference to FIG.

  FIG. 13 is a diagram illustrating an example of another flow of processing in the SNS system 10 when a new terminal is registered in a group in the embodiment of the present invention. Below, the procedure at the time of registering the user terminal 22 to the group G1 is demonstrated.

  The processes from Steps S1 to S4 in FIG. 13 are the same as the processes from Steps S1 to S4 in FIG. In the example of FIG. 13, the user of the administrator terminal 21 selects the item K5 when the screen of FIG. 10C is displayed. In response to this selection, the administrator terminal 21 requests the service server 11 for information related to the e-mail transmitted from the portable terminal 22 (S51). At that time, the administrator terminal 21 transmits the terminal number of the administrator terminal 21 and the group number of the group G1 to the service server 11.

  In response to this request, the service server 11 transmits information about the electronic mail (step S52). At that time, the service server 11 transmits a link of a web page for registering the terminal to the group G1 to the administrator terminal 21. In this link, the group number of the group G1 is obfuscated by a technique such as hashing, and is included as a query.

  When the administrator terminal 21 receives the information about the e-mail, the administrator terminal 21 generates an e-mail including a link of a web page for registering the terminal in the group G1 using the information, and transmits the e-mail to the portable terminal 22 (step S53). ). Thereby, the administrator terminal notifies the mobile terminal 22 that the mobile terminal 22 is invited to the group G1. FIG. 11A is a diagram illustrating the text of an e-mail displayed on the mobile terminal 22. As shown in this figure, this body includes a link L11 to a web page for registering a terminal in the group G1.

  When the link L11 is selected, the mobile terminal 22 requests the service server 11 for a screen for registering the mobile terminal 22 in the group G1 by accessing the selected link (step S8). As a result, in the example of FIG. 13, after the screen of FIG. 10A is displayed, the screen of FIG. 10B is displayed. In other words, the screen display of FIG. 10A is omitted in the example of FIG.

  Information (group number, link) included in the e-mail is preferably encrypted or obfuscated. In this case, the mobile terminal 22 acquires the group number and the link by decrypting the encrypted information or the obfuscated information acquired from the electronic mail. If the information included in the e-mail is encrypted or obfuscated, even if the information leaks from the mobile terminal 22, the group number and the link are not specified. It is possible to prevent you from applying for registration.

  Since the processing from steps S8 to S21 in FIG. 13 is the same as the processing from steps S8 to S21 in FIG. 9, detailed description thereof is omitted. In the example of FIG. 13, the process shown in FIG. 12A or 12B can be executed at the timing shown in the frame W1.

  Note that the method in which the administrator terminal 21 provides the group number and the link to the mobile terminal 22 is not limited to the above-described QR code or e-mail. In addition to these, any means capable of providing a group number and a link can be used. For example, the group number and the link may be directly provided from the administrator terminal to the portable terminal 22 by direct communication such as infrared communication.

  If the group number of group G1 is obfuscated and included in the link as a query, this link may be very long. If the link is actually very long, it is troublesome for the user to input the link directly to the mobile terminal 22. Therefore, in order to avoid the occurrence of such inconvenience, in the present embodiment, a link is transmitted from the administrator terminal 21 to the mobile terminal 22 through a QR code or an e-mail.

  When the portable terminal 22 cannot receive an e-mail but cannot read the QR code, it is desirable to use the QR code. Conversely, when the mobile terminal 22 can receive an e-mail but cannot read a QR code, it is desirable to use the e-mail. If the mobile terminal 22 cannot receive an e-mail or read a QR code, the user directly inputs a link to the mobile terminal or registers the mobile terminal 22 by the method shown in FIG. It is desirable to do.

(Advantages of this embodiment)
As described above, in this embodiment, not the user of the mobile terminal 22 but the mobile terminal 22 itself is registered in the SNS group G1. Therefore, no personal information regarding the user of the mobile terminal 22 is registered in each server. Therefore, the user of the mobile terminal 22 using the SNS system 10 does not need to manage his / her account information. Therefore, even a person with low IT literacy can register the mobile terminal 22 in the SNS system 10 without resistance.

  In addition, since the user himself / herself is not registered in each group, even if registration information regarding a specific group leaks to the outside, it is not known at all who is registered in that group. Thereby, it is possible to prevent the identity of the user who uses the SNS system 10 from being specified or a malicious message being sent to the user. That is, according to the present embodiment, it is possible to provide the SNS system 10 that can be used with peace of mind by each user.

[Embodiment 2]
A second embodiment according to the present invention will be described below. In addition, about the same member as 1st Embodiment mentioned above, the detailed description is abbreviate | omitted by attaching | subjecting the same code | symbol.

  In this embodiment, a procedure for registering a terminal that is shared and used by a plurality of users in a group will be described. Specifically, a procedure for registering the television 24 as a shared terminal in the group G1 will be described.

(TV 24 registration process)
FIG. 14 is a diagram illustrating an example of a process flow in the SNS system 10 when the television 24 is registered in the group G1.

  In the example illustrated in FIG. 14, first, the television 24 requests the service server 11 for a screen for applying for registration to the SNS system 10 (step S <b> 61). In response to this request, the service server 11 transmits a screen for applying for registration to the SNS system 10 to the television 24 (step S62). The television 24 displays the received screen. As a result, the screen shown in FIG. FIG. 15A is a screen for applying for registration in the SNS system 10 displayed on the television 24. This screen includes an item K21 labeled "Register terminal".

  The user of the television 24 selects item K21. In response to this selection, the television 24 applies to the service server 11 for registration in the SNS system 10 (step S62). At that time, the television 24 transmits the terminal number of the television 24 to the service server 11. The terminal number of the television 24 is prepared in advance on the television 24.

(Tentative registration of TV 24)
When receiving the terminal number of the television 24, the service server 11 requests the group management server 12 to temporarily register the television 24 (step S63). At that time, the service server 11 transmits the terminal number of the television 24 to the group management server 12.

  When the terminal number of the television 24 is received, the group management server 12 changes the state of the group management table to a state where the television 24 is provisionally registered. If this is successful, the group management server 12 returns a message to that effect to the service server 11 (step S65).

  When the group management server 12 determines that there is a problem in temporarily registering the television 24 in the group management table, the group management server 12 returns a message to that effect to the service server 11. In response to this reply, the service server 11 transmits an error message to the television 24 (step S66). Thereby, the process shown in FIG. 14 ends abnormally.

  Upon receiving a reply that the temporary registration has been successful, the service server 11 transmits a screen including information for proceeding with the registration of the television 24 to the television 24 (step S66). Specifically, a screen including a QR code in which the terminal number of the television 24 is coded is transmitted. The television 24 displays the received screen. Thereby, the screen shown in FIG. 15B is displayed. This screen includes a QR code C11 in which the terminal number of the television 24 is coded and a terminal number C12 of the television 24. Note that the screen may not include the terminal number C12 in order to maintain confidentiality.

  In parallel with this, the administrator terminal 21 displays the screen shown in FIG. FIG. 16A is a diagram illustrating a screen displayed on the administrator terminal 21 when starting terminal registration. This screen is the same as the screen shown in FIG. The user of the administrator terminal 21 selects the item K3 included in the screen. In response to this selection, the administrator terminal 21 requests the service server 11 for a screen for applying to register the television 24 in the SNS system 10 (step S67).

  In response to this request, the service server 11 transmits a screen for applying to register the television 24 to the SNS system 10 to the administrator terminal 21 (step S68). The administrator terminal 21 displays the received screen. As a result, the screen shown in FIG. 16B is displayed. FIG. 16B is a diagram showing a screen displayed on the administrator terminal 21 when the registration method of the television 24 is selected. This screen includes an item K6 labeled "shoot QR code" and an item K7 labeled "Register".

(Provision of terminal number for TV 24)
After the screen shown in FIG. 16B is displayed, the television 24 provides the terminal number of the television 24 to the administrator terminal 21 (step S69). The procedure is as follows. The user of the administrator terminal 21 selects the item K6 included in the screen shown in FIG. In response to this selection, the administrator terminal 21 activates the camera function. The user of the administrator terminal 21 uses the camera function of the administrator terminal 21 to photograph the QR code C11 displayed on the screen of the television 24. Thereby, the administrator terminal 21 acquires an image of the QR code C11. The administrator terminal 21 acquires the terminal number of the television 24 by analyzing the image.

  Next, the user of the administrator terminal 21 selects the item K7 in the screen shown in FIG. Upon receiving this selection, the administrator terminal 21 applies to the service server 11 to register the television 24 in the group G1 (step S74). At that time, the administrator terminal 21 transmits the terminal number of the television 24 and the terminal number of the group G1 to the service server 11.

  Upon receiving the terminal number of the television 24 and the terminal number of the group G1, the service server 11 checks with the group management server 12 whether the state of the group management server 12 is the provisional registration state of the television 24. An inquiry is made (step S71). At that time, the service server 11 transmits the terminal number of the television 24 and the group number of the group G1 to the group management server 12.

  When receiving the terminal number of the television 24 and the group number of the group G1, the group management server 12 confirms whether or not the group management table state is the provisional registration state of the television 24. When it is confirmed that the temporary registration state is established, the group management server 12 returns a message to that effect to the service server 11 (step S72). Furthermore, the group management server 12 changes the state of the group management table to a state waiting for official registration of the television 24 to the group G1.

  When the group management server 12 cannot confirm that the state of the group management table is the provisional registration state of the television 24, the group management server 12 returns a message to that effect to the service server 11. The group management table is returned to the normal state. In response to this reply, the service server 11 transmits an error message to the administrator terminal 21 (step S73). Thereby, the process shown in FIG. 14 ends abnormally.

  Upon receiving a reply that the TV 24 has been temporarily registered, the service server 11 transmits a screen for applying for formal registration of the TV 24 to the administrator terminal 21 (step S73). The television 24 displays the received screen. Thereby, the screen shown in FIG. 16C is displayed. FIG. 16C is a diagram showing a screen displayed on the administrator terminal 21 when applying for formal registration of the television 24. This screen includes an item K8 labeled "Register". In addition, a field for inputting the terminal name of the television 24 is also included.

(Official registration of TV 24)
The user of the manager terminal 21 inputs the terminal name of the television 24 and further selects the item K14. Upon receiving this selection, the administrator terminal 21 requests the service server 11 to officially register the television 24 in the group G1 (step S74). At that time, the administrator terminal 21 transmits the input name of the television 24, the terminal number of the television 24, and the group number of the group G1 to the service server 11.

  In response to this request, the service server 11 requests the group management server 12 to register the television 24 in the group G1 (step S75). At that time, the service server 11 transmits the name of the television 24, the terminal number of the television 24, and the group number of the group G1 to the group management server 12.

  Upon receiving this request, the group management server 12 confirms whether or not the state of the group management table is in a state of waiting for official registration of the television 24 to the group G1. If it can be confirmed, the group management server 12 officially registers the television 24 in the group G1. At that time, in the group management table, the terminal number of the television 24 is stored in association with the group number of the group G1. As a result, the group management table returns to the normal state.

  If the group management server 12 cannot confirm that the state of the group management table is in the state of waiting for official registration of the television 24 to the group G1, the group management server 12 sends a message to that effect to the service server 11. The group management table is returned to the normal state. In response to this reply, the service server 11 transmits an error message to the administrator terminal 21. Thereby, the process shown in FIG. 14 ends abnormally.

  When the group management server 12 registers the television 24 in the group management table, the group management server 12 requests the terminal management server 13 to register the television 24 in the terminal management table that manages the terminals registered in the group G1 (step S76). . At that time, the group management server 12 transmits the terminal name of the television 24, the terminal number of the television 24, and the group number of the group G1 to the terminal management server 13.

  Upon receiving this request, the terminal management server 13 registers the television 24 in the terminal management table for group G1. Specifically, the terminal number and terminal name of the television 24 are registered in the terminal management table for group G1. When registration is completed, the terminal management server 13 notifies the group management server 12 to that effect (step S77).

  Upon receiving this notification, the group management server 12 notifies the service server 11 that the formal registration of the television 24 to the group G1 has been completed (step S78). Upon receiving this notification, the service server 11 transmits a screen for notifying that the registration of the television 24 is completed to the administrator terminal 21 (step S79). The administrator terminal 21 receives and displays the screen. Thereby, the screen shown in FIG. 16D is displayed. FIG. 16D is a diagram showing a screen for notifying that the registration of the television 24 is completed. The user of the administrator terminal 21 recognizes that the television 24 has been officially registered in the group G1 by viewing this screen.

  After being registered in the group G1, the television 24 keeps holding the terminal number of the television 24 and the group number of the group G1 in a storage unit (not shown). The television 24 can transmit a message to other terminals belonging to the group G1 by using the terminal number of the television 24 and the group number of the group G1. Details of the message transmission procedure will be described later.

(Distribution of terminal numbers)
When the registration process of the television 24 is started, the terminal number of the television 24 is not necessarily prepared in advance in the television 24. In this case, after receiving the screen shown in FIG. 15A from the service server 11, the television 24 determines whether the terminal number of the television 24 is prepared in the television 24. When it is determined that the terminal number of the television 24 is not prepared in advance in the television 24, the terminal number is automatically acquired from the outside. At this time, a process for acquiring the terminal number of the television 24 from the outside is executed at the timing indicated by a frame W2 in FIG. The process performed at this time is essentially the same as the process shown in FIG.

  As described above, even if the terminal number of the television 24 is not prepared in advance in the television 24, the television 24 can be registered in a group. Therefore, the trouble of preparing the terminal number of the television 24 in advance in the television 24 can be eliminated. Moreover, the versatility of the SNS system 10 can be further improved.

(Advantages of this embodiment)
As described above, according to the present embodiment, the television 24 that is a terminal shared and used by a plurality of users can also be registered in the group of the SNS system 10. As a result, the SNS system 10 according to the present embodiment can transmit a message using a shared terminal, which is impossible with the conventional system.

  In addition, the terminal that can be registered in the SNS 10 in the present embodiment is not limited to the television 24. Any terminal that has a screen capable of displaying a certain amount of information can be registered in the SNS system 10 by the method of the present embodiment. Further, in the present embodiment, unlike the first embodiment, even a terminal that cannot receive both e-mail and QR code can be registered in the SNS system 10 without any problem.

[Embodiment 3]
A third embodiment according to the present invention will be described below. In addition, about the member same as 1st or 2nd embodiment mentioned above, the detailed description is abbreviate | omitted by attaching | subjecting the same code | symbol.

  In this embodiment, a procedure for registering home appliances in a group will be described. Specifically, the procedure for registering the robot cleaner 25, which is a home appliance, in the group G1 will be described.

(Registration process of robot cleaner 25)
FIG. 17 is a diagram illustrating an example of a processing flow in the SNS system 10 when registering the robot cleaner 25 in the group G1.

  In the example illustrated in FIG. 17, first, the user of the administrator terminal 21 presses a registration application button provided in the robot cleaner 25. In response to this press, the robot cleaner 25 applies to the service server 11 for registration in the SNS (step S81). At that time, the robot cleaner 25 transmits the terminal number of the robot cleaner 25 to the service server 11. The terminal number of the robot cleaner 25 is prepared in advance in the robot cleaner 25. At this time, it is not determined to which group the robot cleaner 25 applies for registration. As will be described later, the administrator terminal 21 determines a group in which the robot cleaner 25 is registered.

(Tentative registration of robot cleaner 25)
When receiving the terminal number of the robot cleaner 25, the service server 11 requests the group management server 12 to temporarily register the robot cleaner 25 (step S82). At that time, the service server 11 transmits the terminal number of the robot cleaner 25 to the group management server 12.

  When the terminal number of the robot cleaner 25 is received, the group management server 12 changes the group management table state to a state where the robot cleaner 25 is temporarily registered. If this is successful, the group management server 12 returns a message to that effect to the service server 11 (step S83).

  When the group management server 12 determines that there is a problem in temporarily registering the robot cleaner 25 in the group management table, the group management server 12 returns a message to that effect to the service server 11. In response to this reply, the service server 11 transmits an error message to the administrator terminal 21. Thereby, the process shown in FIG. 17 ends abnormally.

  When receiving a reply that the temporary registration has been successful, the service server 11 returns a reply that the temporary registration of the robot cleaner 25 has been completed to the robot cleaner 25 (step S84). Thereby, the robot cleaner 25 will be in the state which has applied for registration to SNS.

  In parallel with this, the administrator terminal 21 requests the service server 11 for a screen for applying to register the robot cleaner 25 in the SNS system 10 (step S85).

  In response to this request, the service server 11 transmits a screen for applying to register the robot cleaner 25 to the SNS to the administrator terminal 21 (step S86). The administrator terminal 21 displays the received screen. As a result, the screen shown in FIG. 16B is displayed. This screen includes an item K6 labeled "shoot QR code" and an item K7 labeled "Register".

(Provision of the terminal number of the robot cleaner 25)
Since the robot cleaner 25 cannot display the QR code, the terminal number of the robot cleaner 25 cannot be provided from the robot cleaner 25 to the manager terminal 21 through the QR code. Therefore, in this embodiment, the user of the manager terminal 21 presses the terminal number transmission button provided in the robot cleaner 25. Thereby, the robot cleaner 25 transmits the terminal number of the robot cleaner 25 to the administrator terminal 21 (step S87). At that time, the robot cleaner 25 can use any communication means such as infrared communication, ultrasonic communication, or wireless communication. The manager terminal 21 acquires the terminal number of the robot cleaner 25 by receiving the terminal number of the robot cleaner 25 from the robot cleaner 25.

  Next, the user of the administrator terminal 21 selects the item K7 in the screen shown in FIG. Upon receiving this selection, the administrator terminal 21 applies to the service server 11 to register the robot cleaner 25 in the group G1 (step S88). Since the processing from step S88 to S98 in FIG. 17 is the same as the processing from step S70 to S79 in FIG. 14, detailed description thereof will be omitted.

  In this embodiment, after being registered in the group G1, the robot cleaner 25 holds the terminal number of the robot cleaner 25, but does not hold the group number of the group G1. Therefore, although the robot cleaner 25 is registered in the group G1 in the SNS system 10, a message cannot be transmitted directly from the robot cleaner 25 to other terminals belonging to the group G1. However, in the SNS system 10, special software (bot 4) is prepared in the message management server 15, and the bot 4 transmits a message to other terminals belonging to the group G1.

  At that time, the bot 4 transmits a message that appears to have been transmitted from the robot cleaner 25. Specifically, a message including the avatar of the robot cleaner 25 is transmitted. Thereby, the user who uses the terminal belonging to the group G1 recognizes that the message transmitted from the bot is the message transmitted from the robot cleaner 25. When the robot cleaner 25 has a sensor, the bot 4 may inquire and collect information obtained by the sensor from the robot cleaner 25 and generate and transmit a message based on the sensor information. The message generated in this manner reflects the state and environment of the robot cleaner 25 well. Therefore, if the bot 4 transmits the message, the user who uses the terminals belonging to the group G1 can be given a stronger impression that the message is transmitted from the robot cleaner 25.

(Distribution of terminal numbers)
When registering the robot cleaner 25 in the group G1, the terminal number of the robot cleaner 25 may not be prepared in the robot cleaner 25 in advance. In this case, the robot cleaner 25 acquires the terminal number of the robot cleaner 25 from the outside. Specifically, before the user of the administrator terminal 21 presses the registration application button of the robot cleaner 25, the user presses the terminal number acquisition button provided in the robot cleaner 25. In response to this press, a process for acquiring the terminal number of the robot cleaner 25 from the outside is executed at the timing indicated by a frame W3 in FIG. The process performed at this time is essentially the same as the process shown in FIG.

  As described above, even if the terminal number of the robot cleaner 25 is not prepared in the robot cleaner 25 in advance, the robot cleaner 25 can be registered in the SNS group. Therefore, the trouble of preparing the terminal number of the robot cleaner 25 in the robot cleaner 25 in advance can be eliminated. Moreover, the versatility of the SNS system 10 can be further improved.

(This embodiment)
As described above, in this embodiment, the robot cleaner 25 that is a home appliance can be registered in the SNS group. Therefore, it is possible to meet the needs of users who want to communicate with home appliances.

[Embodiment 4]
A fourth embodiment according to the present invention will be described below. In addition, about the same member as the 1st-3rd embodiment mentioned above, the detailed description is abbreviate | omitted by attaching | subjecting the same code | symbol.

  In the present embodiment, an example of the flow of processing at the time of message transmission / reception between terminals in the SNS system 19 will be described in detail. Specifically, the flow of processing in the SNS system 10 when the mobile terminal 22 belonging to the group G1 receives a message transmitted from the administrator terminal 21 belonging to the group G1 will be described. Note that this is merely an example for explanation, and message transmission / reception between terminals in the SNS system 10 is not limited thereto. For example, when the administrator terminal 21 receives a message transmitted from the mobile terminal 22, there is no difference in the processing flow. That is, in the SNS system 10, each terminal is not distinguished according to its role or function regarding message transmission / reception.

  First, the administrator terminal 21 activates a dedicated application for using the SNS system 10. When the application is activated, the administrator terminal 21 requests the service server 11 for a screen including the latest message. In response to this, the service server 11 transmits the screen shown in FIG. FIG. 21A shows a screen including the latest message.

  The screen shown in FIG. 21A includes five messages M1 to M5. Each message includes an avatar R1 indicating the sender of the message, a message transmission time R2, a message body R3, and a terminal name R4 that transmitted the message.

(Message details)
As shown in FIG. 21A, the avatar of the message M1 is an avatar having an avatar number A7003. Further, since the terminal name of the message M1 is “Taro's phone”, it can be seen from FIG. 4 that the terminal that has transmitted the message M1 is the terminal having the terminal number D7003. This terminal is the mobile terminal 23.

  That is, the message M1 is a message transmitted by the user using the portable terminal 23 and selecting an avatar having an avatar number A7003. The user of each terminal that has received the message M1 includes information (terminal name) indicating that the avatar having the avatar number A7003 is included in the message M1 and that the transmitting terminal is the portable terminal 23 in the message M1. Know what is being done. Thus, it is recognized who has transmitted the message M1 using which terminal.

  Although this user is likely to be the owner of the portable terminal 23, there is no guarantee that this is the case. Because, in the SNS system 10, not the owner of the mobile terminal 23 but the mobile terminal 23 itself is registered in the group, even if a user other than the owner of the mobile terminal 23 uses the mobile terminal 23. This is because a message having the same content as the message M1 can be transmitted.

  However, those who use each terminal registered in a specific group in the SNS system 10 are premised on those who are familiar with each other and who are reliable, such as family members and close friends. The SNS system 10 is operated with the trust that there is no false message transmission between these persons, or even if the message is falsely transmitted. Therefore, each user can recognize with confidence that the person associated with the avatar or terminal name included in each message is the genuine sender of the message.

  The avatar of the message M2 is an avatar whose avatar number is A7001. Further, since the terminal name of the message M2 is “father's phone”, it can be seen from FIG. 4 that the terminal that transmitted the message M2 is the terminal having the terminal number D7001. That is, the message M2 is a message that the user uses a terminal whose terminal number is D7001, and selects and transmits an avatar whose avatar number is A7001. This terminal is the administrator terminal 21.

  The avatar of the message M3 is an avatar whose avatar number is A7002. Further, since the terminal name of the message M2 is “mom's phone”, it can be seen from FIG. 4 that the terminal that transmitted the message M2 is the terminal having the terminal number D7002. That is, the message M3 is a message that the user uses a terminal whose terminal number is D7002, and selects and transmits an avatar whose avatar number is A7002. This terminal is the mobile terminal 22.

  The avatar of the message M4 is an avatar whose avatar number is A7005. Further, since the terminal name of the message M4 is “vacuum cleaner”, referring to FIG. 4, it can be said that the terminal that has transmitted the message M4 is the terminal having the terminal number D7005. This terminal is a robot cleaner 25.

  However, as described above, the robot cleaner 25 does not have a function of logging in to the SNS system 10 and transmitting a message to other terminals in the group to which the robot cleaner 25 belongs. The message M4 is a message transmitted by the software (bot 4) operating in the service server 11 using the terminal number of the robot cleaner 25 and the avatar having the avatar number A7005. Information indicating that the bot 4 has transmitted the message M4 is not included in the message M4. Therefore, each user recognizes that the message M4 is transmitted from the robot cleaner 25 itself. That is, it is recognized as if a message was transmitted from the robot cleaner 25 to each user.

  In the present embodiment, the bot 4 periodically inquires the robot cleaner 25 for measurement information from the temperature sensor and obtains the information. Then, based on the obtained temperature information, after grasping that the temperature of the room is on an upward trend, a message M4 is generated to notify that. As a result, the message text is written by the anthropomorphic robot cleaner 25.

  The avatar of the message M5 is an avatar whose avatar number is A7002. Further, since the terminal name of the message M2 is “Mom's phone”, it can be seen from FIG. 4 that the terminal that transmitted the message M5 is the terminal having the terminal number D7002. That is, the message M5 is a message that the user uses a terminal whose terminal number is D7002, and selects and transmits an avatar whose avatar number is A7002. This terminal is the mobile terminal 22.

  The text of the message M4 is the content that the robot cleaner 25 proposes to attach an air conditioner. On the other hand, the text of the message M5 is a content that accepts the proposal from the robot cleaner 25. Thus, in the SNS system 10, each user who uses the SNS system 10 can feel as if he / she was able to talk with the robot cleaner 25 through message exchange with the robot cleaner 25.

(Message input screen)
In the SNS system 10, when transmitting a message from the administrator terminal 21, first, the administrator terminal 21 needs to acquire and display a message input screen from the service server 11. The procedure for acquiring the message input screen will be described below with reference to FIG. FIG. 18 is a flowchart showing the flow of processing in the SNS system 10 when the administrator terminal 21 acquires a message input screen.

  The screen shown in FIG. 21A includes an item K31 labeled “message input”. The user of the administrator terminal 21 selects the item K31. Upon receiving this selection, the administrator terminal 21 requests the service server 11 for a screen for inputting a message (step S101). At that time, the administrator terminal 21 transmits the terminal number of the administrator terminal 21 and the group number of the group G1 to the service server 11.

  Upon receiving the terminal number and group number, the service server 11 requests the group management server 12 to confirm whether these numbers have been registered (step S102). At that time, the service server 11 transmits the terminal number of the administrator terminal 21 and the group number of the group G1 to the group management server 12. When the group management server 12 confirms that the administrator terminal 21 is registered in the group G1, the service server 11 transmits a message from the administrator terminal 21 to the service server 11 to the administrator terminal 21. Allow. On the other hand, if it cannot be confirmed, it is not permitted.

(Confirm device)
The group management server 12 searches the group management table using the received terminal number and group number. Thereby, it is confirmed whether or not the administrator terminal 21 is a terminal registered in the group G1. If it can be confirmed, it requests the avatar management server 14 to provide the avatar list of the group G1 (step S103).

  In response to this request, the avatar management server 14 generates an avatar list with reference to the avatar management table for the group G1. The procedure is as follows. First, avatar numbers and avatar names of all avatars included in the avatar management table are extracted. Next, all avatar image file names included in the avatar management table are extracted, and all avatar images specified by these file names are acquired. Then, an avatar list is generated by associating all acquired avatar images with all the extracted avatar numbers and avatar names. In the generated avatar list, for each avatar, an avatar number, an avatar name, and an avatar image are associated with each other.

  The avatar management server 14 transmits the generated avatar list to the group management server 12 (step S104). The group management server 12 transmits the received avatar list to the service server 11 (step S105).

  When the avatar list is received, the service server 11 inquires of the group management server 12 about the avatar number of the avatar last used when the administrator terminal 21 transmits a message (step S106). At that time, the service server 11 transmits the group number of the administrator terminal 21 to the group management server 12.

  Upon receiving this inquiry, the group management server 12 inquires of the terminal management table for the avatar number of the avatar used last when the administrator terminal 21 transmits a message (step S107). At that time, the group management server 12 transmits the group number of the administrator terminal 21 to the terminal management table.

  The terminal management server 13 specifies the avatar number of the avatar used last when the administrator terminal 21 transmits a message by referring to the terminal management table. The avatar number is stored in association with the terminal number of the administrator terminal 21 in the terminal management table. Therefore, the terminal management table extracts this avatar number from the terminal management table and transmits it to the group management server 12 (step S108). The group management server 12 transmits the received avatar number to the service server 11 (step S109).

  When the service server 11 receives the avatar number of the avatar last used by the administrator terminal 21, the service server 11 transmits a message input screen to the administrator terminal 21 (step S110). By transmitting this message input screen, the service server 11 permits the administrator terminal 21 to transmit a message to the service server 11. The service server 11 transmits the avatar list and the avatar number of the avatar last used by the administrator terminal 21 in association with the message input screen. The administrator terminal 21 displays the received screen. Thereby, the screen shown in FIG. 21B is displayed. FIG. 21B is a diagram showing a message input screen.

  In the process illustrated in FIG. 18, the process related to the acquisition of the avatar list is not necessarily performed every time. Since the same user often transmits a message repeatedly using the same avatar, the last-used avatar information may be stored as a cache for a certain period in the administrator terminal 21 and repeatedly used. Thereby, since it is not necessary to perform the communication between each server regarding provision of an avatar list, and the communication for provision to the administrator terminal from the service server 11, it can reduce the communication burden in an SNS system.

  When the acquisition of the message input screen is completed, the SNS system 10 executes a series of processes shown in FIG. FIG. 19 is a flowchart showing the flow of processing in the SNS system 10 when changing an avatar, inputting a message, sending a message, and displaying a message.

  The user of the administrator terminal 21 can select an avatar or transmit a message through the screen shown in FIG. The screen of FIG. 21B includes an avatar whose avatar number is A7001 and a terminal name R5 of the administrator terminal 21. This avatar is the avatar used last by the administrator terminal 21. When the administrator terminal 21 displays the screen of FIG. 21B, the avatar number of the avatar last used by the administrator terminal 21 received from the service server 11 is specified by the avatar number. Display an avatar image.

(Avatar selection)
The user of the administrator terminal 21 does not change the avatar when transmitting a message using the avatar image shown in FIG. In this case, the process shown in FIG. 19 immediately shifts a series of processes in the frame W13. On the other hand, when the user wants to transmit a message using another avatar, the user selects a desired avatar from the avatar list. In this case, a series of processes in the frame W11 in FIG. 19 is executed.

  The flow of processing when selecting an avatar will be described below. First, the user of the manager terminal 21 clicks on an avatar included in the screen of FIG. Thereby, the administrator terminal 21 requests the avatar change screen from the service server 11 (step S111). At that time, the administrator terminal 21 transmits the terminal number of the administrator terminal 21 and the group number of the group G1 to the service server 11.

  When the service server 11 receives the terminal number and the group number, the service server 11 requests the group management server 12 to confirm whether these numbers have been registered (step S112). At that time, the service server 11 transmits the terminal number of the administrator terminal 21 and the group number of the group G1 to the group management server 12.

(Confirm device)
The group management server 12 searches the group management table using the received terminal number and group number. Thereby, it is confirmed whether or not the administrator terminal 21 is a terminal registered in the group G1. If it can be confirmed, it requests the avatar management server 14 to provide the avatar list of the group G1 (step S113).

  In response to this request, the avatar management server 14 generates an avatar list with reference to the avatar management table for the group G1. The procedure is as follows. First, avatar numbers and avatar names of all avatars included in the avatar management table are extracted. Next, all avatar image file names included in the avatar management table are extracted, and all avatar images specified by these file names are acquired. Then, an avatar list is generated by associating all acquired avatar images with all the extracted avatar numbers and avatar names. In the generated avatar list, for each avatar, an avatar number, an avatar name, and an avatar image are associated with each other.

  The avatar management server 14 transmits the generated avatar list to the group management server 12 (step S114). The group management server 12 transmits the received avatar list to the service server 11 (step S115).

  Upon receiving the avatar list, the service server 11 transmits an avatar selection screen to the administrator terminal 21 (step S116). At that time, the service server 11 transmits the avatar list in association with the avatar selection screen. The group management server 12 displays the received screen. Thereby, the screen shown in FIG. 22 is displayed. FIG. 22 is a diagram showing a screen for selecting an avatar displayed on the administrator terminal 21.

  When the administrator terminal 21 displays the avatar selection screen, the avatar image used last by the administrator terminal 21 is displayed at the top of the screen. Further, all avatar images that can be used by the administrator terminal 21 included in the avatar list are displayed in the center of the screen. In the SNS system 10, the avatar for the robot cleaner 25 is not usable except for the robot cleaner 25. Therefore, the administrator terminal 21 displays four avatar images whose avatar numbers are A7001 to A7004.

  Four selectable avatar images are displayed in the avatar selection field 14. Among these, the surrounding avatar is highlighted in the same avatar image displayed on the screen as the avatar image last used by the administrator terminal 21. That is, in the screen of FIG. 22, the avatar image last used by the administrator terminal 21 is the currently selected avatar image.

  The user of the manager terminal 21 selects one desired avatar image from the avatar selection field 14. Then, the selected avatar image is highlighted. After selecting the avatar image, the user selects an item K31 labeled “OK”. Thereby, selection of an avatar is decided. In response to this, the manager terminal 21 requests the service server 11 for a message input screen (step S117). At that time, the administrator terminal 21 transmits the avatar number of the avatar selected by the user of the administrator terminal 21, the terminal number of the administrator terminal 21, and the group number of the group G1 to the service server 11.

  In response to this request, the service server 11 transmits a message input screen to the administrator terminal 21 (step S118). At that time, the avatar number of the avatar selected by the user of the administrator terminal 21, the terminal number of the administrator terminal 21, and the group number of the group G1 are transmitted in association with the message input screen.

  The administrator terminal 21 displays the received message input screen. At that time, a message input screen is displayed in which the avatar image used last is replaced with the avatar image selected by the user.

  Through the series of processes described above, the avatar image at the time of transmitting a message using the administrator terminal 21 can be changed to another desired avatar image.

  As described above, when all the series of processes shown in FIG. 18 are executed, the administrator terminal 21 stores the avatar list in the service server at a time point before executing the series of processes shown in the frame 11 of FIG. 11 has already been obtained. Therefore, in this case, a series of processes in the frame 12 of FIG. 19 may be completed inside the administrator terminal 21. That is, the avatar selection screen is not generated from the service server 11 but is generated and displayed by itself. At that time, the avatar selection screen shown in FIG. 21B is displayed using the avatar list acquired in advance from the service server 11.

(Send Messege)
When a message is transmitted from the administrator terminal 21, a series of processes in the frame W13 in FIG. Before starting the message transmission process, the avatar selection process may or may not be executed. That is, when the administrator terminal 21 continues to use the last used avatar image to transmit a message, the message transmission process is immediately advanced without performing a series of processes in the frame 11.

  First, the user of the administrator terminal 21 inputs a message to be transmitted on the message input screen in FIG. The message input screen shown in FIG. 21B includes an input field I1 for inputting text, an input field I2 for inputting an image, and an input field I3 for inputting sound.

  The user of the administrator terminal 21 inputs text into the input field I1. On the other hand, the image is input to the input field I2. The input column I2 includes a selection column I2a for selecting and inputting an existing image, and a shooting instruction column 12b for shooting and inputting a new image. A fixed number of images stored in the administrator terminal 21 are displayed in the selection field I2a. The user can select a side to be input as a message from these images. When the user selects the shooting instruction field 12b, the camera function of the administrator terminal 21 is activated to perform shooting, and the acquired image is input as a message.

  When the user of the administrator terminal 21 wants to input a voice, the user selects the input field I3 and blows the voice. Thereby, a voice can be input.

  After completing the message input, the user selects the item K32 labeled "Send". Thereby, the administrator terminal 21 transmits to the service server 11 (step S120). At that time, the administrator terminal 21 associates the input message with the terminal number of the administrator terminal 21, the group number of the group G1, the avatar number of the selected avatar, and the message transmission time. Send to server 11.

  When receiving the message, the service server 11 requests the message management server 15 to save the message (step S120). At that time, the service server 11 transmits the message, the terminal number of the administrator terminal 21, the group number of the group G1, the avatar number of the selected avatar, and the message transmission time to the message management server 15. .

  In response to this request, the message management server 15 stores the message in the message management table. At that time, a new message number is generated, and this message number is stored in association with the message, the terminal number of the administrator terminal 21, the group number of the group G1, and the avatar number of the selected avatar. If the message is text, the text is stored as it is. On the other hand, when the message is an image or sound, the image or sound file name is stored in the message management table, and the image or sound file body is separately stored in the storage unit in the message management server 15. When the message storage is completed, the message management server 15 notifies the service server 11 to that effect (step S121).

  Upon receiving this notification, the service server 11 requests the group management server 12 to update the usage history of the administrator terminal 21 (step S122). At that time, the service server 11 transmits the terminal number of the administrator terminal 21, the avatar number of the selected avatar, and the message transmission time to the group management server 12.

  In response to this request, the group management server 12 requests the terminal management server 13 to update the usage history of the administrator terminal 21 (step S123). At that time, the group management server 12 transmits the terminal number of the administrator terminal 21, the avatar number of the selected avatar, and the message transmission time to the terminal management server 13.

In response to this request, the terminal management server 13 updates the usage history of the administrator terminal 21. At that time, the terminal management server 13 updates the last access date and time associated with the terminal number of the administrator terminal 21 in the terminal management table to the transmission time of the message received from the group management server 12. Furthermore, the last used avatar associated with the terminal number of the administrator terminal 21 in the terminal management table is updated to the avatar number of the selected avatar received from the group management server 12. When the update is completed, the terminal management server 13 notifies the group management server 12 to that effect (step S124).
Upon receiving this notification, the group management server 12 notifies the service server 11 that the update of the usage history of the administrator terminal 21 has been completed (step S125). Receiving this notification, the service server 11 transmits to the administrator terminal 21 that the message transmission has been completed (step S126). The administrator terminal 21 receives the notification from the service server 11 and knows that the message transmission has been completed.

  The administrator terminal 21 may request the latest message from the service server 11 immediately after receiving the message transmission completion notification. In this case, a series of processes shown in a frame W14 in FIG. 19 is executed. These processes will be described later.

(Message display processing)
The message transmitted from the administrator terminal 21 is transmitted to other terminals belonging to the group G1. Below, the flow of processing when this message is transmitted to the mobile terminal 22 will be described. In the present embodiment, the service server 11 does not automatically transmit the latest message to the mobile terminal 22 but transmits a message to the mobile terminal 22 after receiving a message acquisition request from the mobile terminal 22. That is, the mobile terminal 22 accesses the service server 11 and receives a message from the service server 11. At that time, a series of processes in the frame 14 of FIG. 19 is executed.

  First, the mobile terminal 22 requests the service server 11 to acquire a message (step S127). At that time, the mobile terminal 22 transmits the terminal number of the mobile terminal 22 and the group number of the group G1 to the service server 11.

(Confirm device)
When the service server 11 receives the terminal number of the mobile terminal 22 and the group number of the group G1, the service server 11 requests the group management server 12 to confirm whether these numbers have been registered. At that time, the service server 11 transmits the terminal number of the administrator terminal 22 and the group number of the group G1 to the group management server 12. When the group management server 12 can confirm that the mobile terminal 22 is registered in the group G <b> 1, the service server 11 can transmit a message to the mobile terminal 22. That is, a message can be received by the portable terminal 22 and the user can view the message. On the other hand, when the service server 11 cannot confirm the message, the service server 11 does not transmit a message to the mobile terminal 22 and therefore cannot receive the message at the mobile terminal.

  The group management server 12 searches the group management table using the received terminal number and group number. Thereby, it is confirmed whether the portable terminal 22 is a terminal registered in the group G1. If it can be confirmed, a message to that effect is returned to the service server 11.

  Receiving this reply, the service server 11 requests the message management server 15 for a list of messages transmitted to each terminal in the group G1 (step S128). At that time, the service server 11 transmits the group number of the group G1 to the message management server 15.

  In response to this request, the message management server 15 generates a list of messages transmitted to each terminal in the group G1. At this time, information relating to a predetermined number of latest messages associated with the group number of the group G1 is extracted from the message management table. Specifically, in the message management table, the avatar number, group number, transmission time, and message content (text, image, voice) associated with the group number of the group G1 are displayed in order from the person with the latest transmission time. A predetermined number is extracted. Then, a message list in which each extracted information is collected is generated. In this message list, for each message, an avatar number, a group number, a transmission time, and message contents are associated with each other.

  The message management server 15 transmits the generated message list to the service server 11. Upon receiving the message list, the service server 11 acquires necessary information for acquiring a message on the screen. At that time, a series of processes in the frame 15 in FIG. 19 is executed.

(Get message information)
FIG. 20 is a diagram showing a flow of a series of processes in the SNS system 10 when the service server 11 acquires message information.

  First, the service server 11 requests the group management server 12 for information related to the avatar corresponding to the avatar number included in the message list (step S131). At that time, the service server 11 transmits the message list to the group management server 12. In response to this request, the group management server 12 requests the message management server 15 for information on the avatar included in the message list (step S132). At that time, the group management server 12 transmits the message list to the message management server 15.

  In response to this request, the message management server 15 acquires information related to the avatar corresponding to the avatar number included in the message list. Specifically, first, the avatar name and the avatar image file name are extracted from the avatar management table. Next, an avatar image specified by the extracted avatar image file name is acquired from the storage unit of the message management server 15. The message management server 15 transmits each acquired avatar name and avatar image to the group management server 12 (step S133). The group management server 12 transmits each received avatar name and avatar image to the service server 11 (step S134).

  Next, the service server 11 requests the group management server 12 for information regarding the terminal corresponding to the terminal number included in the message list (step S135). At that time, the service server 11 transmits the message list to the group management server 12. In response to this request, the group management server 12 requests the terminal management server 13 for information relating to the terminal corresponding to the terminal number included in the message list (step S136). At that time, the group management server 12 transmits the message list to the terminal management server 13.

  In response to this request, the terminal management server 13 acquires information about the terminal corresponding to the terminal number included in the message list. Specifically, the terminal name is extracted from the terminal management table. The terminal management server 13 transmits the extracted terminal names to the group management server 12 (step S137). The group management server 12 transmits the received terminal names to the service server 11 (step S138).

  Referring to FIG. 19 again, when receiving the avatar information and the terminal information, the service server 11 transmits a message display screen to the portable terminal 22 (step S130). At that time, the service server 11 generates a message display screen including the content of the message, the avatar image corresponding to the message, and the terminal name corresponding to the message in each message display field in the screen, Transmit to the terminal 22. The layout of this screen is the same as that shown in FIG. The portable terminal 22 displays the received screen. As a result, a screen including the latest message transmitted from the administrator terminal 21 is displayed on the mobile terminal 22. In other words, the transmission of the message from the administrator terminal 21 to the portable terminal 22 is completed.

(Advantages of this embodiment)
As described above, according to the present embodiment, a message is transmitted while identifying a user who is a sender by using an avatar in an SNS in which a terminal is registered for a group instead of a user. be able to. Accordingly, it is possible to exchange messages between users while the users themselves are not registered.

[Embodiment 5]
A fifth embodiment according to the present invention will be described below. In addition, about the same member as the 1st-4th embodiment mentioned above, the detailed description is abbreviate | omitted by attaching | subjecting the same code | symbol.

  In the present embodiment, a processing flow of the SNS system 10 when a message is transmitted from the television 24 to another terminal registered in the group G1 will be described in detail. Hereinafter, an example in which the mobile terminal 22 receives a message transmitted from the television 24 will be described.

  First, the television 24 activates a dedicated application for using the SNS system 10. When the application is activated, the administrator terminal 21 requests the service server 11 for a screen including the latest message. In response to this, the service server 11 transmits a message display screen to the television 24. The television 24 displays a message display screen and a television program as shown in FIG. FIG. 24A shows a screen including the latest message.

(Message input screen)
When transmitting a message from the television 24 in the SNS system 10, first, the television 24 needs to acquire and display a message input screen from the service server 11. Hereinafter, a procedure for acquiring the message input screen will be described with reference to FIG. FIG. 23 is a flowchart showing the flow of processing in the SNS system 10 when the television 24 acquires a message input screen.

  The screen shown in FIG. 24A includes an item K41 labeled “message input”. The user of the television 24 selects the item K41. In response to this selection, the television 24 requests the service server 11 for a screen for inputting a message (step S101). At that time, the television 24 transmits the terminal number of the television 24 and the group number of the group G1 to the service server 11.

  When the service server 11 receives the terminal number of the television 24 and the group number of the group G1, the service server 11 requests the group management server 12 to confirm whether these numbers have been registered (step S142). At that time, the service server 11 transmits the terminal number of the television 24 and the group number of the group G1 to the group management server 12.

(Confirmation of TV 24 registration)
The group management server 12 searches the group management table using the received terminal number and group number. Thereby, it is confirmed whether or not the television 24 is registered in the group G1. If it can be confirmed, it requests the avatar management server 14 to provide the avatar list of the group G1 (step S143).

  In response to this request, the avatar management server 14 generates an avatar list with reference to the avatar management table for the group G1. The procedure is as follows. First, avatar numbers and avatar names of all avatars included in the avatar management table are extracted. Next, all avatar image file names included in the avatar management table are extracted, and all avatar images specified by these file names are acquired. Then, an avatar list is generated by associating all acquired avatar images with all the extracted avatar numbers and avatar names. In the generated avatar list, for each avatar, an avatar number, an avatar name, and an avatar image are associated with each other.

  The avatar management server 14 transmits the generated avatar list to the group management server 12 (step S144). The group management server 12 transmits the received avatar list to the service server 11 (step S145).

  The television 24 is a terminal shared and used by each user belonging to the group G1. Therefore, it is more likely that a different user uses the television 24 to transmit a message each time than the same user continuously uses the television 24 for message transmission.

  Therefore, in this embodiment, the SNS system 10 causes the user of the television 24 to select an avatar every time a message is transmitted. In order to realize this, when receiving the avatar list from the portable terminal 22, the service server 11 transmits an avatar selection screen to the television 24 (step S146). At that time, the service server 11 transmits the avatar list in association with the avatar selection screen. The television 24 displays the received screen and the television program at the same time. Thereby, the screen shown in FIG. 24B is displayed. FIG. 24B is a diagram illustrating a state in which the avatar selection screen and the television program are displayed at the same time.

  The avatar selection screen shown in FIG. 24B is essentially the same as the avatar selection screen shown in FIG. However, when displaying the avatar selection screen, the television 24 displays the avatar image currently selected in the avatar selection field at the top of the screen. Furthermore, all avatar images that can be used by each terminal registered in the group G1 included in the avatar list are displayed in the center of the screen.

  The user of the television 24 selects a desired one avatar image from the avatar selection field. Then, the selected avatar image is highlighted. After selecting the avatar image, the user selects the item K42 labeled “Determine”. Thereby, selection of an avatar is decided. In response, the television 24 notifies the service server 11 that an avatar has been selected (step S147). At that time, the television 24 transmits the avatar number of the avatar selected by the user of the television 24 and the terminal number of the television 24 to the service server 11.

  Upon receiving this notification, the service server 11 transmits a message input screen to the television 24 (step S148). At that time, the avatar number of the avatar selected by the user of the television 24 and the avatar list are transmitted to the message input screen in association with each other.

  The television 24 displays the received message input screen and the television program at the same time. As a result, the screen shown in FIG. 24C is displayed. FIG. 24C is a diagram illustrating a state in which the message input screen and the television program are displayed at the same time on the television 24. As shown in this figure, the avatar image selected by the user of the television 24 is displayed at the top of the message input screen. Therefore, when a message is sent through this screen, the message is treated as being transmitted using the displayed avatar image.

  The message input screen includes an input field I21 for inputting text and a selection field I22 for selecting a fixed sentence. The user of the television 24 inputs a desired text as a message in the input field I21. The input interface of the television 24 is a remote control, and it is inconvenient to input characters using this. Therefore, the user of the television 24 can input a message by selecting a desired fixed phrase from the selection I21. Thereby, although it is limited to a fixed sentence, a message can be input easily.

  When the message input is completed, the user of the television 24 selects the item K43 labeled "Send". Thereby, the television 24 transmits the message input by the user to the service server 11. Note that the flow of a series of processes for realizing the message input and transmission described above is the same as the flow of the series of processes shown in FIG. 19, and thus detailed description thereof is omitted.

  In the present embodiment, the television 24 may use the avatar that the television 24 last used when transmitting a message, instead of causing the user to select an avatar from the avatar list. That is, after the user selects the item K51 of FIG. 24A, the television 24 displays the screen of FIG. 24C instead of FIG. 24B. At that time, the avatar displayed on the screen is displayed on the television 24. May be the last avatar used when sending the message. If it does in this way, when the same user transmits a message continuously using television 24, the effort which a user chooses an avatar can be eliminated.

(advantage)
As described above, in the present embodiment, a message can be transmitted from the television 24 that is a shared terminal to each terminal belonging to the group G1. At that time, by making the user select an avatar before the user inputs a message, an avatar used by another user in the past is prevented from being used by mistake. Thereby, it is realizable that each user transmits a message using a correct avatar.

  Further, a user who transmits a message using the television 24 does not need to log in to the SNS system 10. Therefore, the message can be easily transmitted through the television 24 without feeling troublesome to log in.

(Advantages of this embodiment)
As described above, according to the present embodiment, a message is transmitted while identifying a user who is a sender by using an avatar in an SNS in which a shared terminal is registered for a group instead of a user. can do. Therefore, other users can know exactly who the sender of the message transmitted from the shared terminal is.

  Further, since the shared terminal itself is registered in the group, it is possible to prevent a message from the shared terminal from being erroneously transmitted to a terminal in another group. That is, it is possible to realize message transmission from the shared terminal while ensuring security.

[Server configuration]
As described above, in each embodiment, in the SNS system 10, a plurality of servers represented by the service server 11 operate in cooperation with each other, thereby providing the SNS to the user. However, this is only an example. Each server may be integrated with each other. For example, the SNS system 10 is also realized by one SNS server having all the individual functional blocks (functional means) for realizing the functions of the individual servers communicating with each terminal such as the administrator terminal 21. It is possible.

  Or it is good also considering the server provided with the functional block of the combination easy to manage for the administrator of SNS system 10 among the individual functional blocks as a component of SNS system 10. For example, the terminal management server 13 and the administrator terminal management server 16 both have relatively low processing loads in the SNS system 10 and manage information in a manner similar to each other. One server that integrates two servers may be a component of the SNS system 10.

[Embodiment 6]
In one SNS server including each server constituting the SNS system 10 as a functional block, each control block of the SNS server is realized by a logic circuit (hardware) formed in an integrated circuit (IC chip) or the like. Alternatively, it may be realized by software using a CPU (Central Processing Unit).

  In the latter case, the SNS server includes a CPU that executes instructions of a program that is software that implements each function, a ROM (Read Only Memory) or a storage in which the program and various data are recorded so as to be readable by the computer (or CPU). An apparatus (these are referred to as “recording media”), a RAM (Random Access Memory) for expanding the program, and the like. And the objective of this invention is achieved when a computer (or CPU) reads the said program from the said recording medium and runs it. As the recording medium, a “non-temporary tangible medium” such as a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, or the like can be used. The program may be supplied to the computer via an arbitrary transmission medium (such as a communication network or a broadcast wave) that can transmit the program. The present invention can also be realized in the form of a data signal embedded in a carrier wave in which the program is embodied by electronic transmission.

[Summary]
In order to solve the above problems, a message transmission method according to the present invention provides:
A message transmission method in which a terminal transmits a message to a management server of a message exchange system,
In the management server, the terminal confirms whether or not the terminal is a terminal registered in a specific group in the message exchange system. A terminal confirmation step that permits transmission of the message to the management server;
An input step in which the user inputs the message in the terminal;
In the terminal, a transmission step of transmitting the input message to the management server;
The management server includes a receiving step for receiving the transmitted message.

  According to the above configuration, terminals, not users, are registered in the message exchange system group. Therefore, the user who uses the message exchange system does not need to manage his / her account information. Thereby, even a person with low IT literacy can use the message exchange system without resistance.

In the message transmission method according to the present invention,
The terminal further comprises an acquisition step of acquiring symbol information symbolizing a sender of the message,
Preferably, in the transmission step, the message is transmitted to the management server in association with the message and the symbol information.

  According to the above configuration, in a message exchange system in which a terminal is registered for a group, not a user, a message is transmitted while identifying a user who is a sender by utilizing symbol information such as an avatar. can do. Therefore, the user can exchange messages while the system is not registered.

In the message transmission method according to the present invention,
The terminal further includes a selection step in which the user selects any one of the plurality of different symbol information.
In the acquisition step, it is preferable to select the symbol information selected by the user.

  According to said structure, the user can select desired symbol information and can transmit a message. Therefore, symbol information suitable for each message can be used properly. In addition, a plurality of users can share the same terminal, and a message can be transmitted in such a way that symbol information is used for each user.

In the message transmission method according to the present invention,
The message exchange system further includes a symbol information management server that holds the plurality of symbol information.
Preferably, the method further includes a providing step of providing the plurality of symbol information to the terminal from the symbol information management server.

  According to the above configuration, since the latest symbol information can be provided from the symbol information management server to the terminal, it is possible to prevent a message with old symbol information from being transmitted by mistake.

In the message transmission method according to the present invention,
A storage step of storing the symbol information associated with a message transmitted by the terminal in the past;
In the acquisition step, the stored symbol information is preferably acquired.

  According to the above configuration, it is possible to eliminate the trouble of selecting the same symbol information every time the same user repeatedly transmits a message.

In the message transmission method according to the present invention,
The symbol information is preferably an image representing the user.

  According to the above configuration, other users can easily know who the sender of the message is.

In order to solve the above problem, a message receiving method according to the present invention provides:
A message receiving method in which a terminal accesses a management server of a message exchange system and receives a message,
In the management server, a terminal confirmation step for confirming whether or not the terminal is a terminal registered in a specific group in the message exchange system;
In the management server, when it is confirmed that the terminal is a terminal registered in a specific group in the message exchange system, a transmission step of transmitting a message to the terminal;
A receiving step for receiving the message at the terminal;
The terminal includes a display step for displaying the received message.

  According to the above configuration, terminals, not users, are registered in the message exchange system group. Therefore, the user who uses the message exchange system does not need to manage his / her account information. Thereby, even a person with low IT literacy can use the message exchange system without resistance.

In the message receiving method according to the present invention, further,
The management server further comprises an acquisition step of acquiring symbol information that symbolizes a sender of the message,
In the transmission step, the symbol information is transmitted,
In the reception step, the symbol information is received,
In the display step, the message and the symbol information are preferably displayed in association with each other.

  According to said structure, the user of the terminal which received the message can know who the sender of a message is.

In order to solve the above problem, the management server according to the present invention provides:
A management server that receives messages from a terminal,
The terminal confirms whether or not the terminal is a terminal registered in a specific group in the message exchange system, and if the terminal is confirmed to be a registered terminal, the message from the terminal to the management server A device verification means that allows transmission of
Receiving means for receiving the message transmitted from the terminal.

  According to the above configuration, even a person with low IT literacy can realize a message exchange system without resistance.

In order to solve the above problems, another management server according to the present invention
A management server that sends messages to the terminal,
Terminal confirmation means for confirming whether the terminal is a terminal registered in a specific group in the message exchange system;
When the terminal is confirmed to be a terminal registered in a specific group in the message exchange system, it is characterized by comprising transmission means for transmitting a message to the terminal.

  According to the above configuration, even a person with low IT literacy can realize a message exchange system without resistance.

In order to solve the above problems, the message exchange system according to the present invention provides:
A message exchange system comprising a terminal and a management server, wherein the terminal transmits a message to the management server,
The management server
Check if the terminal is a terminal registered in a specific group in the message exchange system, and if it can be confirmed that the terminal is a registered terminal, the terminal from the terminal to the management server A device verification means that allows sending messages;
Receiving means for receiving the message transmitted from the terminal,
The terminal
Input means for allowing the user to input the message;
And a transmission means for transmitting the inputted message to the management server.

  According to the above configuration, even a person with low IT literacy can realize a message exchange system without resistance.

In order to solve the above problem, another message exchange system according to the present invention provides:
A message exchange system comprising a terminal and a management server, wherein the terminal accesses the management server and receives a message,
The management server
Terminal confirmation means for confirming whether or not the terminal is a terminal registered in a specific group in the message exchange system;
A transmission means for transmitting a message to the terminal when the terminal is confirmed to be a terminal registered in the specific group in the message exchange system;
The terminal
Receiving means for receiving the message;
And a display means for displaying the received message.

  According to said structure, even if it is a person with low IT literacy, the message exchange system which can be utilized without resistance is realizable.

  The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope shown in the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments. Is also included in the technical scope of the present invention. Furthermore, a new technical feature can be formed by combining the technical means disclosed in each embodiment.

  The present invention can be used in a social network service system capable of sharing a message between terminals.

10 SNS system 11 Service server (management server)
12 Group management server (management server, terminal confirmation means, group construction means)
13 Terminal management server (group construction means)
14 Avatar management server (management server)
15 Message management server (management server, transmission means, reception means)
16 Administrator terminal management server (management server)
17a Application distribution server (management server)
17b Terminal identification information distribution server 21 Mobile terminal (transmission means, reception means, display means)
22 Mobile terminal (transmission means, reception means, display means)
23 Mobile terminal (transmission means, reception means, display means)
24 TV (transmission means, reception means, display means)
25 Vacuum cleaner (transmitting means, receiving means, display means)
31 Internet A7001-A7005 Avatar number D7001-D7005 Terminal number

Claims (12)

A message transmission method in which a terminal transmits a message to a management server of a message exchange system,
In the management server, the terminal confirms whether or not the terminal is a terminal registered in a specific group in the message exchange system. A terminal confirmation step that permits transmission of the message to the management server;
An input step for allowing the user to input the message in the terminal;
In the terminal, a transmission step of transmitting the input message to the management server;
A message transmitting method comprising: a receiving step for receiving the transmitted message in the management server. The terminal further comprises an acquisition step of acquiring symbol information symbolizing a sender of the message,
2. The message transmission method according to claim 1, wherein in the transmission step, the message is transmitted to the management server in association with the message and the symbol information. The terminal further includes a selection step in which the user selects any one of the plurality of different symbol information.
3. The message transmission method according to claim 2, wherein in the obtaining step, the symbol information selected by the user is selected. The message exchange system further includes a symbol information management server that holds the plurality of symbol information.
4. The message transmission method according to claim 3, further comprising a providing step of providing the plurality of symbol information to the terminal from the symbol information management server. A storage step of storing the symbol information associated with a message transmitted by the terminal in the past;
3. The message transmission method according to claim 2, wherein in the obtaining step, the stored symbol information is obtained.   The message transmission method according to claim 2, wherein the symbol information is an image representing the caller. A message receiving method in which a terminal accesses a management server of a message exchange system and receives a message,
In the management server, a terminal confirmation step for confirming whether or not the terminal is a terminal registered in a specific group in the message exchange system;
In the management server, when it is confirmed that the terminal is a terminal registered in a specific group in the message exchange system, a transmission step of transmitting a message to the terminal;
A receiving step for receiving the message at the terminal;
A message receiving method comprising: a display step for displaying the received message in the terminal. The management server further comprises an acquisition step of acquiring symbol information that symbolizes a sender of the message,
In the transmission step, the symbol information is transmitted,
In the reception step, the symbol information is received,
8. The message receiving method according to claim 7, wherein in the display step, the message and the symbol information are displayed in association with each other. A management server that receives messages from a terminal,
The terminal confirms whether or not the terminal is a terminal registered in a specific group in the message exchange system, and if the terminal is confirmed to be a registered terminal, the message from the terminal to the management server A device verification means that allows transmission of
A management server comprising receiving means for receiving the message transmitted from the terminal. A management server that sends messages to the terminal,
Terminal confirmation means for confirming whether the terminal is a terminal registered in a specific group in the message exchange system;
A management server comprising: transmission means for transmitting a message to the terminal when the terminal is confirmed to be a terminal registered in a specific group in the message exchange system. A message exchange system comprising a terminal and a management server, wherein the terminal transmits a message to the management server,
The management server
Check if the terminal is a terminal registered in a specific group in the message exchange system, and if it can be confirmed that the terminal is a registered terminal, the terminal from the terminal to the management server A device verification means that allows sending messages;
Receiving means for receiving the message transmitted from the terminal,
The terminal
Input means for allowing the user to input the message;
A message exchange system comprising: a transmission means for transmitting the inputted message to the management server. A message exchange system comprising a terminal and a management server, wherein the terminal accesses the management server and receives a message,
The management server
Terminal confirmation means for confirming whether or not the terminal is a terminal registered in a specific group in the message exchange system;
A transmission means for transmitting a message to the terminal when the terminal is confirmed to be a terminal registered in the specific group in the message exchange system;
The terminal
Receiving means for receiving the message;
A message exchange system comprising display means for displaying the received message.

Images