Chat system and chat method

Description: TECHNICAL FIELD [Detailed description of the invention]

【0001】

[Technical field to which the invention belongs]

The present invention relates to a chat system and a chat method for enjoying chat using a personal computer, a personal digital assistant, or the like.

【0002】

[Conventional technology]

IRC (Internet Relay Chut), which is a distributed multi-user chat system using the Internet, and various chats on computer communication have existed as typical chat systems from the past, but all of these chat environments have servers. It is provided, and each chat participant can execute a chat by connecting a terminal device such as a personal computer or a mobile information terminal to the server.

【0003】

In the above IRC, chat is executed in units called channels, and there are no particular restrictions on participation except for technical problems such as server processing power, and participants are specified. It is not possible.

【0004】

In addition, the log, which is a record of the chat, will be recorded on the terminal device of the participant of the chat.

【0005】

[Problems to be Solved by the Invention]

However, the IRC as the chat system has a problem that the participants cannot be specified because the chat is performed in units of channels as described above and there are no particular restrictions on participation. To solve this problem, a system has been developed that can encourage terminals connected to the Internet (but not participating in chat) to participate in chat.

【0006】

However, in order to encourage terminals that are not connected to the Internet at that time to participate in the chat, it is necessary to contact them by other methods such as e-mail or telephone instead of the chat system. There was also a problem that the degree of perfection as a system was low.

【0007】

Further, since the chat log is stored in the terminal device owned by each participant, only a small amount of the log can be stored in the terminal device having a particularly small storage capacity.

【0008】

The present invention has been made in view of the above circumstances, and an object of the present invention is a chat system and a chat method capable of realizing a better chat environment by managing and identifying participants. Is to provide.

【0009】

[Means for solving problems]

The invention according to claim 1 is a chat system having a plurality of client terminals and a chat server connected to these client terminals, and the client terminal in the chat requests a client to participate in the chat. The information of the other client terminal is notified to the chat server, and when the notification is received, the chat server requests the other client terminal to participate in the chat based on the requested client information, and the above other The client terminal is characterized in that, in response to this participation request, a reply as to whether or not to participate in the above chat is given.

【0010】

With such a system configuration, participants can be managed and specified according to the wishes of the client who starts the chat, so that a better chat environment can be realized.

【0011】

The invention according to claim 2 is the invention according to claim 1, wherein the chat server connects a line to the other client terminal when the communication line of the other client terminal requested to participate is not connected. When the other client terminal is connected and decides to participate, the other client terminal makes a call back to the chat server after disconnecting the line, connects the communication line, and then participates in the chat.

【0012】

With such a system configuration, in addition to the action of the invention according to claim 1, it is possible to reliably carry out billing processing for the client who participated in the chat, which can be returned to the development of a higher quality chat environment.

【0013】

The invention according to claim 3 is the invention according to claim 1, wherein the chat server is a client terminal that refuses to participate while being requested to participate at the beginning of the chat, or a client terminal that interrupts the chat that was participating. When a request for participation in the chat is received from the company, the chat is allowed to participate in the middle of the chat.

【0014】

With such a system configuration, in addition to the action of the invention according to claim 1, it is possible to reliably manage the intermediate participation in the chat for the client who first wishes to participate.

【0015】

The invention according to claim 4 is the invention according to claim 1, wherein the client terminal participating in the chat participates in the chat with a client terminal other than the client terminal participating in the chat during the chat. The chat server notifies the chat server of the information of the client requesting the request, and when the chat server receives the notification, the chat server requests the client terminal corresponding to the client information to join the chat in the middle based on the requested client information. The client terminal requested to participate in the middle of the process responds to the request for participation and replies whether or not to participate in the chat.

【0016】

With such a system configuration, in addition to the action of the invention according to claim 1, it is possible to add a new client during the chat and encourage its participation.

【0017】

The invention according to claim 5 is a chat system having a plurality of client terminals and a chat server connected to these client terminals, and the chat server adds chat recognition information to each chat to provide the chat. The feature is that the log is saved and the client terminal downloads the corresponding chat log by designating the chat recognition information to the chat server.

【0018】

With such a system configuration, even a client terminal having a particularly small storage capacity can selectively specify and obtain only the necessary chat logs.

【0019】

The invention according to claim 6 is a chat system in which a plurality of chat servers to which client terminals are connected are connected to each other to perform one chat, and the plurality of chat servers each chat with respect to a directly registered client terminal. It is characterized by managing participation and managing logs.

【0020】

With such a system configuration, it is possible to realize a chat environment in a wider area and avoid putting a heavy burden only on a specific chat server.

【0021】

The invention according to claim 7 is a chat method for performing a chat via the Internet, and when a chat participating client terminal requests participation of another client terminal that is not participating in the chat, the other client terminal is requested. When the other client terminal notifies the request for participation and the other client terminal issues a request for participation in response to the notification, the chat is permitted to participate in the chat.

【0022】

With such a method, a new participant can be managed and specified according to the wishes of the client terminal that has already participated in the chat, so that a better chat environment can be realized.

【0023】

The invention according to claim 8 is a chat method for performing a chat via the Internet, in which chat recognition information is added to each chat, the chat log is saved, and the chat recognition information is specified by the client terminal. At that time, the corresponding chat log is downloaded to the client terminal.

【0024】

With such a method, even a client terminal having a particularly small storage capacity can selectively specify and obtain only the necessary chat log.

【0025】

BEST MODE FOR CARRYING OUT THE INVENTION

(First Embodiment) Hereinafter, the first embodiment when the present invention is applied to a chat system using a terminal device such as a personal computer or a mobile information terminal as a client will be described with reference to the drawings.

【0026】

Figure 1 shows the conceptual configuration of the entire system, where 1 is a network (public network, dedicated network, Internet network, etc.), and is operated by a service provider that provides chat services to this network 1. Chat server 2 and various terminal devices such as personal computers and PDAs (Personal Digital Assistants) as client devices owned by users of chat services 3, 3, .... Be connected.

【0027】

Terminal devices 3, 3, .... are all equipped with connection software for connecting to network 1, and have a built-in or intervening modem.

【0028】

The chat server 2 manages a chat user database as shown in FIG. 2 (A) and a chat database as shown in FIG. 2 (B).

【0029】

That is, in the user database shown in FIG. 2 (A), each chat user registered in advance is used as personal data such as a name and address, a terminal device ID, and a nickname representing a participant in the chat. The handle names are managed as one set.

【0030】

Further, in the chat database shown in FIG. 2 (B), a chat ID, a starter ID, a participant ID, a participant ID, a chat log, and a chat log are saved for each chat performed. As for the participant ID and the participant ID, the terminal device ID of the chat user database is used as it is.

【0031】

In addition, regarding the participant ID, an "in-room / absent" flag indicating whether or not the chat is being participated in is additionally set.

【0032】

FIG. 3 shows the appearance configuration of the mobile information terminal 3a, which is one of the terminal devices 3, 3, ...., and has a color liquid crystal display panel on the front of the main body case 11 which is a thin plate-shaped rectangular body. A display input unit 12 integrally formed with a tablet input unit, a speaker 13 that outputs voice information, and a key input unit 14 consisting of, for example, up and down cursor keys (, ) and enter keys (). Is arranged, and an antenna 15 for transmitting and receiving radio waves according to, for example, a digital mobile phone is arranged on the upper end surface.

【0033】

FIG. 4 partially shows the electronic circuit configuration of the mobile information terminal 3a. 21 is a CPU that controls the overall operation, and ROM22, RAM23, and RTC (Real Time Clock) are connected to this CPU21 via a bus. ) 24, the hard disk device (HDD) 25, the tablet input unit 26 forming the display input unit 12, the liquid crystal display unit 27, the key input unit 14, the audio output unit 28, and the wireless communication unit 29 are connected.

【0034】

The ROM 22 fixedly stores the BIOS (basic input / output system) and others, and the RAM 23 has a work memory and the like that temporarily stores the processing data of the CPU 21.

【0035】

The RTC24 measures the current time, and the hard disk device 25 stores an OS (operating system), various application programs, a data file including a telephone directory, and the like.

【0036】

The liquid crystal display unit 27 is composed of a color liquid crystal display panel, its drive circuit, a backlight device, and the like, and displays an operating system and images based on various applications compliant with the operating system. The liquid crystal display unit 27 is displayed on the liquid crystal display unit 27. The tablet input unit 26 is integrally formed to form the display input unit 12.

【0037】

The tablet input unit 26 converts the operation position coordinates into data and inputs it by performing a writing operation or a point operation with a finger or a dedicated stylus pen (not shown here) according to the contents displayed on the liquid crystal display unit 27. A GUI (Graphical User Interface) environment is realized by the display input unit 12 formed by the liquid crystal display unit 27 and the tablet input unit 26, and for example, chatting is performed.

【0038】

The audio output unit 28 digitizes an audio signal having a digital value given from the CPU 21 and drives the speaker 13 in a loudspeaker.

【0039】

The wireless communication unit 29 wirelessly transmits and receives data to and from the chat server 2 via the network 1 by communicating with the nearest base station by the antenna 15 in accordance with the specifications of the digital mobile phone, for example.

【0040】

In addition, at the time of carrying out the chat according to this embodiment, the telephone number of the chat server 2, the telephone book of the communication partner, the ID of the terminal device 3 that participated in the chat, and the starter of the chat when the participation is refused. In addition to storing the ID etc. of the terminal device 3 in the dedicated area of the hard disk device 25, the received chat data shall be temporarily held and stored for backscrolling, but in order to effectively use the small storage capacity. In addition, the chat data shall be deleted when the chat is completed.

【0041】

The various application programs, data files, and the like stored in the hard disk device 25 may be input from an externally connected device, or may be downloaded via the wireless communication unit 29.

【0042】

Next, the operation of the above embodiment will be described.

【0043】

First, the person who wants to start the chat specifies the person who wants to participate in the chat by selecting from the telephone directory registered in the terminal device 3 for execution or by inputting individually. ..

【0044】

FIG. 5 illustrates a display screen on the display input unit 12 in a state where the user of the mobile information terminal 3a is the starter of the chat and the desired participant is selected, and is shown from the upper part of the screen. In order, the selected data area SD that selects and displays the participant data at that time, the registered data area RD that displays the participant data for which the selection is confirmed, the data input area DI that displays the participant data when it is input, An icon area IC consisting of "add", "delete", "register", "notify", and "cancel" icons for designating the operation mode, and a handwritten input recognition area PI for inputting handwritten characters such as participant data are arranged. Of these, the selected data area SD and the registered data area RD are provided with a scroll bar SB so that the display range can be scrolled.

【0045】

FIG. 10 shows the operation contents when the starter of this chat operates the mobile information terminal 3a. At the beginning, the operation by the above icon area IC is waited for, and when the operation is performed, any of the icons is operated. Determine if it has been done (step A01).

【0046】

If the icon is "input", it is input in the handwriting input recognition area PI, the character recognition content is confirmed (step A04), and whether or not the person is registered in the phonebook in advance is the handle name. Judgment by comparison (step A05).

【0047】

If you are a registered person, you do not need to make a new input, so invalidate that input and return to step A01 as it is, but if you are not registered, register it in the phone book newly ( Step A06), further enter the ID and display it in the registered data area RD (step A07), and return to step A01.

【0048】

If the icon is "Select", the candidate participants selected in the selected data area SD at that time are displayed as they are in the registered data area RD together with the ID (step A03), and the process returns to step A01.

【0049】

If the icon is "Delete", as a correction process, the person selected from the persons listed in the registered data area RD at that time is deleted (step A02), and the process returns to step A01.

【0050】

However, if the icon is "Notification", it means that the list of participants has been completed and the operation has been performed to start chat, so at least the ID of the participant selected in the registered data area RD is at least. After confirming that there is one (step A08), connect to the chat server 2 (step A09), and notify the request to start the chat (step A10). At this time, at the same time, the terminal ID of the own machine as the chat starter and the ID of the participant who wishes to participate in the chat are transmitted.

【0051】

After that, it waits for a response from the chat server 2 (step A11), and when there is a response, saves the chat ID obtained from the chat server 2 at the time of the response as a chat history (steps A12, A13).

【0052】

Then, the mode shifts to the chat mode in which the actual chat is performed (step A14), and the response from the chat server 2 is waited for (step A15).

【0053】

When there is a response from the chat server 2 and it receives its own entry message (step A16), it is displayed as chat data in the display input unit 12 (step A17), and further waits for a response from the chat server 2 (step A17). A18).

【0054】

FIG. 6 illustrates the screen displayed by the display input unit 12 at this time. From the top of the screen, the chat data area CD for displaying chat data and the data input area for displaying the contents of the chat sent by itself in a list. A DI, an icon area IC consisting of "send", "delete", "convert", "confirm", and "function" icons for designating an operation mode, and a handwritten input recognition area PI for inputting handwritten characters of chat data are arranged.

【0055】

Of these, in the chat data area CD, a scroll bar SB is added to enable scrolling of the display range. Here, the entry message "Mr. X entered the room (1 person)" using the handle name and other It shows that the response from the participants is waiting.

【0056】

After that, it waits for reception from chat server 2 (step A19), and when it is determined that there is reception, whether the next received content is chat data, chat start permission, or chat stop instruction. (Step A20).

【0057】

If the chat start permission is given, the chat is officially started (step A24), the process as the chat starter is completed, and the chat operation is started.

【0058】

If it is chat data, the chat data is displayed by the display input unit 12 (step A21), and then the state returns to the reception standby state from step A19 again.

【0059】

