US20030197730A1 - Display control method and device - Google Patents

Display control method and device Download PDF

Info

Publication number
US20030197730A1
US20030197730A1 US10/431,434 US43143403A US2003197730A1 US 20030197730 A1 US20030197730 A1 US 20030197730A1 US 43143403 A US43143403 A US 43143403A US 2003197730 A1 US2003197730 A1 US 2003197730A1
Authority
US
United States
Prior art keywords
message
messages
thread
display control
network
Prior art date
Legal status (The legal status 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 status listed.)
Abandoned
Application number
US10/431,434
Inventor
Jun Kakuta
Satoshi Okuyama
Ai Manabe
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
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 Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to US10/431,434 priority Critical patent/US20030197730A1/en
Publication of US20030197730A1 publication Critical patent/US20030197730A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1827Network arrangements for conference optimisation or adaptation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management

Definitions

  • the present invention relates to technology for promoting user convenience in a system in which users share identical networks mutually, enabling simultaneous conversation. More particularly, it relates to technology that makes conversational display easy to view, in a textual conversation system such as IRC (Internet Relay Chat).
  • IRC Internet Relay Chat
  • IRC means a chat system formed by connecting a chat server with a plurality of chat clients on the Internet, and the plurality of chat clients sharing the same virtual space, enabling simultaneous conversation.
  • channel means a virtual space that chat clients share in IRC.
  • a “nickname” utilized in IRC means identifying information for specifying a user.
  • a “topic” means the subject of a channel used in IRC.
  • Mode means information that indicates characteristics of a channel utilized in IRC.
  • Text conversation systems for conducting conversation using text among information terminals on a network have heretofore been offered.
  • Web chat systems that keep a log of messages that WWW (World Wide Web) servers issue have been offered.
  • users carry out conversations via text by sharing a Web Page log (message record).
  • a system for conducting conversation by manipulating user alter egos known as “avatars” within a virtual world has also been offered.
  • IRC in which chat servers signal-distribute conversation to a plurality of chat clients in conformity with IRC protocols have also been offered.
  • the number of participants increases, it can happen that a number of different topics will be going on at once within the same display area.
  • the speaker's gaze can distinguish topics, as can approaching the person speaking.
  • conversations on the Internet however, wherein the condition of the other party cannot be seen, conversations relating to a plurality of topics end up being intermingled and displayed within the same area.
  • the object of the present invention is to display topics respectively segregated from other topics wherein a plurality of topics are under way simultaneously on a network, to promote accurate and efficient communication.
  • the present invention is a display control method utilized in a chat system in which users on information terminals share identical networks mutually, enabling text conversation, the display control method:
  • a channel for example designate particular users, instructing the creation of a message group.
  • Message group information concerned with the created message group is reported to other chat clients in the channel.
  • Message group information may be, for example, nicknames of the users that form the message group, a message group ID, the message group author, and the message group name.
  • Issuing messages to a message group sends that messages out on the channel.
  • the way the message group is displayed conforms to user instructions.
  • the message group can be displayed in the same display area the channel is displayed, or can be displayed independently of the channel display area.
  • the invention is a display control device utilized in a chat device wherein, sharing an identical network mutually, transmission/reception of text messages is possible, and presents the display control device provided with creating means, reporting means, memory means and input/output control means.
  • the creating means correlates messages on the network according to user instructions and creates message groups and predetermined message group information relating to the message groups.
  • the reporting means transmits/receives the created message group information to and from other among display control devices on the network.
  • the memory means stores the message group information.
  • the input/output control means obtains the message groups from the chat device and in accordance with user instructions, enables display of the message groups independently of messages on the network.
  • a user designates the individual users constituting a message group.
  • the creation means creates the message group out of the messages from the designated member users.
  • the creation means also creates message group IDs, and predetermined message group information containing member users and the creating user, which is stored in the memory means.
  • the created message group information is reported by the reporting means to other display control devices in the channel.
  • the report may be either via a chat client, or directly transmitted/received among the display control devices.
  • Other display control devices accept from the reporting means message group information that the other display control devices have created, which is stored in the memory means.
  • the message group can be displayed in a window separate from the messages within the channel.
  • the message groups are obtainable, for example, from a message log that the chat client has created.
  • the present invention in another aspect presents a display control device wherein the creating means in the second aspect of the invention accepts operations directed to the message groups and updates the message group information.
  • the creating means accepts message group link instructions and creates message group information in which linked message groups and the message group link source are correlated.
  • the invention presents a display control device wherein the input/output control means in the second aspect of the invention accepts messages in which the message groups are designated and acquires from the network or sends to the network messages for the message groups.
  • the input/output control means for example in a window displaying the message groups, deems inputted messages to be messages to the message group, and sends them out to the channel.
  • the input/output control means also obtains from the channel messages to message groups transmitted from other display control devices. According to user instructions, the obtained messages are displayed in a window for message groups or in an ordinary chat window.
  • the present invention in yet another aspect presents a display control device wherein the creation means in the second aspect of the invention correlates messages within the network based on selection of the chat device from a user, and creates message groups out of messages from the selected chat devices and message group information containing information that designates the selected chat devices.
  • the creation means creates a message group that will be constituted by messages from the chosen users.
  • Information specifying the users comprising the message group, nicknames, for example, are contained in the message group information. Selecting user names, or selecting user messages can be given as methods of choosing users.
  • the invention presents a display control device wherein that of the second aspect of the invention is provided with a message list correlating messages within the network and message identifying information specifying the messages; wherein the creation means creates, based on selection of the messages from a user, message groups containing the selected messages and message group information containing message-identifying information for the selected messages.
  • the present invention in another aspect presents a display control device wherein the creation means in the second aspect of the invention creates message group information in which a disclosure level of the message groups that are created is contained.
  • the disclosure level setting may be designated by the individual users, or automatically set in according to the type of message group. For example, wherein the message group is created by designating individual users, the creating means sets the disclosure level to “Private.” On the other hand, wherein the message group is created by designating messages, the creating means sets the disclosure level to “Public.”
  • the invention presents a display control device wherein message-group identifying information specifying the message groups is contained in the message group information.
  • Including a message group ID in the message group information enables sharing message groups mutually within the same channel. Consequently, the created message groups can be displayed in common among the users according to each user's respective preference.
  • the invention in yet another aspect presents a display control device wherein the input/output control means in the second aspect of the invention judges based on the message group information whether to display the message groups, and displays the message groups based on the judgment.
  • the input/output control means decides whether or not to display the message group according to, for example, the before-described disclosure level or to the type of message group. Specifically, if the disclosure level is “Public,” the decision is “displayable.” 0 Conversely, if the display level is “Closed to Public,” wherein chat clients constitute the message group, the decision is “not displayable.”
  • the present invention presents a computer-readable recording medium on which is recorded a display control program utilized in a chat device wherein, sharing an identical network mutually, transmission/reception of messages through text is possible, the computer-readable recording medium on which is recorded the display control program for executing steps A-D below.
  • Examples of a computer-readable recording medium herein include computer-readable/writeable floppy disks, hard disks, semiconductor memory, CD-ROMs, DVDs (digital video disks), and MOs (magneto-optical disks).
  • Utilizing the present invention enables the conversation of users chatting by sharing a network such as an electronic meeting room to be displayed to suit each person's liking. Moreover, users can also designate that one another's displays be made in common, enabling them to carry out efficient communication.
  • FIG. 1 is a functional block diagram showing the configuration of a display control device pertaining to the present invention in a first embodiment
  • FIG. 2 is a conceptual illustration of a message list
  • FIG. 3 is a conceptual illustration of an administration table
  • FIG. 4 is a screen example showing a chat client pertaining to the present embodiment, in its state just after activation;
  • FIG. 5 is a screen example following connection to a chat server
  • FIG. 6 is a diagram showing an example of a confirmation window
  • FIG. 7 is a diagram showing an example of a thread window
  • FIG. 8 is a screen example wherein selecting messages creates a thread
  • FIG. 9 is a diagram showing an example of a new thread window wherein users and messages are not selected.
  • FIG. 10 is a diagram showing an example of a selection window wherein “Link” is selected
  • FIG. 11 is a conceptual illustration of a post-thread-linking administration table:
  • FIG. 12 is a diagram showing an example of a selection window wherein “Display” is selected
  • FIG. 13 is a flowchart depicting flow in an input control process that the display control device carries out
  • FIG. 14 is a flowchart depicting flow in an output control process that the display control device carries out
  • FIG. 15 is a flowchart depicting flow in main routine that the display control device carries out
  • FIG. 16 is a flowchart depicting flow in a creation process subroutine
  • FIG. 17 is a flowchart depicting flow in a linking process subroutine
  • FIG. 18 is a flowchart depicting flow in a cancellation process subroutine.
  • FIG. 19 is a flowchart depicting flow in a display process subroutine.
  • FIG. 1 is a function block diagram illustrating the configuration of a display control device in connection with the first embodiment of the present invention.
  • the explanation takes an example in the present embodiment wherein the display control device is adapted to an IRC chat client.
  • the chat client 3 in FIG. 1 can converse with other chat clients via the Internet 1 .
  • the chat client 3 has a display control device 2 , a first input/output control module 31 , a control module 32 , a second input/output control module 33 , and a memory 4 .
  • a brief explanation will be made of the configuration of the chat client 3 apart from the display control device 2 .
  • the first input/output control module 31 carries out data transmission/reception between it and the Internet 1 .
  • the memory 4 stores predetermined information relating to the channels in which the chat client 3 participates. “Predetermined information” is, for example, channel name, nicknames of users in the channel, topics, and channel attributes. A log of messages in the channel is also stored in the memory 4 .
  • the control module 32 ordinarily transmits/receives data between it and the Internet 1 via the first input/output control module 31 . In the present embodiment, however, the control module 32 carries out data transmission/reception via the display control device 2 . The predetermined information among the data received is stored in the memory 4 . Also, messages received from other chat clients are sent to the second input/output control module 33 and displayed. Further, the control module 32 accepts input messages from the second input/output control module 33 and sends them out on the channel via the display control device 2 .
  • the second input/output control module 33 accepts received messages from the control module 32 and outputs them on an input/output section display. The second input/output control module 33 also sends inputted messages from the input/output section to the control module 32 .
  • the display control device 2 has a creation module 21 , a reporting module 22 , a third input/output control module 23 , and an administration module 24 as well as the memory 4 .
  • the display control device 2 shares the memory 4 with the chat client 3 .
  • the memory 4 holds a message list and an administration table, which it adds to predetermined information relating to the channels.
  • a diagram conceptually illustrating a created message list in the memory 4 is shown in FIG. 2.
  • Message lists are created for each channel. Thread IDs (in the figures, noted as “Th.ID”) that specify message groups (called “threads” hereinafter), message IDs that specify messages, and messages are correlated and stored in the message list. It is preferable that the message list be created by appending the message IDs and the thread IDs to the message log that the chat client control module 32 creates.
  • the message IDs are identifying information attached in order to specify the messages, and are, for example, consecutive numbers.
  • the thread IDs are identifying information for specifying threads.
  • the FIG. 2 message list is a message list for the channel “CH1.”
  • the messages in which the message IDs are “1,”“5” and “6” are included in the thread that is specified with thread ID “Th1.”
  • the other messages are included in the thread that is specified with thread ID “Th2.”
  • Thread information relating to each of the threads is described in the administration table.
  • Thread information in the present instance consists of thread IDS, titles, authors, member users, message IDs, link sources, forwarding destination, disclosure level and status.
  • “Titles” are preferably text information for displaying the threads to the users. Preferably, the users can set the titles arbitrarily. “Author” is the nickname of the user who created the thread. “Member users” are the users who construct the thread. This, as will be discussed later, is information that is described wherein the threads are created by selecting the users. In the present embodiment, the threads are created by the users or by selecting any message.
  • Link source as will be discussed later is a linked thread ID wherein a plurality of threads is linked. It is information that is described in the administration table of the user linked to the thread. “Forwarding destination” is information for expressing link sources of threads linked by other users.
  • the creation module 21 receives from the administration module 23 instructions for a process on threads. Following the instructed process, the creation module 21 updates the administration table. As concrete examples of the process on threads, creation, segregation, linking and display can be given. For example, when thread creation is instructed, the creation module 21 creates thread information and records it in the administration table. The creation module 21 also reports updated thread information to the reporting module 22 .
  • the reporting module 22 transmits/receives thread information via the administration module 23 . Specifically, the reporting module 22 receives thread information from other display control devices and updates the administration table and the message list. The reporting module 22 also sends thread information reported from the creation module 21 out to the other display control devices within the channel. Establishing predetermined thread commands is preferable for transmitting/receiving the thread information. For instance, an example of a thread command to create “Th1” is shown below.
  • Thread commands for reporting thread-linking, separating, and deleting are established likewise.
  • the administration module 23 transmits/receives messages via the first input/output control module 31 and updates the message list and the administration table.
  • the administration module 23 judges whether or not received messages are messages in the threads. This decision is executed, for example, according to whether a thread ID is present in the message. Wherein the administration module 23 has judged a message to be in the threads, it sends the message out to the control module 32 and the third input/output module 24 in accordance with user instructions.
  • the administration module 23 also receives messages in the thread window from the third input/output module 24 .
  • the administration module 23 sends the received messages and thread IDs out to the channel.
  • the administration module 23 receives from the third input/output module 24 selection of processes on threads, and directs the processes to the creation module 21 . Wherein it has received selected users and messages from the third input/output module 24 , it also reports this information to the third input/output module 24 .
  • the administration module 22 executes a process in accordance with the selection by directing output of the toolbar 305 shown in FIG. 4 to the third input/output module 24 .
  • the third input/output module 24 displays the toolbar 305 and the various windows.
  • the third input/output module 24 accepts process selections in the toolbar 305 and message input-through the thread window, which it reports to the administration module 23 .
  • the third input/output module 24 accepts and reports to the creation module 21 users, message selections, and thread selections.
  • the third input/output module 24 also receives messages themselves and thread IDs from the administration module 23 , and displays the messages in a designated thread window.
  • FIG. 4 depicts a screen just after booting a chat client relating to the present embodiment.
  • a main screen 301 , a user window 302 , and chat window 303 , and message input field 304 are displayed in the FIG. 4 screen. These windows are likewise as with general IRC clients; therefore explanation is omitted.
  • toolbar 305 is depicted in FIG. 4.
  • the chat client is not connected to the network, and therefore only “Connect” is available on the toolbar 305 .
  • “Connect” is clicked, the chat client is connected via the Internet 1 to a chat server. It is otherwise connected directly to other chat devices or to a WEB server, however, wherein the display control device 2 is applied to other chat devices apart from IRC chat clients.
  • FIG. 5 depicts a screen after connection to a chat server.
  • “connect” on the toolbar 305 is not available.
  • “Create” and “Disconnect” are available. Selecting respective users in the user window 302 and clicking “Create” displays a confirmation window as shown in FIG. 6.
  • FIG. 6 users “jormiya” and user “ohtsuka” are selected. In this case, user “Jun-Jun” would be the author of the thread.
  • the window shown in FIG. 6 is for confirming whether or not to display past messages in the freshly created thread window. Predetermined messages and a “Quote messages” checkbox are displayed in the confirmation window. When the “Quote messages” checkbox is checked and the “OK” button is pressed, a thread window is displayed. The messages displayed in the confirmation window will differ, however, depending on whether member users have been selected, whether messages have been selected, or whether neither has been selected.
  • Thread window 307 when a new thread has been created is depicted in FIG. 7.
  • Thread window 307 includes message window 308 , input field 309 , and title field 310 .
  • User messages composing the thread are displayed in the message window 308 .
  • Messages for the thread can be input in the input field 310 .
  • the default thread name “New Thread 1” is displayed in the title field 310 . Users can change the thread name-as they wish.
  • FIG. 8 depicts the situation in which a thread is created by selecting messages as a whole, or words included in messages. Wherein the thread is created by selecting messages, message IDs are described in the thread information, as shown in aforementioned FIG. 3 administration table. Herein, it is preferable that selecting messages means selecting users.
  • FIG. 10 illustrates a selection window displaying the situation wherein “Link” has been selected on the toolbar.
  • a list of threads created in the channel is displayed in the selection window.
  • the selected threads (link source threads) are displayed in a linked-threads (forwarding destination threads) window.
  • the “Quote Content” checkbox has been checked, past messages from the link source threads are displayed in thread window for forwarding destination threads.
  • the message display order can be, for example, displaying in a time sequence, displaying in a user-and-time sequence, or otherwise designed to meet needs.
  • FIG. 11 depicts an administration table wherein thread “Th3” has been created by user “Jun-Jun” linking thread “Th1” and “Th2.”
  • FIG. 11( a ) illustrates an administration table for user “Jun-Jun.”
  • FIG.( b ) illustrates an administration table for a user apart from user “Jun-Jun.”
  • thread IDs that have become link source threads are described as link sources in the thread information for linked thread “Th3.”
  • thread IDs that have become link source threads are described as forwarding destinations in the thread information for linked thread “Th3.” Accordingly, for user “Jun-Jun,” with whom there are linked users, a thread window is displayed in which messages in threads “Th1” and “Th2” are mixed. Nevertheless, this does not effect the displays for other users. If for example user “Jun-Jun” issues a remark in thread “Th3,” other display control devices receiving the message consult their administration tables and display the message in one forwarding destination thread or another.
  • FIG. 12 illustrates an example of a selection window displaying the situation wherein “Display” has been clicked on the toolbar.
  • a list of created thread titles is displayed in the selection window.
  • the selected thread window is displayed.
  • the “Display Main Screen” checkbox has been checked the thread window is displayed on the main screen.
  • the title “Program” has been selected.
  • FIG. 13 is a flowchart illustrating flow of an input control routine that the display control device 2 executes. Activating the chat client starts the following processes.
  • step SI the third input/output control module 24 stands by for message input into the thread window.
  • step S 2 ensues.
  • step S 2 the third input/output control module 24 acquires the ID of the thread in the acquired message.
  • the thread window being displayed and the thread ID are correlated and held in the third input/output control module 24 .
  • step S 3 the third input/output control module 24 sends the input message content and the thread ID for the message to the administration module 23 .
  • step S 4 the administration module 23 updates the message list and the administration table. Specifically, the administration module 23 writes the message, the thread ID, and the message ID into the message list. The administration module 23 also consults the entries in the administration table and writes the message IDs into the administration table as needed.
  • step S 5 the administration module 23 judges whether or not the chat client has terminated, and if it has not terminated, returns to step Si again and stands by for succeeding input. If it has terminated, the routine ends.
  • FIG. 14 is a flowchart depicting flow of an output control routine that the display control device 2 executes. Like the aforementioned input control routine, activating the chat client starts the following routine.
  • step S 11 the administration module 23 judges whether or not received data is a message from another chat client. If it is a message, step S 12 ensues. If it is other data, later-described step S 19 ensues.
  • step S 12 the administration module 23 judges whether or not the message is in a thread. This decision judges based on whether or not, for example, a thread ID is included in a predetermined position in the message. If the message is in a thread, step S 13 ensues. If not, later-described step S 21 ensues.
  • step S 13 the administration module 23 updates the message list and, if necessary, the administration table. Received messages, message IDs, and thread IDs are written in the message list. Wherein threads for message objects (object threads hereinafter) have not been composed from designated users, the administration module 23 writes the message ID into the administration table.
  • step S 14 the administration module 23 consults the administration table and judges whether the disclosure level of the object thread is “Public” or not. If it is “Public,” step S 15 ensues. Otherwise, later-described step S 18 ensues.
  • step S 15 the administration module 23 , consulting the administration table, judges whether or not the window for the object thread is being displayed. Wherein the thread window is being displayed, step S 16 ensues. Wherein the thread window is not being displayed, the administration module 23 sends the message to the control module 32 , and later-described step S 21 ensues.
  • step S 16 the object thread is publicly open to all users, and therefore the administration module 23 outputs the received message to the thread window.
  • step S 17 the administration module 23 judges whether or not the chat client is terminated or not, and if it is not terminated, returning to aforementioned step S 11 the foregoing routine is repeated. If it is terminated, the routine ends.
  • step S 18 when the object thread is judged to be “Private,” step S 18 ensues.
  • the administration module 23 judges whether or not the user is a member user in the object thread. If “Yes,” aforementioned step S 15 ensues; if “No,” aforementioned step S 17 ensues. That is, the received message is not displayed in either the thread window or in the chat window on the main screen.
  • step S 19 the reporting module 22 judges whether or not the received data is a thread command. If the decision is “Yes,” step S 20 ensues. If the decision is “No,” the reporting module 22 sends the received data to the control module 32 , and later-described step S 21 ensues. That is, when the reporting module receives a thread command such as thread creation reports or link reports, step S 20 ensues. If, however, change in topic or mode reports from the server, change in participating user reports are received, for example, later-described step S 21 ensues. In step S 20 , the administration module 23 updates the administration table. There will be instances in which the update process will differ according to the received thread command.
  • step S 21 if the message is judged not to be a thread, step S 21 ensues.
  • the administration module 23 sends the message to the control module 32 .
  • the message likewise as in ordinary chat clients, is output to the main screen.
  • step S 21 ensues.
  • the administration module 23 sends the thread message to the control module 32 .
  • the thread message not being displayed in the thread window is therefore displayed in the main screen.
  • step 21 ensues.
  • the received data is sent from the reporting module 22 to the control module 32 .
  • the control module 32 likewise as in ordinary IRC routines, stores the received data into the memory 4 .
  • FIG. 15 is a flowchart illustrating flow of the main routine executed by the display control device 2 .
  • activating the chat client starts the following processes.
  • step S 30 the creation module 21 instructs the third input/output control module- 24 to-display the toolbar 305 . This instruction-displays the toolbar 305 in the input/output section.
  • step S 31 the third input/output control module 24 stands by for any process to be selected, and reports a selected process to the administration module 23 .
  • the administration module 23 judges whether or not “Connect” has been selected. If the decision is “Yes,” step S 32 ensues. Otherwise, later-described step S 34 ensues.
  • step S 32 the administration module 23 performs a connection process.
  • the administration module 23 carries out the process of connecting to a chat server.
  • the connection process is carried out with a Web server providing Web chat services.
  • step S 33 the administration module 23 judges whether the chat client has terminated, and if it has not terminated, returns to step S 31 and repeats the foregoing processes. If it has terminated, the routine ends.
  • step S 34 the administration module 23 judges whether or not “Create” has been selected. If “Yes” is the case then step S 35 ensues. If “No” is the case then later-described step S 36 ensues.
  • step S 35 the creation module 21 executes a later-described creation process subroutine.
  • step S 36 the administration module 23 judges whether or not “Link” has been selected, and if “Yes,” step S 37 ensues. If “No,” later-described step S 38 ensues.
  • step S 37 the creation module 21 executes a later-described linking process subroutine.
  • step S 38 the administration module 23 judges whether or not “Separate” has been selected, and if “Yes,” step S 39 ensues. If “No,” later-described step S 40 ensues.
  • step S 39 the creation module 21 executes the later-described creation process subroutine.
  • step S 40 the administration module 23 judges whether or not “Cancel” has been selected. If “Yes,” step S 41 ensues. If “No,” later-described step S 42 ensues.
  • step S 41 the creation module 21 executes a later-described cancellation process subroutine.
  • step S 42 the administration module 23 judges whether or not “Display” has been selected. If “Yes,” step S 43 ensues. If “No,” later-described step S 44 ensues.
  • step S 43 the administration module 23 executes a later-described displaying process subroutine.
  • step S 44 the administration module 23 judges whether or not “Disconnect” has-been selected; if “Yes,” step S 45 ensues, and if “No,” returns to aforementioned step S 33 and repeats the foregoing processes.
  • step S 45 the administration module 23 executes a process for disconnecting from the chat server.
  • FIG. 16 is a flowchart illustrating flow of a creation process that the creation module 21 carries out wherein “Create” has been selected in the toolbar 305 .
  • step S 351 the creation module 21 judges whether or not either users composing a thread, or messages have been selected. If either selection is present, step S 352 ensues. If neither has been selected, later-described step S 354 ensues.
  • step S 352 the creation module 21 directs display of the confirmation window in FIG. 6 to the third input/output control module 24 .
  • step S 353 the third input/output control module 24 stands by for either the “OK” button or the “Cancel” button being pressed.
  • the creation module 21 is notified when the “OK” button is pressed, and step S 354 ensues. Also included in the notification is the status of the “Quote Messages” checkbox.
  • the creation process terminates and the flow returns to aforementioned step S 33 of the main routine.
  • step S 354 wherein neither users composing a thread, nor messages have been selected, the creation module 21 creates and writes into the administration table thread information for a newly created thread.
  • the thread ID is described in the thread information.
  • the disclosure level may be set to “Public.”
  • the creation module 21 creates and writes into the administration table thread information in which selected member users or messages are described.
  • the disclosure level is set to “Private,” and if messages have been selected, to “Public” respectively.
  • step S 355 the creation module 21 judges whether or not “Quote Messages” is checked. If “Yes,” step S 356 ensues; if “No,” later-described step S 357 ensues.
  • step S 356 the creation module 21 acquires requisite messages from the message list. If member users have been selected, member users' messages are acquired using nicknames. If messages have been selected, messages are -acquired using message IDs.
  • step S 357 the creation module 21 sends the acquired messages to the third input/output control module 24 .
  • the third input/output control module 24 displays the thread window and outputs the messages within the window.
  • step S 358 the creation module 21 reports the created thread information to the reporting module 22 .
  • the reporting module 22 creates, and sends out to the channel via the administration module 23 , a thread command reporting creation of the thread. Thereafter, the flow returns to aforementioned step S 33 of the main routine.
  • FIG. 17 is a flowchart of a linking process that the creation module 21 carries out wherein “Link” has been selected in aforementioned toolbar 305 .
  • step S 371 the creation module 21 directs display of the selection window shown in FIG. 10 to the third input/output control module 24 .
  • the creation module 21 also retrieves from the administration table, and sends to the third input/output control module 24 , a title list for the created threads. The list of threads sent out is output to the selection window.
  • step S 372 the third input/output control module 24 stands by for the “OK” button to be pressed, which selects a thread.
  • the third input/output control module 24 notifies the creation module 21 when the “OK” button is pressed.
  • the selected threads as well as the status of the “Quote Content” checkbox are included in this notification.
  • Step S 373 then ensues. If the “Cancel” button is pressed, the linking process terminates.
  • step S 373 the creation module 21 judges whether or not the “Quote Content” checkbox has been checked. If “Yes,” step S 374 ensues. If “No,” later-described step S 380 ensues.
  • step S 374 the creation module 21 reports IDs for the selected threads to the administration module 23 .
  • the administration module 23 acquires messages contained in the reported threads from the message list using the thread IDS.
  • the administration module 23 also rearranges the acquired messages in accordance with predetermined criteria. They can be rearranged, for example, in a time sequence, or rearranged user-by-user.
  • the administration module 23 sends the rearranged messages to the creation module 21 .
  • step S 375 the creation module 21 directs to the third input/output control module 24 display of a new thread window for displaying the linked threads.
  • step S 376 the creation module 21 sends the rearranged messages to the third input/output control module 24 .
  • the third input/output control module 24 displays the received messages in the new thread window.
  • step S 377 the creation module 21 consults the administration table to judge whether or not a window for link source threads is being displayed. If it is being displayed, instruction is to the third input/output control module 24 not to display the link-source window. Wherein this instruction is present, the third input/output control module 24 eliminates the link-source window.
  • step S 378 the creation module 21 updates the administration table. That is, it writes into the new entries predetermined information relating to the linked threads (FIG. 11). In addition, wherein the link source threads are not to be displayed in aforementioned step S 377 , the creation module 21 changes the “Status” of the link source threads.
  • step S 379 the creation module 21 reports to the reporting module 22 that threads have been linked.
  • the reporting module 22 sends out thread commands that report link source thread IDs and forwarding destination thread IDs.
  • thread command example would be as follows.
  • Th_merge Th1,Th2;Th3;Creator Jun-Jun
  • step S 380 a new thread window display instruction for displaying the linked threads is to the third input/output control module 24 .
  • the third input/output control module 24 displays the new thread window.
  • FIG. 18 is a flowchart of processes in a cancellation process subroutine executed wherein “Cancel” has been selected in aforementioned toolbar 305 .
  • Step S 41 in the main routine ensues, the process here below begins.
  • step S 411 the creation module 21 instructs to the third input/output control module 24 display of a selection window similar to FIG. 12.
  • the creation module 21 acquires from the administration table the title list for the threads, which it sends along with the instruction to the third input/output control module 24 .
  • the third input/output control module 24 displays a selection window.
  • the “Cancel” button is pressed, the cancellation process terminates.
  • step S 412 when a thread selection is made and the “OK” button is pressed, the third input/output control module 24 reports to the creation module 21 the selected thread ID.
  • step S 413 the creation module 21 deletes the entry for the reported thread ID from the administration table.
  • step S 414 the creation module 21 deletes the aforementioned cancelled thread ID from the message list.
  • step S 415 the creation module 21 reports cancellation of the thread to the reporting module 22 .
  • the reporting module 22 sends out a thread command reporting the thread cancellation—a thread command as below, for example.
  • the creation module 21 consults the administration table and executes a decision as to whether the cancelled thread is a link thread or not. This decision is executed preceding aforementioned step S 413 . Wherein it is a link thread, the creation module 21 consults the link source thread status and if the status is “Don't Display,” changes it to “Display.” The creation module 21 also acquires messages in the link source threads from the message list.
  • the creation module 21 then causes the link source threads to be displayed by sending an instruction for display of the link source threads, and the acquired messages, to the third input/output control module 24 .
  • the threads are linked, the status of the link source threads is to be stored in memory, and if a linked thread is cancelled, the link source threads are returned to the stored state.
  • FIG. 19 is a flowchart of a display process subroutine that the creation module 21 carries out wherein “Display” has been selected in aforementioned toolbar 305 .
  • step S 431 the creation module 21 directs display of the FIG. 12 selection window to the third input/output control module 24 .
  • the creation module 21 Preceding the instruction, the creation module 21 also retrieves a thread title list from the administration table, which it sends together with the aforementioned instruction to the third input/output control module 24 .
  • the third input/output control module 24 displays a selection window in accordance with the instruction.
  • step S 432 when any thread has been selected and the “OK” button is pressed, the third input/output control module 24 reports the selected thread to the creation module 21 . Step S 433 then ensues. When the “Cancel” button is pressed, the displaying process terminates.
  • step S 433 the creation module 21 specifies IDs for the selected threads.
  • the creation module 21 then acquires messages in the selected threads from the message list using the thread IDs.
  • step S 434 the creation module 21 sends an instruction for thread window display, and the acquired messages, to the third input/output control module 24 .
  • the third input/output control module 24 displays the thread window, and outputs the messages within the window.
  • step S 435 the creation module 21 changes the “Status” of the aforementioned displayed thread in the administration table to “Display.” The flow then returns to aforementioned step S 33 of the main routine.
  • the disclosure level is set automatically, but the user may set the disclosure level with every thread creation. In that case, presumably, a button for setting the disclosure level would be provided in the aforementioned confirmation window of FIG. 6.
  • transmission/reception of thread information is carried out via a chat client, but may be carried out among display control devices directly.

