WO2014045679A1 - Dispositif de gestion, procédé et programme d'administration de messages - Google Patents

Dispositif de gestion, procédé et programme d'administration de messages Download PDF

Info

Publication number
WO2014045679A1
WO2014045679A1 PCT/JP2013/068626 JP2013068626W WO2014045679A1 WO 2014045679 A1 WO2014045679 A1 WO 2014045679A1 JP 2013068626 W JP2013068626 W JP 2013068626W WO 2014045679 A1 WO2014045679 A1 WO 2014045679A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
message
group
users
terminal device
Prior art date
Application number
PCT/JP2013/068626
Other languages
English (en)
Japanese (ja)
Inventor
加藤　禎人
Original Assignee
株式会社コナミデジタルエンタテインメント
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社コナミデジタルエンタテインメント filed Critical 株式会社コナミデジタルエンタテインメント
Publication of WO2014045679A1 publication Critical patent/WO2014045679A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/216—Handling conversation history, e.g. grouping of messages in sessions or threads

Definitions

  • the present invention relates to a technique for allowing a plurality of users to browse messages transmitted from terminal devices of a plurality of users participating in a group.
  • chat the browsing of messages (chat) is actually executed between terminal devices such as mobile phones that can communicate with the management server.
  • chat includes one-on-one chat with a pre-registered partner and group chat between members in a group composed of a plurality of members.
  • group chat a new user can participate as a member from the middle.
  • the present invention has been made in view of such circumstances, and one of its purposes is to provide a technology that makes it possible to replenish and restore past message histories that could not be browsed. It is in.
  • the management device stores, for each of a plurality of users participating in a group, messages transmitted from the users after joining the group.
  • a management apparatus that provides a message history that can be viewed on a user terminal device, and removes the requesting user from a requesting user who is one of the plurality of users.
  • a request processing unit that accepts an application for a request destination user who is a part or all of the users and a request destination use corresponding to the request for an unstored message not stored in a message history corresponding to the request source user
  • a history processing unit that acquires the message history corresponding to the user and adds the message history to the message history corresponding to the requesting user.
  • a message history in which messages sent from each other's users after being joined to the group are stored,
  • a message management method that is provided so as to be viewable on a terminal device of a user, wherein a user who excludes the requesting user from a requesting user who is one of the plurality of users.
  • a step of accepting an application for a requested user who is part or all, and an unstored message not accumulated in a message history corresponding to the requesting user from a message history corresponding to the requested user corresponding to the application And obtaining and adding to a message history corresponding to the requesting user.
  • a program provides, for each of a plurality of users who participate in a group, a message history in which messages transmitted from each other's users are accumulated after joining the group.
  • a request destination which is a part or all of the users excluding the request source user from the request source user who is one of the plurality of users who provides the computer which can be viewed on the terminal device.
  • An application processing unit that accepts an application for a user, and an unstored message that is not stored in a message history corresponding to the requesting user is acquired from a message history that corresponds to the requesting user corresponding to the application, It is made to function as a history process part which performs the process added to the message history corresponding to the said request origin user.
  • FIG. 1 is a diagram showing an overview of a message providing system according to an embodiment of the present invention.
  • the terminal devices operated by the users A, B, C, and D are connected to be communicable with the management server.
  • Users A, B, C, and D are members of group chat.
  • user A joins the group on the way and uses chat with users B, C, and D from the time of participation.
  • users B, C, and D can use chat before user A joins. Under such an assumption, the user A has come to want to know the flow of the chat before participation while the chat is in progress.
  • the user A applies for a message history by operating the terminal device (a).
  • the user A since the user A is a request source of the message history, the user A may be called a request source user.
  • the management server that has accepted the application for the history inquires about the applicability of the application to one or more users B, C, and D, excluding the user A who has applied, among the users constituting the group (b) ).
  • the users B, C, and D are called request destination users because they become request destinations with respect to the request source.
  • the applicability of the application first, the requesting user is made to select one of the users B, C, and D, and the selected person is inquired. Second, the users B, C, and D are inquired. Third, it is assumed that one of the users B, C, and D is inquired to a person selected according to a predetermined rule. The figure shows an example in which user B becomes a requested user.
  • the management server inquires of the user B about whether or not the application is possible and the user B accepts the application (c), the management server stores the message stored corresponding to the requesting user. An unstored message that is not stored in the history is specified, and the specified unstored message is added (supplemented) to the message history (d). As a result, the user A who is the requesting user can browse the message history to which the unstored message is added. In addition, since the requesting user's approval is required to acquire the unstored message, it is possible to prevent a message history made in a certain group from being illegally used by a third party. If importance is attached only to replenishment of unstored messages, the requesting user's consent is not necessarily required.
  • the entire message history is stored as a master in the management storage unit provided on the management server side, and the user's message history is stored without such a management storage unit.
  • a configuration in which only a terminal storage unit provided on the terminal device side of the user is stored locally is conceivable.
  • the message history of each user is also stored in the terminal storage unit on the terminal device side of the user,
  • a configuration is conceivable in which the management storage unit on the management server side stores the information for each user, not on the terminal device side.
  • the configuration in which the user's message history is also stored in the terminal storage unit on the user's terminal device side in the former configuration is the first embodiment and is used without the management storage unit.
  • the latter configuration in which the user's message history is stored locally only in the terminal storage unit on the user's terminal device side is the second embodiment, and among the former configuration, the user's message history is the management storage unit on the management server side.
  • the configuration stored for each user will be described as a third embodiment.
  • FIG. 2 is a diagram showing an overall configuration of the message providing system according to the first embodiment.
  • a plurality of terminal devices 20-1, 20-2, 20-3, 20-4,... are connected via the mobile communication network Nb, the gateway 15, and the Internet Na.
  • the configuration is connected to a management server (management device) 10.
  • the terminal device 20-1 is operated by the user A, and similarly, the terminal devices 20-2, 20-3, and 20-3 are operated by the users B, C, and D. Shall.
  • “ ⁇ (hyphen)” in the reference numerals are omitted. Simply “20”.
  • the management server 10 serves as an intermediary when providing chat as a service provided by itself. Specifically, when providing the chat, the management server 10 forwards a message transmitted from a certain user's terminal device 20 to the terminal device of the other user, or a chat user or group. Or manage.
  • a chat when a certain terminal device 20 is taken as a reference, the user himself / herself (terminal user) of the terminal device 20 and a member composed of one or more other users, in other words, Then, the chat with the user (registered user) registered in the terminal device 20 is assumed. For this reason, one group includes two or more people including the terminal user of the terminal device 20.
  • a chat performed by two users of a terminal user and a registered user as a partner is called a one-to-one chat, or a chat performed by three or more people including a terminal user is a group chat in a narrow sense. Sometimes called.
  • a terminal user selects a group to be a chat destination in advance.
  • FIG. 3 is a block diagram showing a hardware configuration of the management server 10.
  • the management server 10 includes a CPU (Central Processing Unit) 101 that controls the entire apparatus, a RAM (Random Access Memory) 102 that functions as the main memory of the CPU 101, and a ROM that stores a boot program and the like. (Read Only Memory) 103, an interface (I / F) 105 for communicating via a network, an RTC (Real Time Clock) 106 for outputting time information, and a storage unit 108 are included.
  • a database 118 managed by the CPU 101 is constructed.
  • the storage unit 108 stores a program for the management server 10 to provide a chat to the terminal device 20, various data, and the like.
  • the database 118 manages user and group information and the like as will be described later.
  • a program for the management server 10 to provide a chat to the terminal device 20 may be stored in a recording medium. If the recording medium is used, for example, the program can be installed in the management server 10 as a computer.
  • the recording medium storing the program may be a non-transitory recording medium.
  • the non-transitory recording medium is not particularly limited, but may be a recording medium such as a CD-ROM.
  • management server 10 is constructed as a single unit in FIG. 2, it may be configured so that it is distributed to two or more units and is virtually seen as one unit when viewed from the outside.
  • some functions of the management server 10 may be constructed by a server that provides other services.
  • you may comprise so that the management server 10 may connect with the terminal device 20 via a relay server.
  • the terminal device 20 is, for example, a mobile phone operated by a user.
  • the terminal device 20 includes a touch panel 220 superimposed on the display panel 210, and a user can input necessary information and various instructions by touching the screen displayed on the display panel 210. It is a given configuration.
  • FIG. 4 is a block diagram illustrating a hardware configuration of the terminal device 20.
  • the terminal device 20 includes a CPU 201, a memory 202, a communication unit 204, an RTC 206, a storage unit 208, a display panel 210, and a touch panel 220.
  • the CPU 201 controls the entire terminal device 20, and the memory 202 stores a basic program and an application program (chat application) for performing chat in a nonvolatile manner.
  • This chat application creates a message and transmits it to the management server 10 or displays a message received from the management server 10.
  • the chat application is downloaded from a specific distribution site and installed on the terminal device 20. It is a thing.
  • a chat application is uninstalled from a terminal device 20 of a certain user, the contents of the chat (message history) exchanged by the user so far are deleted together with the account.
  • the communication unit 204 communicates with the management server 10 via the mobile communication network Nb or the like.
  • the RTC 206 outputs time information of the current time.
  • a database 218 managed by the CPU 201 is constructed. Details of various storage units managed by the database 218 will be described later.
  • the display panel 210 is a flat display such as a liquid crystal display device or an organic EL (Electro Luminescence) device.
  • the touch panel 220 detects an operation position (two-dimensional coordinate value) for the screen displayed by the display panel 210 and supplies the detected position to the CPU 201.
  • the CPU 201 specifies the operation content on the touch panel 220 such as the moving direction, moving speed, and touch operation of the touch position based on the detection information.
  • the types of touch operations that can be specified include, for example, tap, flick, drag, pinch and the like.
  • tapping is an operation of tapping the display screen with a finger.
  • Flicking is an operation in which the object displayed on the screen is gently touched with a finger.
  • Dragging is an operation of moving an object displayed on the screen in contact with a finger.
  • Pinch is an operation of expanding or narrowing a display screen with two fingers in contact with each other.
  • the terminal device 20 is not limited to the mobile communication network Nb, and may be configured to be connected to a wireless LAN (Local Area Network). When connected to a wireless LAN, the terminal device 20 is connected to the management server 10 via a wireless base station (access point) and the Internet Na.
  • the terminal device 20 is not limited to a mobile phone, and may be a tablet computer or a PDA (Personal Digital Assistant).
  • the following functional blocks are constructed by executing the above program and in the terminal device 20 by executing a chat application installed in advance.
  • FIG. 5 is a diagram showing functional blocks constructed by the message providing system.
  • functional blocks constructed by the management server 10 in the message providing system 1 and the terminal device 20 focused on one of a plurality of units are shown.
  • the display unit 205 is provided in the display area of the display panel 210 and performs various displays and accepts operations on the touch panel 220.
  • the operation detection unit 231 detects an operation on the display unit 205 from the detection signal of the touch panel 220. Operations on the display unit 205 include inputting a message, sending (transmitting, posting) the message, and moving / switching the screen.
  • the management unit 233 attaches various information to the transmission unit 236, receives various information from the management server 10, manages three storage units, Information necessary for display on the display unit 205 is supplied to the display control unit 241.
  • the transmission unit 236 transmits the message supplied from the management unit 233 to the management server 10 together with various attached information. Note that the transmission unit 236 controls the communication unit 204, which is actually hardware, to transmit a message or the like.
  • the display control unit 241 controls the display contents so that an operation on the display unit 205 is reflected when the chat is executed. Specifically, the display control unit 241 causes the display unit 205 to display a list of chat partners on the chat partner list screen, or to post a message or the like supplied from the management server 10 via the management unit 233. Are displayed in this order. When storage processing to be described later is executed, the management unit 233, the transmission partner storage unit TB22, and the terminal storage unit TB23 are constructed even if the chat application is not executed.
  • a user / group storage unit TB11 and a management storage unit TB13 are constructed in the database 118.
  • the receiving unit 121 receives a message to which various information is attached, an application for a message history, acceptance of the application, and the like from the terminal device 20.
  • the application when a member (requesting user) of a certain group operates the terminal device 20 to apply for a message history related to the group, the application is received by the receiving unit 121.
  • the application processing unit 122 accepts the received application, and causes other members (requested users) of the group to perform an operation process on the application. Specifically, as will be described later, the application processing unit 122 causes the request-destination user's terminal device 20 to execute a process of inquiring the request-destination user whether or not to accept the application.
  • the management unit 123 stores the received message and the like in the management storage unit TB13, and uniquely identifies the group ID and the user that uniquely identify the group among the information included in the various information attached to the message and the like Information for accessing the terminal device of the member (user) excluding the user ID among the members of the group specified by the group ID from the identified user ID is stored in the user / group storage unit TB11. Get by referring to. As a result, the received message or the like is stored as a history in the management storage unit TB13, and the transfer destination is specified.
  • the management unit 123 also serves as a history processing unit.
  • an unstored message is specified and specified in the terminal device 20 of the requesting user.
  • An unaccumulated message is acquired from the management storage unit TB13 and supplied to the terminal device 20 via the transfer unit 125.
  • the transfer unit 125 transfers the message received by the receiving unit 121 to the terminal device 20 for which the transfer destination has been specified, or supplies the acquired unstored message to the terminal device 20 of the requesting user.
  • information related to users who can chat and information related to groups to be chatted are stored. Specifically, as information about a user who can chat, the name information of the user, a user ID that uniquely identifies the user, information for accessing the user's terminal device, and the like are registered. In addition, information on the group includes the name information of the group, a group ID that uniquely identifies the group, a user ID of the member that constitutes the group, the group's founder, and which member of the group The information indicating who invited you is also registered.
  • the user ID is generated by the management unit 123 of the management server 10 in the course of this communication when the chat application is activated for the first time on the user terminal device 20 and the terminal device 20 communicates with the management server 10.
  • the user ID is registered in the user / group storage unit TB11 and is transmitted to the terminal device 20 of the user via the transfer unit 125 and stored. Thereby, in the said terminal device 20, the account for performing a chat application is acquired. Further, in the user / group storage unit TB11 in the management server 10, information is registered for all users and all groups. In the transmission partner storage unit TB22 in the terminal device 20 described later, the terminal device 20 And information on the group to be the chat partner is transferred from the user / group storage unit TB11 and registered.
  • the user / group storage unit TB11 in the management server 10 is updated to participate in the group.
  • the terminal device 20 of the user is notified, and the transmission partner storage unit TB22 of each user is updated.
  • FIG. 5 for convenience of explanation, attention is paid to one terminal device 20 (one user), and transmission / reception of information and messages between the terminal device 20 and the management server 10 is illustrated. Not too much.
  • the management server 10 receives a message or the like from the plurality of terminal devices 20, and conversely transfers the message or the like to the plurality of terminal devices 20.
  • a large number of arrows heading toward the receiving unit 121 indicate that messages and the like are received from other terminal devices other than the focused terminal device 20, and a large number of arrows heading from the transfer unit 125 indicate the terminal device 20.
  • the Internet Na, the gateway 15, the mobile communication network Nb in FIG. 2, the I / F 105 in FIG. 3, the communication unit 204 in FIG. 4, and the like are only transmission paths for information and messages.
  • FIG. 1 the Internet Na, the gateway 15, the mobile communication network Nb in FIG. 2, the I / F 105 in FIG. 3, the communication unit 204 in FIG. 4, and the like are only transmission paths for information and messages.
  • terminal user information storage unit TB21 the transmission partner storage unit TB22, and the terminal storage unit TB23 on the terminal device 20 side will be described in order.
  • Terminal user information storage unit when a certain user (terminal user) instructs the chat partner to transmit a message using the terminal device 20, various information such as information indicating the terminal user (sender information) is included in the message.
  • the message is attached and transmitted to the terminal device 20 of the chat partner via the management server 10, while the sender information is added to the message and displayed on the terminal device 20 of the chat partner.
  • the terminal user information storage unit TB21 stores sender information of the terminal user of the terminal device 20.
  • FIG. 6 is a diagram illustrating an example of the terminal user information storage unit TB21.
  • the user name information and the profile image are stored in association with the user ID of the terminal user.
  • the user ID is information for uniquely identifying the user, and the information generated by the management server 10 is registered as described above.
  • the user name information a name for the partner user in the chat to identify the terminal user is registered. For this name, the real name or nickname of the terminal user is used.
  • the profile image information an actual image, an illustration image, and a landscape image of the user are registered and selected or edited by the user.
  • the profile image information may be the link destination (reference destination) of the image information, not the actual image information itself.
  • FIG. 6 shows an example of the terminal user information storage unit TB21 registered in the terminal device 20 of the terminal user whose user ID is “aa11”.
  • a user whose user ID is “aa11” may be referred to as “user A”.
  • the transmission partner storage unit TB22 is for managing the partner in the chat in units of groups on the terminal device 20 side.
  • FIG. 7 is a diagram illustrating an example of the contents stored in the transmission partner storage unit TB22.
  • name (name) information and user IDs of members constituting the group are stored in association with each other.
  • the name information if there are three or more members (terminal users) who are users of the terminal device 20 in the group, the group name is registered, and the members are terminal users. If there are two people including the name, the name of the partner user is registered. However, when there are two people, the name of the other user may be changed to the name of the group afterwards.
  • the registered content is changed to the name of the input group.
  • it may be registered with a name connecting the names of users who have joined the group, and can be changed to the name of the group afterwards.
  • the transmission partner storage unit TB22 stores group members as viewed from the terminal device 20, the members of each group always include a terminal user.
  • a person whose user ID is “aa11” is a terminal user.
  • a user other than the terminal user may be called a registered user or a member because the terminal user can be a chat partner.
  • ⁇ null> indicates an unset empty state.
  • the other user leaves the group only the user ID of the terminal user is registered.
  • chat partner since there is no chat partner, chat with the group is not possible, but when the same registered user or another user is invited and the other party accepts, the number of members of the group becomes two or more. Therefore, it is possible to chat with the same group ID.
  • the group whose group ID is “ax16” is composed of two users: a terminal user whose user ID is “aa11” and a partner user whose user ID is “aa13”. It is stipulated that Therefore, “Yu Takahashi J” registered in the name information of this group is the name of the user whose user ID is “aa13”. Even in the transmission partner storage unit TB22 of the terminal device 20 of the chat partner, the same content as that of the group whose group ID is “ax16” is stored in FIG.
  • the group with the group ID “ay03” has the name “team 246” and the user IDs “aa12”, “aa15”, “aa11” (user A), It is specified to be composed of four members “aa16”.
  • the group is registered in each of the transmission destination storage units TB22 of the terminal device of members other than the user A, that is, members having user IDs “aa12”, “aa15”, and “aa16”. Is done.
  • the user with the user ID “aa12” is “user B”, the user with the user ID “aa15” is “user C”, and the user ID is “user A”.
  • a user who is “aa16” may be referred to as “user D”.
  • the maximum value of the number of members constituting the group is set to “5”, but this is not intended to limit the number of members. It goes without saying that there is no need to set an upper limit on the number of people.
  • ⁇ Terminal storage unit> In the present embodiment, in the terminal device 20, messages and the like transmitted from members registered in the transmission partner storage unit TB 22 are received one by one via the management server 10. The storage destination of the message received at this time is the terminal storage unit TB23. In addition to the text information that is the main body, various accompanying information is attached to the received message or the like.
  • FIG. 8 is a diagram illustrating an example of registered contents in the terminal storage unit TB23.
  • the terminal storage unit TB23 for each posting ID assigned by the management server 10 to uniquely identify a message, a contributor ID indicating a user who posted the message, and a chat partner Group ID, post date / time information indicating the date and time when the message was transmitted, sender's sender information, and character information of the message as the main body are stored in association with each other.
  • the poster user ID is used as the poster ID.
  • the sender information is the name information and profile image information of the poster.
  • the message received from the management server 10 is attached with the posting ID, the poster ID, the group ID, the posting date / time information, and the sender's sender information as supplementary information.
  • the message transmitted from the terminal user terminal device 20 to the management server 10 is attached in a state in which the posting ID is not included in the incidental information.
  • the management unit 123 of the management server 10 assigns a post ID for identifying the message to be included in the incidental information.
  • the message is directly stored in the terminal storage unit TB23 in the terminal device 20 of the terminal device 20 without accompanying the management server 10 together with the accompanying information not including the posting ID.
  • the management server 10 returns the posting ID together with the message reception notification
  • the terminal device 20 stores the returned posting ID in association with the message in the terminal storage unit TB23. become.
  • the main body (text) of the posted message may be managed and stored in another table (not shown) in association with the posting ID.
  • FIG. 9 is a flowchart showing the operation of the terminal device 20.
  • the chat application is activated. Is done.
  • the management unit 233 acquires the user name information of the terminal device 20 from the terminal user information storage unit TB21, while transmitting information about a group that can be chatted from the transmission partner storage unit TB22. get.
  • the management unit 233 supplies the acquired information to the display control unit 241, and the display control unit 241 creates a partner list screen capable of chatting based on the supplied information and causes the display unit 205 to display the partner list screen. As a result, the chat partner list screen is displayed on the display unit 205 (step Sb11).
  • FIG. 13 is a diagram illustrating an example of a chat partner list screen.
  • the display unit 205 displays a list of partner names that can chat with the terminal device 20.
  • the name here is the name of the group if there are three or more members that comprise the terminal user, and the name of the other user if there are two members who have not been changed afterwards. is there.
  • the display control unit 241 displays a profile image associated with the partner user in the vicinity of the display portion of the name of the partner user on the chat partner list screen, and displays it near the name display portion of the group.
  • a button 251 for confirming a member is displayed while indicating that the group includes three or more persons including the user (a group in which a message is transmitted to a plurality of members other than the user).
  • the display control unit 241 displays a button 252 in the upper right corner of the drawing on the chat partner list screen. This button 252 is a software button for instructing the end of the chat application.
  • the management unit 233 acquires a profile image associated with the user ID in the terminal storage unit TB23 using the user ID of the member of the group acquired from the transmission partner storage unit TB22 as a key, The data is transferred to the display control unit 241, and the display control unit 241 displays it in association with the name of the other user.
  • the chat partner is selected, for example, when the user touches the display portion of the name of the partner user or the name of the group.
  • the chat partner list screen is scrolled up and down by an operation such as flicking.
  • the other party that can chat is displayed as a list in which one-to-one chat and group chat are mixed, but may be displayed separately.
  • the operation detection unit 231 determines whether or not an appropriate operation has been performed on the display unit 205 (step Sb12).
  • the appropriate operation is an operation within a range assumed in advance, for example, an operation on a display part of a button or a display part of a name, and an operation such as the flick described above.
  • step Sb12 If there is no operation, or if it is an invalid operation that is not expected even if there is an operation (if the determination result in step Sb12 is “No”), the processing procedure returns to step Sb11. For this reason, the chat partner list screen continues to be displayed until some appropriate operation is performed.
  • the operation detection unit 231 first determines whether or not the operation is an operation on the display portion of the button 252 ( Step Sb13).
  • the operation detection unit 231 notifies the management unit 233 to that effect. To quit the chat app.
  • the operation detection unit 231 next It is determined whether or not the operation is a selection of a chat partner, that is, an operation such as a touch on a display portion of the name of the partner user or the name of the group (step Sb21).
  • step Sb27 a process corresponding to the operation is executed (step Sb27).
  • processing include an operation on the button 251 and a flick of a chat partner list screen.
  • the operation detection unit 231 notifies the management unit 233 of the detection of the operation, and the management unit 233 acquires information about the constituent members of the group corresponding to the button 251.
  • the management unit 233 first accesses the transmission partner storage unit TB22 to acquire the user IDs of the members of the group, and secondly accesses the terminal storage unit TB23 to access the user.
  • the name information and profile image corresponding to the ID are acquired, and thirdly, the acquired information is transferred to the display control unit 241. Based on the transferred information, the display control unit 241 creates and displays a screen for confirming the constituent members of the group corresponding to the button 251.
  • FIG. 14 is an example of a group member list screen.
  • FIG. 14 shows that the button 251 (see FIG. 13) corresponding to the group having the group ID “ay03” and the name “team 246” in the transmission partner storage unit TB22 shown in FIG.
  • the four members constituting the group that is, the user IDs “aa12” (user B), “aa15” (user C), “aa11” (user A) is an example in which the name and profile image of a member who is “aa16” (user D) are displayed.
  • the flick of the chat partner list screen is as described above.
  • the processing procedure returns to the display of the chat partner list screen in step Sb11.
  • step Sb21 if the operation performed on the chat partner list screen is an operation for selecting a chat partner (if the determination result in step Sb21 is “Yes”), the operation detection unit 231 notifies the management unit 233 to that effect. Upon receiving this notification, the management unit 233 extracts the message corresponding to the selected group from the terminal storage unit TB23 and transfers it to the display control unit 241, and displays the chat posting / display screen corresponding to the group. An instruction to display is given (step Sb23).
  • the storage processing for the terminal storage unit TB23 will be described. This is because the chat posting / display screen is displayed based on the content of the terminal storage unit TB23, but the content of the terminal storage unit TB23 is changed (added) by this storage processing.
  • FIG. 10 is a flowchart showing the storage process. This storage process is executed in response to reception of information related to chat from the management server 10. Specifically, the storage process is executed in parallel with the chat application even if the chat application is not executed or the chat application is executed.
  • the following four items are assumed as information related to chat that the terminal device 20 receives from the management server 10. That is, firstly, a message transmitted with accompanying information from another terminal device 20 (via the management server 10), and secondly, a message transmitted from the management server 10 when applying for a chat history. And thirdly, a post ID assigned by the management server 10, and fourthly, information regarding the member after the change when the configuration of the group including the terminal user is changed. Assumed. Among these, for the first and second messages, the message from the management server 10 includes, as ancillary information, a post ID, a contributor ID, a group ID, and post date / time information in addition to the text information that is the message body.
  • the sender's sender information (name information and profile image information) is attached.
  • the message is stored in the terminal storage unit TB23 together with the additional information excluding the post ID, so the post ID that is insufficient at this time Is supplemented.
  • the post ID that is insufficient at this time Is supplemented.
  • the information regarding the member after the change about the 4th it is as having already demonstrated with the transmission other party memory
  • the management unit 233 When any information is received from the management server 10, the management unit 233 first determines whether the information is a message (attached information attached) (step Sb101). If it is a message (if the determination result in step Sb101 is “Yes”), the management unit 233 stores the message in the terminal storage unit TB23 in association with the group ID included in the incidental information (step Sb102). .
  • This storage target is both messages from other terminal devices 20 and unstored messages from the management server.
  • the management unit 233 determines whether the information is a post ID assigned by the management server 10 or not. Is determined (step Sb103). If the information is a posting ID (if the determination result in step Sb103 is “Yes”), the management unit 233 stores the posting ID in the terminal storage unit TB23 in association with the corresponding message (step Sb104). . Further, if the received information is not the posting ID (if the determination result in step Sb103 is “No”), the information is information on the member after the group change. For this reason, the management unit 233 reflects the information regarding the changed member in the registered content of the transmission partner storage unit TB22 (step Sb105).
  • the said storage process is complete
  • the storage process is called. For this reason, every time any information is received from the management server 10, the information received by the storing process is stored and reflected in the storage unit. In this way, in the terminal storage unit TB23, the messages from the other users are stored one by one in association with each other by the storing process, so that a kind of message history is formed. Then, a chat posting / display screen is displayed using such a message history.
  • chat unless a chat is performed, messages from the other users are associated with each group and are not stored in the terminal storage unit TB23, and thus are not displayed on the chat posting / display screen. Therefore, the chat content before joining the group cannot be browsed unless an unstored message is supplemented.
  • the management unit 233 extracts and transfers a message corresponding to the selected group in the terminal storage unit TB23 to the display control unit 241, and also chats corresponding to the group.
  • An instruction to display the posting / display screen is given (step Sb23).
  • FIG. 15 is a diagram illustrating an example of a chat posting / display screen.
  • the display control unit 241 displays messages associated with the selected chat partner group on the display unit 205 in the order of the posting date based on the incidental information. Specifically, the display control unit 241 sorts the forwarded messages in the order of the time indicated by the posting date / time information of the incidental information, and arranges them so that, for example, newer ones are arranged on the upper side of the display unit 205.
  • message display (1) is the newest among message display (1), (2), (3), (7), (9), and it becomes old as it goes down.
  • each message display is as shown in FIG. 16, taking message display (3) as an example.
  • the post date and time (only the time in the figure) is displayed below the profile image.
  • the body of the message is expressed by being surrounded by a speech balloon as if it were emitted from the profile image. In this way, the terminal user of the terminal device 20 and other members share a timeline as if they were chatting.
  • the message displayed on the display unit 205 in FIG. 15 is stored in the terminal storage unit TB23 when the terminal user touches the display part named “Team 246” on the chat partner list screen in FIG. It is an example when it is shown by FIG.
  • the terminal user whose user ID is “aa11” selects the group whose group ID is “ay03” as the chat partner.
  • the group having the group ID “ay03” is selected as the chat partner.
  • (1), (2), (3), (7), and (9) each having the group ID “ay03” are displayed on the display unit 205.
  • a message is displayed. In the example shown in the figure, only five messages are displayed, but the message is displayed by scrolling up and down by an operation such as flicking. In addition, the message display is enlarged or reduced by an operation such as pinching.
  • the chat posting / display screen has display contents as shown in FIG.
  • the terminal user with the user ID “aa11” has selected one of the members with the group ID “ax16”, that is, the member with the user ID “aa13” as the chat partner. Therefore, among the messages registered in the terminal storage unit TB23, (4), (5), (6), (8), and (10) each having the group ID “ax16” are displayed on the display unit 205. Message is displayed.
  • the message display by itself may be displayed in a manner that can be distinguished from the message display by other members.
  • the profile image may be omitted, the balloon shape of the message may be different from the others, or the display color or font of the message body may be different.
  • the chat posting / display screen includes a message input unit 214 and buttons 253, 254, and 255 as shown in FIG. 15 or FIG.
  • the message input unit 214 is an area for inputting a message to be transmitted using a software keyboard or the like
  • the button 253 is a software button for confirming the content of the message input to the message input unit 214 and instructing transmission.
  • the button 254 is a software button for instructing various settings for the currently selected group.
  • the button 255 is a software button for instructing to return to the previous chat partner list screen.
  • the operation detection unit 231 determines whether or not an appropriate operation has been performed on such a chat posting / display screen (step Sb24). If there is no operation, or if the operation is an invalid operation that is not expected even if there is an operation (if the determination result in step Sb24 is “No”), the processing procedure returns to step Sb23. For this reason, the processing procedure circulates through the route of steps Sb23 ⁇ Sb24 ⁇ (Sb23) until some appropriate operation is performed, so the chat posting / display screen continues and the message received in the middle of the circulation route Is stored in the terminal storage unit TB23 by the storage process, the message is additionally displayed on the display unit 205.
  • the following operations are assumed as appropriate operations for the chat posting / display screen. That is, first, an operation on the display part of the button 253, second, an operation on the display part of the button 254, third, an operation on the display part of the button 255, and fourth, other operations. Is assumed. Other operations include a flick for scrolling a message, a pinch for enlarged display, an input operation on the message input unit 214, and the like.
  • step Sb24 When an appropriate operation is performed (when the determination result in step Sb24 is “Yes”), the operation detection unit 231 first performs an operation to transmit a message, that is, an operation on the display portion of the button 253. It is determined whether or not there is (step Sb25). When the operation is on the button 255 (when the determination result of step Sb25 is “Yes”), the operation detection unit 231 displays the content of the message input to the message input unit 214 at the time of the operation, the management unit 233. To supply. The management unit 233 obtains the time information when the instruction is given from the RTC 206 and sets it as the posting date information of the message.
  • time information acquired from the RTC 106 of the management server 10 at the timing when the management server 10 receives the message may be used as message posting date and time information.
  • the management unit 233 acquires the sender information (user name information and profile image information) from the terminal user information storage unit TB21. Then, the management unit 233 adds the terminal user's user ID, post date information, and the chat partner group ID selected in the previous step Sb21 to the message (text) input to the message input unit 214.
  • the sender information is attached as supplementary information and stored in the terminal storage unit TB23. At this time, the posting ID has not been given yet.
  • the management unit 233 supplies the message supplied from the operation detection unit 231 to the transmission unit 236 together with the accompanying information, and the transmission unit 236 transmits the message and the accompanying information to the management server 10 (step Sb26). Thereafter, the processing procedure returns to step Sb23.
  • the receiving unit 121 receives a message or the like, and the management unit 123 assigns a unique posting ID to the received message or the like, and sets the transfer destination of the message to the group ID and the included information. It is specified from the user ID of the sender. Specifically, as described above, the management unit 123 accesses the user / group storage unit TB11, and among the members of the group indicated by the group ID, the user's user ID is excluded from the sender's user ID. The terminal device is specified as the transfer destination of the message.
  • the reason for excluding the sender of the message as the forwarding destination is that the message is stored in the terminal storage unit TB23 in the terminal device 20 of the sender and does not need to be forwarded.
  • the transfer unit 125 transfers the received message to the transfer destination terminal device 20 specified by the management unit 123.
  • the message or the like is stored in association with the group ID in the terminal storage unit TB23 by the storage process (see FIG. 10) (step Sb102). Therefore, in the transfer destination terminal device 20, if the chat application is executed and the same group is selected, the message is additionally displayed on the display unit 205 in the display of the chat posting / display screen (step Sb23). It will be. In this way, the transmitted message is shared among the members of the group.
  • the management server 10 returns the assigned post ID to the terminal device 20 of the terminal user who transmitted the message together with the message reception notification. Thereby, in the terminal device 20, the posting ID returned from the management server 10 is stored in the terminal storage unit TB23 in association with the previous message (step Sb104).
  • step Sb28 the operation detection unit 231 determines whether or not the operation is an operation for designating various settings for the selected group, that is, an operation such as a tap on the display portion of the button 254 (step Sb28).
  • the operation detection unit 231 notifies the management unit 233 to that effect, and the management unit 233 performs group setting described later. Processing is executed (step Sb29). After this group setting process, the processing procedure returns to step Sb23.
  • step Sb30 determines whether or not the operation is an operation for specifying that the operation returns to the chat partner list screen, that is, an operation such as a tap on the display portion of the button 255 (step Sb30).
  • the processing procedure returns to the display of the chat partner list screen in step Sb11.
  • step Sb30 If the operation is not a return operation (if the determination result in step Sb30 is “No”), processing corresponding to the operation performed, specifically, as another operation, for flicking for scroll display or for enlarged display Processing according to the pinch, input operation, etc. is executed (step Sb31). Thereafter, the processing procedure returns to step Sb23.
  • ⁇ Group setting process> When an instruction to set a group is given on the chat posting / display screen, a group setting process is executed.
  • FIG. 11 is a flowchart showing the group setting process.
  • the management unit 233 instructs the display control unit 241 to display the group setting screen on the display unit 205 (step Sb201).
  • FIG. 18 is a diagram illustrating an example of the group setting screen.
  • buttons 255 and 261 to 263 are displayed on the display unit 205.
  • the button 261 is a software button for instructing execution of editing processing of the selected group.
  • the button 262 is a software button for instructing execution of deletion processing of the message history of the selected group. In this message history deletion process, part or all of the message history of the group is deleted.
  • the message associated with the group ID of the group in the terminal storage unit TB23 is before the date and time designated by the posting date and time information It is executed by deleting. Further, all deletion of the message history is performed by deleting all messages associated with the group ID of the group in the terminal storage unit TB23.
  • the button 263 is a software button for instructing supplementation (restoration) of the message history of the selected group.
  • the button 255 is a software button for instructing to return to the previous chat partner list screen.
  • the operation detection unit 231 determines whether or not an appropriate operation has been performed on the display unit 205 (step Sb202).
  • the appropriate operation is an operation on the display portion of the button.
  • step Sb202 If there is no operation (if the determination result in step Sb202 is “No”), the processing procedure returns to step Sb201. For this reason, the display of the group setting screen continues until some appropriate operation is performed.
  • the operation detection unit 231 first performs an operation on the display portion of the button 255, that is, a chat partner list. It is determined whether or not the operation is an instruction to return to the screen (step Sb203). If it is an operation on the display part of the button 255 (if the determination result in step Sb203 is “Yes”), the processing procedure returns to step Sb23. Specifically, the operation detection unit 231 notifies the management unit 233 to that effect, and the management unit 233 instructs the display control unit 241 to return to the display of the chat posting / display screen.
  • step Sb204 the operation detection unit 231 next performs the operation. It is determined whether or not the operation has been performed on the display portion of the button 263, that is, an operation for instructing supplementation of the message history of the selected group. If the operation is on the display portion of the button 263 (if the determination result in step Sb204 is “Yes”, the operation detection unit 231 notifies the management unit 233 of the fact, and the management unit 233 replenishes the message history. (Addition) processing is executed (step Sb205) After this message history replenishment processing, the processing procedure returns to step Sb23.
  • step Sb204 If the operation performed on the group setting screen is not an operation on the display portion of the buttons 255 and 263 (if the determination result in step Sb204 is “No”), the operation is performed using either the button 261 or 262. This is the operation of the display part. Therefore, if the operation detection unit 231 is an operation on the display portion of the button 261, the operation detection unit 231 notifies the management unit 233 to that effect, and the management unit 233 executes the group editing process described above, while the button 261. If it is an operation on the display part, the management unit 233 is notified of this, and the management unit 233 executes the message history deletion process described above (step Sb206). After any processing, the processing procedure returns to step Sb23.
  • FIG. 12 is a diagram illustrating an operation sequence of the message providing system when the message history replenishment process is executed.
  • the management unit 233 instructs the display control unit 241 to display the acceptance partner candidate list screen.
  • the user (requesting user) who requests (requests) supplementation of the message history is prompted to determine the user who obtains consent (step Sb305).
  • the message history replenishment process is executed following the transition of chat partner list screen ⁇ (group selection) ⁇ chat posting / display screen ⁇ (operation of button 254) ⁇ group setting screen ⁇ (operation of button 263). So the group is already selected.
  • the management unit 233 first controls display of information (name information, profile image information) about members other than the requesting user in the group determined to be selected in step Sb21 (see FIG. 9). To the unit 241 to instruct to display a list of candidates for the consent partner.
  • FIG. 19 is a diagram showing an example of a candidate list screen for consent partners.
  • the screen shown in this figure is an example in which user A who is a terminal user touches the display part named “Team 246” on the chat partner list screen (see FIG. 13) in the transition of the previous screen.
  • the three users B, C, and D excluding the user A who is the requesting user are listed together with the profile images.
  • a button 271 for selecting user B as an acceptance partner is displayed in the display unit 205 in association with the name information of user B.
  • buttons 272 and 273 for selecting the users C and D as consent partners are displayed in association with the name information of the users C and D.
  • the operation detecting unit 231 supplies information on the operated button to the managing unit 233.
  • the management unit 233 accesses the terminal storage unit TB23, and reads out the oldest posting date information associated with the group ID of the selected group. Then, the management unit 233 displays the user ID of the requesting user (user A), the user ID of the user (requested user) determined as the consent partner, the group ID, and the posting date / time. The information is transferred to the transmission unit 236, and the transmission unit 236 transmits the information to the management server 10 (step Sb306).
  • the requesting user's terminal device notifies the management server 10 that an application for supplementing the message history has been made, and the message history storage status for the group at the terminal device is reported. become.
  • user B is determined as the consent partner.
  • the receiving unit 121 receives an application and a report from the terminal device 20-1 of the user A who is the requesting user, and supplies it to the management unit 123. While the management unit 123 transfers the application to the application processing unit 122, information necessary for creating the next consent inquiry screen, for example, name information of the requesting user, name information of the group corresponding to the group ID, and the like.
  • the user / group storage unit TB11 and information for accessing the terminal device 20-2 of the requested user (user B) is also acquired from the user / group storage unit TB11 and transferred.
  • the information necessary for creating the consent inquiry screen includes a group name information and a standard notification text using the name information of the request-destination user.
  • the application processing unit 122 when the application processing unit 122 receives an application by the requesting user via the management unit 123, the application processing unit 122 instructs the terminal device 20-2 of the requesting user to respond to the application. This instruction is supplied to the transfer unit 125.
  • the transfer unit 125 transmits information necessary for creating the consent inquiry screen and an instruction from the application processing unit 122 to the terminal device 20-2 of the selected request destination user (user B) (step Sb307).
  • the management unit 233 transfers the information to the display control unit 241 and displays a consent inquiry screen for the display control unit 241. Instruct to display. Thereby, the display control unit 241 displays the consent inquiry screen on the display unit 205 (step Sb308).
  • FIG. 20 is a diagram illustrating an example of the consent inquiry screen.
  • a notification sentence for asking the requesting user about the consent to supplement the message history is displayed by a balloon 281.
  • the name of the group selected by the request-destination user is inserted into the first "" part from the top. Further, the name of the requested user is inserted in the second “” part, the date and time of the posting date information is inserted in the third “” part, and the other part is standard.
  • a button 283 indicating consent for supplementing the message history and a button 284 indicating suspension are displayed.
  • the consent inquiry screen shown here is merely an example, and may not be a screen.
  • the notification text may be displayed in an e-mail format with at least a specific link destination for confirming the will for consent, and the intention of acceptance may be indicated when the user moves to the link destination.
  • step Sb309 it is determined whether or not the requesting user has given consent to the application for supplementing the message history. It should be noted that in the other party user's terminal device 20-2, the inquiry and acceptance of consent may be displayed and confirmed by, for example, interruption prior to the execution of the chat application, and the processing of the chat application is consistent. May be executed as
  • FIG. 20 shows a case where user A who is a member of a group whose group name is “team 246” (group ID: “ay03”) has applied for supplementation of an unstored message as a requesting user. It is an example of the screen which asks other members about acceptance of the application.
  • the chat in this case includes one-on-one chat in addition to group chat. Even in the one-to-one chat, the terminal user may delete the message history by mistake. Therefore, even in the one-to-one chat, the partner may be asked for consent. Since it is not necessary to display the group name, the consent inquiry screen for the chat partner in the one-to-one chat is as shown in FIG.
  • step Sb310 when the request destination user operates the display part of the button 283 and approves replenishment of the message history by the request source user (the determination result in step Sb309 is “ When “Yes”, the management server 10 is notified of consent (step Sb310).
  • the operation to the display part of the button 284 is performed and the requesting user's consent to supplement the message history is suspended, the subsequent processing is not performed, and the terminal device 20-2 of the requesting user Return to the previous operation before displaying the consent inquiry screen. If suspended, the processing after step Sb310 is not executed, so that the unstored message is not supplemented to the terminal device 20-1 of the requesting user. When the request is put on hold, it may be notified to the requesting user's terminal device 20-1.
  • the management unit 123 which also serves as a history processing unit, sends the group ID and posting date / time information previously transmitted from the terminal device 20-1 of the requesting user. From this, unstored messages that are not stored in the terminal device 20-1 are specified (step Sb311a). Specifically, the management unit 123 is a message associated with the group ID among the messages stored in the management storage unit TB13, and the posting date / time information transmitted from the terminal device 20-1 is the posting date / time information. All items older than the information are specified as unstored messages in the terminal device 20-1.
  • the management unit 123 reads out the identified unstored message from the management storage unit TB13 together with associated information (post ID, contributor ID, group ID, post date information, and sender information) to be associated with the transfer unit 125. Then, the transfer unit 125 transmits the unstored message and the accompanying information thereof to the terminal device 20-1 of the requesting user (step Sb312a).
  • the storage process shown in FIG. 10 is executed (step Sb314).
  • the unstored message is stored in the terminal storage unit TB23 in association with the group ID and the like by the storage process (step Sb102). ) Will be.
  • a message that has not been accumulated before is displayed retroactively by performing an operation such as flicking on the display unit 205. be able to.
  • step Sb306 When the user A becomes a requesting user and requests replenishment of an unstored message, the application is transmitted to the management server 10 together with the posting date / time information of (z) (step Sb306).
  • the management server 10 is associated with the group. All messages older than the posted date / time information in (z) are specified as unstored messages in the terminal device 20-1 for the group (step Sb311a). That is, the unstored message specified at this time is a target to be supplemented in the terminal device 20-1.
  • the management server 10 transmits the unstored message specified as the replenishment target and stores it in the terminal storage unit TB23 of the terminal device 20-1. Thereby, in the terminal device 20-1, as a result of storing the unstored message, the message history is supplemented retroactively before the posting date and time of (z).
  • the starting point of the posting date information in the unstored message is when the group is opened. (When the group is opened). For example, when the requesting user applies for an unstored message, the date and time information indicating when the “from” message is desired among the unstored messages is specified, while the management server 10 The section 123) may specify that the posting date / time information is after the date / time information, and transmit it to the requesting terminal device to replenish it. Similarly, when the requesting user applies for an unstored message, date / time information indicating “until when” message chat is desired among the unstored messages may be specified.
  • the request is made.
  • it is set as the structure which determines one consent partner from the members except a prior user, it is not restricted to this, It is good also as a rule which determines one consent partner by a predetermined rule.
  • it may be a rule that determines a user (establisher) who opened the group as an acceptance partner, or a rule that determines a member (inviter) who invited the terminal user to the group as an acceptance partner. .
  • it becomes unnecessary to display the candidate list screen of the consent partner on the terminal device of the request destination user.
  • the management unit 123 of the management server 10 identifies the group's founder from the request destination user and the invitee of the request destination user with reference to the user / group storage unit TB11, and identifies the founder / The inviter may be determined as a request destination user and may be the transmission destination of the consent inquiry screen. It should be noted that such a rule cannot be applied to a request-destination user equal establishment person. In this case, as described above, a configuration may be adopted in which one consent partner is determined from other members.
  • the management unit 123 acquires the oldest posting date and time information associated with the group from each of the group member terminal devices, and requests the user of the oldest terminal device, that is, the terminal device having the most message history, as the requested user. It is good also as a structure automatically determined as. In addition, when two or more consent partners are selected and the consent is obtained earliest among them, the processing after step Sb310a may be executed.
  • FIG. 23 is a diagram illustrating a configuration of a message providing system according to the second embodiment.
  • the management storage unit TB13 of the management server 10 is configured to store all the messages and the like transmitted from the user terminal device 20, but in the second embodiment, this management The storage unit TB13 is eliminated. For this reason, the message etc. which the group member transmitted are memorize
  • the terminal device of the approved requesting user is specified from the stored contents of the terminal storage unit TB23 and is transmitted to the terminal device of the request source user.
  • the message history replenishment process in the group setting process is different. This is the same as in the first embodiment. Therefore, the second embodiment will be described with a focus on message history replenishment processing. Also in the second embodiment, when a message history supplement is instructed on the group setting screen (see FIG. 18), a message history supplement process is executed.
  • FIG. 24 is a diagram illustrating an operation sequence of the message providing system when the message history replenishment process is executed in the second embodiment.
  • the message transmitted by the group member is stored only in the terminal storage unit TB23 of the terminal device 20 of the group member, but the accumulation state of the message in each member is the group.
  • each member differs depending on the time of participation or deletion. For this reason, even if an application for replenishment of unstored messages is made, there is no guarantee that the message history to be replenished will always be stored in the terminal device of the request-destination user who is the consent partner. Therefore, in the second embodiment, the message history storage state of each member is notified so that it can be referred to when the requesting user determines the consent partner. For this reason, steps Sb301 to Sb304 are added as compared with the first embodiment of FIG.
  • the operation detection unit 231 notifies the management unit 233 of the operation content.
  • the management unit 233 transmits, via the transmission unit 236, an application for supplementing the unstored message to the management server 10 together with the group ID of the selected group and the requesting user ID (step Sb301).
  • the receiving unit 121 receives information from the terminal device 20 of the request destination user and supplies the information to the management unit 123.
  • the management unit 123 specifies the terminal device 20 that is the inquiry destination from the group ID and the user ID in order to know the accumulation state of the message history in the terminal device 20 of each member.
  • the terminal device 20 of the member excluding the request source user corresponding to the user ID is specified with the message history storage state as an inquiry destination.
  • the message history storage state For example, in a group consisting of users A, B, C, and D, if user A is a requesting user who applied for supplementation of unstored messages, terminal device 20-2 (user B) , 20-3 (user C) and 20-4 (user D) are specified as inquiry destinations.
  • the management unit 123 displays the accumulation status of the message history associated with the group ID for the identified terminal device 20, that is, the terminal devices 20-2, 20-3, and 20-4 in the above example. Inquiry is made via 125 (step Sb302).
  • the management unit 233 accesses the terminal storage unit TB23 and associates it with the group.
  • the oldest post date information is acquired, and the post date information and the user ID of the terminal device 20 are returned to the management server 10 via the transmission unit 236 (step Sb303).
  • the receiving unit 121 receives post date information and the like from the terminal device 20 of the request destination user and supplies the post date information and the like to the management unit 123, and the management unit 123 receives the post date and time received from the inquired terminal device 20.
  • Information or the like is transmitted to the requesting user's terminal device 20 via the transfer unit 125 (step Sb304).
  • the management unit 233 In the terminal device 20 of the request source user, when the management unit 233 receives the posting date information and the like, the posting date information and the like are supplied to the display control unit 241. Then, the management unit 233 instructs the display control unit 241 to display the acceptance partner candidate list screen. As a result, the user (requesting user) who requests (requests) supplementation of the message history is prompted to determine the user who obtains consent (step Sb305).
  • FIG. 25 is a diagram illustrating an example of a candidate list screen for consent partners.
  • the screen shown in FIG. 12 is an example in which user A who is a terminal user touches the display portion named “Team 246” on the chat partner list screen. It is.
  • the screen shown in FIG. 25 is closer to the display portion of the consent partner, and the bar graphs 281 and 282 based on the posting date information transmitted from the terminal device of each consent partner. , 283 are added.
  • the bar graphs 281, 282, and 283 extend to the left as the date and time indicated by the posted date and time information transmitted from the corresponding user terminal device become older when the right ends are aligned as current. Is displayed.
  • the bar graph is displayed in a state of extending to the left side, that is, extending toward the past. , It is visually determined whether the most messages are stored.
  • the terminal device 20-2 since the bar graph 281 of the user B is the longest, it can be seen that the terminal device 20-2 stores the largest number of message histories.
  • the candidates of the consent partner may be displayed so that they become higher as the storage amount of the message history is larger, that is, rearranged in the longest order of the bar graph.
  • the candidates of the consent partner may be displayed so that they become higher as the storage amount of the message history is larger, that is, rearranged in the longest order of the bar graph.
  • a bar graph 280 based on the posting date / time information of the user A who is the request destination user is displayed for comparison. If the posting date / time information transmitted from the terminal device of a member of a group is newer than the oldest posting date / time information associated with the group in the request destination user's terminal device, The unstored message of the requesting user is not stored. For this reason, such a member (user C in the example in the figure) may be excluded from the candidate list of consent partners.
  • the management unit 233 displays the request source as in the first embodiment.
  • the user ID of the user (user A), the user ID of the user B (requested user) determined as the consent partner, the group ID, and the posting date / time information are transferred to the transmission unit 236,
  • the transmission unit 236 transmits these pieces of information to the management server 10 (step Sb306).
  • the requesting user's terminal device notifies the management server 10 that an application for supplementing the message history has been made, and the message history storage status for the group at the terminal device is reported. become.
  • the management unit 123 receives the information necessary for creating the consent inquiry screen and the request destination user.
  • Information for accessing the terminal device 20-2 is acquired and supplied to the transfer unit 125, while the application processing unit 122 responds to the request to the terminal device 20-2 of the request destination user. Indicate what should be done.
  • This instruction is supplied to the transfer unit 125.
  • the transfer unit 125 sends the information required for creating the consent inquiry screen (including the user ID of the request source user) and the instruction from the application processing unit 122 to the terminal device 20-2 of the selected request destination user. Transmit (step Sb307).
  • the consent inquiry screen is displayed (step Sb308), and it is determined whether or not the requesting user has consented to supplementing the message history (step Sb309).
  • the terminal device of the request destination user replaces the management server 10
  • an unstored message is specified based on the group ID and the posting date / time information previously transmitted from the terminal device of the requesting user (step Sb311b).
  • the management unit 233 associates the message stored in the terminal storage unit TB23 with the group ID, and the posting date / time information is used by the request source. All messages older than the posted date information transmitted from the user are specified as unstored messages at the requesting user. Subsequently, the management unit 233 reads the identified unstored message from the terminal storage unit TB23 together with associated information (post ID, contributor ID, group ID, post date information, and sender information) associated therewith. At this time, the management unit 233 attaches the user ID of the requesting user included in the information necessary for creating the previous consent inquiry screen to the read unstored message together with the accompanying information, 236. The transmission unit 236 transmits the unstored message or the like to the management server 10 (step Sb312b).
  • the management server 10 When the management server 10 receives an unstored message or the like from the terminal device of the request-destination user, the management server 10 transmits (transfers) the unstored message together with the accompanying information to the request-source user's terminal device (step Sb313). At this time, in the management server 10, the incidental information of the unstored message received from the requesting user's terminal device includes the posting ID. On the other hand, when a user performs a chat message transmission operation on the terminal device (step Sb26), the incidental information of the message received from the terminal device by the management server 10 does not include the posting ID.
  • the management unit (history processing unit) 123 of the management server 10 receives a message from the terminal device, if the post ID is included in the incidental information of the message, the message is transmitted to the requesting user. It is determined that the message is an unstored message to be transferred to the terminal device, and the unstored message and incidental information are transmitted with the user ID of the attached request source user as the transfer destination. On the other hand, when the management unit 123 receives a message from the terminal device and the post ID is not included in the accompanying information of the message, the managing unit 123 sets the message and the accompanying information among the group members specified by the group ID. The sending of the member terminal device excluding the contributor ID with the posting ID is as described above.
  • step Sb3114 when the management unit 233 receives an unstored message from the management server 10, a storage process (see FIG. 10) is executed (step Sb314). For this reason, the unstored message is stored in the terminal storage unit TB23 in association with the group ID and the like (step Sb102), so the unstored message is supplemented in the group. For this reason, in the request source user's terminal device 20, on the chat posting / display screen (step Sb23), the supplemented message can be displayed retroactively by an operation such as flicking on the display unit 205.
  • step Sb311b when the request destination user operates the button 271 corresponding to the user B, in the terminal device of the user B who is the request destination user, all items older than the posted date / time information in (z) Is identified as an unaccumulated message to be replenished (step Sb311b).
  • the unstored message specified as the replenishment target is transmitted from the requesting user's terminal device to the management server 10 (step Sb312b), and the management server 10 transfers the unstored message to the requesting user's terminal device. (Step Sb313) and stored in the terminal storage unit TB23.
  • the accumulated history is replenished before the posting date / time information of (z).
  • the non-accumulated message to be supplemented is not stored on the management server 10 side, but is stored on the terminal device side of the partner user who is a member. For this reason, the oldest non-stored message to be replenished is not always the time when the group is opened as in the first embodiment.
  • the requesting user may specify “from when” or “until”, but the corresponding message is any terminal device of the group member. It is not always remembered.
  • the candidate list screen of the consent partner is displayed.
  • a bar graph indicating the history accumulation state may be sequentially displayed in association with the member. Further, the bar graph indicating the holding state of the member's message history is not unique to the second embodiment, and may be displayed similarly in the first embodiment.
  • an unstored message is not necessarily stored, for example, an opener / invite person may be determined as an approved partner according to a predetermined rule as in the first embodiment.
  • the terminal device user who has the largest number of message histories may be automatically determined as the requested user. That is, in step Sb304, when the management unit 123 acquires post date information and the like from the inquired terminal device 20, the user of the terminal device having the most message history is found. For this reason, the management unit 123 may determine the user of the terminal device having the largest number of message histories as the request destination user, and inquire the request destination user about approval of the unstored message. Therefore, the management unit 123 does not need to display a list display screen of the consent partner for the requesting user. In the second embodiment, two or more approval partners are selected, and if approval is obtained earliest among them, the processing after step Sb311b may be executed in the terminal device of the approver at that time.
  • FIG. 28 is a diagram illustrating a configuration of a message providing system according to the third embodiment.
  • all messages transmitted from the terminal device 20 of the user are stored in the management storage unit TB13 of the management server 10, and a message related to a certain user is used for the usage.
  • a terminal storage unit TB23 is eliminated from the configuration of the terminal storage unit TB23.
  • management storage units TB33-1, TB33-2, TB33-3, TB33-4,... Corresponding to each user are provided.
  • the terminal storage unit TB23 constructed in the user terminal device 20 in the first embodiment is replaced with a management storage unit TB33 individually corresponding to each user on the management server 10 side in the third embodiment. ⁇ 1, TB33-2, TB33-3, TB33-4,... Therefore, when the processing of the chat posting / display screen (step Sb23) is executed in the terminal device 20 of a certain user, for example, the terminal device 20 communicates with the management server 10 and on the management server 10 side. A message or the like associated with the group is acquired from the terminal storage unit corresponding to the user.
  • the third embodiment is substantially the same as the first embodiment in terms of operation, except that the location where the terminal storage unit is provided is different. Therefore, further explanation is omitted.
  • a message history in which messages transmitted from the users after joining the group are stored in the terminal device 20 of the user.
  • the management device for example, the management server 10 provided so as to be viewable is a part or all of the users excluding the requesting user from the requesting user who is one user among the plurality of users.
  • An application processing unit 122 that accepts an application for a request-destination user and an unstored message that is not accumulated in a message history corresponding to the request-source user are acquired from a message history corresponding to the request-destination user according to the application,
  • a history processing unit 123 that performs processing to be added to the message history corresponding to the requesting user.
  • an unstored message that is not stored in the message history corresponding to the requesting user is acquired from the message history corresponding to the requesting user according to the requesting user application, Since it is added to the message history corresponding to the former user, the past message history that could not be browsed can be browsed.
  • the message sometimes refers to text information that is a text, but is not limited thereto, and may be a still image, a moving image, or a voice, or may include these. Therefore, the browsing of the message includes reproduction of moving images and sounds. Note that “perform processing” includes both the case where the user executes the processing and the case where the other person is instructed to execute the processing.
  • “Accepting an application” is not necessary until the application is accepted, and is used to mean that the application has been accepted (requested user).
  • “A message transmitted from a user” refers to a message transmitted (posted or transmitted) from a terminal device operated by the user based on the operation of the user. “Part or all of the users excluding the requesting user” may be one of the remaining users excluding the requesting user from the users participating in the group, or the remaining users. It is used in the sense that everyone is okay. Further, the “message history corresponding to the requesting user” may be message histories that are different from each other associated with each user, or may be a message history common to the users.
  • the history processing unit 123 displays an unstored message that is not stored in the message history corresponding to the requesting user, and a message that corresponds to the requesting user who accepted the application.
  • a configuration may be adopted in which processing is acquired from the history and added to the message history corresponding to the requesting user.
  • the message history corresponding to each of a plurality of users is stored in the management storage unit TB13, and the history processing unit 123 is not yet stored from the message history stored in the management storage unit TB13 corresponding to the request destination user according to the application.
  • the stored message may be acquired and added to the message history corresponding to the requesting user.
  • the message history corresponding to the requesting user may be stored in the terminal device 20 of the requesting user, or the management server 10 can distinguish the plurality of users. You may remember.
  • the message history corresponding to each of the plurality of users is stored in the terminal storage unit TB23 of each terminal device 20, and the history processing unit 123 stores the message history in the terminal storage unit TB23 corresponding to the requested user according to the application.
  • a configuration may be adopted in which an unstored message is acquired from the acquired message history, and the acquired unstored message is added to the message history stored in the terminal storage unit TB23 corresponding to the requesting user.
  • the message included in the message history is associated with the user who sent the message and the date and time information sent, and is the oldest date and time information among the messages included in the message history corresponding to the requesting user. Based on this, an unstored message is identified among the messages included in the message history corresponding to the requesting user, and the history processing unit 123 adds the identified unstored message to the message history corresponding to the requesting user. It is good also as a mode which makes it process. There are three or more users participating in the group, and the application processing unit 122 selects the request destination user selected by the request source user from among the plurality of users excluding the request source user. It is good also as an aspect which receives the application with respect to.
  • the application processing unit 122 receives an application from the requesting user, the requesting user among the plurality of users according to a predetermined rule. It is good also as an aspect which determines one user as a request destination user who responds to application from the users except for.
  • the predetermined rule may be a user who has the largest number of corresponding message histories among users other than the requesting user among a plurality of users as a request-destination user who responds to the application.
  • the control method of the management device for example, the message management method of the management server 10 is: For each of a plurality of users participating in the group, a message history in which messages transmitted from the users after the participation in the group are accumulated is provided so as to be viewable on the terminal device 10 of the user.
  • a message management method A step of accepting an application from a requesting user who is one of a plurality of users to a requesting user who is a part or all of the users excluding the requesting user, and the requesting user Obtaining a non-accumulated message that is not accumulated in the message history corresponding to the request from the message history corresponding to the requesting user according to the application, and adding the message to the message history corresponding to the requesting user; Is provided.
  • the program browses a message history in which messages transmitted from each other's users since joining the group are viewed on the user's terminal device. Accepting requests for requesting users who are part or all of the users excluding the requesting user from the requesting user who is one of the multiple users. Acquires unstored messages that are not stored in the message history corresponding to the request processing user and the requesting user from the message history corresponding to the requesting user who responds to the request, and corresponds to the requesting user It is made to function as a history processing unit that performs processing to be added to the history.
  • the program may be recorded on a recording medium. If this recording medium is used, the program can be installed in the computer, for example.
  • the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM.
  • ⁇ Account deletion and re-registration> For example, when chat is being performed in a group consisting of two users F and G, when the user F uninstalls the chat app, the user F chat account is deleted. At the same time, in the terminal device of the user F, the message history that has been exchanged with the user G so far is also deleted. In this state, in order for the user F to participate in the chat using the chat application again, it is necessary to acquire a new account. At this time, since a new (different from the previous) user ID is given to the user F, the user F as viewed from the user G is treated as another user F1. On the other hand, since it seems that the user F has been withdrawn from the above group, the user G is in a state of participating in the group alone. Here, when the user F1 joins the group by the invitation of the user G, the group is composed of two users, the user F1 and the user G. Therefore, the user F1 and the user G 1 One-on-one chat becomes possible.
  • the user G Since the message history exchanged with the user G is deleted in the terminal device of the user F1 (F), if the user F1 (F) wants to recover it, the user G is supplemented with unstored messages. Will be applied for. If the application is approved, the deleted message history is restored in the terminal device of the user F1 (F) (in the second embodiment, the user G exchanges with the user F). Only if the deleted message has not been deleted). However, when the user F deletes the account, the user / group storage unit TB11 of the management server 10 rewrites the name information of the user F to, for example, “unknown” and the profile image of the user F It will be in a deleted state.
  • the message history stored in the management storage unit TB13 is synchronized with the state of the user / group storage unit TB11 of the management server 10, the message history is stored in the terminal device of the user F1 by the management storage unit TB13. Even after the resurrection, the name information of the message history includes the name of the user G, “unknown”, and the user F1.
  • the message history stored in the terminal storage unit TB23 of the user G is synchronized with the state of the user / group storage unit TB11 of the management server 10
  • the message is transmitted from the terminal device of the user F1. Even if the history is revived by the terminal storage unit TB23, the user G, “unknown”, and the user F1 still appear in the name information of the history of the message.
  • the terminal device is provided with a function of replacing “unknown” with the name of the user F1 and registering the profile image of the user F1 as the profile image deleted for “unknown”. Then, it becomes possible to treat as the “unknown” equal user F1.
  • the button 254 for instructing the transition to the group setting screen is provided on the chat posting / display screen (FIGS. 15 and 17), but may be provided on a higher-level chat partner list screen, for example.
  • the chat partner is not selected at that stage, and therefore the chat partner (group) to be set may be selected and then the setting screen may be displayed.
  • the chat partner list screen if the operation is different from the touch operation for shifting to the chat posting / display screen with the chat partner (group) (for example, long press operation), the group setting screen is displayed. You may do it.
  • management unit 123 is expressed as an integrated block that also serves as a history processing unit, but may be considered as a separate block.
  • ⁇ Message format> For chat chat, only text is used, but a voice signal, a still image, or a moving image may be used, or a combination of these may be used as appropriate.
  • the message includes an audio signal or a moving image, reproduction of these is browsing.
  • the terminal device 20 has been described as a configuration having the touch panel 220, it may be configured to have operation elements such as hardware keys and switches and perform various input operations via these operation elements.
  • the management server 10 includes and manages the database 118, but may be managed by a server other than the management server 10, that is, managed by cloud computing.
  • the terminal device 20 is configured to include and manage the database 218, but may be managed by cloud computing by the management server 10 or another server. That is, the management storage units TB13, TB33-1 and the like may be managed by a server other than the management server 10, and the terminal storage unit TB23 may be managed by another server.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention concerne le remplissage d'un historique de messages dans une application de conversation en ligne. Selon l'invention, un serveur de gestion peut fournir un historique de messages de messages accumulés, envoyés entre chacun des utilisateurs d'un groupe après qu'ils ont rejoint le groupe, d'une manière qui peut être visualisée sur le dispositif terminal d'un utilisateur. Le serveur de gestion permet de plus à un utilisateur demandeur, qui est l'un des utilisateurs parmi la pluralité d'utilisateurs, d'exécuter une opération d'établissement d'une requête d'application à un ou plusieurs utilisateurs faisant l'objet d'une demande, qui sont des utilisateurs autres que l'utilisateur demandeur et, dans la mesure où une application est approuvée par un utilisateur faisant l'objet de la demande, entraîne un traitement selon lequel les messages accumulés qui n'ont pas été accumulés dans l'historique de messages de l'utilisateur demandeur font l'objet d'une acquisition à partir de l'historique de messages de l'utilisateur faisant l'objet de la demande qui a approuvé l'application et sont ajoutés à l'historique de messages de l'utilisateur demandeur.