If it is an instruction to cancel the chat, it is assumed that the chat could not be started, and after displaying a message to that effect on the display input unit 12 (step A22), the chat server via the network 1 The connection with 2 is disconnected (step A23), and this process ends.

【0060】

On the other hand, at the start of such a chat, the chat server 2 executes the processes shown in FIGS. 11 to 14.

【0061】

That is, when the chat server 2 receives the chat start request (step B01), the chat user database shown in FIG. 2 (A) is referred to and registered using the terminal ID of the starter attached to the request. Check if you are a chat user (step B02).

【0062】

Here, if the user is not registered as a chat user, the chat cannot be started. Therefore, a notification for refusing to start the chat is notified to the starter (step B04), and the chat is started with the starter. The connection is disconnected (step B05), this process is terminated once, and the next start request is waited for.

【0063】

If you are registered as a chat user, issue a chat ID (step B06), and use that chat ID to save and set the necessary items in the chat database as shown in Fig. 2 (B) above (step B06). Step B07), and after all the occupancy / absence flags for each participant ID are tentatively set to occupancy (step B08), the starter is notified with the chat ID that issued the chat permission response (step B09). ..

【0064】

Next, the entry message of the starter is generated as chat data (step B10), this is additionally saved as a chat log in the chat database (step B11), and the chat data is transmitted to the starter (step B12).

【0065】

After that, the content of the ID of the participant who the starter wishes to participate in the chat is read out for one person, the content is confirmed (step B13), and after confirming that there is (step B14), the participant ID is entered. Use it to refer to the chat user database (step B15) and check if you are a registered chat user (step B16).

【0066】

If you are a registered chat user, execute the connection with the terminal device stored corresponding to the participant's ID as it is (step B17), and after confirming that the connection was successful. (Step B18), execute a notification requesting the terminal device of the target participant to participate in the chat (Step B19), and confirm that the same process is performed for other participants. After changing and setting (step B20), the process returns to the process from step B13 above.

【0067】

In addition, if it is determined in step B16 above that the ID of the desired participant is not registered in the chat user database, or if it is determined in step B18 above that the connection with the participant was not successful, that participation is made. Generate an error message as chat data indicating that it is not possible to chat with the participant using the person ID (step B21), and additionally save this as a chat log in the chat database (step B22). Send the chat data to the starter (step B23), then change and set the contents of the participant ID to be confirmed to execute the same process for other participants (step B20), and then again from step B13 above. Return to the process of.

【0068】

FIG. 7 illustrates an error message displayed on the mobile information terminal 3a used by the starter at this time, and shows the contents shown in FIG. 6 in the chat data area CD on the screen having the same configuration as that in FIG. In addition, the handle name is used as an error message to indicate the state in which the contents such as "Mr. A's error" and "Mr. 000-000-0000's error" are displayed.

【0069】

However, when the process from step B13 is repeatedly executed while sequentially updating and changing the participant ID for the participants who wished to participate in the chat from the starter in step B20 above, the process for all participants is completed. , Step B14 confirmed that there were no more participants, then at least all participating vehicles that the initiator wanted to join the chat could connect to chat server 2 via network 1. Whether or not a chat can be performed is determined based on whether or not there is one (step B24).

【0070】

Here, if it is determined that there is no participant who can connect and the chat cannot be performed, the mobile information terminal 3a requesting the start of the chat is notified of the cancellation of the chat (step B25), and then the start is performed. After disconnecting from the person (step B26), delete the data related to this chat ID in the chat database (step B27), finish this process once and wait for the next start request. To do.

【0071】

Also, if there is at least one participant who was able to connect in step B24 and there is a possibility that they can chat, then request to join the chat and wait for a response to this request ( Step B28) receives a response notification from the connected device (step B29), and determines whether the content of the response accepts or refuses to participate in the chat. Determine (step B30).

【0072】

If the participant is accepted to participate in the chat, a notification is given to the participant's terminal device 3 to allow reconnection (callback) (step B37), and then the connection is temporarily disconnected (step). B38), it is determined whether or not the terminal device 3 of the participant who has responded to the request to participate in the chat remains (step B36), and if so, the process returns to the process from step B29 again.

【0073】

In steps B37 and B38, the chat participating terminals are made to call back (because the caller is charged at present and the communication charge is high), but it changes depending on the form of the service. For example, if the callee charge or communication charge is low, the connection can be continued without reconnecting.

【0074】

If it is determined in step B29 above that the response was to refuse to participate in the chat, the terminal ID is saved in the chat database on the side of the person who refused to participate (step B31), and then the target terminal is also used. The connection with the device 3 is disconnected (step B32), and then a refusal message indicating that the participant is refused to join the chat using the participant ID is generated as chat data (step B33). Is additionally saved as a chat log in the chat database (step B34), and after sending the chat data to the starter (step B35), the terminal device of the participant who responded to the request to participate in the chat. It is determined whether or not 3 remains (step B36), and if so, the process returns to the process from step B29.

【0075】

FIG. 8 illustrates an error message displayed on the mobile information terminal 3a used by the starter at this time, and shows the contents shown in FIG. 6 in the chat data area CD on the screen having the same configuration as that in FIG. In addition to, the handle name is used as a refusal message to indicate the state in which the content "Mr. A refused." Is displayed.

【0076】

Then, if it is determined in step B36 that there is no other terminal device 3 of the participant who responded to the request to participate in the chat, the participant who next responded to the request to participate in the chat It is determined whether or not at least one of the terminal devices 3 has accepted the participation (step B39).

【0077】

If there is nothing to accept, the mobile information terminal 3a that requested the start of the chat is notified of the cancellation of the chat (step B50), and then the connection with the starter is disconnected (step B51). ), Delete the data related to this chat ID in the chat database (step B52), end this process once and wait for the next start request.

【0078】

In addition, if it is determined in step B39 above that there is at least one that has accepted the participation in the chat, then it is determined whether or not there is a terminal device 3 for which the response to the request for participation in the chat has not been confirmed (step B40). ), If it is determined that it still remains, after waiting for the terminal device 3 to be reconnected for a certain period of time, reconnection is performed to start a new billing process for the terminal device 3. Then (steps B42, B43), save and set the terminal ID on the participant side of the chat database (step B44).

【0079】

Next, the corresponding occupancy / absence flag is set in the occupancy content (step B45), and a response notification permitting chat is sent to the target participant's terminal device 3 together with the chat ID (step B46). , Generate an entry message as chat data indicating that the participant joins the chat using the participant ID (step B47), additionally save this as a chat log in the chat database (step B48), and chat. After simultaneously transmitting the chat data to at least two or more terminal devices 3 including the starter's mobile information terminal 3a that has transitioned to the mode (step B49), there are other responses to requests to participate in the chat. The process returns to the process from step B40 above in order to determine whether or not the unconfirmed terminal device 3 still remains.

【0080】

FIG. 9 illustrates an entry message displayed on the starter's mobile information terminal 3a, which is transitioning to the chat mode at this time. In the chat data area CD on the screen having the same configuration as that of FIG. In addition to the contents shown in Fig. 6, the handle name was used as the entry message, "Mr. Y entered the room." Indicates that the guide message "Chat start OK" is displayed, which indicates that the chat can be executed because the chat has become possible.

【0081】

Then, when it is determined in step B40 above that there are no unconfirmed terminal devices 3 in response to the chat participation request, the starter's mobile information terminal 3a transitioning to the chat mode and participation accepted for participation are performed. A notification is given to the terminal device 3 of the user to allow the start of the chat (step B41), and the process at the start of the chat by the chat server 2 is completed.

【0082】

Next, the operation contents of the terminal device 3 on the participant side requested by the starter to participate in the chat will be described with reference to FIG.

【0083】

At the beginning of the operation, when a request to join the chat is received from the chat server 2 together with the terminal ID of the starter and the line is connected (step C01), the terminal ID of the starter is saved (step C02) and the incoming call is received. After making the notification, the display unit displays the request for participation in the chat together with the handle name of the starter, and the key input unit confirms whether to accept the request and participate in the chat or reject it. This is done by the operation in (step C03).

【0084】

Here, it is determined whether or not the key operation to accept the participation in the chat has been performed (step C04), and when it is determined that the key operation to reject without accepting has been performed (or timed out). Notifies the chat server 2 to reject the chat (step C05), disconnects the connection state with the chat server 2 (step C06), and ends this process.

【0085】

If it is determined in step C04 above that the key operation for accepting the participation in the chat has been performed, the chat server 2 is notified to accept the request for participation in the chat (step C07), and the response is made. After waiting for (step C08), a notification of reconnection permission is received from chat server 2 (step C09), and the connection with chat server 2 is temporarily disconnected (step C10).

【0086】

After that, when the chat server 2 is reconnected to execute the chat (step C11) and the chat permission response is received from the chat server 2 (step C12), the chat ID received in the above step C01 is used as the chat history. After saving (step C13), the mode shifts to chat mode (step C14).

【0087】

Then, it waits for a response from the chat server 2 (step C15), and when there is a response, displays an entry message as chat data obtained by the response on the display unit (step C16).

【0088】

After that, it waits for a response from chat server 2 again (step C17), and when there is a response, it receives a chat start permission notification sent from chat server 2 (step C18), and then starts chat. Then, the process shifts to the transmission / reception of chat data (step C19), and the process at the start is temporarily completed.

【0089】

The billing process for the subsequent chat by the chat server 2 to the terminal device 3 is performed from the time of reconnection in step C11.

【0090】

Next, FIG. 16 describes a series of operations performed by the chat server 2 during the chat.

【0091】

As shown in the figure, when the chat is executed, the chat server 2 receives the terminal ID and the chat data from each terminal device 3 that is chatting (step D01), and the chat user uses the terminal ID. Get the corresponding handle name from the database (step D02).

【0092】

Next, the acquired handle name and the received chat data are combined (step D03), the obtained chat data with the handle name is saved as a chat log in the chat database (step D04), and the chat is joined at that point. The chat data with the saved handle name is sent to all the terminal devices 3 (step D05), and the series of processes is completed. The chat server 2 is from one of the chat participants. This series of processes is repeatedly executed each time chat data is received.

【0093】

When a person who refuses to participate in the chat at the beginning of the chat or a person who interrupts the participation in the chat rejoins the chat being performed from the middle, the following operations are executed. To.

【0094】

FIG. 18 shows the operation contents of the terminal device 3 that wants to participate in the chat in the middle. At the beginning, the chat that the user wants to participate in is selected from the terminal IDs of the starters saved in step C02 of FIG. Do this (step E01) and then connect to chat server 2 (step E02).

【0095】

When the chat server 2 can be connected, the chat server 2 is notified of the request to join the chat in the middle with the terminal ID of the own machine and the terminal ID of the starter selected above (step E03), and the chat for this is performed. Wait for a response from server 2 (step E04).

【0096】

Then, when there is a response from the chat server 2, it is received (step E05), and the received content is for permitting participation in the chat in the middle, or the terminal ID of the own machine refuses to participate. Determine if the request for participation was a notification that it was not on the list as suspended participation (step E06).

【0097】

Here, in the case of an unauthorized notification, after displaying a message on the display unit indicating that the request for participation in the chat is invalid and the user cannot participate (step E15), the connection with the chat server 2 is established. Disconnect (step E16), and this process ends.

【0098】

Also, if it is determined in step E06 above that there was a response from the chat server 2 that allows mid-course participation in the chat, the chat ID of that chat is set to be saved as a chat history (step E07), and the chat mode is immediately entered. (Step E08), wait for a response from chat server 2 (step E09).

【0099】

Then, when there is a response of chat data from the chat server 2, this is received (step E10), and the entry message as chat data obtained by the response is displayed on the display unit (step E11).

【0100】

After that, it waits for a response from chat server 2 (step E12), and when there is a response, it receives a chat start permission notification sent from chat server 2 (step E13), and then starts chat. Assuming that the process shifts to the transmission and reception of chat data (step E14), the process at the start of the chat for mid-term participation is temporarily terminated.

【0101】

FIG. 19 illustrates the operation contents of the chat server 2 that has received the notification from the terminal device 3 requesting the intermediate participation as described above, and attaches the terminal ID and the starter ID to the above notification. The received chat server 2 (step F01) first checks the chat user database using its terminal ID (step F02), and determines whether or not it is a user registered in this chat server 2 (step F01). Step F03).

【0102】

Here, if the terminal ID is not listed in the chat user database and it is determined that the terminal device 3 that sent the terminal ID sent an illegal mid-term participation request, the terminal device 3 After sending the fraudulent notification to (step F17), the connection with the terminal device 3 is disconnected (step F18), and this process ends.

【0103】

If it is determined in step F03 above that the terminal device 3 that sent the notification requesting mid-term participation is a user registered in this chat server 2, the chat database is further checked using the starter ID. Then (step F04), it is determined whether or not the chat registered with the starter ID exists (step F05).

【0104】

Here, if it is determined that the chat by the starter ID does not exist, the process proceeds from the issuance of the fraudulent notification in step F17 above, but if it is determined that it exists, the next step is performed. Refer to the terminal ID of the terminal device 3 and the participation refusal ID of the chat database (step F06), and the terminal device 3 that sent the participation request in the middle refused to participate at the beginning of the chat. Determine if or not (step F07).

【0105】

If you are a participant refusal, after changing the data to move the participant refusal ID in the chat database to the participant ID (step F08), the terminal device 3 that sent the participation request notification on the way On the other hand, a chat ID is added to notify a response that allows participation in the chat (step F09).

【0106】