Abstract

The disclosure is directed to methods and devices for displaying conversations on a network for ease of viewing in accordance with user preferences. Based on thread (message-group) forming instructions from users, as well as on member users' instructions, threads are created from member users' remarks. Instead of designating users, remarks that include threads may be designated. Thread information relating to the created threads is at the same time created and stored. The thread information includes predetermined information such as thread IDs, member users and authors. The created thread information is reported to other users in the network, and is in common with thread information within the network. Remarks within a thread may be displayed in a thread window 307 only, or displayed in both it and a conversation window 303, configurable to suit according to user instructions.

Description

    BACKGROUND OF THE INVENTION
  • 1. Technical Field [0001]
  • The present invention relates to technology for promoting user convenience in a system in which users share identical networks mutually, enabling simultaneous conversation. More particularly, it relates to technology that makes conversational display easy to view, in a textual conversation system such as IRC (Internet Relay Chat). [0002]
  • In the present invention, “IRC” means a chat system formed by connecting a chat server with a plurality of chat clients on the Internet, and the plurality of chat clients sharing the same virtual space, enabling simultaneous conversation. [0003]
  • Furthermore, “channel” means a virtual space that chat clients share in IRC. A “nickname” utilized in IRC means identifying information for specifying a user. A “topic” means the subject of a channel used in IRC. “Mode” means information that indicates characteristics of a channel utilized in IRC. [0004]
  • 2. Description of Related Art [0005]
  • Text conversation systems (simply “chat systems” below) for conducting conversation using text among information terminals on a network have heretofore been offered. For example, Web chat systems that keep a log of messages that WWW (World Wide Web) servers issue have been offered. In Web chat systems users carry out conversations via text by sharing a Web Page log (message record). A system for conducting conversation by manipulating user alter egos known as “avatars” within a virtual world has also been offered. Still further, IRC in which chat servers signal-distribute conversation to a plurality of chat clients in conformity with IRC protocols have also been offered. These chat systems, conventionally, have been used as systems directed to the general user. Nevertheless, the actual situation recently is that use in business has been increasing, such as for in-house communications and brief meetings. [0006]
  • A plurality of users—in general three persons or more—often join in on chat systems. When the number of participants increases, it can happen that a number of different topics will be going on at once within the same display area. In real-world conversations, the speaker's gaze can distinguish topics, as can approaching the person speaking. In conversations on the Internet, however, wherein the condition of the other party cannot be seen, conversations relating to a plurality of topics end up being intermingled and displayed within the same area. [0007]
  • In chat systems on the WWW, modifying the colors of displayed messages facilitates distinguishing topics. Because changing colors of the messages for every topic is a bother for the user, however, at present this method is seldom used. [0008]
  • Further, in IRC creating channels that differ according to topic is easy. In reality, however, multiple topics often break out within a single channel. [0009]
  • SUMMARY OF THE INVENTION
  • The object of the present invention is to display topics respectively segregated from other topics wherein a plurality of topics are under way simultaneously on a network, to promote accurate and efficient communication. [0010]
  • In order to address the aforementioned problems, in one aspect the present invention is a display control method utilized in a chat system in which users on information terminals share identical networks mutually, enabling text conversation, the display control method: [0011]
  • (A) correlating messages on the network based on user instructions and creating message groups and predetermined message group information relating to the message groups; [0012]
  • (B) sharing the created message group information with users on the network; [0013]
  • (C) sending messages to the message groups out to the network; and [0014]
  • (D) in accordance with user instructions displaying the message groups independently of messages on the network. [0015]
  • Taking an example wherein it is applied to IRC will illustrate the display control method of the present invention. Participants on a channel for example designate particular users, instructing the creation of a message group. Message group information concerned with the created message group is reported to other chat clients in the channel. Message group information may be, for example, nicknames of the users that form the message group, a message group ID, the message group author, and the message group name. Issuing messages to a message group sends that messages out on the channel. The way the message group is displayed conforms to user instructions. The message group can be displayed in the same display area the channel is displayed, or can be displayed independently of the channel display area. [0016]
  • In a further aspect the invention is a display control device utilized in a chat device wherein, sharing an identical network mutually, transmission/reception of text messages is possible, and presents the display control device provided with creating means, reporting means, memory means and input/output control means. [0017]
  • The creating means correlates messages on the network according to user instructions and creates message groups and predetermined message group information relating to the message groups. The reporting means transmits/receives the created message group information to and from other among display control devices on the network. The memory means stores the message group information. The input/output control means obtains the message groups from the chat device and in accordance with user instructions, enables display of the message groups independently of messages on the network. [0018]
  • Likewise as described before, taking an example wherein it is applied to IRC will illustrate the display control device. A user, for example, designates the individual users constituting a message group. The creation means creates the message group out of the messages from the designated member users. The creation means also creates message group IDs, and predetermined message group information containing member users and the creating user, which is stored in the memory means. The created message group information is reported by the reporting means to other display control devices in the channel. The report may be either via a chat client, or directly transmitted/received among the display control devices. Other display control devices accept from the reporting means message group information that the other display control devices have created, which is stored in the memory means. [0019]
  • With input/output control means, in accordance with user instructions, the message group can be displayed in a window separate from the messages within the channel. Of course, it is also possible to display both messages within a channel and message groups together in the same window. The message groups are obtainable, for example, from a message log that the chat client has created. [0020]
  • The present invention in another aspect presents a display control device wherein the creating means in the second aspect of the invention accepts operations directed to the message groups and updates the message group information. [0021]
  • For example, the creating means accepts message group link instructions and creates message group information in which linked message groups and the message group link source are correlated. [0022]
  • In a further aspect the invention presents a display control device wherein the input/output control means in the second aspect of the invention accepts messages in which the message groups are designated and acquires from the network or sends to the network messages for the message groups. [0023]
  • The input/output control means, for example in a window displaying the message groups, deems inputted messages to be messages to the message group, and sends them out to the channel. The input/output control means also obtains from the channel messages to message groups transmitted from other display control devices. According to user instructions, the obtained messages are displayed in a window for message groups or in an ordinary chat window. [0024]
  • The present invention in yet another aspect presents a display control device wherein the creation means in the second aspect of the invention correlates messages within the network based on selection of the chat device from a user, and creates message groups out of messages from the selected chat devices and message group information containing information that designates the selected chat devices. [0025]
  • When a user chooses individual users within a channel, the creation means creates a message group that will be constituted by messages from the chosen users. Information specifying the users comprising the message group, nicknames, for example, are contained in the message group information. Selecting user names, or selecting user messages can be given as methods of choosing users. [0026]
  • In a still further aspect the invention presents a display control device wherein that of the second aspect of the invention is provided with a message list correlating messages within the network and message identifying information specifying the messages; wherein the creation means creates, based on selection of the messages from a user, message groups containing the selected messages and message group information containing message-identifying information for the selected messages. [0027]
  • Selecting not the users, but specific messages creates the message groups. Message IDs that specify designated messages are contained in the message group information. [0028]
  • The present invention in another aspect presents a display control device wherein the creation means in the second aspect of the invention creates message group information in which a disclosure level of the message groups that are created is contained. [0029]
  • The disclosure level setting may be designated by the individual users, or automatically set in according to the type of message group. For example, wherein the message group is created by designating individual users, the creating means sets the disclosure level to “Private.” On the other hand, wherein the message group is created by designating messages, the creating means sets the disclosure level to “Public.”[0030]
  • In a further aspect the invention presents a display control device wherein message-group identifying information specifying the message groups is contained in the message group information. [0031]
  • Including a message group ID in the message group information enables sharing message groups mutually within the same channel. Consequently, the created message groups can be displayed in common among the users according to each user's respective preference. [0032]
  • The invention in yet another aspect presents a display control device wherein the input/output control means in the second aspect of the invention judges based on the message group information whether to display the message groups, and displays the message groups based on the judgment. [0033]
  • The input/output control means decides whether or not to display the message group according to, for example, the before-described disclosure level or to the type of message group. Specifically, if the disclosure level is “Public,” the decision is “displayable.”[0034] 0 Conversely, if the display level is “Closed to Public,” wherein chat clients constitute the message group, the decision is “not displayable.”
  • In still a further aspect, the present invention presents a computer-readable recording medium on which is recorded a display control program utilized in a chat device wherein, sharing an identical network mutually, transmission/reception of messages through text is possible, the computer-readable recording medium on which is recorded the display control program for executing steps A-D below. [0035]
  • (A) a step of correlating messages on the network based on instructions from a user and creating message groups and predetermined message group information relating to the message groups; [0036]
  • (B) a step of transmitting/receiving the created message group information among other chat devices within the network; [0037]
  • (C) a step of storing the message group information; and [0038]
  • (D) a step of obtaining the message groups from the chat device and in accordance with instructions from users displaying the message groups independently of messages within the network. [0039]
  • Examples of a computer-readable recording medium herein include computer-readable/writeable floppy disks, hard disks, semiconductor memory, CD-ROMs, DVDs (digital video disks), and MOs (magneto-optical disks). [0040]
  • Utilizing the present invention enables the conversation of users chatting by sharing a network such as an electronic meeting room to be displayed to suit each person's liking. Moreover, users can also designate that one another's displays be made in common, enabling them to carry out efficient communication. [0041]
  • The foregoing and other objects, features, aspects and advantages of the present invention will become more apparent from the following detailed description in conjunction with the accompanying drawings.[0042]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a functional block diagram showing the configuration of a display control device pertaining to the present invention in a first embodiment; [0043]
  • FIG. 2 is a conceptual illustration of a message list; [0044]
  • FIG. 3 is a conceptual illustration of an administration table; [0045]
  • FIG. 4 is a screen example showing a chat client pertaining to the present embodiment, in its state just after activation; [0046]
  • FIG. 5 is a screen example following connection to a chat server; [0047]
  • FIG. 6 is a diagram showing an example of a confirmation window; [0048]
  • FIG. 7 is a diagram showing an example of a thread window; [0049]
  • FIG. 8 is a screen example wherein selecting messages creates a thread; [0050]
  • FIG. 9 is a diagram showing an example of a new thread window wherein users and messages are not selected; [0051]
  • FIG. 10 is a diagram showing an example of a selection window wherein “Link” is selected; [0052]
  • FIG. 11 is a conceptual illustration of a post-thread-linking administration table: [0053]
  • (a) Linker's administration table, and [0054]
  • (b) Administration table for a user apart from the linker; [0055]
  • FIG. 12 is a diagram showing an example of a selection window wherein “Display” is selected; [0056]
  • FIG. 13 is a flowchart depicting flow in an input control process that the display control device carries out; [0057]
  • FIG. 14 is a flowchart depicting flow in an output control process that the display control device carries out; [0058]
  • FIG. 15 is a flowchart depicting flow in main routine that the display control device carries out; [0059]
  • FIG. 16 is a flowchart depicting flow in a creation process subroutine; [0060]
  • FIG. 17 is a flowchart depicting flow in a linking process subroutine; [0061]
  • FIG. 18 is a flowchart depicting flow in a cancellation process subroutine; and [0062]
  • FIG. 19 is a flowchart depicting flow in a display process subroutine. [0063]
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • Next, a display control device of the present invention will be definitely explained with reference to the drawings. [0064]
  • First Embodiment [0065]
  • Configuration [0066]
  • FIG. 1 is a function block diagram illustrating the configuration of a display control device in connection with the first embodiment of the present invention. For ease of description, the explanation takes an example in the present embodiment wherein the display control device is adapted to an IRC chat client. [0067]
  • (1) Chat Client [0068]
  • The [0069] chat client 3 in FIG. 1 can converse with other chat clients via the Internet 1. The chat client 3 has a display control device 2, a first input/output control module 31, a control module 32, a second input/output control module 33, and a memory 4. To begin with, a brief explanation will be made of the configuration of the chat client 3 apart from the display control device 2.
  • The first input/[0070] output control module 31 carries out data transmission/reception between it and the Internet 1.
  • The memory [0071] 4 stores predetermined information relating to the channels in which the chat client 3 participates. “Predetermined information” is, for example, channel name, nicknames of users in the channel, topics, and channel attributes. A log of messages in the channel is also stored in the memory 4.
  • The [0072] control module 32 ordinarily transmits/receives data between it and the Internet 1 via the first input/output control module 31. In the present embodiment, however, the control module 32 carries out data transmission/reception via the display control device 2. The predetermined information among the data received is stored in the memory 4. Also, messages received from other chat clients are sent to the second input/output control module 33 and displayed. Further, the control module 32 accepts input messages from the second input/output control module 33 and sends them out on the channel via the display control device 2.
  • The second input/[0073] output control module 33 accepts received messages from the control module 32 and outputs them on an input/output section display. The second input/output control module 33 also sends inputted messages from the input/output section to the control module 32.
  • (2) Display Control Device [0074]
  • The [0075] display control device 2 has a creation module 21, a reporting module 22, a third input/output control module 23, and an administration module 24 as well as the memory 4. The display control device 2 shares the memory 4 with the chat client 3.
  • The memory [0076] 4 holds a message list and an administration table, which it adds to predetermined information relating to the channels. A diagram conceptually illustrating a created message list in the memory 4 is shown in FIG. 2. Message lists are created for each channel. Thread IDs (in the figures, noted as “Th.ID”) that specify message groups (called “threads” hereinafter), message IDs that specify messages, and messages are correlated and stored in the message list. It is preferable that the message list be created by appending the message IDs and the thread IDs to the message log that the chat client control module 32 creates.
  • The message IDs are identifying information attached in order to specify the messages, and are, for example, consecutive numbers. The thread IDs are identifying information for specifying threads. The FIG. 2 message list is a message list for the channel “CH1.” The messages in which the message IDs are “1,”“5” and “6” are included in the thread that is specified with thread ID “Th1.” The other messages are included in the thread that is specified with thread ID “Th2.”[0077]
  • A diagram conceptually illustrating an administration table created in the memory [0078] 4 is shown in FIG. 3. For ease of description, the message list is as is in FIG. 2. Predetermined information (called “thread information” hereinafter) relating to each of the threads is described in the administration table. Thread information in the present instance consists of thread IDS, titles, authors, member users, message IDs, link sources, forwarding destination, disclosure level and status.
  • “Titles” are preferably text information for displaying the threads to the users. Preferably, the users can set the titles arbitrarily. “Author” is the nickname of the user who created the thread. “Member users” are the users who construct the thread. This, as will be discussed later, is information that is described wherein the threads are created by selecting the users. In the present embodiment, the threads are created by the users or by selecting any message. [0079]
  • “Link source” as will be discussed later is a linked thread ID wherein a plurality of threads is linked. It is information that is described in the administration table of the user linked to the thread. “Forwarding destination” is information for expressing link sources of threads linked by other users. [0080]
  • “Disclosure Level,” if “Public,” indicates that messages within the thread are approved to be open to all of the users. If “Private,” it indicates that messages within the thread are approved to be open only to users in the thread. The thread author would best make the disclosure level setting. It is also possible that with the disclosure level of a thread formed by users being “Private,” the disclosure level of the other threads be set to “Private.” In the present embodiment, the disclosure level of threads created by selecting users is automatically made “Private.” “Status” indicates whether or not a window exclusively for threads (called “thread window” hereinafter) is currently being displayed. [0081]
  • The [0082] creation module 21 receives from the administration module 23 instructions for a process on threads. Following the instructed process, the creation module 21 updates the administration table. As concrete examples of the process on threads, creation, segregation, linking and display can be given. For example, when thread creation is instructed, the creation module 21 creates thread information and records it in the administration table. The creation module 21 also reports updated thread information to the reporting module 22.
  • The [0083] reporting module 22 transmits/receives thread information via the administration module 23. Specifically, the reporting module 22 receives thread information from other display control devices and updates the administration table and the message list. The reporting module 22 also sends thread information reported from the creation module 21 out to the other display control devices within the channel. Establishing predetermined thread commands is preferable for transmitting/receiving the thread information. For instance, an example of a thread command to create “Th1” is shown below.
  • Th_create;ThID=Th1;Creator=Jun-Jun;User=Jun-Jun,ohtsuka,jormiya;Private [0084]
  • Thread commands for reporting thread-linking, separating, and deleting are established likewise. [0085]
  • The [0086] administration module 23 transmits/receives messages via the first input/output control module 31 and updates the message list and the administration table. The administration module 23 judges whether or not received messages are messages in the threads. This decision is executed, for example, according to whether a thread ID is present in the message. Wherein the administration module 23 has judged a message to be in the threads, it sends the message out to the control module 32 and the third input/output module 24 in accordance with user instructions.
  • The [0087] administration module 23 also receives messages in the thread window from the third input/output module 24. The administration module 23 sends the received messages and thread IDs out to the channel.
  • Furthermore, the [0088] administration module 23 receives from the third input/output module 24 selection of processes on threads, and directs the processes to the creation module 21. Wherein it has received selected users and messages from the third input/output module 24, it also reports this information to the third input/output module 24. For example, the administration module 22 executes a process in accordance with the selection by directing output of the toolbar 305 shown in FIG. 4 to the third input/output module 24.
  • In accordance with instructions from the [0089] administration module 23 and the creation module 21, the third input/output module 24 displays the toolbar 305 and the various windows. The third input/output module 24 accepts process selections in the toolbar 305 and message input-through the thread window, which it reports to the administration module 23. The third input/output module 24 accepts and reports to the creation module 21 users, message selections, and thread selections. The third input/output module 24 also receives messages themselves and thread IDs from the administration module 23, and displays the messages in a designated thread window.
  • Screen [0090]
  • The following will illustrate examples of screens displayed by a display control device of the present invention. For ease of description, the message list is as is shown FIG. 2. [0091]
  • FIG. 4 depicts a screen just after booting a chat client relating to the present embodiment. A [0092] main screen 301, a user window 302, and chat window 303, and message input field 304 are displayed in the FIG. 4 screen. These windows are likewise as with general IRC clients; therefore explanation is omitted.
  • In addition to the aforementioned general IRC screen, [0093] toolbar 305 is depicted in FIG. 4. The chat client is not connected to the network, and therefore only “Connect” is available on the toolbar 305. When “Connect” is clicked, the chat client is connected via the Internet 1 to a chat server. It is otherwise connected directly to other chat devices or to a WEB server, however, wherein the display control device 2 is applied to other chat devices apart from IRC chat clients.
  • FIG. 5 depicts a screen after connection to a chat server. In this state “connect” on the [0094] toolbar 305 is not available. On the other hand, “Create” and “Disconnect” are available. Selecting respective users in the user window 302 and clicking “Create” displays a confirmation window as shown in FIG. 6. In FIG. 6, users “jormiya” and user “ohtsuka” are selected. In this case, user “Jun-Jun” would be the author of the thread.
  • The window shown in FIG. 6 is for confirming whether or not to display past messages in the freshly created thread window. Predetermined messages and a “Quote messages” checkbox are displayed in the confirmation window. When the “Quote messages” checkbox is checked and the “OK” button is pressed, a thread window is displayed. The messages displayed in the confirmation window will differ, however, depending on whether member users have been selected, whether messages have been selected, or whether neither has been selected. [0095]
  • An example of a [0096] thread window 307 when a new thread has been created is depicted in FIG. 7. Thread window 307 includes message window 308, input field 309, and title field 310. User messages composing the thread are displayed in the message window 308. Messages for the thread can be input in the input field 310. The default thread name “New Thread 1” is displayed in the title field 310. Users can change the thread name-as they wish.
  • In the FIG. 7 state, “Create,” “Cancel,” and “Disconnect” are available on the [0097] toolbar 305. Wherein a selecting users creates the thread, thread-composing users are described in the thread information, as shown in the administration table in aforementioned FIG. 3.
  • An example screen wherein a thread is created not by selecting users, but by selecting messages, is shown in FIG. 8. FIG. 8 depicts the situation in which a thread is created by selecting messages as a whole, or words included in messages. Wherein the thread is created by selecting messages, message IDs are described in the thread information, as shown in aforementioned FIG. 3 administration table. Herein, it is preferable that selecting messages means selecting users. [0098]
  • It is possible, furthermore, to create threads without selecting users or messages. For example, wherein “Create” is pressed without making any selection, as shown in FIG. 9 a [0099] new thread window 307 is simply displayed with no message. Displaying a list of users in the channel by displaying a user list 311, shown in FIG. 9 in the new thread window, is desirable.
  • FIG. 10 illustrates a selection window displaying the situation wherein “Link” has been selected on the toolbar. A list of threads created in the channel is displayed in the selection window. When two or more threads are selected and the “OK” button is pressed, the selected threads (link source threads) are displayed in a linked-threads (forwarding destination threads) window. Wherein the “Quote Content” checkbox has been checked, past messages from the link source threads are displayed in thread window for forwarding destination threads. The message display order can be, for example, displaying in a time sequence, displaying in a user-and-time sequence, or otherwise designed to meet needs. [0100]
  • FIG. 11 depicts an administration table wherein thread “Th3” has been created by user “Jun-Jun” linking thread “Th1” and “Th2.” FIG. 11([0101] a) illustrates an administration table for user “Jun-Jun.” FIG.(b) illustrates an administration table for a user apart from user “Jun-Jun.” In FIG. 11(a), thread IDs that have become link source threads are described as link sources in the thread information for linked thread “Th3.” In FIG. 11(b), thread IDs that have become link source threads are described as forwarding destinations in the thread information for linked thread “Th3.” Accordingly, for user “Jun-Jun,” with whom there are linked users, a thread window is displayed in which messages in threads “Th1” and “Th2” are mixed. Nevertheless, this does not effect the displays for other users. If for example user “Jun-Jun” issues a remark in thread “Th3,” other display control devices receiving the message consult their administration tables and display the message in one forwarding destination thread or another.
  • FIG. 12 illustrates an example of a selection window displaying the situation wherein “Display” has been clicked on the toolbar. A list of created thread titles is displayed in the selection window. When any of the threads is selected and the “OK” button is pressed, the selected thread window is displayed. Further, when the “Display Main Screen” checkbox has been checked the thread window is displayed on the main screen. In the FIG. 12 example, the title “Program” has been selected. [0102]
  • Process Flow [0103]
  • The following explains, by giving concrete examples, the flow of processes that the [0104] display control device 2 executes. The display control device 2 independently performs the input control routine, output control routine and main routine below.
  • (1) Input Control Routine [0105]
  • FIG. 13 is a flowchart illustrating flow of an input control routine that the [0106] display control device 2 executes. Activating the chat client starts the following processes.
  • Initially, in step SI the third input/[0107] output control module 24 stands by for message input into the thread window. When a message is input into the thread window, step S2 ensues.
  • In step S[0108] 2 the third input/output control module 24 acquires the ID of the thread in the acquired message. Herein, the thread window being displayed and the thread ID are correlated and held in the third input/output control module 24.
  • In step S[0109] 3, the third input/output control module 24 sends the input message content and the thread ID for the message to the administration module 23.
  • In step S[0110] 4 the administration module 23 updates the message list and the administration table. Specifically, the administration module 23 writes the message, the thread ID, and the message ID into the message list. The administration module 23 also consults the entries in the administration table and writes the message IDs into the administration table as needed.
  • In step S[0111] 5, the administration module 23 judges whether or not the chat client has terminated, and if it has not terminated, returns to step Si again and stands by for succeeding input. If it has terminated, the routine ends.
  • (2) Output Control Routine [0112]
  • FIG. 14 is a flowchart depicting flow of an output control routine that the [0113] display control device 2 executes. Like the aforementioned input control routine, activating the chat client starts the following routine.
  • Initially* in step S[0114] 11, the administration module 23 judges whether or not received data is a message from another chat client. If it is a message, step S12 ensues. If it is other data, later-described step S19 ensues.
  • In step S[0115] 12, the administration module 23 judges whether or not the message is in a thread. This decision judges based on whether or not, for example, a thread ID is included in a predetermined position in the message. If the message is in a thread, step S13 ensues. If not, later-described step S21 ensues.
  • In step S[0116] 13, the administration module 23 updates the message list and, if necessary, the administration table. Received messages, message IDs, and thread IDs are written in the message list. Wherein threads for message objects (object threads hereinafter) have not been composed from designated users, the administration module 23 writes the message ID into the administration table.
  • In step S[0117] 14, the administration module 23 consults the administration table and judges whether the disclosure level of the object thread is “Public” or not. If it is “Public,” step S15 ensues. Otherwise, later-described step S18 ensues.
  • In step S[0118] 15, the administration module 23, consulting the administration table, judges whether or not the window for the object thread is being displayed. Wherein the thread window is being displayed, step S16 ensues. Wherein the thread window is not being displayed, the administration module 23 sends the message to the control module 32, and later-described step S21 ensues.
  • In step S[0119] 16, the object thread is publicly open to all users, and therefore the administration module 23 outputs the received message to the thread window.
  • In step S[0120] 17, the administration module 23 judges whether or not the chat client is terminated or not, and if it is not terminated, returning to aforementioned step S11 the foregoing routine is repeated. If it is terminated, the routine ends.
  • In aforementioned step S[0121] 14, when the object thread is judged to be “Private,” step S18 ensues. In step S18, the administration module 23 judges whether or not the user is a member user in the object thread. If “Yes,” aforementioned step S15 ensues; if “No,” aforementioned step S17 ensues. That is, the received message is not displayed in either the thread window or in the chat window on the main screen.
  • In aforementioned step S[0122] 11, when the received data is judged not to be a message, step S19 ensues. In step S19, the reporting module 22 judges whether or not the received data is a thread command. If the decision is “Yes,” step S20 ensues. If the decision is “No,” the reporting module 22 sends the received data to the control module 32, and later-described step S21 ensues. That is, when the reporting module receives a thread command such as thread creation reports or link reports, step S20 ensues. If, however, change in topic or mode reports from the server, change in participating user reports are received, for example, later-described step S21 ensues. In step S20, the administration module 23 updates the administration table. There will be instances in which the update process will differ according to the received thread command.
  • In the foregoing step S[0123] 12, if the message is judged not to be a thread, step S21 ensues. Herein, in step S21, the administration module 23 sends the message to the control module 32. The message, likewise as in ordinary chat clients, is output to the main screen.
  • Further, wherein in aforementioned step S[0124] 15 the decision is that the window for the object thread is not being displayed, step S21 ensues. Herein, in step S21, the administration module 23 sends the thread message to the control module 32. The thread message not being displayed in the thread window is therefore displayed in the main screen.
  • Further, wherein in aforementioned step S[0125] 19 the decision is that the received data is neither a message nor a thread command, step 21 ensues. There are instances in which the joining/departing of channel participating users, change in topic, altering channel mode, or altering channel operator characteristics, for example, are received. Herein, the received data is sent from the reporting module 22 to the control module 32. The control module 32, likewise as in ordinary IRC routines, stores the received data into the memory 4.
  • Main Routine Flow [0126]
  • The following explains the flow of the main routine executed by the [0127] display control device 2. FIG. 15 is a flowchart illustrating flow of the main routine executed by the display control device 2. Like the aforementioned input control routine and output control routine, activating the chat client starts the following processes.
  • In step S[0128] 30, the creation module 21 instructs the third input/output control module-24 to-display the toolbar 305. This instruction-displays the toolbar 305 in the input/output section.
  • In step S[0129] 31, the third input/output control module 24 stands by for any process to be selected, and reports a selected process to the administration module 23. The administration module 23 judges whether or not “Connect” has been selected. If the decision is “Yes,” step S32 ensues. Otherwise, later-described step S34 ensues.
  • In step S[0130] 32, the administration module 23 performs a connection process. In the present example, the administration module 23 carries out the process of connecting to a chat server. However, wherein a display control device of the present invention is applied to Web chat, for example, the connection process is carried out with a Web server providing Web chat services.
  • In step S[0131] 33, the administration module 23 judges whether the chat client has terminated, and if it has not terminated, returns to step S31 and repeats the foregoing processes. If it has terminated, the routine ends.
  • In the decision in aforementioned step S[0132] 31 is “No,” step S34 ensues. In step S34, the administration module 23 judges whether or not “Create” has been selected. If “Yes” is the case then step S35 ensues. If “No” is the case then later-described step S36 ensues.
  • In step S[0133] 35, the creation module 21 executes a later-described creation process subroutine.
  • In step S[0134] 36, the administration module 23 judges whether or not “Link” has been selected, and if “Yes,” step S37 ensues. If “No,” later-described step S38 ensues.
  • In step S[0135] 37, the creation module 21 executes a later-described linking process subroutine.
  • In step S[0136] 38, the administration module 23 judges whether or not “Separate” has been selected, and if “Yes,” step S39 ensues. If “No,” later-described step S40 ensues.
  • In step S[0137] 39, the creation module 21 executes the later-described creation process subroutine.
  • In step S[0138] 40, the administration module 23 judges whether or not “Cancel” has been selected. If “Yes,” step S41 ensues. If “No,” later-described step S42 ensues.
  • In step S[0139] 41, the creation module 21 executes a later-described cancellation process subroutine.
  • In step S[0140] 42, the administration module 23 judges whether or not “Display” has been selected. If “Yes,” step S43 ensues. If “No,” later-described step S44 ensues.
  • In step S[0141] 43, the administration module 23 executes a later-described displaying process subroutine.
  • In step S[0142] 44, the administration module 23 judges whether or not “Disconnect” has-been selected; if “Yes,” step S45 ensues, and if “No,” returns to aforementioned step S33 and repeats the foregoing processes.
  • In step S[0143] 45, the administration module 23 executes a process for disconnecting from the chat server.
  • That is, in the main routine, the [0144] toolbar 305 is displayed and processes selected by the user are carried out.
  • (3-1) Creation Process Subroutine [0145]
  • FIG. 16 is a flowchart illustrating flow of a creation process that the [0146] creation module 21 carries out wherein “Create” has been selected in the toolbar 305. When aforementioned step S35 ensues in the main routine, the following process starts.
  • In step S[0147] 351, the creation module 21 judges whether or not either users composing a thread, or messages have been selected. If either selection is present, step S352 ensues. If neither has been selected, later-described step S354 ensues.
  • In step S[0148] 352, the creation module 21 directs display of the confirmation window in FIG. 6 to the third input/output control module 24.
  • In step S[0149] 353, the third input/output control module 24 stands by for either the “OK” button or the “Cancel” button being pressed. The creation module 21 is notified when the “OK” button is pressed, and step S354 ensues. Also included in the notification is the status of the “Quote Messages” checkbox. When the “Cancel” button is pressed, the creation process terminates and the flow returns to aforementioned step S33 of the main routine.
  • In step S[0150] 354, wherein neither users composing a thread, nor messages have been selected, the creation module 21 creates and writes into the administration table thread information for a newly created thread. In particular, the thread ID is described in the thread information. Here the disclosure level may be set to “Public.”
  • Conversely wherein either selection is present, the [0151] creation module 21 creates and writes into the administration table thread information in which selected member users or messages are described. In addition, if member users have been selected the disclosure level is set to “Private,” and if messages have been selected, to “Public” respectively.
  • In step S[0152] 355, the creation module 21 judges whether or not “Quote Messages” is checked. If “Yes,” step S356 ensues; if “No,” later-described step S357 ensues.
  • In step S[0153] 356, the creation module 21 acquires requisite messages from the message list. If member users have been selected, member users' messages are acquired using nicknames. If messages have been selected, messages are -acquired using message IDs.
  • In step S[0154] 357, the creation module 21 sends the acquired messages to the third input/output control module 24. The third input/output control module 24 displays the thread window and outputs the messages within the window.
  • In step S[0155] 358, the creation module 21 reports the created thread information to the reporting module 22. The reporting module 22 creates, and sends out to the channel via the administration module 23, a thread command reporting creation of the thread. Thereafter, the flow returns to aforementioned step S33 of the main routine.
  • Moreover, the process carried out wherein “Separate” has been selected on the toolbar is like the thread-creation process, and explanation therefore will be omitted. [0156]
  • (3-2) Link Process Subroutine [0157]
  • FIG. 17 is a flowchart of a linking process that the [0158] creation module 21 carries out wherein “Link” has been selected in aforementioned toolbar 305. When aforementioned step S37 ensues in the main routine, the following process starts.
  • In step S[0159] 371, the creation module 21 directs display of the selection window shown in FIG. 10 to the third input/output control module 24. The creation module 21 also retrieves from the administration table, and sends to the third input/output control module 24, a title list for the created threads. The list of threads sent out is output to the selection window.
  • In step S[0160] 372, the third input/output control module 24 stands by for the “OK” button to be pressed, which selects a thread. The third input/output control module 24 notifies the creation module 21 when the “OK” button is pressed. The selected threads as well as the status of the “Quote Content” checkbox are included in this notification. Step S373 then ensues. If the “Cancel” button is pressed, the linking process terminates.
  • In step S[0161] 373, the creation module 21 judges whether or not the “Quote Content” checkbox has been checked. If “Yes,” step S374 ensues. If “No,” later-described step S380 ensues.
  • In step S[0162] 374, the creation module 21 reports IDs for the selected threads to the administration module 23. The administration module 23 acquires messages contained in the reported threads from the message list using the thread IDS. The administration module 23 also rearranges the acquired messages in accordance with predetermined criteria. They can be rearranged, for example, in a time sequence, or rearranged user-by-user. The administration module 23 sends the rearranged messages to the creation module 21.
  • In step S[0163] 375, the creation module 21 directs to the third input/output control module 24 display of a new thread window for displaying the linked threads.
  • In step S[0164] 376, the creation module 21 sends the rearranged messages to the third input/output control module 24. The third input/output control module 24 displays the received messages in the new thread window.
  • In step S[0165] 377, the creation module 21 consults the administration table to judge whether or not a window for link source threads is being displayed. If it is being displayed, instruction is to the third input/output control module 24 not to display the link-source window. Wherein this instruction is present, the third input/output control module 24 eliminates the link-source window.
  • In step S[0166] 378, the creation module 21 updates the administration table. That is, it writes into the new entries predetermined information relating to the linked threads (FIG. 11). In addition, wherein the link source threads are not to be displayed in aforementioned step S377, the creation module 21 changes the “Status” of the link source threads.
  • In step S[0167] 379, the creation module 21 reports to the reporting module 22 that threads have been linked. The reporting module 22 sends out thread commands that report link source thread IDs and forwarding destination thread IDs. Wherein, for example, user “Jun-Jun” links thread IDs “Th1” and “Th2,” a thread command example would be as follows.
  • Th_merge Th1,Th2;Th3;Creator=Jun-Jun [0168]
  • If “No” is judged in aforementioned step S[0169] 373, step S380 ensues. In step S380, a new thread window display instruction for displaying the linked threads is to the third input/output control module 24. In response to the instruction, the third input/output control module 24 displays the new thread window.
  • (3-3) Cancellation Process Subroutine [0170]
  • FIG. 18 is a flowchart of processes in a cancellation process subroutine executed wherein “Cancel” has been selected in [0171] aforementioned toolbar 305. When aforementioned step S41 in the main routine ensues, the process here below begins.
  • Initially, in step S[0172] 411, the creation module 21 instructs to the third input/output control module 24 display of a selection window similar to FIG. 12. Preceding the instruction the creation module 21 acquires from the administration table the title list for the threads, which it sends along with the instruction to the third input/output control module 24. In accordance with the instruction, the third input/output control module 24 displays a selection window. When the “Cancel” button is pressed, the cancellation process terminates.
  • In step S[0173] 412, when a thread selection is made and the “OK” button is pressed, the third input/output control module 24 reports to the creation module 21 the selected thread ID.
  • In step S[0174] 413, the creation module 21 deletes the entry for the reported thread ID from the administration table.
  • In step S[0175] 414, the creation module 21 deletes the aforementioned cancelled thread ID from the message list.
  • In step S[0176] 415, the creation module 21 reports cancellation of the thread to the reporting module 22. The reporting module 22 sends out a thread command reporting the thread cancellation—a thread command as below, for example.
  • Th_delete;ThID=Th1;Creator=Jun-Jun;User=Jun-Jun,ohtsuka,jormiya;private [0177]
  • The process flow then returns to aforementioned step S[0178] 33 of the main routine.
  • Herein, in case the cancelled thread is a linked thread, if when the link was made the link source threads were set to “Don't Display,” it is desirable to once again make the status of the link source threads “Display.” Therein, at first the [0179] creation module 21 consults the administration table and executes a decision as to whether the cancelled thread is a link thread or not. This decision is executed preceding aforementioned step S413. Wherein it is a link thread, the creation module 21 consults the link source thread status and if the status is “Don't Display,” changes it to “Display.” The creation module 21 also acquires messages in the link source threads from the message list. The creation module 21 then causes the link source threads to be displayed by sending an instruction for display of the link source threads, and the acquired messages, to the third input/output control module 24. Presumably, when the threads are linked, the status of the link source threads is to be stored in memory, and if a linked thread is cancelled, the link source threads are returned to the stored state.
  • (3-4) Displaying Process Subroutine [0180]
  • FIG. 19 is a flowchart of a display process subroutine that the [0181] creation module 21 carries out wherein “Display” has been selected in aforementioned toolbar 305. When aforementioned step S43 ensues in the main routine, the process here below starts.
  • In step S[0182] 431, the creation module 21 directs display of the FIG. 12 selection window to the third input/output control module 24. Preceding the instruction, the creation module 21 also retrieves a thread title list from the administration table, which it sends together with the aforementioned instruction to the third input/output control module 24. The third input/output control module 24 displays a selection window in accordance with the instruction.
  • In step S[0183] 432, when any thread has been selected and the “OK” button is pressed, the third input/output control module 24 reports the selected thread to the creation module 21. Step S433 then ensues. When the “Cancel” button is pressed, the displaying process terminates.
  • In step S[0184] 433, the creation module 21 specifies IDs for the selected threads. The creation module 21 then acquires messages in the selected threads from the message list using the thread IDs.
  • In step S[0185] 434, the creation module 21 sends an instruction for thread window display, and the acquired messages, to the third input/output control module 24. The third input/output control module 24 displays the thread window, and outputs the messages within the window.
  • In step S[0186] 435, the creation module 21 changes the “Status” of the aforementioned displayed thread in the administration table to “Display.” The flow then returns to aforementioned step S33 of the main routine.
  • Other Embodiments [0187]
  • (a) In aforementioned FIG. 7, messages that have been displayed in [0188] thread window 307 are also displayed in chat window 303. The setting, however, can be such that messages displayed in thread window are not displayed in the chat window. Preferably, the settings are such that the user can make them.
  • (b) In the aforementioned first embodiment, the disclosure level is set automatically, but the user may set the disclosure level with every thread creation. In that case, presumably, a button for setting the disclosure level would be provided in the aforementioned confirmation window of FIG. 6. [0189]
  • (c) In the aforementioned first embodiment, transmission/reception of thread information is carried out via a chat client, but may be carried out among display control devices directly. [0190]
  • (d) For the situation in which a user that has linked threads issues messages to the thread window, a configuration is conceivable wherein other users' display control devices display the messages in all windows for those link source threads. Further, the text display method may be varied so as to distinguish the messages in the link threads. [0191]
  • (e) Wherein threads are created, it is possible to make all members' display the same by sending to the selecting parties the selected message ID together with the thread creation command. [0192]
  • Various details of the present invention may be changed without departing from its spirit nor its scope. Furthermore, the foregoing description of the embodiments according to the present invention is provided for illustration only, and not for the purpose of limiting the invention as defined by the appended claims and their equivalents. [0193]