PCT/JP2013/068626 2012-09-21 2013-07-08 Dispositif de gestion, procédé et programme d'administration de messages WO2014045679A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2012207934A JP5631947B2 (ja) 2012-09-21 2012-09-21 管理装置、メッセージ管理方法およびプログラム
JP2012-207934 2012-09-21

Publications (1)

Publication Number Publication Date
WO2014045679A1 true WO2014045679A1 (fr) 2014-03-27

Family

ID=50341005

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2013/068626 WO2014045679A1 (fr) 2012-09-21 2013-07-08 Dispositif de gestion, procédé et programme d'administration de messages

Country Status (2)

Country Link
JP (1) JP5631947B2 (fr)
WO (1) WO2014045679A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015201181A (ja) * 2014-04-01 2015-11-12 株式会社リコー 情報処理システム及び情報保存方法
CN110557322A (zh) * 2018-05-30 2019-12-10 富士施乐株式会社 信息处理装置和非暂时性计算机可读介质
US11024286B2 (en) 2016-11-08 2021-06-01 National Institute Of Information And Communications Technology Spoken dialog system, spoken dialog device, user terminal, and spoken dialog method, retrieving past dialog for new participant
EP4340325A1 (fr) * 2022-09-15 2024-03-20 Samsung SDS Co., Ltd. Dispositif et procédé de récupération d'historique de dialogue en ligne précédent de salle de dialogue en ligne

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10845982B2 (en) 2014-04-28 2020-11-24 Facebook, Inc. Providing intelligent transcriptions of sound messages in a messaging application
CN104506410B (zh) * 2014-12-03 2017-10-20 小米科技有限责任公司 即时通讯的方法和装置
JP2017042362A (ja) * 2015-08-26 2017-03-02 株式会社スクウェア・エニックス チャットシステム用プログラム、およびチャットシステム
JP6159782B2 (ja) * 2015-11-26 2017-07-05 Ｌｉｎｅ株式会社 情報処理装置の制御方法、情報処理装置および制御プログラム並びに端末の制御方法および端末制御プログラム
JP2017152032A (ja) * 2017-04-26 2017-08-31 Ｌｉｎｅ株式会社 情報処理装置の制御方法、情報処理装置および制御プログラム並びに端末の制御方法および端末制御プログラム
JP7196425B2 (ja) * 2018-05-30 2022-12-27 富士フイルムビジネスイノベーション株式会社 情報処理装置及びプログラム
JP7124458B2 (ja) * 2018-05-30 2022-08-24 富士フイルムビジネスイノベーション株式会社 情報処理装置及びプログラム
JP2021071898A (ja) * 2019-10-30 2021-05-06 富士ゼロックス株式会社 情報処理装置、情報処理システム及びプログラム
JP2021177321A (ja) * 2020-05-08 2021-11-11 Ｌｉｎｅ株式会社 プログラム、表示方法、端末

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002108792A (ja) * 2000-09-26 2002-04-12 Nec Software Hokkaido Ltd チャット方法
JP2007108953A (ja) * 2005-10-12 2007-04-26 Vision Arts Kk チャットプログラム
WO2009144862A1 (fr) * 2008-05-28 2009-12-03 パナソニック株式会社 Dispositif terminal de communication, procédé de contrôle de communication et programme de contrôle de communication

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002108792A (ja) * 2000-09-26 2002-04-12 Nec Software Hokkaido Ltd チャット方法
JP2007108953A (ja) * 2005-10-12 2007-04-26 Vision Arts Kk チャットプログラム
WO2009144862A1 (fr) * 2008-05-28 2009-12-03 パナソニック株式会社 Dispositif terminal de communication, procédé de contrôle de communication et programme de contrôle de communication

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015201181A (ja) * 2014-04-01 2015-11-12 株式会社リコー 情報処理システム及び情報保存方法
US11024286B2 (en) 2016-11-08 2021-06-01 National Institute Of Information And Communications Technology Spoken dialog system, spoken dialog device, user terminal, and spoken dialog method, retrieving past dialog for new participant
CN110557322A (zh) * 2018-05-30 2019-12-10 富士施乐株式会社 信息处理装置和非暂时性计算机可读介质
EP4340325A1 (fr) * 2022-09-15 2024-03-20 Samsung SDS Co., Ltd. Dispositif et procédé de récupération d'historique de dialogue en ligne précédent de salle de dialogue en ligne

Also Published As

Publication number Publication date
JP5631947B2 (ja) 2014-11-26
JP2014063342A (ja) 2014-04-10

Similar Documents

Publication Publication Date Title
JP5631947B2 (ja) 管理装置、メッセージ管理方法およびプログラム
JP6055731B2 (ja) メンバー追加を拡張するためのメッセージングサービスシステム及びその方法
KR101521332B1 (ko) 인스턴트 메시징 서비스 및 인스턴트 메시징 서비스로부터 확장된 복수의 서비스들을 제공하는 방법
JP6667993B2 (ja) サーバ、サーバの制御方法およびプログラム
JP7002082B2 (ja) 業務客体基盤の業務活動処理装置及び方法
US11662877B2 (en) Image distribution method, image distribution server device and chat system
CN103959708B (zh) 包括用于协作远程应用共享和注释的交互式数字表层的非耦合应用扩展
US11010012B2 (en) Display control method, first terminal, and storage medium
JP2007140696A (ja) コミュニケーションシステム、機器およびプログラム
KR101631287B1 (ko) 채팅방 관리 방법 및 단말
JP6145614B2 (ja) 端末装置、メッセージ表示システム、端末装置の制御方法およびプログラム
JP2020047000A (ja) 情報処理システム、方法及びプログラム
JP5995621B2 (ja) 端末装置、システム、端末装置の制御方法およびプログラム
JP2023522672A (ja) 情報インタラクション方法、装置、電子機器、および記憶媒体
JP5903011B2 (ja) 端末装置、端末装置の制御方法およびプログラム
JP2005050113A (ja) インスタントメッセージ利用システム，送信クライアント，中継サーバ，受信クライアント，インスタントメッセージ利用方法およびそのプログラム。
JP2009070395A (ja) コミュニケーションシステム、機器およびプログラム
JP6014416B2 (ja) 端末装置、管理サーバ、端末装置の制御方法およびプログラム
JP2011164844A (ja) コミュニティシステム、コミュニティシステム制御サーバおよびコミュニティシステム提供方法
JP6234099B2 (ja) 情報通信システム
JP7405344B2 (ja) 組織情報連絡システム、組織情報連絡システムのプログラム
JP2019179365A (ja) 会議装置、会議システム、情報処理方法およびプログラム
JP7244245B2 (ja) 情報処理方法、プログラム、端末、情報処理装置、電子装置
KR102427253B1 (ko) Sns 상에서 정보를 결합한 의사 전달 시스템 및 방법
JP6639066B2 (ja) 端末、端末の制御方法およびプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13839529

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13839529

Country of ref document: EP

Kind code of ref document: A1