JP6575486B2 - Server, message group management system, and message group management method - Google Patents

Description

  The present invention relates to a server that relays messages. The present invention also relates to a message group management system including the server and communication devices. Further, the present invention relates to a message group management method.

  An application for exchanging messages may be installed in a communication device. For example, the communication device is a PC, a mobile phone, a smartphone, or a tablet computer. An application (software) that realizes real-time (instantaneous) message exchange may be referred to as an instant messenger.

  A technique relating to instant messaging is described in Patent Document 1. Specifically, in Patent Document 1, a user request for generating a topic in a user group is received from the initiating user, a topic and a corresponding topic group are generated in the user group, and a user who joins the topic Receive requests from requesting users, add requesting users to the corresponding topic group, receive messages related to the topic from participating users in the topic group, and send messages to users in the topic group A method is described. By this method, interference from irrelevant topics is reduced and the amount of unnecessary messages sent from the server is reduced (see Patent Document 1: Claim 1, paragraph [0015], etc.).

Special table 2010-533906 gazette

  There are a plurality of applications (software) that realize the instant message function (chat function). For example, there are Skype, Facebook Messenger, and LINE. When using these services, a user installs an application (software) in a communication device owned by the user. Application distributors install servers. The server relays messages between clients (communication devices). This server may be referred to as an instant message server. Instant messages can be exchanged using communication devices, applications, and servers. Networks such as the Internet are often used for communication paths.

  Some applications that implement instant messaging can use the group function. For example, the owner creates a new group. Anyone can create a group. The newly created group is registered on the server. You can also add members to the group. The server receives an instant message sent by one member of the group. The server simultaneously delivers received instant messages to other members. As a result, messages can be exchanged so as to have a conversation among a plurality of members. Therefore, the group function is sometimes referred to as group chat.

  A user can belong to multiple groups. Then, there may be a case where a plurality of groups having some members in common and talking about the same topic are created. If these groups can be put together, the group will be activated. However, at present, groups cannot be easily organized. In order to summarize, for example, it is necessary for someone to confirm all the members of each group and to create a new group on the communication device. In addition, it may take a lot of time to delete a group. Thus, there is a problem that group management is not easy.

  The technique described in Patent Document 1 only allows a topic group to be created in the group. It is not a group. Therefore, the above problem cannot be solved.

  In view of the above-described problems of the prior art, the present invention handles similar topics and makes it possible to easily manage a plurality of groups including similar members.

  In order to solve the above problem, a server according to claim 1 includes a communication unit, a storage unit, and a control unit. The communication unit is connected to a communication network, receives a message transmitted from a communication device of a member belonging to a group, and transmits the received message to communication devices of other members belonging to the same group. The storage unit stores the exchanged message as a message log. The control unit extracts, as an extraction group, a plurality of groups having the same members over a predetermined extraction condition. The control unit recognizes the topic of each extraction group based on the message log of each extraction group. The control unit determines whether to submit a merge proposal to the extraction group based on the recognized topic. When it is determined that the merge proposal is to be issued, the control unit causes the communication unit to transmit a merge proposal related to whether or not to merge the extraction group toward a communication device of a member belonging to each of the extraction groups. When it determines with not giving the said merge proposal, the said control part does not make the said merge proposal transmit from the said communication part. The communication unit receives merge permission or merge rejection from the communication device that has transmitted the merge proposal. The merge permission is an answer indicating that the merge is permitted. The merge rejection is a reply that the merge is not permitted. When receiving the merge permission from the communication devices of the members belonging to the extraction group, the control unit generates a merge group including all members of each extraction group as members.

  According to the present invention, it is possible to easily merge similar members and groups dealing with similar topics.

It is explanatory drawing which shows an example of the management system of the message group which concerns on embodiment. An example of the message exchange in the group in the communication apparatus which concerns on embodiment is shown. It is a figure which shows an example of the group which the server which concerns on embodiment extracted. It is a flowchart which shows an example of the flow of determination of whether to give the merge proposal which concerns on embodiment. It is a figure which shows an example of the term dictionary which concerns on embodiment. It is an example of the topic count number according to the embodiment. It is a flowchart which shows an example of the flow of the production | generation of the merge group which concerns on embodiment. It is a flowchart which shows an example of the flow of determination of the merge group which concerns on embodiment. It is a flowchart which shows an example of the flow of deletion of the inactive group in the server which concerns on embodiment.

  Hereinafter, embodiments of the present invention will be described with reference to FIGS. In this description, a message management system 100 (corresponding to a message group management system) including the server 1 and the communication device 2 will be described as an example. However, each element such as configuration and arrangement described in this embodiment does not limit the scope of the invention and is merely an illustrative example.