Claims (10)

What is claimed is:
1. A display control method utilized in a chat system in which users on information terminals share identical networks mutually, enabling text conversation, the display control method:
correlating messages within the network based on user instructions and creating message groups and predetermined message group information relating to the message groups;
sharing the created message group information with users within the network;
sending messages to the message groups out to the network; and
in accordance with user instructions displaying the message groups independently of messages within the network.
2. A display control device utilized in a chat device wherein, sharing an identical network mutually, transmission/reception of text messages is possible, the display control device provided with:
creating means for correlating messages on the network based on user instructions and creating message groups and predetermined message group information relating to the message groups;
reporting means for transmitting/receiving the created message group information to and from other among display control devices on the network;
memory means for storing the message group information; and
input/output control means for obtaining the message groups from the chat device and in accordance with instructions from users, enabling display of the message groups independently of messages within the network.
3. The display control device set forth in claim 2, wherein the creating means accepts operations directed to the message groups and updates the message group information.
4. The display control device set forth in claim 2, wherein said input/output control means further accepts messages in which the message groups are designated and acquires from the network or sends to the network messages to the message groups.
5. The display control device set forth in claim 2, wherein said creation means correlates messages within the network based on selection of the chat device from a user, and creates message groups out of messages from the selected chat devices and message group information containing information specifying the selected chat devices.
6. The display control device set forth in claim 2, further provided with a message-list correlating messages within the network and message identifying information specifying the messages; wherein
said creation means creates, based on selection of the messages from a user, message groups containing the selected messages and message group information containing message-identifying information for the selected messages.
7. The display control device set forth in claim 2, wherein the creation means creates message group information in which a disclosure level of the created message groups is contained.
8. The display control device set forth in claim 2, wherein message-group identifying information specifying the message groups is contained in the message group information.
9. The display control device set forth in claim 2, wherein the input/output control means judges based on the message group information whether to display the message groups, and displays the message groups based on the judgment.
10. A computer-readable recording medium on which is recorded a display control program utilized in a chat device wherein, sharing an identical network mutually, transmission/reception of messages through text is possible, the computer-readable recording medium on which is recorded the display control program for-executing:
(A) a step of correlating messages on the network based on instructions from a user and creating message groups and predetermined message group information relating to the message groups;
(B) a step of transmitting/receiving the created message group information among other chat devices within the network;
(C) a step of storing the message group information; and
(D) a step of obtaining the message groups from the chat device and in accordance with instructions from users displaying the message groups independently of messages within the network.
US10/431,434 1999-03-19 2003-05-08 Display control method and device Abandoned US20030197730A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/431,434 US20030197730A1 (en) 1999-03-19 2003-05-08 Display control method and device

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
JP07534399A JP3644580B2 (en) 1999-03-19 1999-03-19 Display control method and apparatus
JP11-075343 1999-03-19
US09/468,936 US6630944B1 (en) 1999-03-19 1999-12-22 Display control method and device
US10/431,434 US20030197730A1 (en) 1999-03-19 2003-05-08 Display control method and device

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/468,936 Continuation US6630944B1 (en) 1999-03-19 1999-12-22 Display control method and device