Furthermore, using the terminal ID of the terminal device 3, an entry message indicating that the participant participates in the chat is generated as chat data (step F10), and this is additionally saved as a chat log in the chat database (step F11). ), The chat data is continuously transmitted to the terminal device 3, and then a response permitting the start of the chat is notified (step F13), and this process ends.

【0107】

If the terminal device 3 that sent the participation request in the middle of step F07 did not refuse to participate at the beginning of the chat, then the terminal ID of the terminal device 3 and the chat database. Refer to the participant ID and the corresponding room / absence flag (step F14), and there is a participant ID that matches the terminal ID of the terminal device 3 that sent the participation request in the middle, and the corresponding room / absence flag. It is determined whether or not the terminal device 3 is a person who left the room on the way depending on whether or not the content indicates the absence (step F15).

【0108】

Here, if it is determined that the person is not a person who left the room in the middle, the process proceeds from the issuance of the fraudulent notification in step F17, but if the person is a person who leaves the room in the middle, the participant in the chat database is concerned. After setting the occupancy / absence flag corresponding to the ID to the occupancy (step F16), the process proceeds from the above step F09, and the terminal device 3 is processed to participate in the chat again.

【0109】

FIG. 17 illustrates chat data displayed by the display input unit 12 of the starter's mobile information terminal 3a, for example, when there is an intermediate participation in this way, and a chat on the screen having the same configuration as that of FIG. 6 above. In the data area CD, in addition to the contents shown in Fig. 6 above, the entry message "Mr. A has entered the room" using the handle name, the number of people "4 people" who are in the room at that time, and the number of people who have entered the room at that time. A guide message "Chat start OK" indicating that the chat can be executed because there are multiple items, and the chat data "Yattokiyo" from "Mr. A" who participated in the middle are displayed. Indicates the state of being.

【0110】

In the middle of chatting in this way, the operation when an operation other than chat data input is executed by the function operation of the terminal device 3 (3a) among the participants including the chat starter will be described.

【0111】

FIG. 20 illustrates a state in which the function selection screen is displayed on the display input unit 12 of the mobile information terminal 3a during the chat. In addition to the various icons of the icon area IC, a new chat data area CD is also displayed. The icon area ICa will be displayed. In this icon area ICa, an icon "addition" for adding a new participant to the chat and an icon "leaving" for leaving the room in the middle of the participating chat are displayed.

【0112】

Then, FIG. 21 shows the content of the operation to be executed when the function selection operation is performed on the mobile information terminal 3a and the above icon "addition" is specified, and the display content on the display input unit 12 at that time. Is the same as the state shown in FIG. 5, and at the beginning, the operation by the icon area IC is waited, and when the operation is performed, it is determined which icon is operated (step G01).

【0113】

If the icon is "input", it is input in the handwriting input recognition area PI, the character recognition content is confirmed (step G04), and whether or not the person is registered in the phonebook in advance is the handle name. Judgment by comparison (step G05).

【0114】

If you are a registered person, you do not need to make a new input, so invalidate that input and return to step G01 as it is, but if you are not registered, after registering it in the phone book newly ( Step G06), further enter the ID and display it in the registered data area RD (step G07), and return to step G01.

【0115】

If the icon is "Select", the candidate participants selected in the selected data area SD at that time are displayed as they are in the registered data area RD together with the ID (step G03), and the process returns to step G01.

【0116】

If the icon is "Delete", as a correction process, the person selected from the persons listed in the registered data area RD at that time is deleted (step G02), and the process returns to step G01.

【0117】

However, if the icon is "Notification", it means that the list of participants to be added is completed and the operation is performed to restart the chat, so the ID of the participant selected in the registered data area RD After confirming that there is at least one (step G08), send a chat participant addition request notification to chat server 2 with the ID of the participant who wants to join the new chat (step G08). Step G09), this process is completed, and the screen returns to the display screen as shown in FIG. 20 above.

【0118】

FIGS. 22 to 24 show the processing contents executed by the chat server 2 that has received the chat participant addition request notification.

【0119】

When the chat participant addition request notification is received from the terminal device 3 (3a) at the beginning (step H01), the content of the ID of the participant who wishes to participate in the chat added to the notification is read out for one person. Check the contents (step H02), confirm that there is (step H03), refer to the chat user database using the participant ID (step H04), and be a registered chat user. Check whether or not (step H05).

【0120】

If you are a registered chat user, execute the connection with the terminal device stored corresponding to the participant's ID as it is (step H06), and after confirming that the connection was successful. (Step H07), a notification requesting the target participant's terminal device 3 to participate in the chat is executed (step H08), and the same process is executed for other similarly added participants. After changing and setting the contents of the participant ID to be confirmed (step H09), the process returns to the above step H02 again.

【0121】

If it is determined in step H05 above that the ID of the participant desired is not registered in the chat user database, or if it is determined in step H07 above that the connection with the participant was not successful, that is the case. An error message indicating that it is not possible to chat with the participant using the participant ID is generated as chat data (step H10), and this is additionally saved as a chat log in the chat database (step H11). Send the chat data to all participants who are currently in the chat (step H12), and then confirm that other participants who wish to add will also be asked to perform the same process. Participant ID content After changing and setting (step H09), the process returns to the process from step H02 above.

【0122】

However, the process from step H02 is repeatedly executed while sequentially updating and changing the participant ID for the participants who newly requested the participants to participate in the chat in the above step H09, and the process for all the participants is performed. When finished, it is confirmed in step H03 that there are no more participants, then a notification is received from the terminal device 3 requesting participation in the chat (step H13), and the content of the response goes to the chat. Determine whether to accept or deny participation in (step H14).

【0123】

If it accepts participation in the chat, it notifies the participant's terminal device 3 to allow reconnection (step H21), then disconnects the connection once (step H22), and then, etc. It is also determined whether or not the terminal device 3 of the participant who has additionally responded to the request for participation in the chat remains (step H20), and if so, the process returns to the process from step H13 again.

【0124】

In addition, if it is determined that the notification received in step H14 above refuses to participate in the chat, after saving the terminal ID on the side of the person who refuses to participate in the chat database (step H15), it is also targeted. The connection with the terminal device 3 is disconnected (step H16), and then a refusal message indicating that the participant is refused to participate in the chat using the participant ID is generated as chat data (step H17). , Save this as a chat log in the chat database (step H18), send the chat data to all the participants who are currently in the chat (step H19), and then go to the chat. It is determined whether or not the terminal device 3 of the participant who has notified the participation request of the above remains (step H20), and if so, the process returns to the process from the above step H13 again.

【0125】

Then, if it is determined in step H20 that there is no other terminal device 3 of the participant who responded to the request for additional participation in the chat, the participant who next responded to the request for participation in the chat It is determined whether or not at least one of the terminal devices 3 of the above has accepted the participation (step H23).

【0126】

If there is nothing to accept, this process is terminated at that point and the chat continues as it is.

【0127】

In addition, if it is determined that there is at least one person who has accepted the participation in the above step H23 chat, then it is determined whether or not there is a terminal device 3 for which the response to the request for participation in the chat has not been confirmed (step H24). If it is determined that the terminal device 3 still remains, the terminal device 3 is reconnected to start the billing process for the newly added terminal device 3 after waiting for the terminal device 3 to be reconnected for a certain period of time. (Steps H25 and H26), and save and set the terminal ID on the participant side of the chat database (step H27).

【0128】

Next, the corresponding occupancy / absence flag is set in the occupancy content (step H28), and a response notification permitting chat is sent to the target participant's terminal device 3 together with the chat ID (step H29). , Generate an entry message indicating that the participant participates in the chat as chat data using the participant ID (step H30), additionally save this as a chat log in the chat database (step H31), and then use the participant ID. After simultaneously transmitting the same chat data to all the terminal devices 3 participating in the chat at that time (step H32), there are still other terminal devices 3 for which the response to the request for additional participation in the chat has not been confirmed. Return to the process from step H24 above to determine whether or not.

【0129】

Then, when it is determined in step H24 above that there are no unconfirmed terminal devices 3 in response to the request for additional participation in the chat, the transition to the chat mode is performed at that time, and the new participation in the chat is accepted. The terminal device 3 of the additional participant is notified to allow the start of the chat (step H33), and the process of adding the participant by the chat server 2 is completed.

【0130】

Next, with reference to FIG. 25, the operation contents of the terminal device 3 on the side requested to participate as an additional member by the chat participants during the chat will be described.

【0131】

At the beginning of the operation, when a request to join the chat is received from the chat server 2 together with the terminal ID of the starter and the line is connected (step I01), the terminal ID of the starter is saved (step I02) and the incoming call is received. After making the notification, the display unit displays the request for participation in the chat together with the handle name of the starter, and the key input unit confirms whether to accept the request and participate in the chat or reject it. (Step I03).

【0132】

Here, it is determined whether or not the key operation to accept the participation in the chat has been performed (step I04), and if it is determined that the key operation to reject the chat has been performed without accepting it, the chat server 2 is notified. After giving a notification to reject the chat (step I05), the connection state with the chat server 2 is disconnected (step I06), and this process ends.

【0133】

If it is determined in step I04 above that the key operation for accepting the participation in the chat has been performed, the chat server 2 is notified to accept the request for participation in the chat (step I07), and the response is made. After waiting for (step I08), a notification of reconnection permission is received from chat server 2 (step I09), and the connection with chat server 2 is temporarily disconnected (step I10).

【0134】

After that, when the chat server 2 is reconnected to execute the chat (step I11) and the chat permission response is received from the chat server 2 (step I12), the chat ID received in the above step I01 is used as the chat history. After saving (step I13), move to chat mode (step I14).

【0135】

Then, it waits for a response from the chat server 2 (step I15), and when there is a response, the entry message as chat data obtained by the response is first displayed on the display unit (step I16), and the same is subsequently obtained. The contents of the chat that has been performed up to that point based on the chat data are displayed on the display unit together with the position before the above entry message (step I17).

【0136】

After that, it waits for a response from chat server 2 again (step I18), and when there is a response, it receives a chat start permission notification sent from chat server 2 (step I19), and then starts chatting. Then, the process shifts to the transmission / reception of chat data (step I20), and the process at the start of participation in the terminal device 3 requested to participate as an additional member is temporarily terminated.

【0137】

The billing process for the subsequent chat by the chat server 2 to the terminal device 3 is performed from the time of reconnection in step I11.

【0138】

Next, in the middle of a chat, a function selection operation is performed on one of the terminal devices 3 participating in the chat, and the icon "leave" of the icon area ICa shown in FIG. 20 above is specified. The operation of is described.

【0139】

FIG. 27 shows the content of the operation executed by the terminal device 3 that has performed the exit operation from the chat. At the beginning, a notification of the exit request from the chat is sent to the chat server 2 (step J01). When a disconnection request for the chat is received from the received chat server 2 (step J02), the connection with the chat server 2 is disconnected at that time (step J03), and the chat stored on the terminal device 3 is related. All chat logs are deleted at once (step J04), and this process ends.

【0140】

In addition, as a result of the above-mentioned exit processing being executed on one of the terminal devices 3 participating in the chat during the chat, the terminal device 3 of the chat starter is participating in the chat. If the chat is only available, or if the request to leave the room is issued from the terminal device 3 of the starter of the chat, the chat server 2 connects at that time assuming that the chat cannot be continued any more. Make a forcible disconnection request to the terminal device 3 that is running.

【0141】

FIG. 28 shows the processing in the terminal device 3 that receives the disconnection request from the chat server 2 in such a case. At the beginning, when the disconnection request for the chat is received from the chat server 2 (step K01), the process is performed. At this point, the connection with the chat server 2 is disconnected (step K02), and all the chat logs related to the chat stored on the terminal device 3 are deleted at once (step K03), and this process is completed.

【0142】

Then, the operation contents of the chat server 2 that receives the exit request from the terminal device 3 will be described with reference to FIG.

【0143】

At the beginning, when the exit request notification from the terminal device 3 participating in the chat is received (step L01), the chat database is created using the terminal ID and chat ID of the terminal device 3 that sent the exit request notification. Confirm and determine whether it is the participant or the initiator of the chat that sent the exit request notification (step L03).

【0144】

Here, if it is determined that the terminal ID belongs to the participant's terminal device 3, the chat server 2 sends a disconnection request notification to the terminal device 3 (step L04), and then connects with the terminal device 3. Disconnect (step L05) and set the room / absence flag attached to the participant ID of the corresponding chat ID in the chat database to the absent side (step L06).

【0145】

After that, using the handle name of the participant ID that notified the exit request, an exit message indicating that the participant leaves the chat is generated as chat data (step L07), and this is used as a chat log in the chat database. In addition to additionally saving (step L08), the chat data is simultaneously transmitted to all other terminal devices 3 participating in the chat at that time (step L09), and at that time due to the above participant leaving the room. Participate in the chat and check the number of connected terminal devices 3 by the number set in the occupancy / absence flag on the participant side of the chat database (step L10).

【0146】

FIG. 26 illustrates chat data on the mobile information terminal 3a, for example, displaying the exit message sent from the chat server 2 at this time. The chat data area CD on the screen having the same configuration as that of FIG. 6 above. In the chat data of "Mr. Y", "I'm sorry, I'm leaving.", The message "Mr. Y left the room." Using the handle name and the number of people still in the room at that time, "3 people." Indicates the state in which is displayed.

【0147】

Here, the chat server 2 determines whether or not there is anyone participating in the chat other than the starter of the chat (step L11), and if it is determined that there are still participants other than the starter. , In order to continue chatting after that, this process is temporarily terminated.

【0148】

In addition, if it is determined in step L11 that no one other than the chat starter is participating in the chat due to the above participant leaving the room, the chat cannot be continued any more, so the start is started. After sending a disconnection request notification to the terminal device 3 of the user (step L12) and disconnecting from the terminal device 3 of the initiator (step L13), the corresponding chat in the chat database is assumed to end the chat. The chat log of the ID is locked so as not to be added any more (step L14), and this process ends.

【0149】

Further, if it is determined that the person who sent the exit request notification using the terminal ID and chat ID of the terminal device 3 that sent the exit request notification in step L03 is the starter of the chat, the chat is immediately started. After sending a disconnect request notification to all participants' terminal devices 3 including the starter participating in the chat at that time (step L15) and disconnecting from all those terminal devices 3 (step L15). Step L16), set the presence / absence flags of all participants other than the starter in the chat database to the absent side (step L17), and then proceed to step L14 above to end the chat in the chat database. The chat log of the corresponding chat ID in is locked so as not to be added any more, and this process ends.

【0150】

After the chat is finished, the chat server 2 can be accessed from the individual terminal device 3 of the starter or the participant of the chat to view the chat log.

【0151】

FIG. 30 shows the processing contents when the terminal device 3 requests the chat server 2 to view the chat log. First, the terminal device 3 initially saves a list of chats that have participated in the past. After selecting the one you want to view the chat log (step M01), connect to the chat server 2 (step M02).

【0152】

Then, a chat log viewing request notification is sent to the connected chat server 2 by adding the terminal ID of the own device and the chat ID desired to be viewed (step M03), and the chat server responds to this. If there is a response from 2, it will be received (step M04).

【0153】

Here, if the content of the response received from the chat server 2 determines whether the chat log is permitted to be viewed or an error has occurred (step M05), and if the content is permitted to be viewed, it is determined. Move to chat log viewing mode.

【0154】

In this chat log browsing mode, some operation related to browsing is performed (step M07), and it is determined whether the operation is for acquiring the chat log or for terminating browsing. (Step M08).

【0155】

If it is determined that the purpose is to acquire the chat log here, a chat log acquisition request notification is sent to the chat server 2 (step M09), and the chat server 2 sends the notification in response to the sent notification. After receiving the incoming chat log and displaying it on the display (step M10), the process of waiting for the next operation is repeatedly executed.

【0156】

Then, when it is determined that the operation for ending the chat log browsing has been performed in the above step M08, a chat log browsing end request notification is sent to the chat server 2 (step M11), and the chat server 2 responds in response. When the disconnection request is received from (step M12), the connection with the chat server 2 is disconnected (step M13), and this process ends.

【0157】

If the content of the response received from the chat server 2 in step M05 above is an error, the chat log corresponding to the sent chat ID does not exist in the chat database of the chat server 2, or this terminal device 3 Assuming that the terminal ID of the chat server 2 is not registered as the terminal ID of the participant corresponding to the corresponding chat ID in the chat database of the chat server 2, immediately disconnect the connection with the chat server 2 (step M14), and then the chat The record is deleted from the stored chat list data (step M15), and this process ends.

【0158】

Next, with reference to FIG. 31, the processing content on the chat server 2 side that receives the chat log viewing request from the terminal device 3 as described above will be described.

【0159】

In the chat server 2, when the terminal device 3 connects via the network 1 and receives the chat log viewing request notification from the terminal device 3 (step N01), the terminal of the terminal device 3 added to the notification is first received. The chat user database is referred to using the ID (step N02), and it is determined whether or not the terminal device 3 is the original chat user (step N03).

【0160】

Here, if it is determined that the terminal ID of the corresponding terminal device 3 is registered in the chat user database, the chat database is further referred to by the chat ID added to the above chat log viewing request notification (step N06). , Determine if the corresponding chat log exists (step N07).

【0161】

Here, if it is determined that the corresponding chat log also exists, then the terminal ID on the participant side in the chat data of the corresponding chat ID in the chat database is used using the terminal ID added to the above chat log viewing request notification. Refers to, and determines whether or not the terminal ID exists, that is, whether or not the terminal device 3 that has sent the browsing request notification has participated in the chat (step N09).

【0162】

Then, if it is determined that the terminal ID exists here as well, the terminal device 3 that has sent this browsing request notification confirms this as the one that browses the chat log in which the own device participates, and the terminal device concerned. Send a chat log viewing permission notification to 3 (step N10), and shift to the chat log viewing mode (step N11).

【0163】

After that, it waits for a response from the terminal device 3 (step N12), and when there is a response, determines whether the notification is a chat log acquisition request or a chat log viewing end (step N13), and chats. If it is a log acquisition request, the chat log corresponding to the request is read from the chat database and transmitted (step N14), and then the process of returning to the above step N12 and waiting for a response is repeated.

【0164】

Then, when it is determined in step N13 that the notification of the end of viewing the chat log has been made, after sending a request notification to disconnect the connection to the terminal device 3 (step N15), the connection is actually disconnected (step N15). N16) This is the end of this process.

【0165】

If it is determined that the terminal ID of the terminal device 3 sent in step N03 above is not registered in the chat user database, or the chat data corresponding to the chat ID sent in step N07 above is the chat database. If it is determined that it does not exist in, or if it is determined in step N09 above that the terminal ID of the terminal device 3 does not exist in the terminal ID of the participant side in the chat data of the corresponding chat ID in the chat database, either Also, assuming that you are not qualified to view the chat log, notify the terminal device 3 of the error message (step N04), disconnect the connection (step N05), and complete this process. To do.

【0166】

Finally, as a summary of the above operations, signal transmission / reception between the chat server 2 at the time of chat execution and chat log viewing, the chat starter's terminal A, and the chat participant's terminal B will be described.

【0167】

FIGS. 32 to 34 show an example of the flow of signals sent and received between the chat starter's terminal A, the chat server 2, and the chat participant's terminal B from the start to the end of the chat. After the chat starter's terminal A makes a line connection with the chat server 2 (Fig. 32 (1)), the chat start request notification is sent by adding the terminal ID of the own machine and the terminal ID that wants to participate. (Fig. 32 (2)).

【0168】

Upon receiving this, the chat server 2 confirms the terminal A, issues a chat ID to the terminal A, and returns a chat permission response (Fig. 32 (3)). And send the entry message as chat data (Fig. 32 (4)).

【0169】

Next, the chat server 2 makes a line connection with the terminal B based on the terminal ID desired by the terminal A of the starter (Fig. 32 (5)), and then requests to participate in the chat (Fig. 32 (6). )) Then, when the acceptance is made from the terminal B (Fig. 32 (7)), after notifying the terminal B of the callback permission (Fig. 33 (1)), once the line with the terminal B is established. Disconnect (Fig. 33 (2)).

【0170】

Terminal B automatically calls back to chat server 2 to connect to the line (Fig. 33 (3)), and then the billing process from chat server 2 is started. Receive the chat permission response with the chat ID added (Fig. 33 (4)).

【0171】

At this point, the chat server 2 delivered the entry message of terminal B as chat data to both terminals A and B (Fig. 33 (5)), and since there were multiple terminals participating in the chat, The chat start permission is also distributed to both parties as if the chat can be started (Fig. 33 (6)).

【0172】

After that, chat data with the caller's terminal ID added is sent and received between terminal A and terminal B via the chat server 2 (Fig. 33 (7)).

【0173】

Then, when terminal A, which is the starter, sends a chat end request notification to chat server 2 (Fig. 34 (1)), the chat server 2 that receives this is assumed to end this chat. A line disconnection request is sent to both parties (Fig. 34 (2)), and the line connection is disconnected between the chat server 2 and terminals A and B, respectively, to end the chat (Fig. 34 (3)). ..

【0174】

FIG. 35 shows the flow of signals sent and received to and from the chat server 2 when the chat participant's terminal, including the chat starter, browses the chat log. First, the terminal communicates with the chat server 2. After making a line connection (Fig. 35 (1)), add the terminal ID of your own device and the chat ID you want to view, and send a chat log viewing request notification (Fig. 35 (2)).

【0175】

Upon receiving this, the chat server 2 confirms the terminal itself and whether or not the terminal has participated in the chat log desired to be viewed, and then grants the terminal permission to view the chat log. Notify (Fig. 35 (3)), and each time a chat log acquisition request is sent from the terminal (Fig. 35 (4)), the corresponding slot chat log data is sent to the terminal (Fig. 35 (5)). )).

【0176】

Then, when the terminal sends a request notification to the chat server 2 to end the viewing of the chat log (Fig. 35 (6)), the chat server 2 that receives this is assumed to end the viewing of this chat log. A line disconnection request is sent to the terminal (Fig. 35 (7)), which disconnects the line connection between the terminal and the chat server and ends the chat log viewing (Fig. 35 (8)).

【0177】

As described in detail above, in the first embodiment of the present invention, participants can be managed and specified according to the desire of the terminal that starts the chat, so that the chat is of better quality under the responsibility of the starter. The environment can be realized.

【0178】

In addition, the terminal on the side requested to participate calls back to the chat server when it decides to participate, and the chat server 2 can charge the terminal that has called back, so that the chat can be performed. It is possible to reliably carry out billing processing for the terminals that participated in the event, which can be returned to the development of a better chat environment.

【0179】

Furthermore, the chat server 2 notifies the chat starter information by, for example, a handle name when requesting participation in each terminal at the beginning of the chat, and the terminal that refuses to participate while being requested to participate at the beginning of the chat, or participates. The terminal that interrupted the chat made a participation request to the starter, and in response to this participation request, the chat server confirmed the starter and allowed mid-course participation in the chat, so that the chat was joined halfway. Can be managed reliably.

【0180】

In the middle of a chat, the terminal participating in the chat notifies the chat server of the information of the terminal newly requesting participation, and the chat server receiving the notification requests the requested terminal to participate in the middle of the chat. Since the terminal requested to participate can decide whether or not to participate, it is possible to add a new terminal even during the chat and encourage the participation, and a more open chat environment can be realized.

【0181】

In addition, the chat server 2 adds a chat ID to each chat and saves the chat log, and by specifying the chat ID to the chat server 2 from the terminal of the participant including the starter, the corresponding chat log Since it is possible to download, even if the terminal has a particularly small storage capacity, it is not necessary to save the chat log by itself, and only the chat log to be viewed can be selectively specified and obtained.

【0182】

(Second Embodiment) Hereinafter, a second embodiment when the present invention is applied to a chat system using a terminal device such as a personal computer or a personal digital assistant as a client will be described with reference to the drawings.

【0183】

Fig. 36 shows the conceptual configuration of the entire system, and for convenience, it is divided and connected. However, 1a to 1c are networks (public network, dedicated network, Internet network, etc.), and these networks 1a to 1c On the other hand, it consists of multiple chat servers 2a to 2c operated by service providers that provide chat services, and a personal computer or PDA as a client device owned by a user who uses the chat service, although not shown here. Various terminal devices 3, 3, .... are connected.

【0184】

Terminal devices 3, 3, ...., which are not shown here, are all equipped with connection software for connecting to networks 1a to 1c, and have a built-in or intervening modem.

【0185】

Further, a management server 4 for managing the processing order of a plurality of chat servers 2a to 2c is provided, and each chat server 2a to 2c has a server ID representing the server in advance.

【0186】

The chat servers 2a to 2c each manage a chat user database as shown in FIG. 37 (A) and a chat database as shown in FIG. 37 (B), respectively.

【0187】

That is, in the chat user database shown in FIG. 37 (A), each chat user registered in advance is used as personal data such as a name and address, a terminal device ID, and a nickname representing a participant in the chat. The handle name and the server ID to be used are managed as one set, and the contents of this chat user database are common to the chat servers 2a to 2c.

【0188】

Further, in the chat database shown in FIG. 37 (B), a chat ID, a starter ID, a participant ID, a participant ID, a list of servers used, and a chat log are saved for each chat performed. Regarding the starter ID, the participant ID, and the participant ID, the terminal device ID of the chat user database is used as it is, and the corresponding server ID is additionally set.

【0189】

In particular, for the participant ID, an "in-room / absent" flag indicating whether the chat is being participated in or ended is additionally set.

【0190】

In each chat server 2a ~ 2c, the chat log in the chat data is saved with a serial number only for the remark part of the user of the chat participant among the chat participants, and the chat flow is the server ID and remark. The person ID and the serial number for each speaker shall be saved as a set in the chat log table of format as shown in FIG. 38.

【0191】

The circuit configurations of the individual terminal devices 3 connected to the networks 1a to 1c are almost the same as those shown in FIG. 3, and the same reference numerals are used in the same parts. Omit.

【0192】

Next, the operation of the above embodiment will be described.

【0193】

In addition, since the basic operation from the start to the end of the chat and the viewing of the chat log, especially on each terminal device 3, is almost the same as the content described in the first embodiment above, each terminal device is described here. The description of the operation in 3 shall be omitted, and in particular, the operation between the chat servers 2a and 2c and the management server 4 shall be described in detail.

【0194】

40 to 45 show the operation of the chat server 2 (2a to 2c) (hereinafter abbreviated as "chat server 2x") that receives the chat start request from the terminal device 3 connected to itself.

【0195】

Initially, when a chat start request is received (step O01), the chat user database shown in Fig. 37 (A) above is referred to using the terminal ID of the starter attached to the request, and registered in the own machine. Check if you are a chat user (step O02).

【0196】

Here, if the user is not registered as a chat user, the chat cannot be started. Therefore, a notification for refusing to start the chat is notified to the starter (step O11), and the chat is started with the starter. Disconnect (step O12), end this process, and wait for the next start request.

【0197】

If you are registered as a chat user, issue a chat ID (step O04), and use that chat ID to save and set the necessary items in the chat database as shown in Fig. 37 (B) above (step O04). Step O05), and after all the occupancy / absence flags for each participant ID are temporarily set to occupancy (step O06), the starter is notified together with the chat ID that issued the chat permission response (step O07). ..

【0198】

Next, the entry message of the starter is generated as chat data (step O08), this is additionally saved as a chat log in the chat database (step O09), and the chat data is transmitted to the starter (step O10).

【0199】

After that, the content of the ID of the participant who the starter wishes to participate in the chat is read out for one person, the content is confirmed (step O13), and after confirming that there is (step O14), the participant ID is entered. Use it to refer to the chat user database (step O15) and check if you are a registered chat user (step O16).

【0200】

If you are a registered chat user, check the server used by the server ID (step O17), add the confirmed server ID to the data of the server list in the chat database, and save it (step O18). ), Determine if the saved server ID represents this chat server 2x own machine (step O19), and only if it represents the own machine, that is, the participant also owns the machine. Save the participant's terminal ID only if it is the terminal device 3 registered in (step O20), and confirm the contents of the participant ID to execute the same process for other participants. After changing and setting (step O21), the process returns to the process from step O13 above.

【0201】

In addition, if it is determined in step O16 above that the ID of the desired participant is not registered in the chat user database, it indicates that it is not possible to chat with that participant using that participant ID. Generate an error message as chat data (step O22), add it to the chat database as a chat log (step O23), send the chat data to the initiator (step O24), and then for other participants After changing and setting the contents of the participant ID to be confirmed to execute the same process (step O21), the process returns to the process from step O13 again.

【0202】

However, when the process from step O13 is repeatedly executed while sequentially updating and changing the participant ID for the participants who wished to participate in the chat from the starter in step O21 above, the process for all participants is completed. , Step O14 confirms that there are no more participants, then lists it as being used to realize the chat, which is listed in the list of used servers saved in the chat database at that time. For each chat server 2 (2a ~ 2c) (hereinafter abbreviated as "chat server 2y"), a part of the contents of the chat database based on the corresponding chat ID is read and added, and then chat is performed. Send a request notification (step O25).

【0203】

FIG. 39 shows the format of the data transmitted from the chat server 2x to the chat server 2y in addition to the execution request notification, in addition to the chat ID, the terminal ID of the starter, and the server ID (of the chat server 2x). Then, each terminal ID of the desired participant and the corresponding server ID are listed, and finally, a summary of server IDs is additionally set as a list of servers used.

【0204】

After that, on the chat server 2x to which the chat starter belongs, for the participants managed by the own machine, the contents of the participant's ID are read for one person and the contents are confirmed (step O26). After confirming that (step O27), execute the connection with the terminal device stored corresponding to the participant's ID (step O28), and after confirming that the connection was successful (step O29). ), Execute a notification requesting the target participant's terminal device to participate in the chat (step O30), and then confirm the contents of the participant ID to confirm that other participants will also perform the same process. After changing and setting (step O31), the process returns to the process from step O26 above.

【0205】

In addition, if it is determined in step O29 above that the connection with the participant managed by the own machine was not successful, an error message indicating that the participant ID cannot be used to chat with the participant is not possible. Is generated as chat data (step O32), this is additionally saved as a chat log in the chat database (step O33), the chat data is sent to the starter (step O34), and then other devices managed by the own machine. After changing and setting the contents of the participant ID to be confirmed to execute the same process for the participants (step O31), the process returns to the process from step O26 again.

【0206】

However, for the participants managed by the own machine, the processing from step O26 is repeatedly executed while sequentially updating and changing the participant ID in the above step O31, and the processing for all the participants managed by the own machine is performed. When finished, it is confirmed in step O27 that there are no more participants, and then waits for a response from another chat server 2y or a terminal device managed by the player to the request to participate in the chat. (Step O35).

【0207】

Here, if a notification is made from the chat server 2y or the terminal device managed by the player during this response standby, this is received (step O36), and whether the source of the notification is the chat server 2y. , Or determine if it is a terminal device managed by your own device (step O37).

【0208】

If it is from a terminal device managed by your device, then determine whether the content of the notification is to accept or refuse to participate in the chat (step O38). ..

【0209】

If the participant is accepted to participate in the chat, a notification is given to the participant's terminal device 3 to allow reconnection (callback) (step O45), and then the connection is temporarily disconnected (step). O46), it is determined whether or not there is any other response notification from the participant's terminal device 3 managed by the player (step O44), and if so, the process returns to the process from step O36.

【0210】

If it is determined that the notification received in step O38 above refuses to participate in the chat, the terminal ID is saved on the side of the person who refuses to participate in the chat database (step O39), and then the terminal device is used. Disconnect from 3 (step O40), then use the participant ID to generate a rejection message as chat data indicating that the participant refused to join the chat (step O41). This chat data is additionally saved in the chat database as a chat log (step O42), and at this point, all the terminal devices 3 connected to this chat server 2x are in chat mode including the starter. (Step O43), determine whether there are any other response notifications from the participant's terminal device 3 managed by the player (Step O44), and if so, from step O36 above again. Return to processing.

【0211】

If it is determined in step O37 above that the source of the notification is another chat server 2y, then it is determined whether or not the connection with the participant managed by that chat server 2y is successful. (Step O47).

【0212】

Here, if it is determined that the connection with the participant managed by another chat server 2y is not successful, an error message indicating that the chat with the participant cannot be performed using the participant ID is not possible. Is generated as chat data (step O56), this is additionally saved as a chat log in the chat database (step O51), and at this point, the chat mode including the starter is included in the terminal device 3 connected to this chat server 2x. After sending this chat data to all of the above (step O52), it is determined whether or not there are other response notifications from the participant's terminal device 3 managed by the own machine. (Step O44) If there is, the process returns to the process from step O36.

【0213】

In addition, when the notification that the connection with the participant managed by the other chat server 2y is successful is received in the above step O47, the content of the notification then accepts the participation in the chat as a result of the connection. Determine if it is or rejects (step O48).

【0214】

If the participation in the chat is accepted, the terminal ID of the participant's terminal device 3 in the chat database is saved in the participant side, and the used server ID is also saved (step O53). , Set the corresponding occupancy / absence flag on the occupancy side (step O54), and then use the participant ID to generate an entry message as chat data indicating that the participant will join the chat (step O55). ), Add this to the chat database as a chat log (step O51), and at this point for all devices 3 connected to this chat server 2x that are in chat mode, including the starter. After sending the chat data (step O52), determine whether there are any other response notifications from the participant's terminal device 3 managed by the player (step O44), and if so, the above again. Return to the process from step O36.

【0215】

In addition, if it is determined in step O48 above that the response from the participant managed by another chat server 2y is to refuse to participate in the chat, the terminal ID is used on the side of the person who refused to participate in the chat database. After saving to (step O49), a refusal message indicating that the participant refused to join the chat is generated as chat data using the participant ID (step O50), and this is chatted to the chat database. In addition to saving it as an additional log (step O51), this chat data is sent to all chat mode devices including the starter on the terminal device 3 connected to this chat server 2x at this point. In (step O52), it is determined whether or not there is any other response notification from the participant's terminal device 3 managed by the player (step O44), and if so, the process returns to the process from step O36.

【0216】

However, if the process from step O36 above is repeatedly executed, and in step O44, the response notifications from the terminal devices 3 of all the participants managed by the own machine are received and it is determined that there are no more remaining, the next step is to this chat. It is determined whether or not the terminal device 3 whose response to the participation request has not been confirmed still remains (step O57).

【0217】

If it is determined that there is still a response from the terminal device 3, or after waiting for a certain period of time to reconnect (step O58), if there is any response, the response is another. Determine whether it is related to the connection of the terminal device via the chat server 2y, or whether the unconfirmed terminal device 3 is the terminal device related to the own device and has been reconnected (step O59). ).

【0218】

Here, if the response is related to the connection of the terminal device via another chat server 2y, then it is determined whether or not the connection was successful (step O60), and the connection was not successful. If it is determined, an error message indicating that it is not possible to chat with the participant using the participant ID is generated as chat data (step O61), and this is additionally saved as a chat log in the chat database. (Step O62), and then send this chat data to all devices 3 connected to this chat server 2x that are in chat mode, including the starter (step O63). ), Return to the process from step O57 above.

【0219】

If it is determined in step O60 above that the connection of the terminal device via the other chat server 2y is successful, then as a result of the connection, is the content of the notification accepting participation in the chat? , Or to reject (step O64).

【0220】

If the participation in the chat is accepted, the terminal ID of the participant's terminal device 3 in the chat database is saved in the participant side, and the used server ID is also saved (step O67). , Set the corresponding occupancy / absence flag on the occupancy side (step O68), and then use the participant ID to generate an entry message as chat data indicating that the participant will join the chat (step O69). ), Add this to the chat database as a chat log (step O62), and at this point for all devices 3 connected to this chat server 2x that are in chat mode, including the starter. After sending the chat data (step O63), the process returns to the process from step 57 above.

【0221】

If the response via the other chat server 2y in step O64 above refuses to participate in the chat, save the terminal ID on the side of the person who refuses to participate in the chat database (step O65). ), Generate a refusal message as chat data indicating that the participant refused to join the chat using the participant ID (step O66), and additionally save this as a chat log in the chat database () In step O62), send this chat data to all devices 3 connected to this chat server 2x that are in chat mode, including the initiator (step O63), and then again. Return to the process from step O57 above.

【0222】

If it is determined in step O59 above that the response obtained is when the unconfirmed terminal device 3 managed by the own device reconnects, the terminal ID is given to the participant side of the chat database. Set to save (step O70), set the corresponding occupancy / absence flag to the contents of the occupancy (step O71), and send a response notification that allows chat to the target participant's terminal device 3 together with the chat ID. After that (step O72), an entry message indicating that the participant will join the chat is generated as chat data using the participant ID (step O73), and this is additionally saved as a chat log in the chat database. (Step O62), after sending this chat data to all the terminal devices 3 connected to this chat server 2x at this point that are in chat mode, including the starter (step O63), The process returns to the process from step O57 above.

【0223】

Then, the process from the above step O57 is repeatedly executed, and finally, if it is determined in this step O57 that there are no more terminal devices 3 for which the response to the request for participation in this chat has not been confirmed, the chat is started at that time. Whether or not the chat can be performed is determined based on whether or not there is at least one terminal device 3 that has accepted the participation (step O74).

【0224】

Here, if it is determined that there is at least one terminal device 3 that has accepted the participation in the chat and the chat can be performed, the terminals of the other participants who have accepted the participation via the other chat server 2y. A chat start permission notification is sent to the device 3 (step O79), and the chat is also performed for each terminal device 3 that is managed by the device and has transitioned to the chat mode including the starter of this chat. (Step O80) is sent, and the process at the start of chat on this chat server 2x is completed.

【0225】

In addition, if it is determined in step O74 above that there is no terminal device 3 that has accepted the participation in the chat other than the starter and the chat cannot be performed, the other chat servers 2y are contacted. After sending the notification to cancel this chat (step O75), the terminal device 3 connected to the chat server 2x and requesting the start of the chat is also notified to cancel the chat (step O76), and then. After disconnecting from the starter (step O76), the data related to this chat ID in the chat database is deleted (step O77), and this process is temporarily terminated and there is a next start request. Wait for

【0226】

The other chat server 2y that receives the chat participation request from the chat server 2x that manages the terminal device 3 of the chat starter executes the following processing.

【0227】

FIGS. 46 to 48 show the processing contents at the start of the chat in the chat server 2y, and when the chat execution request is initially received from the chat server 2x (step P01), it is added to the execution request. , Check each terminal ID of the desired participant and the corresponding server ID in the data of the chat database (step P02), and after confirming that some of them have unconfirmed contents (step P03), Read one person's worth, refer to the chat user database using the participant ID (step P04), determine whether or not to use this chat server 2y own device (step P05), and then own Only when the machine is used, the terminal ID of the participant is saved (step P06), and the content of the participant ID to be read is changed and set so that the same process is executed for other participants. After that (step P07), the process returns to the process from step P02 above.

【0228】

In this way, by repeatedly executing the process from step P02, the terminal ID is saved only for the desired participants who need to be managed by their own machine.

【0229】

Then, if it is determined in step P03 that the terminal ID of the desired participant whose content is unconfirmed has disappeared, then, regarding the participant managed by this chat server 2y own machine, the content of the participant's ID is read for one person. After confirming the contents (step P08) and confirming that there is (step P09), the connection with the terminal device stored corresponding to the participant's ID is executed (step P10), and the connection is established. After confirming success (step P11), execute a notification requesting the target participant's terminal device to participate in the chat (step P12), and then perform the same process for other participants. After changing and setting the contents of the participant ID to be confirmed to be executed (step P14), the process returns to the process from the above step P08 again.

【0230】

In addition, if it is determined in step P11 that the connection with the participant managed by the player has not been successful, the above chat will be notified using the participant ID to indicate that the connection with the participant has failed. Send to server 2x (step P13), and then change and set the contents of the participant ID to confirm to execute the same process for other participants managed by your own machine (step P14), and then step again. Return to the process from P08.

【0231】

However, for the participants managed by the own machine, the process from step P08 is repeatedly executed while sequentially updating and changing the participant ID in the above step P14, and the processes for all the participants managed by the own machine are performed. When finished, it is confirmed in step P09 that there are no more participants, and then the response from the terminal device managed by the player to the request for participation in the chat is awaited (step P15).

【0232】

Here, when any notification is made from the terminal device managed by the own device, this is received (step P16), and then the content of the notification is to accept or reject the participation in the chat. Determine if it is to be done (step P17).

【0233】

If the participant is accepted to participate in the chat, a notification is given to the participant's terminal device 3 to allow reconnection (callback) (step P21), and then the connection is temporarily disconnected (step). P22), it is determined whether or not there is any other response notification from the participant's terminal device 3 managed by the player (step P20), and if so, the process returns to the process from step P15.

【0234】

In addition, if it is determined in step P17 above that the received notification refuses to participate in the chat, the terminal ID is added and a notification indicating that the participation in the chat is refused is sent to the chat server. After sending to 2x (step P18), disconnect from the terminal device 3 (step P19), and check whether there are any other response notifications from the participant's terminal device 3 managed by the player. Judgment (step P20), if any, returns to the process from step P15 above.

【0235】

However, if the process from step P15 above is repeatedly executed, and in step P20, the response notifications from the terminal devices 3 of all the participants managed by the own machine are received and it is determined that there are no more remaining, the next step is to this chat. It is determined whether or not the terminal device 3 whose response to the participation request has not been confirmed still remains (step P23).

【0236】

If it is determined that it still remains, after waiting for a certain period of time to reconnect with the terminal device 3 (step P24), when the connection is made, the terminal ID is saved in the participant side of the chat database. Set (step P25), set the corresponding occupancy / absence flag to the occupancy content (step P26), and send a response notification that allows chat to the target participant's terminal device 3 together with the chat ID. (Step P27), after sending a notification to the chat server 2x using the participant ID that the participant has accepted the participation in the chat (step P28), again from step P23 above. Return to processing.

【0237】

Then, the process from the above step P23 is repeatedly executed, and finally it is determined in this step P23 that there are no more terminal devices 3 for which the response to the request for participation in this chat has not been confirmed. Ends the process at the start of chat.

【0238】

The operation on the chat server 2 (2x, 2y) during the execution of the chat started in this way will be described with reference to FIG. 49.

【0239】

In the chat server 2 that manages the speaking side of the chat data, when the chat data is received by adding the terminal ID from the terminal device 3 that makes the speaking (step Q01), the chat user database is used to respond using the terminal ID. Obtain the handle name to be used (step Q02), combine the handle name and chat data to create new chat data (step Q03), and save this chat data in the chat log of the chat database (step Q04). ..

【0240】

Next, wait for the order in which the player acquires the right to speak by accessing the management server 4 (step Q05), and when the right to speak is acquired, the serial number for each speaker is added in the format of the chat log table of contents shown in FIG. 38 above. Then, save it as chat data accompanying the remark (step Q06).

【0241】

Next, the chat log table and chat data are added to all the other chat servers 2 listed in the used server list to notify the transmission request of the remark (step Q07), and then the own machine manages it. The above chat data is also sent to each terminal device 3 (step Q08), and then the right to speak is released to the management server 4 (step Q09). Finish a series of processing related to the remarks made by.

【0242】

On the other hand, when the chat server 2 on the relay side receives the speech transmission request sent from the chat server 2 on the speaking side and relays it to each terminal device 3 managed by the own device, when the notification is received (step Q51). , After performing additional update of the corresponding chat log table of the chat database of the own machine using the chat log table attached to the notification (step Q52), each of the received chat data is managed by the own machine. The chat data is transmitted to the terminal device 3 (step Q53), and the series of processes related to relaying to the terminal device 3 managed by the own device is completed.

【0243】

In this way, during the chat, each terminal device 3 communicates only with the chat server 2 that manages its own device.

【0244】

Next, with reference to FIGS. 50 and 51, the operation contents of the chat server 2 that has been notified by the terminal device 3 managed by the own device to request the intermediate participation in the chat that has already been performed will be described.

【0245】

At that time, the chat server 2 (step R01) that received the above notification from the terminal device 3 managed by the own device with the terminal ID and the starter ID attached first checks the chat user database using the terminal ID. Then (step R02), it is determined whether or not the terminal device 3 is a user registered in this chat server 2 (step R03).

【0246】

Here, if the terminal ID is not listed in the chat user database and it is determined that the terminal device 3 that sent the terminal ID sent an illegal mid-term participation request, the terminal device 3 After sending the fraudulent notification to (step R04), the connection with the terminal device 3 is disconnected (step R05), and this process ends.

【0247】

If it is determined in step R03 above that the terminal device 3 that sent the notification requesting mid-term participation is a user registered in this chat server 2, the chat database is further checked using the starter ID. Then (step R06), it is determined whether or not the chat registered with the starter ID exists (step R07).

【0248】

Here, if it is determined that the chat by the starter ID does not exist, the process proceeds from the issuance of the fraudulent notification in step R04 above, but if it is determined that it exists, the next step is performed. Refer to the terminal ID of the terminal device 3 and the participation refusal ID of the chat database (step R08), and the terminal device 3 that sent the participation request in the middle refused to participate at the beginning of the chat. Determine if or not (step R09).

【0249】

If you are a refusal to participate, after making a data change to move the refusal ID in the chat database to the participant ID (step R10), all other chats listed in the server list used. After adding the above-mentioned update part of the chat database to the server 2, it notifies that there was an intermediate participation (step R14), and further gives the chat ID to the terminal device 3 that sent the intermediate participation request notification. In addition, notify the response that allows participation in the chat (step R15).

【0250】

After that, the terminal device 3 is notified of a response permitting the start of the chat (step R16), and then the entry message indicating that the participant participates in the chat is chatted using the terminal ID of the terminal device 3. Generate it as data (step R17), add it to the chat database as a chat log (step R18), and send the chat data to all terminal devices 3 managed by your own device. To finish.

【0251】

If the terminal device 3 that sent the participation request in the middle of step R09 did not refuse to participate at the beginning of the chat, then the terminal ID of the terminal device 3 and the chat database. Refer to the participant ID and the corresponding room / absence flag (step R11), and there is a participant ID that matches the terminal ID of the terminal device 3 that sent the participation request on the way, and the corresponding room / absence flag. It is determined whether or not the terminal device 3 has left the room in the middle depending on whether or not is set to be absent (step R12).

【0252】

Here, if it is determined that the person is not the person who left the room in the middle, the process proceeds from the issuance of the fraudulent notification in step R04 above, but if the person is the person who left the room in the middle, the participant in the chat database is concerned. After setting the occupancy / absence flag corresponding to the ID to the occupancy (step R13), the process proceeds from the above step R14, and the terminal device 3 is processed to participate in the chat again.

【0253】

On the other hand, when the chat server 2 participating in this chat does not manage the terminal device 3 of the intermediate participant, when the intermediate participation notification in step R14 is received (step R51), this The chat database of the own machine is updated and set by using the update part of the chat database received together with (step R52).

【0254】

Next, the processing contents of the chat server 2 that receives the chat participant addition request notification from the terminal device 3 managed by the own machine will be described with reference to FIGS. 52 to 56.

【0255】

The chat server 2 that receives the chat participant addition request notification from the terminal device 3 managed by the own machine reads the contents of the terminal ID of the participant who wishes to participate in the chat added to the notification for one person. Check the contents (step S01), confirm that there is (step S02), refer to the chat user database using the participant ID (step S03), and be a registered chat user. Check whether or not (step S04).

【0256】

If you are a registered chat user, check the ID of the server used attached to the terminal ID (step S05), and if the server ID is not yet listed in the list of servers used in the chat database. Is to save a new server location (step S06).

【0257】

After that, it is determined whether or not the server ID is the server ID of the own machine, that is, whether or not the terminal device 3 additionally requested as a participant is the terminal device 3 managed by the own machine (step S07). If it is determined that it is the server ID of the machine, the terminal ID of the participant is saved (step S08).

【0258】

If it is determined in step S07 that the server ID is not that of the own machine and the terminal device 3 additionally requested as a participant is not the terminal device 3 managed by the own machine, a new chat is made. Save the server ID as a request for participation (step S09).

【0259】

After that, in order to execute the same process for the other participants requested to be added, the content of the participant ID to be read is changed and set (step S10), and then the process returns to the process from step S01 again.

【0260】

However, when the process from step S01 is repeatedly executed while sequentially updating and changing the participant ID for the participants who newly wish to participate in the chat in step S10 above, the process for all participants is completed. In step S02, it is confirmed that there are no more participants, and then it is necessary to request the chat server 2 other than the own machine to participate in the terminal device 3, that is, whether or not it is necessary to make a request. , It is determined whether or not at least one of the terminal devices 3 newly requested to participate is managed by a chat server 2 other than the own device (step S14).

【0261】

Here, if it is determined that it is necessary to make a request to another chat server 2, the server ID saved in step S09 above is further compared with the server ID described in the list of servers used in the chat database. Then, it is determined whether or not a chat execution request to the chat server 2 that has not participated in the chat until then is necessary (step S16).

【0262】

If it is determined that a chat request is required, a chat request notification is sent to the chat server 2 that has not participated in the chat until then, with the contents of the chat database at that time added (step S16). ).

【0263】

If it is determined in step S15 that the chat execution request is not necessary, the contents of the chat database at that time are added to each chat server 2 based on the server ID saved in step S09 above, and the chat is entered. Send a participant addition request notification (step S17).

【0264】

After that, this time, the contents of the terminal ID of the terminal device 3 managed by the own machine, which was saved in the process in step S08 above, are read out for one person and the contents are confirmed (step S18), and after confirming that there is (step S18). Step S19), execute the connection with the terminal device 3 (step S20), confirm that the connection was successful (step S21), and then join the chat with the terminal device 3 of the new target participant. (Step S22), change and set the contents of the participant ID to be confirmed so that the same processing can be performed for other similarly added participants (step S23), and then again. Return to the process from step S18 above.

【0265】

If it is determined in step S21 above that the connection with the participant was not successful, an error message indicating that the chat with the participant cannot be performed using the participant ID is generated as chat data. Then (step S24), add this to the chat database as a chat log (step S25), and save the chat data to all terminal devices 3 and others under the control of the own device participating in the chat at that time. Send to chat server 2 (step S26), then change and set the contents of the participant ID to be confirmed (step S23) so that the same process can be performed for other added participants, and then again. Return to the process from step S18 above.

【0266】

In this way, among the terminal devices 3 managed by the own device in step S23 above, the participant IDs are sequentially updated and changed for the terminal devices 3 that are currently participating in the chat and are newly requested to participate in the chat. While repeating the process from step S18 and finishing the process for all additional participants, if it is confirmed in step S19 that there are no more additional participants, then another chat server 2 or own machine Waits for a response from the terminal device managed by (step S27).

【0267】

Here, when a notification is made from another chat server 2 or a terminal device managed by the own device, this is received (step S28), and the source of the notification is another chat server 2 or Determine if the terminal device 3 is managed by your own device (step S29).

【0268】

If it is from the terminal device 3 managed by your own device, then determine whether the content of the notification is to accept or refuse to add to the chat and participate. (Step S30).

【0269】

If the participant is accepted to participate in the chat, a notification is given to the participant's terminal device 3 to allow reconnection (callback) (step S31), and then the connection is temporarily disconnected (step). S32), it is determined whether or not there is any other response notification from the participant's terminal device 3 managed by the player (step S33), and if so, the process returns to the process from step S28.

【0270】

If it is determined that the notification received in step S30 above refuses to participate in the chat, the terminal ID is saved on the side of the person who refuses to participate in the chat database (step S34), and then the terminal device is used. The connection with 3 is disconnected (step S35), and then a refusal message indicating that the participant refused to join the chat is generated as chat data using the participant ID (step S36), and this is generated. In addition to additionally saving it as a chat log in the chat database (step S37), this chat data is sent to all the devices 3 connected to this chat server 2 that are in chat mode at this point. In (step S38), it is determined whether or not there is any other response notification from the participant's terminal device 3 managed by the player (step S33), and if so, the process returns to the process from step S28.

【0271】

If it is determined that the source of the notification received in step S29 is another chat server 2, then the connection status with the participant managed by that chat server 2 is determined (step S50). ).

【0272】

Here, if it is determined that the connection with the participant managed by the other chat server 2 is not successful, an error message indicating that the chat with the participant cannot be performed using the participant ID is not possible. Is generated as chat data (step S60), this is additionally saved as a chat log in the chat database (step S58), and this chat is made to all terminal devices 3 connected to this chat server 2 at this point. After transmitting the data (step S59), it is determined whether or not there is any other response notification from the participant's terminal device 3 managed by the player (step S33), and if so, from step S28 above again. Return to the processing of.

【0273】

In addition, when the notification that the connection with the participant managed by the other chat server 2 is successful is received in the above step S50, the content of the notification then accepts the participation in the chat as a result of the connection. Determine whether it is or rejects (step S52).

【0274】

If the participation in the chat is accepted, the terminal ID of the participant's terminal device 3 in the chat database is saved in the participant side, and the used server ID is also saved (step S53). , Set the corresponding occupancy / absence flag on the occupancy side (step S54), and then use the participant ID to generate an entry message as chat data indicating that the participant will join the chat (step S55). ), Add this to the chat database as a chat log (step S58), and at this point, this chat data for everything that is in chat mode on the terminal device 3 connected to this chat server 2. (Step S59), determine whether there are any other response notifications from the participant's terminal device 3 managed by the player (Step S33), and if so, from step S28 above again. Return to processing.

【0275】

If it is determined in step S52 above that the response from the participant managed by the other chat server 2 is to refuse to participate in the chat, the terminal ID is used on the side of the person who refused to participate in the chat database. After saving to (step S56), a refusal message indicating that the participant refused to join the chat is generated as chat data using the participant ID (step S57), and this is chatted to the chat database. It is additionally saved as a log (step S58), and this chat data is sent to all the devices 3 connected to this chat server 2 that are in chat mode at this point (step S59). ), It is determined whether or not there is a response notification from the participant's terminal device 3 managed by the own machine (step S33), and if so, the process returns to the process from step S28 again.

【0276】

Furthermore, assuming that the notification was received from the chat server 2 that had not participated in the chat in step S28 above, the content of the notification in step S50 tells the terminal device 3 managed by the new chat server 2. If it is determined that the connection is successful and the participation in the chat is accepted or refused, or if it is determined that the connection with the terminal device 3 managed by the new chat server 2 has failed, either After updating and setting the contents of the chat database to reflect the contents (step S51), it is judged whether or not there is any other response notification from the participant's terminal device 3 managed by the own machine (step S51). S33) If there is, the process returns to the process from step S28 above.

【0277】

In this way, the process from step S28 is repeatedly executed, and when it is determined in step S33 that there are no more response notifications from the terminal device 3 of the participant managed by the own machine, the additional participant managed by the own machine is left. Regarding the terminal device 3 of the above, it is determined whether or not there is still a terminal device 3 whose response to the request for participation in this chat has not been confirmed (step S39).

【0278】

If it is determined that it still remains, there is a response from the terminal device 3 or another chat server 2, or it waits for a certain period of time to reconnect (step S40), and then there is some response. And this is received, and it is determined whether the response is from another chat server 2 or a reconnection from the terminal device 3 managed by the own device (step S41).

【0279】

Here, if the response is related to the connection of the terminal device via the other chat server 2, the terminal device managed by the other chat server 2 is executed by executing the processes of steps S50 to S59 above. While responding to the response from 3, if the connection is from the terminal device 3 managed by the own device, add the terminal ID to the participant side of the chat database and save and set it (step S42). , Set the corresponding occupancy / absence flag to the occupancy content (step S43), and send a response notification to the target participant's terminal device 3 to allow chat with the chat ID (step S44). Using the participant ID, an entry message indicating that the participant will join the chat is generated as chat data (step S45), and this is additionally saved as a chat log in the chat database (step S46), and at this point in time. After sending this chat data to all the devices in chat mode on the terminal device 3 connected to this chat server 2 (step S47), the process returns to the process from step S39 above.

【0280】

Then, the process from the above step S39 is repeatedly executed, and finally in this step S39, when it is determined that there is no terminal device 3 whose response to the participation request in the middle of the chat is unconfirmed, a new chat is started. A chat start permission notification is sent to the terminal device 3 of the participant who accepted the participation via the other chat server 2 to which the participation has been added (step S48), and the participant manages it by himself / herself and newly participates in this chat. Similarly, a chat start permission notification is sent to each terminal device 3 that has transitioned to the chat mode (step S49), and the chat is performed from the terminal device 3 managed by the own device on this chat server 2. The process when the notification of the additional participant request is received is terminated.

【0281】

Next, using FIGS. 57 and 58, when a chat participant addition request notification is issued on the terminal device 3 managed by another chat server 2, it is executed on the chat server 2 that has already participated in the same chat. The processing to be performed will be described.

【0282】

First, when a participant's additional request notification is received from another chat server 2 at the beginning of the process (step T01), the terminal related to the terminal device 3 managed by the own device based on the contents of the chat database added to the notification. After confirming the ID (step T02) and confirming that some of them have unconfirmed contents (step T03), read one of them and use the chat corresponding to the participant's terminal ID. Refer to the personal database, execute the connection with the terminal device 3 (step T04), and determine whether the connection was successful (step T05).

【0283】

Here, if it is determined that the connection is successful, a notification requesting the target terminal device to participate in the chat is executed (step T06), and then the same processing is performed for other participants. After changing and setting the contents of the participant ID to be confirmed to be executed (step T07), the process returns to the process from step T02 above.

【0284】

In addition, if it is determined in step T05 that the connection with the terminal device 3 managed by the own device has not been successful, a notification indicating that the connection with the terminal device 3 has failed using the terminal ID is sent as described above. An error message is sent to the chat server 2 that sent the participant's additional request notification (step T08), and then an error message indicating that it is not possible to chat with the participant using the terminal ID of the terminal device 3. Is generated as chat data (step T09), this is additionally saved as a chat log in the chat database (step T10), and at this point, the terminal device 3 connected to the chat server 2 is in chat mode. After sending this chat data to all things (step T11), the process returns to the process from step T02 above.

【0285】

In this way, by repeatedly executing the process from step T02, the participation request to the chat is made only for the additional desired participants who need to be managed by the own machine.

【0286】

Then, when it is determined in step T03 that the terminal ID of the new desired participant whose content is unconfirmed has disappeared, the response from the one that made the above participation request on the terminal device 3 managed by this chat server 2 own machine is next. Wait (step T12), receive any notification (step T13), and determine if the content of the notification accepts or refuses to participate in the chat. (Step T14).

【0287】

If the participant is accepted to participate in the chat, a notification is given to the participant's terminal device 3 to allow reconnection (callback) (step T15), and then the connection is temporarily disconnected (step). T16), it is determined whether or not there is any other response notification from the participant's terminal device 3 managed by the player (step T23), and if so, the process returns to the process from step T12.

【0288】

If it is determined in step T14 above that the received notification refuses to participate in the chat, the connection with the terminal device 3 is disconnected (step T17), and then the terminal ID is entered into the chat database. (Step T18), and send a new non-participation notification to all chat servers 2 participating in this chat with the updated part of the chat database (step T19).

【0289】

After that, using the terminal ID of the terminal device 3 that refused to participate, a refusal message indicating that new participation in the chat was refused was generated as chat data (step T20), and this was added to the chat database as a chat log. Save it (step T21), and send this chat data to all the devices 3 connected to this chat server 2 that are in chat mode at this point (step T22), and so on. It is also determined whether or not the response notification from the participant's terminal device 3 managed by the own machine remains (step T23), and if so, the process returns to the above step T12 again.

【0290】

However, if the process from step T12 above is repeatedly executed, and in step T23, the response notifications from the terminal devices 3 of all the participants managed by the own machine are received and it is determined that there are no more remaining, the next step is to this chat. It is determined whether or not the terminal device 3 whose response to the participation request has not been confirmed still remains (step T24).

【0291】

If it is determined that there is still a connection, after waiting for a certain period of time for the terminal device 3 to be reconnected (step T25), if there is a reconnection, the reconnection is performed to the participant side of the chat database. Save and set the terminal ID of the terminal device 3 and the server ID used (step T26), and set the corresponding occupancy / absence flag in the database to the contents of the occupancy (step T27).

【0292】

Then, after adding the update part of the chat database to all chat servers 2 participating in the chat at that time and sending a new participation notification (step T28), the chat ID is sent to the terminal device 3. Is added to send a response notification to allow participation in the chat (step T29), and then an entry message indicating that the participant joins the chat is generated as chat data using the terminal ID (step T29). T30), add this to the chat database as a chat log (step T31), and at this point, this chat for everything that is in chat mode on the terminal device 3 connected to this chat server 2. The data is transmitted (step T32), and the terminal device 3 of the additional participant who newly accepted the participation in the chat, which is managed by the own machine, is notified to allow the start of the chat (step T33). ), Then return to the process from step T24 above.

【0293】

When the new participation notification is sent in step T28 or the new non-participation notification is sent in step T19, the other chat server 2 participating in the chat receives this (step T51). The content of the chat database in the own machine will be updated and set using the update part of the chat database added to the notification (step T52).

【0294】

Then, after repeatedly executing the process from step T24 above, when it is determined that there is no unconfirmed response to the request for additional participation in the chat in the terminal device 3 managed by the own device, this is the above. The process when the chat server 2 receives the chat participant addition request notification from the other chat server 2 is terminated.

【0295】

Next, the processing on the chat server 2 that received the exit request notification during the chat is described with reference to FIGS. 59 and 60.

【0296】

FIG. 59 shows the operation contents of the chat server 2 when the terminal device 3 managed by the own device leaves the chat room in the middle of the participation.

【0297】

In the figure, when a exit request notification is received from the terminal device 3 managed by the own device during a chat (step U01), the chat database is used with the terminal ID and chat ID of the terminal device 3 that sent the exit request notification. Confirm (step U02).

【0298】

Here, is it the participant of the chat who sent the exit request notification only when the chat server 2 is the chat server 2 that manages the terminal device 3 of the starter of the chat? , Or determine if it is the starter (step U03).

【0299】

If it is determined in this step U03 that the terminal ID belongs to the terminal device 3 of another participant instead of the starter, or the chat server 2 does not manage the terminal device 3 of the starter of the chat in the first place. In the case of the chat server 2, the chat server 2 disconnects the connection with the terminal device 3 after sending the disconnection request notification to the terminal device 3 that sent the exit request notification (step U04). Then (step U05), the room / absence flag attached to the participant ID of the corresponding chat ID in the chat database is set to the absent side (step U06).

【0300】

After that, the update part of the above chat database is added, and the chat exit notification is sent to all the other chat servers 2 participating in the chat (step U07).

【0301】

Then, using the handle name of the terminal device 3 that sent the exit request notification, an exit message indicating that the participant leaves the chat is generated as chat data (step U08), and this is added to the chat database as a chat log. While saving (step U09), the chat data is simultaneously transmitted to all the participants in the chat in the terminal device 3 managed by the chat server 2 at that time (step U10). Participate in the chat at that time by leaving the room of the above participant, and check the number of connected terminal devices 3 by the number set in the room in the room / absence flag on the participant side of the chat database ( Step U11).

【0302】

Here, the chat server 2 determines whether or not there is anyone participating in the chat other than the starter of the chat (step U12), and if it is determined that there are still participants other than the starter. , In order to continue chatting after that, this process is temporarily terminated.

【0303】

In addition, if it is determined in step U12 that no one other than the starter of the chat has participated in the chat due to the exit of the participant, the chat cannot be continued anymore, so the chat cannot be continued. After sending a chat end notification to all other chat servers 2 participating in (step U13), the chat log of the corresponding chat ID in the chat database is locked so as not to be added any more. Ends this process with.

【0304】

Further, this chat server 2 is a chat server 2 that manages the terminal device 3 of the monitor of the chat, and it is the terminal device 3 of the starter of the chat that sent the exit request notification in the above step U03. If it is determined that, the chat server 2 sends a disconnection request notification to the terminal device 3 of the starter who sent the exit request notification (step U14), and then connects to the terminal device 3 of the starter. (Step U15) and set the room / absence flag attached to the terminal ID of the starter of the corresponding chat ID in the chat database to the absent side (step U16).

【0305】

After that, the update part of the above chat database is added and a chat exit notification is sent to all other chat servers 2 participating in the chat (step U17), and further to all other chat servers 2. And send a chat end notification (step U18).

【0306】

Furthermore, a disconnection request is sent to all the terminal devices 3 other than the above-mentioned starter managed by the own device that have participated in the chat (step U19), and the connection with them is disconnected (step U19). Step U20), reset the occupancy / absence flag corresponding to each terminal ID in the corresponding chat database to the absent side (step U21), add the updated part of this chat database again, and join the chat. A chat exit notification is sent to all other chat servers 2 (step U22), and the process on the chat server 2 when the terminal device 3 managed by the own device leaves the chat halfway is terminated.

【0307】

FIG. 60 shows the processing contents when the chat server 2 participating in the chat receives each notification of leaving and ending the chat from another chat server 2.

【0308】

First, the chat server 2 that receives the chat exit notification from the other chat server 2 by the processing in step U07, U17 or U22 (step U51) is based on the update part of the chat database added to the notification each time. Update and set the contents of the chat database of your own machine (step U52).

【0309】

In addition, the chat server 2 that has received the chat exit notification in this way waits for the chat end notification that will be continuously sent from the same other chat server 2 after that, and actually ends this chat. When the notification is received (step U71), a disconnection request is also sent to all the terminal devices 3 managed by the own device that participated in the chat (step U72), and the connection with them is disconnected. From (step U73), reset the occupancy / absence flag corresponding to each terminal ID in the corresponding chat database to the absent side (step U74), add the updated part of this chat database again, and join the chat. When a chat exit notification is sent to all other chat servers 2 (step U75), and the terminal device 3 managed by the other chat server 2 leaves the chat room halfway, the chat exit, The process performed by the chat server 2 that received each end notification is terminated.

【0310】

Finally, after the chat is performed as described above, when the individual terminal device 3 of the starter or participant of the chat requests to view the chat log, the chat server 2 that manages the terminal device 3 The contents of the processing to be executed will be described.

【0311】

When the chat server 2 receives a chat log viewing request notification from the terminal device 3 managed by the own device (step V01), it first uses the terminal ID of the terminal device 3 attached to the notification to use chat. Refer to the person database (step V02) and determine whether the terminal device 3 is the original chat user (step V03).

【0312】

Here, if it is determined that the terminal ID of the corresponding terminal device 3 is registered in the chat user database, the chat database is further referred to by the chat ID added to the above chat log viewing request notification (step V04). , Determine if the corresponding chat log exists (step V05).

【0313】

Here, if it is determined that the corresponding chat log also exists, then the terminal ID on the participant side in the chat data of the corresponding chat ID in the chat database is used using the terminal ID added to the above chat log viewing request notification. (Step V06), and determines whether or not the terminal ID exists, that is, whether or not the terminal device 3 that has sent the browsing request notification has participated in the chat (step V07).

【0314】

Then, if it is determined that the terminal ID still exists here as well, it is confirmed that the terminal device 3 that sent the browsing request notification is to browse the chat log in which the terminal device 3 is participating, and the terminal device 3 is checked. Send a chat log viewing permission notification (step V08) and shift to the chat log viewing mode (step V09).

【0315】

After that, it waits for a response from the terminal device 3 (step V12), and when there is a response, determines whether the notification is a chat log acquisition request or a chat log viewing end (step V13).

【0316】

Here, if it is determined that the notification is a chat log acquisition request, the corresponding chat log table showing the format shown in Fig. 38 above is checked (step V14), and whether the chat log to be viewed is in the own device. It is determined whether or not, that is, whether or not the terminal device 3 that has sent the browsing request was the terminal device 3 managed by the chat server 2 at the time of chat execution (step V15).

【0317】

If it is determined that the target chat log is in the own machine, the corresponding chat log data is read from the chat database as it is in response to the acquisition request and sent to the terminal device 3 (step V16), and then again. The process of returning to step V12 and waiting for a response is repeated.

【0318】

If it is determined in step V15 that the target chat log is not in the own machine, the server ID, the terminal ID of the speaker, and the serial number for each speaker are added together with the server ID of the own machine for the purpose. Send a log acquisition request notification to the chat server 2 where the chat log data to be executed exists (step V17), and wait for the response (step V18).

【0319】

When the chat server 2 that matches the server ID attached to this log acquisition request notification receives the sent log acquisition request notification (step V51), it chats in consideration of the data attached to the notification. Check the log table (step V52), read the corresponding chat data from the chat database as a response to the acquisition request, and return it to the chat server 2 that sent the above notification (step V53).

【0320】

When the chat server 2 on the log acquisition request side receives this response (step V19), it reads the received chat log data from the chat database as a response to the acquisition request and sends it to the terminal device 3 (step V16), and continues. Then, the process of returning to the above step V12 and waiting for a response is repeated.

【0321】

Then, after repeatedly executing the process from step 12 above, if it is determined that the notification of the end of viewing the chat log has been made in step V13, a request notification for disconnecting the connection is sent to the terminal device 3 at that time. After that (step V20), the connection is actually disconnected (step V21), and this process ends.

【0322】

If it is determined in step V03 above that the terminal ID of the sent terminal device 3 is not registered in the chat user database, or in step V05 above, the chat data corresponding to the chat ID sent is When it is determined that it does not exist in the chat database, or when it is determined in step V09 above that the terminal ID of the terminal device 3 does not exist in the terminal ID of the participant side in the chat data of the corresponding chat ID in the chat database. Is not qualified to view the desired chat log, and after notifying the terminal device 3 of an error message (step V10), disconnects the connection (step V11). With the above, the processing of the chat server 2 for the browsing request from the terminal device 3 managed by the own device is completed.

【0323】

As described above, in the second embodiment described above, the plurality of chat servers 2a to 2c control the management server 4 only for the terminal devices 3, 3, ... As clients managed by their own machines. Since the chat participation is managed and the log is managed based on the above, it is possible to avoid putting a heavy burden only on a specific chat server while realizing a chat environment in a wider area.

【0324】

In the first and second embodiments described above, it has been described that the chat user is authenticated and managed only by the terminal ID of the terminal device 3, but the password may also be used in combination.

【0325】

Further, in the above embodiment, the terminal devices 3, 3, ... As client devices such as a personal computer and a PDA and the chat server 2 (2a to 2c) are connected to the network 1 (1a to 1c). However, it may be connected via the Internet or LAN.

【0326】

Furthermore, regarding the viewing of the above chat log, by confirming the terminal ID and chat ID of the terminal device 3, it is possible to view the log of the entire chat in which the viewing requester using the terminal device 3 participated. However, it may be possible to browse only the chat log from the time when the viewing requester enters the chat to the time when the viewing requester leaves the chat.

【0327】

In addition, the present invention can be implemented with various modifications within a range that does not deviate from the gist thereof.

【0328】

[Effect of the invention]

According to the invention of claim 1, since the participants can be managed and specified at the request of the client who starts the chat, a better quality chat environment can be realized.

【0329】

According to the invention of claim 2, in addition to the effect of the invention of claim 1, the billing process for the client who participated in the chat can be surely carried out, which can be returned to the development of a better quality chat environment. ..

【0330】

According to the invention of claim 3, in addition to the effect of the invention of claim 1, it is possible to reliably manage the intermediate participation in the chat for the client who first wishes to participate.

【0331】

According to the invention of claim 4, in addition to the effect of the invention of claim 1, it is possible to add a new client in the middle of the chat and encourage its participation.

【0332】

According to the invention of claim 5, even a client terminal having a particularly small storage capacity can selectively specify and obtain only the necessary chat log.

【0333】

According to the invention of claim 6, it is possible to avoid putting a heavy burden only on a specific chat server while realizing a chat environment in a wider area.

【0334】

According to the invention of claim 7, a new participant can be managed and specified at the request of the client terminal already participating in the chat, so that a better chat environment can be realized.

【0335】

According to the invention of claim 8, even a client terminal having a particularly small storage capacity can selectively specify and obtain only the necessary chat log.

[Simple explanation of drawings]

[Figure 1]

The figure which shows the conceptual structure of the whole system which concerns on 1st Embodiment of this invention.

[Figure 2]

The figure which illustrates the database structure in the chat server which concerns on the embodiment.

[Fig. 3]

The figure which shows the appearance structure of the mobile information terminal which concerns on the embodiment.

[Fig. 4]

The block diagram which shows the circuit structure of the mobile information terminal which concerns on the embodiment.

[Fig. 5]

The figure which illustrates the display screen of the mobile information terminal which tries to start the chat which concerns on the embodiment.

[Fig. 6]

The figure which illustrates the display screen just before the start of the mobile information terminal which tries to start the chat which concerns on the embodiment.

[Fig. 7]

The figure which illustrates the display screen of the mobile information terminal at the time of a participant error after the start of the chat which concerns on the embodiment.

[Fig. 8]

The figure which illustrates the display screen of the mobile information terminal at the time of the participant refusal after the start of the chat which concerns on the embodiment.

[Fig. 9]

The figure which illustrates the display screen of the mobile information terminal after the start of the chat which concerns on the embodiment.

[Fig. 10]

A flowchart showing the operation contents performed by the start requester on the terminal device at the start of the chat according to the embodiment.

[Fig. 11]

A flowchart showing the operation contents of the chat server at the start of the chat according to the embodiment.

[Fig. 12]

A flowchart showing the operation contents of the chat server at the start of the chat according to the embodiment.

[Fig. 13]

A flowchart showing the operation contents of the chat server at the start of the chat according to the embodiment.

[Fig. 14]

A flowchart showing the operation contents of the chat server at the start of the chat according to the embodiment.

[Fig. 15]

A flowchart showing the operation contents of the terminal device that has received the participation request at the start of the chat according to the embodiment.

[Fig. 16]

The flowchart which shows the normal operation content in the chat server at the time of chat execution which concerns on the same embodiment.

[Fig. 17]

The figure which exemplifies the display screen on the mobile information terminal when there is an intermediate participation in the chat which concerns on the embodiment.

[Fig. 18]

A flowchart showing the operation contents of the terminal device that participates in the chat according to the embodiment.

[Fig. 19]

The flowchart which shows the operation content in the chat server which received the request notification of the participation in the middle which concerns on the same embodiment.

[Fig. 20]

The figure which illustrates the function selection screen displayed in the display input part of the mobile information terminal in the middle of a chat which concerns on the embodiment.

[Fig. 21]

The flowchart which shows the operation content in the terminal device which requests the addition of the chat participant which concerns on the embodiment.

[Fig. 22]

The flowchart which shows the operation content of the chat server which received the additional request notification of the chat participant which concerns on the same embodiment.

[Fig. 23]

The flowchart which shows the operation content of the chat server which received the additional request notification of the chat participant which concerns on the same embodiment.

[Fig. 24]

The flowchart which shows the operation content of the chat server which received the additional request notification of the chat participant which concerns on the same embodiment.

[Fig. 25]

A flowchart showing the operation contents of the terminal device that has received a request to participate in the chat as a newly added member according to the embodiment.

[Fig. 26]

The figure which illustrates the leaving message displayed in the display input part of the mobile information terminal in the middle of the chat which concerns on the embodiment.

[Fig. 27]

The flowchart which shows the processing content when the chat participant which concerns on the same embodiment leaves a room.

[Fig. 28]

A flowchart showing the processing content when the chat starter according to the embodiment leaves the room.

[Fig. 29]

A flowchart showing the processing contents of the chat server that has received the chat exit request notification according to the embodiment.

[Fig. 30]

A flowchart showing the processing contents of the terminal device for viewing the chat log according to the embodiment.

[Fig. 31]

A flowchart showing the processing contents of the chat server for viewing the chat log in response to the request according to the embodiment.

[Fig. 32]

The figure which shows the sending and receiving of a signal between a chat server and a terminal at the time of chat execution which concerns on the same embodiment.

[Fig. 33]

The figure which shows the sending and receiving of a signal between a chat server and a terminal at the time of chat execution which concerns on the same embodiment.

[Fig. 34]

The figure which shows the sending and receiving of a signal between a chat server and a terminal at the time of chat execution which concerns on the same embodiment.

[Fig. 35]

The figure which shows the sending and receiving of the signal between the chat server and the terminal at the time of browsing the chat log which concerns on the embodiment.

[Fig. 36]

The figure which shows the conceptual structure of the whole system which concerns on 2nd Embodiment of this invention.

[Fig. 37]

The figure which illustrates the database structure in the chat server which concerns on the embodiment.

[Fig. 38]

The figure which shows the format of the chat log table of contents added to the chat log in the chat data which concerns on the embodiment.

[Fig. 39]

The figure which shows the format of the update data of the chat database sent and received between the chat servers which concerns on this embodiment.

[Fig. 40]

A flowchart showing the processing contents of the chat server at the start of the chat according to the embodiment.

[Fig. 41]

A flowchart showing the processing contents of the chat server at the start of the chat according to the embodiment.

[Fig. 42]

A flowchart showing the processing contents of the chat server at the start of the chat according to the embodiment.

[Fig. 43]

A flowchart showing the processing contents of the chat server at the start of the chat according to the embodiment.

[Fig. 44]

A flowchart showing the processing contents of the chat server at the start of the chat according to the embodiment.

[Fig. 45]

A flowchart showing the processing contents of the chat server at the start of the chat according to the embodiment.

[Fig. 46]

A flowchart showing the processing contents of the chat server at the start of the chat according to the embodiment.

[Fig. 47]

A flowchart showing the processing contents of the chat server at the start of the chat according to the embodiment.

[Fig. 48]

A flowchart showing the processing contents of the chat server at the start of the chat according to the embodiment.

[Fig. 49]

A flowchart showing the processing contents of the chat server during chat execution according to the embodiment.

[Fig. 50]

The flowchart which shows the operation content in the chat server which received the request notification of the participation in the middle which concerns on the same embodiment.

[Fig. 51]

The flowchart which shows the operation content in the chat server which received the request notification of the participation in the middle which concerns on the same embodiment.

[Fig. 52]

The flowchart which shows the operation content in the chat server which received the additional request notification of a participant from the terminal device managed by the own machine which concerns on the embodiment.

[Fig. 53]

The flowchart which shows the operation content in the chat server which received the additional request notification of a participant from the terminal device managed by the own machine which concerns on the embodiment.

[Fig. 54]

The flowchart which shows the operation content in the chat server which received the additional request notification of a participant from the terminal device managed by the own machine which concerns on the embodiment.

[Fig. 55]

The flowchart which shows the operation content in the chat server which received the additional request notification of a participant from the terminal device managed by the own machine which concerns on the embodiment.

[Fig. 56]

The flowchart which shows the operation content in the chat server which received the additional request notification of a participant from the terminal device managed by the own machine which concerns on the embodiment.

[Fig. 57]

The flowchart which shows the operation content in the chat server which received the participant addition request notification to the terminal device managed by the own machine from another chat server which concerns on the same embodiment.

[Fig. 58]

The flowchart which shows the operation content in the chat server which received the participant addition request notification to the terminal device managed by the own machine from another chat server which concerns on the same embodiment.

[Fig. 59]

The flowchart which shows the operation content in the chat server which received the request notification of leaving the room in the middle from the terminal device managed by the own machine which concerns on this embodiment.

[Fig. 60]

A flowchart showing the operation contents performed by the chat server in which the other chat server according to the embodiment is notified of the end of the chat due to the participant leaving the room in the middle.

[Fig. 61]

A flowchart showing the operation contents of a chat server that receives a chat log viewing request from a terminal device managed by the own machine according to the embodiment.

[Fig. 62]

A flowchart showing the operation contents of a chat server that receives a chat log viewing request from a terminal device managed by the own machine according to the embodiment.

[Explanation of symbols]

1,1a ~ 1c ... network 2,2a ~ 2c ... Chat server 3 ... Terminal equipment 3a ... Mobile information terminal 4 ... Management server 11 ... Body case 12 ... Display input section 13 ... Speaker 14 ... Key input section 15 ... antenna 21 ... CPU 22 ... ROM 23 ... RAM 24 ... RTC 25 ... Hard disk drive (HDD) 26 ... Tablet input 27 ... Liquid crystal display 28 ... Audio output 29 ... Wireless communication department CD ... chat data area DI ... data entry area IC, ICa ... Icon area PI ... Handwriting input recognition area RD ... Registered data area SB ... scroll bar SD ... Selected data area