(Message management system 100)
First, an example of the message management system 100 according to the embodiment will be described with reference to FIG. FIG. 1 is an explanatory diagram illustrating an example of a message management system 100 according to the embodiment.

  The message management system 100 includes a server 1 and a communication device 2. The server 1 is an instant message server 1. The server 1 provides an instant message function. An image forming apparatus may be used as the server 1. Therefore, the server 1 may include a printing unit 1a that performs printing based on image data.

  The communication device 2 is a device that can communicate with the server 1 via the communication network 200. For example, a smartphone, a PC, a tablet computer, and a mobile phone can be used as the communication device 2. Each user possesses the communication device 2. In the following description, an example in which a smartphone is used as the communication device 2 will be described. The server 1 can communicate with a plurality of communication devices 2. For convenience, FIG. 1 shows only one communication device 2.

  An IM application 2a for using an instant message is installed in the communication device 2. IM is an abbreviation for Instant Messenger. The communication device 2 is a client that receives a service from the server 1. The user registers account information 13 (user information) in the server 1 using the communication device 2, application, and communication network 200. Since messages are exchanged, the message management system 100 includes a plurality of communication devices 2. In FIG. 1, for convenience, only one communication device 2 is illustrated.

  The server 1 includes a control unit 10, a communication unit 11, and a storage unit 12. The control unit 10 is a substrate that controls the server 1. The control unit 10 controls the communication unit 11 and the storage unit 12 based on the data stored in the storage unit 12. The control unit 10 includes a server CPU 10a for calculation and control. The control unit 10 processes a request from the communication device 2 and provides a processing result to any one of the communication devices 2.

  The communication unit 11 is connected to a communication network 200 (network). The communication unit 11 includes communication hardware. For example, the communication unit 11 includes a socket and a communication control circuit. The communication unit 11 receives a message transmitted from the communication device 2 via the communication network 200. The communication unit 11 transmits the received message to the destination (other communication device 2) via the communication network 200. The storage unit 12 is a combination of storage devices such as ROM, RAM, and HDD. The storage unit 12 stores various data. For example, the storage unit 12 stores a control program, control data, and setting data for the server 1. The storage unit 12 stores an account (account information 13) of each user. The storage unit 12 stores the exchanged message as a message log 14.

  Next, the communication device 2 will be described. The communication device 2 includes a processing unit 20, a memory unit 21, a display panel 22, a touch panel 23, an imaging unit 24, an audio processing unit 25, a microphone 25a, a reproduction processing unit 26, a speaker 26a, and a wireless communication unit 27.

  The processing unit 20 is a circuit that controls the operation of the communication device 2. As the processing unit 20, an integrated circuit in which a CPU and an image processing circuit are integrated into one chip can be used. The processing unit 20 controls the operation of the communication device 2 based on the OS, program, application, and data.

  The memory unit 21 includes a ROM, a RAM, and a flash memory. The memory unit 21 stores a control program, control data, image data, and IM application 2a for the communication device 2. The processing unit 20 controls each unit of the communication device 2 according to the control program and control data stored in the memory unit 21 and the IM application 2a. The user performs an activation operation of the IM application 2a using the touch panel 23. When the activation operation is performed, the processing unit 20 executes the IM application 2a.

  The display panel 22 displays various information according to the request from the processing unit 20. The display panel 22 is a liquid crystal panel or an organic EL panel. The touch panel 23 is connected to the processing unit 20. The processing unit 20 recognizes the touch position based on the output of the touch panel 23. The processing unit 20 recognizes the touched operation image among the operation images displayed on the display panel 22. The operation image is, for example, an icon, a button, or a key.

  The imaging unit 24 is a camera provided in the communication device 2. The sound processing unit 25 performs signal processing on the sound input from the microphone 25a. The reproduction processing unit 26 causes the speaker 26a to reproduce the audio data received by the wireless communication unit 27.

  The wireless communication unit 27 includes an antenna and a communication circuit. The wireless communication unit 27 can access a data communication line or a telephone line provided by the mobile communication carrier in accordance with an instruction from the processing unit 20. The wireless communication unit 27 can access the server 1 via the communication network 200. The wireless communication unit 27 can exchange data with the server 1.

(Message exchange in group)
Next, an example of message exchange in a group in the message management system 100 according to the embodiment will be described with reference to FIG. FIG. 2 shows an example of message exchange in a group in the communication device 2 according to the embodiment.

  Messages can be exchanged by starting the IM application 2a on the communication device 2. FIG. 2 shows an example of the display panel 22 during activation of the IM application 2a. A message input area F1 is provided below the screen. A send button B1 is provided in the message input area F1. When an area outside the send button B1 in the message input area F1 is touched, the processing unit 20 displays a software keyboard (not shown). The user can create a message to be input and sent to the software keyboard. When the transmission button B1 is touched, the processing unit 20 causes the wireless communication unit 27 to transmit a message input toward the server 1.

  In the message management system 100, a group function is provided. FIG. 2 shows an example of a state in which the group function is used in the IM application 2a. Each user can create a group by operating the IM application 2a. The creator of a group becomes the owner of that group. For example, a group creator inputs information necessary for group creation to the communication device 2 (touch panel 23). The input information is the group name and group members. The operation result is transmitted from the communication device 2 to the server 1. The server 1 stores the received information as group data 15 (see FIG. 1). Thereby, the server 1 (control part 10) can recognize which user belongs to which group.

  When a message based on the group function is received, the server 1 transmits the message to the communication devices 2 other than the sender at the same time. That is, the communication unit 11 receives a message transmitted from the member communication device 2 belonging to the group. And the communication part 11 transmits the received message to the communication apparatus 2 of the other member which belongs to the same group.

  FIG. 2 shows an example of message exchange using the group function. The group name of the group illustrated in FIG. 2 is ZZZZ. The communication device 2 displays each member's message based on a certain format. FIG. 2 shows an example in which A, B, C, and D speak as members. FIG. 2 shows an example in which the message transmission time, the name of the member who transmitted the message, and the message content (text) are displayed in this order. The display format varies depending on the application. For example, message text may be placed in a balloon. The storage unit 12 of the server 1 also stores messages exchanged by the group function as a message log 14. The storage unit 12 stores each message as a log in units of groups.

(Group extraction)
Next, a group extraction process of the server 1 according to the embodiment will be described with reference to FIG. FIG. 3 is a diagram illustrating an example of groups extracted by the server 1 according to the embodiment.

  The server 1 accepts group registration. Information on the newly created group (member, owner, group name, etc.) is transmitted from the communication device 2 to the server 1. The group information is registered in the storage unit 12 of the server. As the number of groups increases, the burden on the server 1 may increase. Generally, the group owner has the authority to dissolve the group. The group is retained unless dissolved. Some groups have not exchanged messages for a long time. If the number of groups can be effectively reduced, the burden on the server 1 may be reduced.

  If a plurality of groups are merged and the original group is dissolved (deleted), the number of groups can be progressively reduced. Therefore, the server 1 extracts groups that match certain conditions (extraction process). The control unit 10 extracts a plurality of groups having the same member over a predetermined extraction condition. The extraction conditions can be determined as appropriate. In this embodiment, the extraction condition is 50%. That is, the extraction condition is that at least half of the members belonging to each group are common. Hereinafter, the extracted group is referred to as an extraction group.

  Note that the control unit 10 periodically performs extraction processing. The period can be arbitrarily determined. For example, a cycle such as several days, one week, more than ten days, two weeks, three weeks, one month, several months, half a year, and one year can be defined. When a predetermined period has elapsed since the extraction process was performed first, the control unit 10 starts the extraction process. Further, when the server 1 (communication unit 11) receives an instruction from the computer of the server 1 administrator, the processing unit 20 may start the extraction process.

  FIG. 3 shows an example of extraction by the server 1. In FIG. 3, the server 1 extracts the first group and the second group. The members of the first group (communication device 2) are A, B, C, D, and E. The owner of the first group is A. There are six members (F, B, C, D, G, H) of the second group (communication device 2). The owner of the second group is F.

  In the example of FIG. 3, among the members of the first group and the second group, B, C, and D belong to both groups. In one group (first group), the number of common members is equal to or greater than the extraction condition. In the other group (second group), the number of common members is equal to or greater than the extraction condition. The server 1 extracts the first group and the second group. The first group and the second group are treated as extraction groups. When a group is extracted, a determination is made whether to submit a merge proposal.

(Determining whether to submit a merge proposal)
Next, an example of a flow for determining whether or not to submit a merge proposal according to the embodiment will be described with reference to FIGS. 2 and 4 to 6. FIG. 4 is a flowchart illustrating an example of a flow for determining whether or not to submit a merge proposal according to the embodiment. FIG. 5 is a diagram illustrating an example of the term dictionary 16 according to the embodiment. FIG. 6 is an example of topic counts according to the embodiment.

  First, the control unit 10 prepares a message log 14 for each extraction group (step # 11). In the example of FIG. 3, the control unit 10 prepares a first group message log 14 and a second group message log 14. The control unit 10 reads the message log 14 of each extraction group stored in the HDD of the storage unit 12 into the RAM of the storage unit 12. In this case, the control unit 10 may prepare all message logs 14 of each extraction group.

  If there are too many message logs 14, the amount of data processing increases. Therefore, the control unit 10 may prepare message logs 14 for a predetermined number of days for each extraction group. The predetermined number of days can be determined as appropriate. For example, the predetermined number of days may be about several days to one month. In this case, the control unit 10 prepares a message log 14 for a predetermined number of days retroactively from the latest message.

  The control unit 10 divides the message log 14 of each extraction group into a plurality of sessions (step # 12). The control unit 10 divides a plurality of messages having a common topic into one session. The topic often changes when the time interval between messages opens. Therefore, the control unit 10 may set a message having a time interval longer than a predetermined first time as another session. The first time can be determined as appropriate. The first time can be 10 minutes to 1 hour. For example, the first time may be 40 minutes. In this case, the control unit 10 provides a session boundary at a position where the message interval is 40 minutes or more.

  Usually, when talking about a certain topic, messages are exchanged in a short time. Therefore, the control unit 10 may collect messages within a predetermined second time in the same session. For example, the second time may be about 10 minutes. In this case, the control unit 10 initially handles one message as one session. And based on the time interval of a message, the control part 10 merges a session.

  Based on these criteria, the control unit 10 divides the message log 14 of each extraction group into a plurality of sessions. In the message exchange shown in FIG. 2, a message from 09:00:00 A to 09:02 C is taken as one session. In addition, a 10:26 D message is taken as one session from a 10:20 C message.

  Next, the control unit 10 recognizes keywords included in the session based on the term dictionary 16 (step # 13). The storage unit 12 stores a term dictionary 16 (see FIG. 1). A topic is defined in the term dictionary 16. In the term dictionary 16, keywords belonging to the topic are defined. FIG. 5 shows an example of the term dictionary 16. In the term dictionary 16, a plurality of topics (categories) are defined. FIG. 5 shows a term dictionary 16 in which topics such as games, sports, entertainment, travel, hobbies, and food are defined. More or less topics may be defined in the term dictionary 16.

  A plurality of keywords are defined for one topic. FIG. 5 shows an example of keywords defined for game topics. The leftmost table in FIG. 5 shows an example of a topic (category). The right side of the topic table is a table showing an example of keywords included in the topic. The numbers in the leftmost column of a table showing an example of keywords are numbers (indexes). In instant messages, abbreviated words are easily used for convenience of input. Therefore, a plurality of synonyms may be defined as keywords for one index. There may be three or more synonyms. In FIG. 5, synonyms are defined side by side in the horizontal direction.

  Then, the control unit 10 determines the topic of the session based on the recognized keyword and the term dictionary 16 (step # 13). The control unit 10 determines that the topic corresponding to the keyword included in the session is the topic of the session. When the session does not include any keyword defined in the term dictionary 16, the control unit 10 determines that there is no topic for the session.

  The message exchange shown in FIG. 2 will be described as an example. In the session from message A at 09:00 in FIG. 2 to message C at 09:02, keywords of the topic of the game are included. Specifically, “play”, “players”, and “graphics” are included. Therefore, the control unit 10 determines that the topic of the session from the message A at 09:00 to the message C at 09:02 is a game. Further, the term dictionary 16 of the embodiment does not include any word as a keyword for each word from a 10:20 C message to a 10:26 D message. In this case, the control unit 10 determines that there is no topic.

  In conversation, the topic may fly. Therefore, when a plurality of keywords of different topics are included in one session, the control unit 10 may determine a plurality of topics as the topics of the session for one session. On the other hand, the control unit 10 may determine only one topic per session. When keywords of different topics are included in one session, the control unit 10 determines the topic having the largest number of keywords as the topic of the session. Further, the control unit 10 may not determine a topic having a number of keywords equal to or less than a predetermined number as a session topic. For example, the predetermined number can be 2-3.

  Based on the topic of each session, the control unit 10 determines whether or not to submit a merge proposal to each extraction group (step # 14). The merge proposal is a notification for confirming whether or not each extraction group is allowed to merge. When the frequent topics of each extraction group are the same, the control unit 10 determines that a merge proposal is to be issued to each extraction group.

  The control unit 10 aggregates the number of times determined as the topic of the session (number of determinations) for each topic and for each extraction group. In other words, the control unit 10 sums up the number of determinations for each topic for each extraction group. For each topic, the control unit 10 obtains the ratio of the number of determinations of the topic to the total number of determinations. The control unit 10 determines that a topic whose calculated ratio is equal to or more than a predetermined reference value is a frequent topic. The reference value can be determined as appropriate. For example, the reference value can be 50%.

  When the frequent topics are the same in each extraction group, the control unit 10 determines that a merge proposal is to be issued to each extraction group. When there is no frequent topic, the control unit 10 determines that no merge proposal is given to each extraction group. Moreover, when a frequent topic is not common in each extraction group, the control part 10 determines with not giving a merge proposal to an extraction group.

  FIG. 5 shows an example of the total number of determinations. In the first group, the number of determined topics is 20 in all sessions. In the second group, it is 40. In the first group, the number of times that the topic is determined to be a game (number of sessions) is 11. Therefore, the ratio is 11/20 = 55%. In the second group, the number of times that the topic is determined to be a game (number of sessions) is 25. Therefore, the ratio is 25/40 = 62.5%. Frequent topics are common in the first group and the second group. In this case, the control unit 10 determines to submit a merge proposal to the first group and the second group.

  When it is determined that a merge proposal is to be issued (Yes in Step # 15), the control unit 10 causes the communication unit 11 to transmit the merge proposal to the member communication devices 2 belonging to each extraction group (Step # 16). When it is determined that no merge proposal is to be issued (No in step # 15), the control unit 10 does not cause the communication unit 11 to transmit the merge proposal (step # 17). After step # 16 or step # 17, this flow ends (end). Server 1 waits for a reply from the destination of the merge proposal.

  The member proposed to be merged returns to the server 1 whether to merge or not. In other words, the communication device 2 that has received the merge proposal from the server 1 transmits merge permission or rejection to the server 1. When there is no response from the notifier within a predetermined time after transmitting the merge proposal, the server 1 may consider that the merge rejection or merge permission response has been received. The predetermined period can be several days, for example.

  The control unit 10 may cause the communication unit 11 to transmit the merge proposal to the communication devices 2 of all the members of each extraction group determined to issue the merge proposal. Moreover, the control part 10 may transmit a merge proposal only to the communication apparatus 2 of the owner of each extraction group determined to give a merge proposal. After transmitting to the owner only, when receiving a request for transmission of the merge proposal to all members from the owner's communication device 2, the control unit 10 sends to the communication devices 2 of all members of each extraction group determined to issue the merge proposal. A merge proposal may be sent to the destination.

  Server 1 includes information about the merge in the merge proposal. For example, the server 1 includes information such as a notification date and time, each extraction group name, and a member of each extraction group. The communication device 2 (processing unit 20) that has received the merge proposal causes the display panel 22 to display the notified information.

  The processing unit 20 also displays a button for answering the merge proposal. That is, the processing unit 20 displays a button for answering the merge permission and a button for answering the merge rejection. For example, the processing unit 20 displays a button including a character string “Merge OK” as a merge permission button. In addition, the processing unit 20 displays a button including a character string “not merged” as a merge rejection button. When the merge permission button is operated, the processing unit 20 causes the wireless communication unit 27 to transmit merge permission to the server 1. When the merge rejection button is operated, the processing unit 20 causes the wireless communication unit 27 to transmit the merge rejection to the server 1.

(Generate merged group)
Next, an example of the flow of generating a merge group according to the embodiment will be described with reference to FIG. FIG. 7 is a flowchart illustrating an example of a flow of generating a merge group according to the embodiment.

  The start of FIG. 7 is the time when the merge proposal is transmitted. First, the control unit 10 continues to check whether or not responses have been received from all the communication devices 2 that have transmitted the merge proposal (Step # 21, No in Step # 21 → Step # 21). When the merge proposal is transmitted only to the owner, the control unit 10 confirms whether or not a response from the communication device 2 of each owner of each extraction group has been received. When the merge proposal is transmitted to the communication devices 2 of all members of each extraction group, the control unit 10 confirms whether or not the responses from the communication devices 2 of all members have been received.

  When responses have been received from all the communication devices 2 that have transmitted the merge proposal (Yes in Step # 21), the control unit 10 determines whether or not to create a merge group based on the response results (Step # 22). Here, the merged group is a new group generated by the server 1. The merged group shall have all members of each extraction group as members.

  When the merge proposal is transmitted only to the owner, when the merge permission is received from the communication devices 2 of all owners, the control unit 10 determines to create a merge group. On the other hand, when the merge rejection is received from the communication device 2 of any owner, the control unit 10 determines that no merge group is generated. When the merge proposal is transmitted to the communication devices 2 of all members of each extraction group, the control unit 10 determines to generate a merge group when the number of merge permission receptions is equal to or greater than the number of merge rejection receptions. On the other hand, when the number of merge permission receptions is smaller than the number of merge rejection receptions, the control unit 10 determines that a merge group is not generated. In other words, when the merge permission number (the number of approvals) is equal to or greater than a majority of the total number of members, the control unit 10 determines to generate a merge group. In addition, when the merge permission is received from one of the communication devices 2 that has transmitted the merge proposal, the control unit 10 may determine to generate a merge group.

  When it is determined that a merged group is to be generated (Yes in Step # 23), the control unit 10 generates a merged group (Step # 24). The control unit adds the newly generated merged group data to the group data 15 in the storage unit 12. Then, the control unit 10 causes the communication unit 11 to transmit a notification that the merged group has been generated to the communication devices 2 of all members of the merged group (step # 25). The control unit 10 includes information such as the creation date and time of the merged group, the owner name of the merged group, each extracted group name, and all members of the merged group in the notification. In addition, the control part 10 makes the owner of each extraction group of a merge source the joint owner of a merge group. Based on this notification, the IM application 2a (processing unit 20) registers the merged group data 2b in the memory unit 21 (see FIG. 1). As a result, messages can be exchanged based on the merged group.

  When it is determined that no merge group is to be generated (No in Step # 23), the control unit 10 does not generate a merge group (Step # 26). After step # 25 and step # 26, this flow ends (end).

(Consolidation of consolidation group)
Next, an example of the flow of determining the merged group according to the embodiment will be described based on FIG. FIG. 8 is a flowchart illustrating an example of a merge group determination flow according to the embodiment.

  The start of FIG. 8 is when a predetermined waiting time elapses from the generation of the merged group. The fixed waiting time is a time for the member to consider whether or not to maintain the merged group. During the settling time, members try to exchange messages with the merged group. The fixed waiting time can be several days. For example, 3 days.

  First, the control unit 10 causes the communication unit 11 to transmit a confirmation notification for confirming whether or not to maintain the merged group, to the member communication devices 2 belonging to the merged group (step # 31). The control unit 10 may cause the communication unit 11 to transmit a confirmation notification toward the communication devices 2 of all members of the merged group. In addition, the control unit 10 may cause only the co-owner's communication device 2 to transmit a confirmation notification. After transmitting only the joint owner to the confirmation request to all members from the communication device 2 of the joint owner, the control unit 10 sends a confirmation notification to the communication devices 2 of all the members of the merged group. Also good.

  The server 1 includes information on the merge in the confirmation notification. For example, the server 1 includes information such as the creation date and time of the merged group, the joint owner name of the merged group, each extracted group name, and all members of the merged group. The communication device 2 (processing unit 20) that has received the confirmation notification causes the display panel 22 to display the notified information.

  In accordance with the information, the server 1 also displays a response button on the communication device 2. That is, the processing unit 20 displays a merge maintenance reply button and a maintenance unnecessary reply button. For example, the processing unit 20 displays a button including a character string “maintain merge (delete old group)” as a merge maintenance reply button. In addition, the processing unit 20 displays a button including a character string “maintenance not required” as a button for a maintenance unnecessary answer. When the merge maintenance reply button is operated, the processing unit 20 causes the wireless communication unit 27 to transmit the maintenance reply toward the server 1. When the maintenance unnecessary answer button is operated, the processing unit 20 causes the wireless communication unit 27 to transmit an unnecessary answer to the server 1.

  The control unit 10 continues to check whether or not the response indicating whether or not the maintenance is necessary has been received from all the communication devices 2 that have transmitted the confirmation notification (No in Step # 32, Step # 32 → Step # 32). When the confirmation notification is transmitted only to the joint owner, the control unit 10 confirms whether or not a response from the communication device 2 of each joint owner has been received. On the other hand, when the confirmation notification is transmitted to the communication devices 2 of all the members of each merged group, the control unit 10 confirms whether or not the response from the communication devices 2 of all the members has been received. When responses have been received from all the communication devices 2 that have transmitted confirmation notifications (Yes in step # 32), the control unit 10 determines whether to maintain the merged group based on the response results (step # 33). .

  When the confirmation notification is transmitted only to the joint owner, when the maintenance reply is received from the communication devices 2 of all the joint owners, the control unit 10 determines to maintain the merged group. On the other hand, when an unnecessary answer is received from the communication device 2 of any joint owner, the control unit 10 determines that the merged group is not maintained. When the confirmation notification is transmitted to the communication devices 2 of all members of the merged group, the control unit 10 determines to maintain the merged group when the number of maintenance responses received is equal to or greater than the number of unnecessary responses received. On the other hand, when the number of maintenance responses received is smaller than the number of unnecessary responses received, the control unit 10 determines not to maintain the merged group. In other words, when the number of favors for maintaining the merge is equal to or greater than a majority of the total number of members, the control unit 10 determines to maintain the merged group. Note that the control unit 10 may determine to maintain the merged group when receiving at least one maintenance reply from the communication device 2 that has transmitted the confirmation notification.

  When it is determined that the merged group is not maintained (No in Step # 34), the control unit 10 deletes the merged group (Step # 35). The control unit 10 causes the storage unit 12 to delete data related to the merged group from the message log 14 and the group data 15. The control unit 10 does not delete each extraction group that is the basis of the merged group (step # 36). On the other hand, when it is determined that the merged group is to be maintained (Yes in Step # 34), the control unit 10 deletes each extraction group that is the basis of the merged group (Step # 37). The control unit 10 causes the storage unit 12 to delete data related to each extraction group from the message log 14 and the group data 15. This flow is terminated by step # 36 and step # 37.

(Deleting inactive groups)
Next, an example of the flow of deleting an inactive group in the server 1 according to the embodiment will be described with reference to FIG. FIG. 9 is a diagram illustrating an example of a flow of deleting an inactive group in the server 1 according to the embodiment.

  In the instant messaging service, there are groups that have not been used for a long time. Generally, the owner has the authority to delete (dissolve) a group. Unused groups will continue to exist unless the owner deletes them. If a group that has not been active for a long time is deleted, the burden on the server 1 can be reduced. Therefore, the server 1 proposes deletion of the inactive group.

  The start of FIG. 9 is when the server 1 detects an inactive group. Inactive groups are detected at regular intervals. For example, an inactive group is detected once every few weeks or months. The control unit 10 detects an inactive group from the registered groups based on the message log 14. The control unit 10 determines that a group for which a predetermined lifetime has elapsed since the last message was issued is an inactive group. The duration can be determined as appropriate. For example, it can be determined appropriately such as one month, several months, one year, ten and several months, and several years. The flowchart of FIG. 9 is executed for each group determined to be an inactive group.

  First, the control unit 10 causes the communication unit 11 to transmit an inactive group deletion notice (step # 41). The control unit 10 sends a deletion notice to the communication devices 2 of the members belonging to the inactive group. The control unit 10 may cause the deletion notice to be transmitted to the communication devices 2 of all members of the inactive group. In addition, the control unit 10 may transmit a deletion notice only to the communication device 2 of the owner of the inactive group. In addition, after transmitting to only the owner, when the request for transmission of the deletion notice to all members is received from the owner's communication device 2, the control unit 10 causes the communication devices 2 of all members of the inactive group to send the deletion notice. May be.

  Further, the server 1 includes information on the inactive group in the deletion notice. For example, the server 1 has the name of the inactive group, the owner name of the inactive group, the member of the inactive group, the date and time when the message was last exchanged in the inactive group, and the time elapsed since the last message exchange. Include information such as The communication device 2 (processing unit 20) that has received the deletion notice causes the display panel 22 to display the notified information.

  In accordance with the information, the server 1 also displays a reply button on the communication device 2. Based on the deletion notice, the processing unit 20 displays a deletion acceptance button and a deletion rejection button. For example, the processing unit 20 displays a button including a character string “delete” as a delete acceptance button. In addition, the processing unit 20 displays a button including a character string “not deleted” as a delete rejection button. When the deletion approval button is operated, the processing unit 20 causes the wireless communication unit 27 to transmit the deletion approval to the server 1. When the deletion rejection button is operated, the processing unit 20 causes the wireless communication unit 27 to transmit a deletion rejection to the server 1.

  The control unit 10 continues to check whether or not an answer indicating the necessity of deletion has been received from all the communication devices 2 that have transmitted the deletion notice (Step # 42, No in Step # 42 → Step # 42). When the deletion advance notice is transmitted only to the owner, the control unit 10 confirms whether or not a response from the owner's communication device 2 has been received. On the other hand, when the deletion notice is transmitted to the communication devices 2 of all members of the inactive group, the control unit 10 confirms whether or not the response from the communication devices 2 of all members has been received. When the response has been received from all the communication devices 2 that have transmitted the deletion notice (Yes in Step # 42), the control unit 10 determines whether or not to maintain the inactive group based on the response result (Step # 43). ).

  When the deletion advance notice is transmitted only to the owner, the control unit 10 determines to delete the inactive group when the deletion consent is received from the communication device 2 of the owner. On the other hand, when the deletion rejection is received from the owner communication device 2, the control unit 10 determines not to delete the inactive group. When the deletion advance notice is transmitted to the communication devices 2 of all members of the inactive group, the control unit 10 determines to delete the inactive group when the number of deletion approvals received is equal to or greater than the number of deletion rejections received. On the other hand, when the number of received deletion approvals is smaller than the number of received deletion rejections, the control unit 10 determines not to delete the inactive group. In other words, the control unit 10 determines to delete the inactive group when the number of approvals for deletion is greater than a majority of the total number of members. Note that the controller 10 may delete the inactive group when receiving at least one deletion approval from the communication device 2 of the member of the inactive group.

  When it is determined not to delete the inactive group (No in step # 44), the control unit 10 does not delete the inactive group (step # 45). On the other hand, when it is determined that the inactive group is to be deleted (Yes in step # 44), the control unit 10 deletes the inactive group (step # 46). The control unit 10 causes the storage unit 12 to delete data related to the inactive group among the message log 14 and the group data 15. This flow is finished (step) by step # 45 and step # 46.

  As described above, the server 1 according to the embodiment includes the communication unit 11, the storage unit 12, and the control unit 10. The communication unit 11 is connected to the communication network 200, receives a message transmitted from a member communication device 2 belonging to a group, and transmits the received message to another member communication device 2 belonging to the same group. The storage unit 12 stores the exchanged message as a message log 14. The control unit 10 extracts a plurality of groups having the same member as an extraction group over a predetermined extraction condition. The control unit 10 recognizes the topic of each extraction group based on the message log 14 of each extraction group. The control unit 10 determines whether to submit a merge proposal to the extraction group based on the recognized topic. When it is determined that a merge proposal is to be issued, the control unit 10 causes the communication unit 11 to transmit a merge proposal regarding whether or not to merge the extraction group toward the member communication devices 2 belonging to each extraction group. When it is determined that the merge proposal is not issued, the control unit 10 does not cause the communication unit 11 to transmit the merge proposal. The communication unit 11 receives merge permission or merge rejection from the communication device 2 that has transmitted the merge proposal. Merger permission is an answer to allow merger. The merger refusal is a reply that the merger is not permitted. When the merge permission is received from the communication devices 2 of the members belonging to the extraction group, the control unit 10 generates a merge group including all members of each extraction group as members.

  Thereby, the group which handles the same member and the same topic can be merged easily. In addition, an amalgamation group will be created after making proposals to members and obtaining their consent. Therefore, unintentional group merging is not performed. In addition, a group with many members in common is the target of the merger. You can prevent merging of unknown groups. In addition, a merge target is determined based on the message log 14. Therefore, it is possible to provide an opportunity to meet those who can talk on the same topic (preference). It is also possible to activate group conversation by changing the group environment.

  The storage unit 12 also stores a term dictionary 16 in which topics and keywords belonging to the topics are defined. The control unit 10 divides a message included in the message log 14 of the extraction group into a plurality of sessions. The control unit 10 recognizes a keyword included in the session for each session. The control unit 10 determines the topic of the session based on the recognized keyword and the term dictionary 16. The control unit 10 totals the number of times determined as the topic of the session for each topic and for each extraction group, and determines a frequent topic based on the total result. When the frequent topic is the same in each extraction group, the control unit 10 determines that the merge proposal is issued, and determines that the merge proposal is not issued when there is no frequent topic and when the frequent topic is not common to each extraction group. . Thereby, it can be determined accurately whether the frequent topics of each extraction group are the same. It is possible to accurately determine whether the tastes of the extraction groups are similar.

  When a predetermined waiting time has elapsed since the merged group was generated, the control unit 10 confirms whether or not to maintain the merged group toward the communication devices 2 of the members belonging to the merged group. Confirmation notification is transmitted to the communication unit 11. The communication unit 11 receives a maintenance response or an unnecessary response from the communication device 2 that has transmitted the confirmation notification. The maintenance response is a response to maintain the consolidation group. Unnecessary responses are responses that do not maintain the consolidation group. When the maintenance reply is received from the communication devices 2 of the members belonging to the merged group, the control unit 10 maintains the merged group and deletes the extraction group. Thereby, it can be determined based on a member's intention whether to leave a merged groove. Here, the greater the number of groups created, the greater the burden on the server 1. Each extraction group is automatically deleted when maintaining the merged group. Since the merged group is maintained, the former members of the deleted extraction group can still exchange messages. There is no inconvenience. By creating a merged group, groups that are no longer used can be progressively eliminated (organized). And the burden of the server 1 can be reduced. For example, the number of groups to be managed is reduced. Further, the message log 14 of the extraction group stored in the server 1 can be deleted.

  The authority of group dissolution may be given to the group owner. Therefore, the control unit 10 causes the communication unit 11 to transmit a confirmation notification toward the communication device 2 of the owner of each extraction group merged into the merged group. When the maintenance reply is received from all owner communication devices 2, the control unit 10 maintains the merged group and deletes each extraction group. When an unnecessary answer is received from the communication device 2 of any owner, the control unit 10 deletes the merged group and does not delete each extraction group. Thereby, based on the intention of the owner of each extraction group, it can be decided whether a merged group is maintained or deleted.

  In addition, the control unit 10 causes the communication unit 11 to transmit a confirmation notification toward the communication devices 2 of all members of the merged group. When the number of maintenance responses received from the communication device 2 that transmitted the confirmation notification is equal to or greater than the number of unnecessary responses received, the control unit 10 maintains the merged group and deletes each extraction group. When the number of maintenance responses received from the communication device 2 that transmitted the confirmation notification is smaller than the number of unnecessary responses received, the control unit 10 deletes the merged group and does not delete each extraction group. Thereby, based on the majority vote of all the members of a merged group (each extraction group), it can determine whether a merged group is maintained or deleted.

  There is a tendency that exchanges for one topic are performed together in a relatively short time. On the other hand, when there is no more to speak, conversation (message) stops. There may be a relatively long time before the next message starts. Therefore, the control unit 10 sets a message having a time interval longer than a predetermined first time as another session, or sets a message within a predetermined second time as the same session. All messages in the extraction group can be separated by session. The message log 14 can be delimited when it is recognized that the message flow of a certain topic has been cut off. The message log 14 can be divided so that the topic can be clearly determined.

  Moreover, the control part 10 transmits the merge proposal to the communication part 11 toward the communication apparatus 2 of the owner of each extraction group determined to issue a merge proposal. When the merge permission is received from the communication devices 2 of all owners, the control unit 10 generates a merge group. When the merge rejection is received from the communication device 2 of any owner, no merge group is generated. Thereby, it can be determined whether to create a merged group based on the intention of the owner of each extraction group.

  Moreover, the control part 10 transmits the merge proposal to the communication part 11 toward the communication apparatus 2 of all the members of each extraction group determined to give a merge proposal. When the number of merge permission receptions is equal to or greater than the number of merge rejection receptions, the control unit 10 generates a merge group. When the number of merge permission receptions is smaller than the number of merge rejection receptions, the control unit 10 does not generate a merge group. Based on the majority vote of all members of each extraction group, it can be decided whether or not to create a merged group.

  The extraction condition is that more than half of the members belonging to the group are common. As a result, it is possible to easily merge groups in which more than half the members belong to each other.

  In addition, the control unit 10 determines, based on the message log 14, a group in which a predetermined lifetime has elapsed since the last message was issued as an inactive group. The control unit 10 causes the communication unit 11 to transmit an inactive group deletion notice to the member communication devices 2 belonging to the inactive group. When the deletion rejection is received from the communication device 2 of the member belonging to the inactive group, the control unit 10 does not delete the inactive group. When the deletion consent is received from the communication device 2 of the member belonging to the inactive group, the control unit 10 deletes the inactive group. As a result, a group that has not been used for a long time can be deleted. The burden on the server 1 can be reduced. In addition, deletion of the group can be notified to members of the inactive group. Inactive groups can be deleted in response to a response to the notice. In other words, whether or not to delete the inactive group can be determined according to the intention of the member of the inactive group.

  Moreover, the server 1 which concerns on embodiment, and the communication apparatus 2 which transmits / receives a message relayed to the server 1 are included. It is possible to provide a message management system 100 that can easily merge similar members and groups dealing with similar topics.

  The message group management method according to the present invention connects a server to a communication network. A message transmitted from a communication device of a member belonging to the group is received, and the received message is transmitted to communication devices of other members belonging to the same group. The exchanged message is stored as a message log. A plurality of groups having the same members over the predetermined extraction condition are extracted as extraction groups. Based on the message log of each extraction group, the topic of each extraction group is recognized. It is determined whether or not to submit a merge proposal to the extraction group based on the recognized topic. When it is determined that the merge proposal is to be issued, a merge proposal regarding whether or not to merge the extraction group is transmitted to the communication devices of the members belonging to each extraction group. When it is determined not to issue the merge proposal, the merge proposal is not transmitted. Merge permission or denial is received from the communication device that has transmitted the merge proposal. The merge permission is an answer indicating that the merge is permitted. The merge rejection is a reply that the merge is not permitted. When the merge permission is received from communication devices of members belonging to the extraction group, a merge group including all members of each extraction group as members is generated. Thereby, the same effect as the above-mentioned server can be acquired.

  Although the embodiment of the present invention has been described, the scope of the present invention is not limited to this, and various modifications can be made without departing from the spirit of the invention.

  The present invention can be used for a server. It can also be used in a message group management system including a server and a communication device.

DESCRIPTION OF SYMBOLS 100 Message management system 1 Server 10 Control part 11 Communication part 12 Storage part 14 Message log 16 Term dictionary 2 Communication apparatus 200 Communication network

Claims (12)

A communication unit connected to a communication network, receiving a message transmitted from a communication device of a member belonging to the group, and transmitting the received message to a communication device of another member belonging to the same group;
A storage unit for storing the exchanged messages as a message log;
A control unit that extracts a plurality of groups having the same members as an extraction group over a predetermined extraction condition,
The controller is
Recognizing the topic of each extraction group based on the message log of each extraction group, determining whether to submit a merge proposal to the extraction group based on the recognized topic;
When it is determined that the merge proposal is to be issued, a merge proposal relating to whether or not the extraction group is allowed to be merged is sent to the communication unit toward communication devices of members belonging to each of the extraction groups
When it is determined not to issue the merge proposal, the merge proposal is not transmitted from the communication unit,
The communication unit receives merge permission or merge rejection from the communication device that transmitted the merge proposal,
The merger permission is an answer to permit the merger,
The refusal of merging is a reply that merging is not permitted,
When receiving the merge permission from a communication device of a member belonging to the extraction group, the control unit generates a merge group including all members of each extraction group as members. The storage unit stores a term dictionary in which a topic and a keyword belonging to the topic are defined,
The control unit divides a message included in the message log of the extraction group into a plurality of sessions,
For each session, recognize the keyword included in the session;
Determine the topic of the session based on the recognized keyword and the term dictionary;
For each topic and for each extraction group, the number of times determined as the topic of the session is aggregated, frequent topics are determined based on the aggregation results, and when the frequent topics are the same in each extraction group, the merge proposal is 2. The server according to claim 1, wherein the server determines that the merge proposal is not issued when there is no frequent topic and when the frequent topic is not common to each extraction group. When a predetermined waiting time elapses after generating the merged group,
The control unit causes the communication unit to transmit a confirmation notification for confirming whether or not to maintain the merged group toward communication devices of members belonging to the merged group,
The communication unit receives a maintenance response or an unnecessary response from the communication device that has transmitted the confirmation notification,
The maintenance answer is an answer to maintain the merged group,
The unnecessary answer is an answer not to maintain the merged group,
The server according to claim 1 or 2, wherein when the maintenance response is received from a communication device of a member belonging to the merged group, the merged group is maintained and the extraction group is deleted. The controller is
Sending the confirmation notification to the communication unit towards the communication device of the owner of each extraction group merged in the merged group,
When the maintenance answer is received from all the communication devices of the owner, the merged group is maintained and each extraction group is deleted,
4. The server according to claim 3, wherein when the unnecessary answer is received from any of the communication devices of the owner, the merged group is deleted and each of the extraction groups is not deleted. The controller is
Sending the confirmation notification to the communication unit toward the communication devices of all members of the merged group,
When the number of maintenance responses received from the communication device that transmitted the confirmation notification is equal to or greater than the number of unnecessary responses received, maintain the merged group and delete each extraction group,
4. The merged group is deleted and the extracted groups are not deleted when the number of maintenance responses received from the communication device that has transmitted the confirmation notification is smaller than the number of unnecessary responses received. The server described in.   The control unit sets a message having a time interval longer than a predetermined first time as another session, or sets a message within a predetermined second time as the same session. The server according to any one of claims 2 to 5, characterized in that: The controller is
Sending the merge proposal to the communication unit toward the communication device of the owner of each extraction group determined to issue the merge proposal,
When the merge permission is received from all the communication devices of the owner, the merge group is generated,
The server according to any one of claims 1 to 6, wherein the merge group is not generated when the merge rejection is received from any of the owner communication devices. The control unit causes the communication unit to transmit the merge proposal to the communication devices of all members of each extraction group determined to issue the merge proposal,
When the number of merge permission receptions is equal to or greater than the number of merge rejection receptions, the merge group is generated,
The server according to any one of claims 1 to 6, wherein the merge group is not generated when the number of merge permission receptions is smaller than the number of merge rejection receptions.   9. The server according to claim 1, wherein the extraction condition is that at least half of the members belonging to the group are common. The controller is
Based on the message log, a group in which a predetermined lifetime has elapsed since the last message was issued is determined as an inactive group,
The control unit, to the communication device of the member belonging to the inactive group, to cause the communication unit to send a deletion notice of the inactive group,
When receiving a deletion refusal from a communication device of a member belonging to the inactive group, do not delete the inactive group,
The server according to any one of claims 1 to 9, wherein when a deletion consent is received from a communication device of a member belonging to the inactive group, the inactive group is deleted. A server according to any one of claims 1 to 10,
A message group management system comprising: a communication device that relays messages to the server and transmits / receives messages. Connect the server to the communication network,
Receives messages sent from member communication devices belonging to the group,
Send the received message to the communication device of another member belonging to the same group,
Memorize exchanged messages as a message log,
Extract multiple groups with the same members as extraction groups above the predefined extraction conditions,
Recognizing the topic of each extraction group based on the message log of each extraction group;
Determine whether to submit a merge proposal to the extraction group based on the recognized topic;
When it is determined that the merge proposal is issued, a merge proposal regarding whether or not to merge the extraction group is transmitted to communication devices of members belonging to each of the extraction groups,
When it is determined that the merge proposal is not issued, the merge proposal is not transmitted,
Receiving merge permission or merge rejection from the communication device that sent the merge proposal,
The merger permission is an answer to permit the merger,
The refusal of merging is a reply that merging is not permitted,
A message group management method, comprising: generating a merge group including all members of each extraction group as members when receiving the merge permission from a communication device of a member belonging to the extraction group.

Images