Publications (1)

Publication Number Publication Date
US20030197730A1 true US20030197730A1 (en) 2003-10-23

Family

ID=13573525

Family Applications (2)

Application Number Title Priority Date Filing Date
US09/468,936 Expired - Fee Related US6630944B1 (en) 1999-03-19 1999-12-22 Display control method and device
US10/431,434 Abandoned US20030197730A1 (en) 1999-03-19 2003-05-08 Display control method and device

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/468,936 Expired - Fee Related US6630944B1 (en) 1999-03-19 1999-12-22 Display control method and device

Country Status (2)

Country Link
US (2) US6630944B1 (en)
JP (1) JP3644580B2 (en)

Cited By (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040085354A1 (en) * 2002-10-31 2004-05-06 Deepak Massand Collaborative document development and review system
WO2005104433A1 (en) * 2004-04-21 2005-11-03 Koninklijke Philips Electronics, N.V. System and method for managing threads in a network chat environment
US20060026593A1 (en) * 2004-07-30 2006-02-02 Microsoft Corporation Categorizing, voting and rating community threads
US20060059235A1 (en) * 2004-09-15 2006-03-16 International Business Machines Corporation System and method for multi-threaded discussion within a single instant messenger pane
US20070174408A1 (en) * 2006-01-26 2007-07-26 International Business Machines Corporation Filtering unnecessary chat artifacts from persistent chats
US20080256188A1 (en) * 2007-01-29 2008-10-16 Deepak Massand Method of removing metadata from email attachments
US20080275992A1 (en) * 2005-02-09 2008-11-06 Access Systems Americas, Inc. System and method of managing connections between a computing system and an available network using a connection manager
US20080301193A1 (en) * 2006-01-29 2008-12-04 Deepak Massand Method of compound document comparison
US20090006979A1 (en) * 2007-06-27 2009-01-01 International Business Machines Corporation Text exchange facility for joining multiple text exchange communications into a single topic based communication
US20090112991A1 (en) * 2007-10-29 2009-04-30 International Business Machines Corporation Instant conversation in a thread of an online discussion forum
US20090319917A1 (en) * 2008-06-24 2009-12-24 Omri Fuchs Multi-User Conversation Topic Change
US20100057460A1 (en) * 2004-12-20 2010-03-04 Cohen Michael H Verbal labels for electronic messages
US20100210291A1 (en) * 2009-02-17 2010-08-19 John Lauer Short Code Provisioning and Threading Techniques for Bidirectional Text Messaging
US20100241943A1 (en) * 2009-03-17 2010-09-23 Litera Technology Llc. System and method for the comparison of content within tables separate from form and structure
CN101867634A (en) * 2010-03-03 2010-10-20 深圳市同洲电子股份有限公司 Information prompting method and device in mobile terminal
US20110145744A1 (en) * 2009-12-15 2011-06-16 International Business Machines Corporation Abbreviated user interface for instant messaging to minimize active window focus changes
US20120198531A1 (en) * 2011-01-31 2012-08-02 Microsoft Corporation Multi-device session pairing using a visual tag
US20140237394A1 (en) * 2013-02-20 2014-08-21 Samsung Electronics Co., Ltd. Apparatus and method for controlling messenger in terminal
US9483451B2 (en) 2013-03-14 2016-11-01 Scribestar Ltd. System and method for handling user editing history based on spawning, merging data structures of directed acyclic graph
US9756002B2 (en) 2014-03-21 2017-09-05 Litera Technologies, LLC Systems and methods for email attachments management
US10025782B2 (en) 2013-06-18 2018-07-17 Litera Corporation Systems and methods for multiple document version collaboration and management
US10257155B2 (en) 2004-07-30 2019-04-09 Microsoft Technology Licensing, Llc Suggesting a discussion group based on indexing of the posts within that discussion group
US10536408B2 (en) 2015-09-16 2020-01-14 Litéra Corporation Systems and methods for detecting, reporting and cleaning metadata from inbound attachments
US10685177B2 (en) 2009-01-07 2020-06-16 Litera Corporation System and method for comparing digital data in spreadsheets or database tables
US11256854B2 (en) 2012-03-19 2022-02-22 Litera Corporation Methods and systems for integrating multiple document versions

Families Citing this family (98)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000076342A (en) * 1998-09-01 2000-03-14 Canon Inc Device and method for purchase request authentication and computer-readable storage medium
US20020021307A1 (en) * 2000-04-24 2002-02-21 Steve Glenn Method and apparatus for utilizing online presence information
US7159008B1 (en) * 2000-06-30 2007-01-02 Immersion Corporation Chat interface with haptic feedback functionality
US7028263B2 (en) * 2000-07-19 2006-04-11 Research In Motion Limited User interface and method for viewing short messages on a wireless device
GB2366706B (en) * 2000-08-31 2004-11-03 Content Technologies Ltd Monitoring electronic mail messages digests
US7035903B1 (en) * 2000-11-22 2006-04-25 Xerox Corporation Systems and methods for the discovery and presentation of electronic messages that are related to an electronic message
JP2002215518A (en) * 2000-11-22 2002-08-02 Xerox Corp System and method for message management
US8024408B1 (en) 2000-11-22 2011-09-20 Xerox Corporation System and method for managing a computer-mediated discussion forum
US8539030B2 (en) * 2000-11-22 2013-09-17 Xerox Corporation System and method for managing digests comprising electronic messages
US6934734B2 (en) * 2000-12-04 2005-08-23 International Business Machines Corporation Method and apparatus for managing and presenting changes to an object in a data processing system
US6993564B2 (en) * 2000-12-22 2006-01-31 At&T Corp. Method of authorizing receipt of instant messages by a recipient user
JP4213360B2 (en) * 2001-05-15 2009-01-21 株式会社東芝 Knowledge accumulation support system and reply message processing method in the same system
JP4740487B2 (en) * 2001-08-10 2011-08-03 株式会社リコー Message processing device and its control program
US7716287B2 (en) 2004-03-05 2010-05-11 Aol Inc. Organizing entries in participant lists based on communications strengths
US7774711B2 (en) 2001-09-28 2010-08-10 Aol Inc. Automatic categorization of entries in a contact list
US7192235B2 (en) 2001-11-01 2007-03-20 Palm, Inc. Temporary messaging address system and method
US7137074B1 (en) * 2002-05-31 2006-11-14 Unisys Corporation System and method for displaying alarm status
US8150922B2 (en) * 2002-07-17 2012-04-03 Research In Motion Limited Voice and text group chat display management techniques for wireless mobile terminals
US7640293B2 (en) * 2002-07-17 2009-12-29 Research In Motion Limited Method, system and apparatus for messaging between wireless mobile terminals and networked computers
US7111044B2 (en) * 2002-07-17 2006-09-19 Fastmobile, Inc. Method and system for displaying group chat sessions on wireless mobile terminals
US7363594B1 (en) * 2002-08-19 2008-04-22 Sprint Communications Company L.P. Workflow event editor
US8037150B2 (en) 2002-11-21 2011-10-11 Aol Inc. System and methods for providing multiple personas in a communications environment
US7636755B2 (en) * 2002-11-21 2009-12-22 Aol Llc Multiple avatar personalities
US7263614B2 (en) 2002-12-31 2007-08-28 Aol Llc Implicit access for communications pathway
US7945674B2 (en) 2003-04-02 2011-05-17 Aol Inc. Degrees of separation for handling communications
US20040179037A1 (en) 2003-03-03 2004-09-16 Blattner Patrick D. Using avatars to communicate context out-of-band
US7908554B1 (en) 2003-03-03 2011-03-15 Aol Inc. Modifying avatar behavior based on user action or mood
US7231229B1 (en) 2003-03-16 2007-06-12 Palm, Inc. Communication device interface
US7835504B1 (en) 2003-03-16 2010-11-16 Palm, Inc. Telephone number parsing and linking
US20040210639A1 (en) * 2003-03-26 2004-10-21 Roy Ben-Yoseph Identifying and using identities deemed to be known to a user
US7669134B1 (en) 2003-05-02 2010-02-23 Apple Inc. Method and apparatus for displaying information during an instant messaging session
US7640506B2 (en) * 2003-06-27 2009-12-29 Microsoft Corporation Method and apparatus for viewing and managing collaboration data from within the context of a shared document
US7900160B2 (en) * 2003-12-29 2011-03-01 International Business Machines Corporation System and method for illustrating a menu of insights associated with visualizations
US7500200B2 (en) * 2004-09-15 2009-03-03 International Business Machines Corporation System and method for instant messenger busy gauge
US7539732B2 (en) * 2004-09-15 2009-05-26 International Business Machines Corporation Client based instant messenger queue limit
US8683351B2 (en) * 2004-10-26 2014-03-25 International Business Machines Corporation Chat user interface for threaded text chat systems
US9652809B1 (en) 2004-12-21 2017-05-16 Aol Inc. Using user profile information to determine an avatar and/or avatar characteristics
US7734695B2 (en) * 2005-03-08 2010-06-08 International Business Machines Corporation Personal and timed chat interface
US8832569B2 (en) * 2006-01-25 2014-09-09 International Business Machines Corporation Scrolling chat for participation in multiple instant messaging conversations
US8001184B2 (en) * 2006-01-27 2011-08-16 International Business Machines Corporation System and method for managing an instant messaging conversation
US7661067B2 (en) * 2006-02-21 2010-02-09 International Business Machines Corporation Method for providing quick responses in instant messaging conversations
US20070198645A1 (en) * 2006-02-21 2007-08-23 Yen-Fu Chen Method for providing in-context responses to instant messaging conversations
US7779004B1 (en) 2006-02-22 2010-08-17 Qurio Holdings, Inc. Methods, systems, and products for characterizing target systems
US7764701B1 (en) 2006-02-22 2010-07-27 Qurio Holdings, Inc. Methods, systems, and products for classifying peer systems
US7882194B2 (en) * 2006-02-23 2011-02-01 International Business Machines Corporation System, method and program for managing chat sessions
US7769144B2 (en) * 2006-07-21 2010-08-03 Google Inc. Method and system for generating and presenting conversation threads having email, voicemail and chat messages
US8121263B2 (en) 2006-07-21 2012-02-21 Google Inc. Method and system for integrating voicemail and electronic messaging
US7873988B1 (en) 2006-09-06 2011-01-18 Qurio Holdings, Inc. System and method for rights propagation and license management in conjunction with distribution of digital content in a social network
US7992171B2 (en) 2006-09-06 2011-08-02 Qurio Holdings, Inc. System and method for controlled viral distribution of digital content in a social network
US9304675B2 (en) 2006-09-06 2016-04-05 Apple Inc. Portable electronic device for instant messaging
US7801971B1 (en) 2006-09-26 2010-09-21 Qurio Holdings, Inc. Systems and methods for discovering, creating, using, and managing social network circuits
US7925592B1 (en) 2006-09-27 2011-04-12 Qurio Holdings, Inc. System and method of using a proxy server to manage lazy content distribution in a social network
US7782866B1 (en) 2006-09-29 2010-08-24 Qurio Holdings, Inc. Virtual peer in a peer-to-peer network
US8554827B2 (en) 2006-09-29 2013-10-08 Qurio Holdings, Inc. Virtual peer for a content sharing system
US8418069B2 (en) * 2006-09-29 2013-04-09 International Business Machines Corporation Spinning off chat threads
US7886334B1 (en) * 2006-12-11 2011-02-08 Qurio Holdings, Inc. System and method for social network trust assessment
US8346864B1 (en) 2006-12-13 2013-01-01 Qurio Holdings, Inc. Systems and methods for social network based conferencing
US7698380B1 (en) 2006-12-14 2010-04-13 Qurio Holdings, Inc. System and method of optimizing social networks and user levels based on prior network interactions
US7730216B1 (en) 2006-12-14 2010-06-01 Qurio Holdings, Inc. System and method of sharing content among multiple social network nodes using an aggregation node
US9195996B1 (en) 2006-12-27 2015-11-24 Qurio Holdings, Inc. System and method for classification of communication sessions in a social network
US9140552B2 (en) 2008-07-02 2015-09-22 Qualcomm Incorporated User defined names for displaying monitored location
US9031583B2 (en) 2007-04-11 2015-05-12 Qualcomm Incorporated Notification on mobile device based on location of other mobile device
US20080254811A1 (en) 2007-04-11 2008-10-16 Palm, Inc. System and method for monitoring locations of mobile devices
US8315652B2 (en) 2007-05-18 2012-11-20 Immersion Corporation Haptically enabled messaging
US9954996B2 (en) 2007-06-28 2018-04-24 Apple Inc. Portable electronic device with conversation management for incoming instant messages
US8327272B2 (en) 2008-01-06 2012-12-04 Apple Inc. Portable multifunction device, method, and graphical user interface for viewing and managing electronic calendars
JP4889690B2 (en) * 2008-06-30 2012-03-07 ヤフー株式会社 Conversation display method and server apparatus
US8108777B2 (en) 2008-08-11 2012-01-31 Microsoft Corporation Sections of a presentation having user-definable properties
US9935792B2 (en) * 2009-02-24 2018-04-03 Blackberry Limited System and method for switching between conversations in instant messaging applications
JP5679252B2 (en) * 2009-03-04 2015-03-04 Necソリューションイノベータ株式会社 Electronic medical record system
JP5162508B2 (en) * 2009-03-23 2013-03-13 株式会社ソニー・コンピュータエンタテインメント Client device, image display method, image processing program, and storage medium storing image processing program
JP2010109995A (en) * 2009-12-04 2010-05-13 Kazuhiro Yamamoto Voice chat system having call-significance function
EP2517399B1 (en) 2009-12-21 2017-01-25 Kik Interactive Inc. Systems and methods for accessing and controlling media stored remotely
US20120117164A1 (en) * 2010-11-10 2012-05-10 Yegor Bugayenko Method and Software of NetBout
JP5777135B2 (en) * 2010-11-22 2015-09-09 株式会社フォーカルワークス Post processing system
US20120297305A1 (en) * 2011-05-17 2012-11-22 Microsoft Corporation Presenting or sharing state in presence
US9411506B1 (en) * 2011-06-28 2016-08-09 Google Inc. Providing additional functionality for a group messaging application
KR101793990B1 (en) * 2011-10-12 2017-11-07 주식회사 케이티 Letter message receiving·sending apparatus and method for handheld terminal
US9042266B2 (en) 2011-12-21 2015-05-26 Kik Interactive, Inc. Methods and apparatus for initializing a network connection for an output device
JP6102016B2 (en) * 2012-11-12 2017-03-29 株式会社コナミデジタルエンタテインメント Display device and program
JP5917373B2 (en) * 2012-11-12 2016-05-11 株式会社コナミデジタルエンタテインメント Display device, control method, and program
US9210113B2 (en) * 2013-02-13 2015-12-08 Blackberry Limited Method, system and apparatus for automatically unsuppressing threads
JP6269654B2 (en) * 2013-03-29 2018-01-31 日本電気株式会社 Display control apparatus, display control method, and program
JP5995220B2 (en) 2014-07-11 2016-09-21 インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Machines Corporation Apparatus and method for processing messages
US11902232B1 (en) 2014-11-18 2024-02-13 Amazon Technologies, Inc. Email conversation linking
US10044662B1 (en) * 2014-11-18 2018-08-07 Amazon Technologies, Inc. Email conversation linking
US11093125B1 (en) 2014-12-09 2021-08-17 Amazon Technologies, Inc. Email conversation linking
US10110523B2 (en) 2015-02-13 2018-10-23 Avaya Inc. System and method for topic based segregation in instant messaging
JP6356169B2 (en) 2016-03-03 2018-07-11 Line株式会社 Display control method, program, and terminal
US11218431B2 (en) * 2016-09-09 2022-01-04 Tariq JALIL Method and system for facilitating user collaboration
US10402371B2 (en) 2017-07-20 2019-09-03 Slack Technologies, Inc. Method, apparatus and computer program product for generating externally shared communication channels
US11341093B2 (en) 2017-07-20 2022-05-24 Slack Technologies, Llc Method, apparatus and computer program product for generating externally shared communication channels
US10541825B2 (en) * 2017-07-20 2020-01-21 Slack Technologies, Inc. Method, apparatus and computer program product for generating externally shared communication channels
WO2019163079A1 (en) * 2018-02-23 2019-08-29 富士通株式会社 Conversation control program, conversation control method, and conversation control device
US11757953B2 (en) * 2018-05-29 2023-09-12 Freshworks Inc. Online collaboration platform for collaborating in context
KR102561557B1 (en) * 2018-11-30 2023-08-01 세일즈포스 인코포레이티드 Method, apparatus, and computer program product for creating externally shared communication channels
US11099726B1 (en) * 2019-04-30 2021-08-24 Slack Technologies, Inc. Group-based communication system and apparatus configured to manage user-defined channel labels associated with a plurality of group-based communication channels
WO2023136804A1 (en) * 2020-06-01 2023-07-20 Tariq Jalil Method and system for facilitating user collaboration

Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5793365A (en) * 1996-01-02 1998-08-11 Sun Microsystems, Inc. System and method providing a computer user interface enabling access to distributed workgroup members
US5880731A (en) * 1995-12-14 1999-03-09 Microsoft Corporation Use of avatars with automatic gesturing and bounded interaction in on-line chat session
US5949414A (en) * 1996-10-31 1999-09-07 Canon Kabushiki Kaisha Window control with side conversation and main conference layers
US5956491A (en) * 1996-04-01 1999-09-21 Marks; Daniel L. Group communications multiplexing system
US6014136A (en) * 1996-03-05 2000-01-11 Casio Computer Co., Ltd. Data processing apparatus with communication function
US6151621A (en) * 1997-04-10 2000-11-21 International Business Machines Corp. Personal conferencing system
US6175619B1 (en) * 1998-07-08 2001-01-16 At&T Corp. Anonymous voice communication using on-line controls
US6212548B1 (en) * 1998-07-30 2001-04-03 At & T Corp System and method for multiple asynchronous text chat conversations
US6219045B1 (en) * 1995-11-13 2001-04-17 Worlds, Inc. Scalable virtual world chat client-server system
US6256663B1 (en) * 1999-01-22 2001-07-03 Greenfield Online, Inc. System and method for conducting focus groups using remotely loaded participants over a computer network
US6336133B1 (en) * 1997-05-20 2002-01-01 America Online, Inc. Regulating users of online forums
US6345290B2 (en) * 1997-12-19 2002-02-05 Fujitsu Limited Chat system displaying attribute information, number of statements or amount of statements in registered channel
US6370563B2 (en) * 1996-09-30 2002-04-09 Fujitsu Limited Chat system terminal device therefor display method of chat system and recording medium
US6393461B1 (en) * 1998-02-27 2002-05-21 Fujitsu Limited Communication management system for a chat system
US6487584B1 (en) * 1998-03-18 2002-11-26 Sony International (Europe) Gmbh Multiple personality internet account
US7478334B2 (en) * 2005-01-20 2009-01-13 International Business Machines Corporation Folding text in side conversations

Patent Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6219045B1 (en) * 1995-11-13 2001-04-17 Worlds, Inc. Scalable virtual world chat client-server system
US5880731A (en) * 1995-12-14 1999-03-09 Microsoft Corporation Use of avatars with automatic gesturing and bounded interaction in on-line chat session
US5793365A (en) * 1996-01-02 1998-08-11 Sun Microsystems, Inc. System and method providing a computer user interface enabling access to distributed workgroup members
US6014136A (en) * 1996-03-05 2000-01-11 Casio Computer Co., Ltd. Data processing apparatus with communication function
US5956491A (en) * 1996-04-01 1999-09-21 Marks; Daniel L. Group communications multiplexing system
US6370563B2 (en) * 1996-09-30 2002-04-09 Fujitsu Limited Chat system terminal device therefor display method of chat system and recording medium
US5949414A (en) * 1996-10-31 1999-09-07 Canon Kabushiki Kaisha Window control with side conversation and main conference layers
US6151621A (en) * 1997-04-10 2000-11-21 International Business Machines Corp. Personal conferencing system
US6336133B1 (en) * 1997-05-20 2002-01-01 America Online, Inc. Regulating users of online forums
US6345290B2 (en) * 1997-12-19 2002-02-05 Fujitsu Limited Chat system displaying attribute information, number of statements or amount of statements in registered channel
US6393461B1 (en) * 1998-02-27 2002-05-21 Fujitsu Limited Communication management system for a chat system
US6487584B1 (en) * 1998-03-18 2002-11-26 Sony International (Europe) Gmbh Multiple personality internet account
US6175619B1 (en) * 1998-07-08 2001-01-16 At&T Corp. Anonymous voice communication using on-line controls
US6212548B1 (en) * 1998-07-30 2001-04-03 At & T Corp System and method for multiple asynchronous text chat conversations
US6256663B1 (en) * 1999-01-22 2001-07-03 Greenfield Online, Inc. System and method for conducting focus groups using remotely loaded participants over a computer network
US7478334B2 (en) * 2005-01-20 2009-01-13 International Business Machines Corporation Folding text in side conversations

Cited By (48)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11263389B2 (en) 2002-10-31 2022-03-01 Litera Corporation Collaborative hierarchical document development and review system
US9105007B2 (en) 2002-10-31 2015-08-11 Litéra Technologies, LLC Collaborative hierarchical document development and review system
US20040085354A1 (en) * 2002-10-31 2004-05-06 Deepak Massand Collaborative document development and review system
US7818678B2 (en) * 2002-10-31 2010-10-19 Litera Technology Llc Collaborative document development and review system
US20100235763A1 (en) * 2002-10-31 2010-09-16 Litera Technology Llc. Collaborative hierarchical document development and review system
WO2005104433A1 (en) * 2004-04-21 2005-11-03 Koninklijke Philips Electronics, N.V. System and method for managing threads in a network chat environment
US20070255791A1 (en) * 2004-04-21 2007-11-01 Koninklijke Philips Electronics, N.V. System and Method for Managing Threadsd in a Network Chat Environment
US20060026593A1 (en) * 2004-07-30 2006-02-02 Microsoft Corporation Categorizing, voting and rating community threads
US10257155B2 (en) 2004-07-30 2019-04-09 Microsoft Technology Licensing, Llc Suggesting a discussion group based on indexing of the posts within that discussion group
US20060059235A1 (en) * 2004-09-15 2006-03-16 International Business Machines Corporation System and method for multi-threaded discussion within a single instant messenger pane
US20100057460A1 (en) * 2004-12-20 2010-03-04 Cohen Michael H Verbal labels for electronic messages
US8831951B2 (en) * 2004-12-20 2014-09-09 Google Inc. Verbal labels for electronic messages
US20080275992A1 (en) * 2005-02-09 2008-11-06 Access Systems Americas, Inc. System and method of managing connections between a computing system and an available network using a connection manager
US20070174408A1 (en) * 2006-01-26 2007-07-26 International Business Machines Corporation Filtering unnecessary chat artifacts from persistent chats
US20080301193A1 (en) * 2006-01-29 2008-12-04 Deepak Massand Method of compound document comparison
US7818660B2 (en) 2006-01-29 2010-10-19 Litera Technology Llc Method of compound document comparison
US8527864B2 (en) 2006-01-29 2013-09-03 Litera Technologies, LLC Method of compound document comparison
US20100318530A1 (en) * 2006-01-29 2010-12-16 Litera Technology Llc. Method of Compound Document Comparison
US20080256188A1 (en) * 2007-01-29 2008-10-16 Deepak Massand Method of removing metadata from email attachments
US7895276B2 (en) 2007-01-29 2011-02-22 Litera Technology Llc Method of managing metadata in attachments to e-mails in a network environment
US9807093B2 (en) 2007-01-29 2017-10-31 Litera Corporation Methods and systems for remotely removing metadata from electronic documents
US8060575B2 (en) 2007-01-29 2011-11-15 Litera Technology Llc Methods and systems for managing metadata in email attachments in a network environment
US8977697B2 (en) 2007-01-29 2015-03-10 Litera Technology Llc Methods and systems for removing metadata from an electronic document attached to a message sent from a mobile electronic device
US20090006979A1 (en) * 2007-06-27 2009-01-01 International Business Machines Corporation Text exchange facility for joining multiple text exchange communications into a single topic based communication
US20160028662A1 (en) * 2007-10-29 2016-01-28 International Business Machines Corporation Instant conversation in a thread of an online discussion forum
US9177284B2 (en) * 2007-10-29 2015-11-03 International Business Machines Corporation Instant conversation in a thread of an online discussion forum
US9716677B2 (en) * 2007-10-29 2017-07-25 International Business Machines Corporation Instant conversation in a thread of an online discussion forum
US20090112991A1 (en) * 2007-10-29 2009-04-30 International Business Machines Corporation Instant conversation in a thread of an online discussion forum
US8375308B2 (en) * 2008-06-24 2013-02-12 International Business Machines Corporation Multi-user conversation topic change
US20090319917A1 (en) * 2008-06-24 2009-12-24 Omri Fuchs Multi-User Conversation Topic Change
US10685177B2 (en) 2009-01-07 2020-06-16 Litera Corporation System and method for comparing digital data in spreadsheets or database tables
US8463304B2 (en) * 2009-02-17 2013-06-11 Zipwhip, Inc. Short code provisioning and threading techniques for bidirectional text messaging
US20100210291A1 (en) * 2009-02-17 2010-08-19 John Lauer Short Code Provisioning and Threading Techniques for Bidirectional Text Messaging
US8381092B2 (en) 2009-03-17 2013-02-19 Litera Technologies, LLC Comparing the content between corresponding cells of two tables separate from form and structure
US8136031B2 (en) 2009-03-17 2012-03-13 Litera Technologies, LLC Comparing the content of tables containing merged or split cells
US20100241943A1 (en) * 2009-03-17 2010-09-23 Litera Technology Llc. System and method for the comparison of content within tables separate from form and structure
US9177298B2 (en) * 2009-12-15 2015-11-03 International Business Machines Corporation Abbreviated user interface for instant messaging to minimize active window focus changes
US20110145744A1 (en) * 2009-12-15 2011-06-16 International Business Machines Corporation Abbreviated user interface for instant messaging to minimize active window focus changes
CN101867634A (en) * 2010-03-03 2010-10-20 深圳市同洲电子股份有限公司 Information prompting method and device in mobile terminal
US20120198531A1 (en) * 2011-01-31 2012-08-02 Microsoft Corporation Multi-device session pairing using a visual tag
US11256854B2 (en) 2012-03-19 2022-02-22 Litera Corporation Methods and systems for integrating multiple document versions
US9565146B2 (en) * 2013-02-20 2017-02-07 Samsung Electronics Co., Ltd. Apparatus and method for controlling messenger in terminal
US20140237394A1 (en) * 2013-02-20 2014-08-21 Samsung Electronics Co., Ltd. Apparatus and method for controlling messenger in terminal
US9483451B2 (en) 2013-03-14 2016-11-01 Scribestar Ltd. System and method for handling user editing history based on spawning, merging data structures of directed acyclic graph
US10025782B2 (en) 2013-06-18 2018-07-17 Litera Corporation Systems and methods for multiple document version collaboration and management
US9756002B2 (en) 2014-03-21 2017-09-05 Litera Technologies, LLC Systems and methods for email attachments management
US11438286B2 (en) 2014-03-21 2022-09-06 Litera Corporation Systems and methods for email attachments management including changing attributes
US10536408B2 (en) 2015-09-16 2020-01-14 Litéra Corporation Systems and methods for detecting, reporting and cleaning metadata from inbound attachments

Also Published As

Publication number Publication date
JP3644580B2 (en) 2005-04-27
US6630944B1 (en) 2003-10-07
JP2000267976A (en) 2000-09-29

Similar Documents

Publication Publication Date Title
US6630944B1 (en) Display control method and device
US7426540B1 (en) Chat sending method and chat system
JP3964872B2 (en) Data structure, method and system for multimedia communication
US7436428B2 (en) System and method for including participants in a conference call
US6173314B1 (en) Application sharing system with user managed address for conferencing
US9729476B2 (en) Personalization of recent contacts list
US8204935B2 (en) Method and apparatus for providing egalitarian control in a multimedia collaboration session
US8917310B2 (en) Multiparty communications systems and methods that optimize communications based on mode and available bandwidth
US9215095B2 (en) Multiple personalities
US7577711B2 (en) Chat room communication network implementation enabling senders to restrict the display of messages to the chat room chronological displays of only designated recipients
US7596596B2 (en) Chat marking and synchronization
US20070208806A1 (en) Network collaboration system with conference waiting room
CN105915436A (en) System and method for topic based segregation in instant messaging
Zhang et al. RSVP: a new resource reservation protocol
US20040215722A1 (en) Communications systems and methods
JPH03192845A (en) Interactive system control system
JP2001249875A (en) System and method for setting state
CN102307105A (en) Method for initiating conference by group
KR20150001362A (en) Apparatus and method for processing multicast traffic in an openflow environment
Maeno et al. Distributed desktop conferencing system (MERMAID) based on group communication architecture
KR20050114624A (en) Method for managing selective presence for an instantaneous messaging service in a telecommunication network such as an internet network
JP2007042137A5 (en)
JP4485035B2 (en) Virtual space security methods
CN102007753A (en) Method and system for telecommunication sessions using only initial signal messages
CN115550326B (en) Method and system for realizing multi-party conference cascade by using virtual conference

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION