KR20050040645A - Method and system for transmitting and receiving file between terminals - Google Patents

Abstract

The present invention provides a system and method for file transmission and reception between terminal devices in a messenger service system. To this end, the present invention transmits a receiver capability request message for inquiring whether the counterpart client terminal can interpret the file when a file transfer request is made by the user to the counterpart client terminal in a system providing a messenger service. And receiving a receiver capability response message including information on the interpretation capability of the corresponding file of the counterpart client terminal device, and determining whether to transmit the corresponding file according to a result of the file interpretation capability of the counterpart client terminal device; Receiving the file interpretation capability inquiry message from the client terminal device, receives information on the file interpretation capability from the counterpart client terminal device, and interprets the corresponding file of the counterpart client terminal device in the receiver response message; To include the information in the server adapted to sending to the client terminal characteristics.

Description

System and method for file transmission and reception between terminal devices {METHOD AND SYSTEM FOR TRANSMITTING AND RECEIVING FILE BETWEEN TERMINALS}

The present invention relates to a system and method for file transmission and reception between terminal devices, and more particularly, to a system and method for file transmission and reception during connection between terminal devices through a messenger service.

As the Internet becomes widespread, people are increasingly sending and receiving Internet instant messages (hereinafter referred to as 'messages') through Internet instant messengers (such as ICQ, AOL, etc.). have. Messages can be delivered over the Internet to PC-to-PC or PC-to-server and server-to-PC. In addition, in recent years, with the development of mobile phone technology, a mobile communication company provides a service for delivering a message to a mobile phone terminal (for example, a PCS phone) through the Internet.

1 is a diagram illustrating a system for providing a messenger service. As shown in FIG. 1, the client terminal apparatuses 100, 102, and 104 are terminals capable of providing a messenger service to access the server 110 through the Internet network 108 or the mobile communication wireless network 106. Can be. In addition, the server 110 for providing a messenger service is provided with a presence information database 112, the friend list information of the client terminal (100, 102, 104), the status information of each friend in the list, the address of the friends Presence information such as information, contact information, and the like are stored. That is, the presence information herein refers to friend list information stored by the client terminal devices 100, 102 and 104 and the server 110 to perform a messenger service, status information of each friend in the list, address information of friends, contact information ( contact) information data such as information. The client terminal apparatus 100, 102, 104 connects to the server 110, requests presence information from the server 110 to receive a messenger service, and receives the presence information from the server 110. The client terminal devices 100, 102, and 104 connected to the messenger server 110 through the connection process as described above may transmit a message to the counterpart client terminal device connected to the server 11.

Next, an instance messaging process between the client terminal device 10 and the server 110 will be described with reference to FIG. 2. 2 is a signal flow diagram illustrating an instant messaging process in a messenger system.

First, after the client terminal device 10 accesses the server 110 for a messenger service, in step 202, the client terminal device 10 transmits a message transmission request (SendMessageRequest) signal for transmitting a message to the counterpart client terminal. When the server 100 receives the message transmission request signal from the client terminal device 10, the server 100 checks the client terminal device 10 requesting the corresponding message transmission. If the client terminal device 10 is a valid terminal device, the server 100 transmits a SendMessage Response signal to the message transmission request in step 208. As such, the data structure of the message transmission request signal transmitted from the client terminal device 10 to the server 110 is shown in Table 1 below.

Information element Requirements information type Explanation Message type necessary SendMessageRequest Message identifier Transaction ID necessary String Identifies the transaction Section ID necessary String Section ID for the section Forward-report-request necessary Boolean Display if user wants delivery report Message information necessary Structure Message information data Contents Condition String / Binary data Content of instant message

In Table 1, a session ID is used to identify a session between the server 110 and the client terminal device 10. In addition, a unique transaction ID is assigned to one request and response between one server 110 and client terminal 10. Herein, the transaction refers to the response of the server 110 to the request of the client terminal device 10 or the response 10 of the client to the request of the server 110. And if the client terminal 10 wants to report whether the message transmission request (SendMessageRequest) has been delivered, and displays in the delivery report request element.

As described above, the server 110 receiving the message transmission request (SendMessageRequest) transmits a response (SendMessage Response) to the client terminal device 10 in response to the message transmission request, the response signal for this message transmission request The data structure is shown in Table 2.

Information element Requirements information type Explanation Message type necessary SendMessageResponse Message identifier Transaction ID necessary String Identifies the transaction Section ID necessary String Section ID for the section result necessary Result Result of SendMessageResquest Message ID Condition String The server generates a message ID for this message

In Table 2, the message ID element is distinguished from the message type element and indicates what message is the corresponding message of the message type, and the message ID element means an ID uniquely assigned to the message.

As such, the client terminal device 10 may request the server 110 to transmit a message for the counterpart client terminal device. A file may be attached when the message is transmitted, which is a case where the user of the client terminal device 10 transmits the file to the counterpart client terminal device. For example, when a user wants to send a file to a counterpart, when the user selects a messenger's send file menu and selects a desired file on the client terminal device 10 or accessible by the client terminal device 10, The client terminal device 10 of the user attaches a predetermined file selected by the user while transmitting a message transmission request (SendMessageRequest) to the server 110.

Then, the server 110 inquires of the other client terminal device to accept the file reception, and when the other client terminal device accepts the file reception, the server 110 transmits the file attached to the corresponding message transmission request to the other client terminal device.

However, the counterpart client terminal device may not interpret the attached file transmitted by the client terminal device 10. For example, when the user of the client terminal device 10 wants to play music or show an image to the counterpart, the corresponding music file or image file is transmitted to the counterpart using the messenger's file transfer function. However, there may be a case where the music file or the image file is a file that cannot be executed on the counterpart client terminal device. If the music file is an MP3 format music file, and the client terminal does not have the software to play the MP3 file, the user terminal selects the existing software to play the MP3 file. However, in general, when software is installed in a terminal device, the format of a file that can be interpreted by the installed software is registered in the terminal device. Therefore, when the client terminal device asks the user to select a software for opening a file, the file has a format of an unregistered file, and thus the file cannot be opened and executed. Therefore, in this case, not only the time required for the client terminal device 10 to transmit a file to the counterpart client terminal device, but also the radio resources occupied for transmitting the file are wasted.

Accordingly, an object of the present invention is to provide a system and a method in which a client terminal device transmits only a file that can be interpreted by a counterpart client terminal device.

Another object of the present invention is to provide a system and method capable of preventing traffic increase due to unnecessary file transfer between client terminal devices.

The present invention for achieving the above object provides a system and method for file transmission and reception between terminal devices in a messenger service system. To this end, the present invention transmits a receiver capability request message for inquiring whether the counterpart client terminal can interpret the file when a file transfer request is made by the user to the counterpart client terminal in a system providing a messenger service. And receiving a receiver capability response message including information on the interpretation capability of the corresponding file of the counterpart client terminal device, and determining whether to transmit the corresponding file according to a result of the file interpretation capability of the counterpart client terminal device; Receiving the file interpretation capability inquiry message from the client terminal device, receives information on the file interpretation capability from the counterpart client terminal device, and interprets the corresponding file of the counterpart client terminal device in the receiver response message; To include the information comprises a server for transmitting to the client terminal.

In addition, the present invention for achieving the above object is a method for transmitting and receiving files between the client terminal device in a system for providing a messenger service, the file transfer request from the first client terminal device to the second client terminal device by the user; Sending a receiver capability request message to the server of the messenger service, inquiring whether or not the second client terminal device can interpret the file, and interpreting the corresponding file of the second client terminal device from the server. And if the receiver capability response message including the capability information is received, determining whether to transmit the corresponding file according to the result of the file interpretation capability of the second client terminal device.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In describing the present invention, if it is determined that the detailed description of the related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

In order to prevent unnecessary file transmission and reception between client terminal devices in the messenger service system according to the present invention, the client terminal device is a primitive asking whether the other client terminal device can interpret the corresponding file before actually performing the file transmission. Create and send to the server. Then, the server generates and transmits a primitive that asks whether the file to be transmitted to the counterpart client terminal device can be interpreted, and receives a result of whether or not the file is interpretable from the counterpart client terminal device. Finally, when the server transmits the result of the file interpretation capability of the counterpart client terminal device to the client terminal device to which the file is to be transmitted, the client terminal device transmits the file according to the result of the file interpretation capability of the other client terminal device. Determine whether or not.

First, the system for communication between the client terminal device 10 and the server 110 will be described with reference to FIG. 1.

The client terminal device 10 includes all terminals capable of providing a messenger service, such as a computer 100, a mobile phone 102, a personal digital assistant (PDA) 104, and the like. The client terminal device 10 transmits a message transmission request message to the server 110 to transmit a message to the counterpart client terminal device.

Specifically, after the client terminal device 10 accesses the server 110 for the messenger service, if the user of the client terminal device 10 composes a message on the messenger screen and transmits the message (for example, pressing the enter key). Press), the client terminal device 10 sends a message transmission request (SendMessageRequest) message for transmitting the message to the server (110). As described above, the message transmission request message includes not only the actual message content but also various identification information related to the message. When the user of the client terminal device 10 wants to transmit a file such as a music file or an image file to the other party, the user of the client terminal device 10 selects a file transfer menu of a messenger function, and is stored in the client terminal device 10 or the client terminal device ( 10) Select the file you want to access and send it. Then, the client terminal device 10 sends a primitive signal to the server 110 to inquire whether the counterpart client terminal device can interpret the file before transmitting the SendMessageRequest to which the predetermined file is attached. Create and send Then, the server 110 generates a primitive signal for inquiring the interpretation capability of the counterpart client terminal device about the file to be transmitted from the client terminal device 10 and transmits it to the counterpart client terminal device. When the counterpart client terminal receives the primitive signal for querying the interpretation capability, the counterpart client terminal determines its interpretation capability from the information on the file to be transmitted included in the message. In general, when software is installed in a terminal device, a file format that can be interpreted by the installed software is registered in the terminal device. Accordingly, the counterpart client terminal device can know whether the corresponding file can be opened or executed based on the registered file format. According to another exemplary embodiment of the present invention, when the counterpart client terminal device receives a primitive signal for inquiring about the interpretation ability of the file to be transmitted from the server 110, the counterpart client terminal device displays the information on the file included in the signal to the user. The user can determine the interpretation ability of the file. As described above, the counterpart client terminal device determines a parsing capability of the file to be transmitted, and then generates a primitive signal including information on its corresponding parsing capability and transmits it to the server 110. Then, the server 110 generates a response primitive signal including information on the corresponding file interpretation capability from the counterpart client terminal device and transmits the response primitive signal to the client terminal device 10. After receiving the response primitive from the server 110, the client terminal device 10 determines whether to transmit the corresponding file according to the result of the file interpretation capability of the counterpart client terminal device.

Then, the client terminal device 10 inquires the file interpretation capability of the other client terminal device 20 through the server 110 and receives the results of the client terminal device 10 and the server 110. And the message transaction performed between the counterpart client terminal device 20 will be described with reference to FIG.

3 is a signal flow diagram illustrating a message transaction performed between client terminal devices and a server prior to file transmission according to an embodiment of the present invention. First, after the first client terminal device 10 accesses the server 110 for a messenger service, the user of the client terminal device 10 may compose a message on the messenger screen and transmit the message. 10 transmits a SendMessageRequest message for transmitting a message to the server 110. When the user of the first client terminal device 10 transmits a predetermined file to the counterpart, the server 110 transmits a message transmission request (SendMessageRequest) to which the predetermined file is attached.

At this time, the first client terminal device 10 transmits the message transmission request to which the predetermined file is attached to the server 110 in step 300 according to the present invention. It generates and sends a Recipient Capability Request message as a primitive signal for inquiring whether a file can be interpreted. The data structure for the receiver capability request signal is shown in Table 3.

Information element Requirements information type Explanation Message type necessary RecipientCapability Request Message identifier Transaction ID necessary String Identifies the transaction Section ID necessary String Section ID for the section Message information necessary Structure Message Information Data (File Information)

In Table 3, the message information element includes information about a file to be transmitted to the second client terminal device 20 by the first client terminal 10. The message information element of such a Recipient Capability Request message has the following contents.

<! ELEMENT RecipientCapability-request (MessageInfo)>

<! ELEMENT MessageInfo (MessageID ?, MessageURI ?, ContentType ?,

ContentEncoding ?, ContentSize, Recipient, Sender, DateTime ?, Validity?)>

The message information element includes information on the size, type, compression, etc. of the attached file. In this way, the first client terminal device 10 transmits a Recipient Capability Request message having the above contents to the server 110 so that the server 110 transmits the message to the second client terminal 20. SendMessageRequest Use to query whether the attachment attached to the message can be interpreted. When the server 110 receives the receiver capability request from the first client terminal device 10, the server 110 transmits a recipient capability response (RecipientCapability-Response) having the data structure of Table 4 below to the first client terminal device 10. do.

Information element Requirements information type Explanation Message type necessary RecipientCapability-Response Message identifier Transaction ID necessary String Identifies the transaction Section ID necessary String Section ID for the section result necessary Result Result of RecipientCapability Request Message ID Condition String The server generates a message ID for this message

 The first client terminal 10 secures the primitive ID through the receiver capability response received from the server 110. The result element and the message ID element of the recipient capability response message have the following contents.

<! ELEMENT RecipientCapability-Response (Result, MessageID)>

<! ELEMENT Result (Code, Description ?, DetailedResult *)>

<! ELEMENT MessageID (#PCDATA)>

Then, in step 304, the server 110 may request a primitive signal for querying the interpretation capability of the second client terminal device 2 with respect to the file to be transmitted from the first client terminal device 10 to the second client terminal device 20. As a receiver, a Recipient Client Capability Request message having a data structure as shown in Table 5 below is generated and transmitted to the second client terminal device 20.

Information element Requirements information type Explanation Message type necessary RecipientClientCapability Request Message identifier Transaction ID necessary String Identifies the transaction Section ID necessary String Section ID for the section Message information necessary Structure Message Information Data (File Information)

The message information element of the RecipientClientCapability Request message has the following contents.

<! ELEMENT RecipientClientCapability-Request (MessageInfo)>

<! ELEMENT MessageInfo (MessageID ?, MessageURI ?, ContentType ?,

ContentEncoding ?, ContentSize, Recipient, Sender, DateTime ?, Validity?)>

As such, since the receiver client capability request message includes information on the size, type, compression, etc. of the attached file, the second client terminal device 20 requests the receiver client capability request for inquiring about an analysis capability of the corresponding file. Upon receiving the message, it is possible to determine its own interpretation capability from the information on the file to be transmitted from the first client terminal device 10 included in the message. As described above, when the software is installed in the terminal device, the format of the file that can be interpreted by the installed software is registered in the terminal device, so that the second client terminal device 20 downloads the file based on the registered file format. Determine if it can be opened or run. In addition, according to another embodiment of the present invention, when the second client terminal apparatus receives the receiver client capability request message for inquiring about the interpretation capability of the corresponding file, the second client terminal apparatus provides the user with information about the file included in the message. It can be displayed so that the user can determine the interpretability of the file.

As described above, the second client terminal device 20 determines its own interpretation capability for the file to be transmitted, and then, in step 306, a recipient client capability response message as a primitive signal including information on the corresponding file interpretation capability. Generate and transmit to the server (110). The data structure of the receiver client capability response message is shown in Table 6.

Information element Requirements information type Explanation Message type necessary RecipientClientCapability Response Message identifier Transaction ID necessary String Identifies the transaction Section ID necessary String Section ID for the section result necessary Structure Result for RecipientClientCapability-Request

The result element of such a RecipientClientCapability Response message has the following content.

<! ELEMENT RecipientClientCapability-Response (Result)>

<! ELEMENT Result (Code, Description ?, DetailedResult *)>

When the server 110 receives the receiver client capability response including the information on the file interpretation capability from the second counterpart client terminal device 20, the server 110 receives the information on the file interpretation capability and the primitive obtained in the step 302. Using the ID, a Recipient Capability Result message having a data structure as shown in Table 7 as a response primitive signal is generated and transmitted to the first client terminal device 10.

Information element Requirements information type Explanation Message type necessary RecipientCapability Result Message identifier Transaction ID necessary String Identifies the transaction Section ID necessary String Section ID for the section result necessary Structure Result for RecipientCapability-Request

The result element of such a Recipient CapabilityResult message has the following contents.

<! ELEMENT RecipientCapabilityResult (Result)>

<! ELEMENT Result (Code, Description ?, DetailedResult *)>

When the first client terminal device 10 receives the receiver capability result message from the server 110, the first client terminal device 10 generates a receiver capability result response message for notifying that the receiver capability result message has been received without error in step 310. To 110. The data structure of the receiver capability result response message is shown in Table 8.

Information element Requirements information type Explanation Message type necessary RecipientCapabilityResult response Message identifier Transaction ID necessary String Identifies the transaction Section ID necessary String Section ID for the section result necessary Result Result of RecipientCapabilityResult Message ID Condition String The server generates a message ID for this message

The result element and the message ID element of the Recipient Capability Result Response message have the following contents.

<! ELEMENT RecipientCapabilityResult-Response (Result, MessageID)>

<! ELEMENT Result (Code, Description ?, DetailedResult *)>

<! ELEMENT MessageID (#PCDATA)>

The first client terminal device 10 determines whether to send the attached file based on the information on the corresponding file interpretation capability of the second client terminal device 20 included in the receiver capability result message. Specifically, when it is determined that the first client terminal device 10 can interpret the corresponding file of the second client terminal device 20 from the receiver capability result message from the server 110, the message transmission request ( SendMessageRequest) to the server 110. If the second client terminal device 20 cannot interpret the attached file, the first client terminal device 10 indicates to the user that the second client terminal device 20 cannot interpret the attached file. Inform by displaying a message on the screen. In addition, the first client terminal device 10 does not transmit the message transmission request (SendMessageRequest) to which the predetermined file to be transmitted is attached to the server 110.

Hereinafter, the overall flow for transmitting the file to the second client terminal device 20 through the messenger service will be described with reference to FIG. 4. 4 is a control flowchart 400 when a terminal transmits a file to a counterpart terminal through a messenger service according to the first embodiment of the present invention.

Referring to FIG. 4, first, the client terminal device 10 determines whether the user has sent an instance message in step 402. This instance message is a message transmitted by the user to the counterpart terminal device through the messenger server as described above. If there is an attempt to transmit an instance message by the user, the client terminal device 10 creates a SendMessageRequest message for transmitting the message. If the user transmits a file such as a music file or an image file to the counterpart, the client terminal device 10 generates a message transmission request (SendMessageRequest) to which a predetermined file is attached.

In operation 404, the client terminal 10 determines whether there is an attachment file in the corresponding instance message. If a file is attached to the message transmission request (SendMessageRequest) according to the present invention, the client terminal device 10 checks the server 110 to inquire whether the counterpart client terminal device can interpret the file in step 406. A message is generated and transmitted to the server 110. Then, the server 110 inquires the other client terminal device 20 of the analysis capability for the file to be transmitted from the client terminal device 10 and receives the result and transmits it to the client terminal device 10. In step 408, the client terminal device 10 checks whether the server 110 receives a response primitive signal including information on the corresponding file interpretation capability from the counterpart client terminal device. When the client terminal autonomous 10 receives the response primitive signal from the server 110, the client terminal 10 proceeds to step 410 based on the information on the corresponding file interpretation capability of the counterpart client terminal 20. Determines whether the file attached to (SendMessageRequest) can be interpreted.

If it is determined that the counterpart client terminal device 20 can interpret the corresponding file, the client terminal device 10 transmits a message transmission request (SendMessageRequest) to which the predetermined file is attached to the server 110 in step 414.

On the other hand, if the client terminal device 10 determines that the counterpart client terminal device 20 cannot interpret the attachment, the client terminal device 10 indicates to the user that the counterpart client terminal device 20 cannot interpret the attachment file in step 412. , Notifies by displaying a message on the display unit. In addition, the client terminal device 10 does not transmit the message transmission request (SendMessageRequest) to which the predetermined file to be transmitted is attached to the server 110.

As described above, before the client terminal device transmits a file to the counterpart client terminal device in the messenger service system, the client terminal device inquires whether the counterpart client terminal device can interpret the corresponding file, and Receive the result. The client terminal device determines whether to transmit the corresponding file according to the result of the received file interpretation capability of the counterpart client terminal device.

On the other hand, in the above-described first embodiment of the present invention, the client terminal device does not transmit the file if the counterpart client terminal device cannot interpret the file to be transmitted. However, the user of the client terminal device or the counterpart client terminal device may want to transmit or receive the attached file even if the counterpart client terminal device cannot interpret the transmitted file. Further, even if the counterpart client terminal apparatus cannot interpret the attached file, there is a possibility that the counterpart client terminal device can interpret the replacement file modified from the attached file. In this case, the client terminal device may transmit the replacement file in which the counterpart client terminal device transforms the attachment file so that the counterpart client terminal device can interpret the corresponding attachment file.

Hereinafter, a case in which the client terminal device modifies an attachment file and transmits the replacement file to the counterpart client terminal device will be described with reference to FIG. 5. 5 is a control flowchart 500 when a terminal transmits a file to a counterpart terminal through a messenger service according to a second embodiment of the present invention. Steps 502 to 508 of the file transfer control flow 500 according to the second embodiment shown in FIG. 5 are the same as steps 402 to 408 of the file transfer control flow 400 according to the first embodiment. Is omitted.

Referring to FIG. 5, the client terminal device 10 transmits the attachment file to be transmitted by the counterpart client terminal device 20 through the server 110 before transmitting the file to the counterpart client terminal device 20 in steps 502 to 508. It inquires whether it can interpret, and receives the result about the file analysis capability of the counterpart client terminal device 20.

Subsequently, the client terminal device 10 requests the other client terminal device 20 to send a message (SendMessageRequest) based on the information on the corresponding file interpretation capability of the counterpart client terminal device 20 included in the receiver capability response message in step 510. Determine if the file to be attached to can be interpreted. In this case, the information on the file interpretation capability included in the receiver capability response message transmitted from the counterpart client terminal 20 through the server 110 may be analyzed as to whether the attachment file to be transmitted can be interpreted as described above. Rather, it contains information about the existence of alternative interpretation capabilities for attachments. For example, when the client terminal device 10 attempts to transmit a 65,000 color JPEG image having a resolution of 640 * 480 to the counterpart terminal device 20 as an attached file, the counterpart terminal device 20 may determine that the client terminal device 10 is configured to transmit the attached file. Even if the attachment to be transmitted, i.e., 65,000 color JPEG images of 640 * 480 resolution, cannot be interpreted, 256 color JPEG images of 640 * 480 resolution can be interpreted. Alternatively, the other terminal device 20 may interpret 256 color JPEG images having a resolution of 640 * 480, but may not have enough memory, or may not interpret 256 color JPEG images having a resolution of 640 * 480, but may interpret GIF images. There may be it.

As described above, the counterpart client terminal 20 transmits an attachment file through the server 110 with a receiver capability response message having information on overall capability related to JPEG image interpretation as well as whether or not the JPEG image interpretation capability is available. It transmits to the client terminal device (10). In the present invention, the overall capability associated with such an attachment is referred to as an alternative interpretation capability.

Accordingly, the client terminal device 10 transmits the replacement file to the counterpart client terminal 20 based on the information on the alternative interpretation capability included in the information on the corresponding file interpretation capability from the counterpart client terminal 20 in step 512. Determine if it can be interpreted. If the counterpart client terminal 20 can interpret the replacement file, the client terminal 10 proceeds to step 514 to determine whether the counterpart client terminal 20 can generate the substitute file that can be interpreted. That is, the client terminal 20 has, for example, 65,000 color JPEG image files of 640 * 480, but does not generate 256 color JPEG image files of 640 * 480 resolution that the other client terminal 20 can interpret. You may not be able to. If it is determined that the client terminal 10 can generate a substitute file that the counterpart client terminal 20 can interpret, the client terminal 10 generates a substitute file by modifying the attachment file originally intended to be transmitted. At this time, the client terminal device 10 changes the format, size, etc. of the attached file to generate a replacement file, that is, a new attached file. Alternatively, the client terminal device 10 may change the attached file into a file of a new format by using predetermined software. The client terminal device 10 then determines, for example, whether to transmit the attachment in step 518 by the user. At this time, the user of the client terminal device 10 can not generate and transmit the replacement file, or attach to the counterpart client terminal device 20 even if the counterpart client terminal device 20 cannot interpret the original attachment or the replacement file. You can have a file transfer.

Accordingly, when the client terminal device 10 is instructed to transmit the attachment, the client terminal 10 proceeds to step 520 and transmits a message transmission request (SendMessageRequest) to which the predetermined file which is the original attachment or the replacement file is attached, to the server 110. do.

On the other hand, if the client terminal device 10 is instructed not to transmit the attachment to the counterpart client terminal device 20, for example, in step 522, the user has not transmitted the attachment to the counterpart client terminal device 20. Inform them by displaying a message on. In addition, the first client terminal device 10 does not transmit the message transmission request (SendMessageRequest) to which the predetermined file is attached to the server 110.

As described above, the client terminal device transmits the attached file even if the counterpart client terminal device cannot interpret the transmitted file. In addition, even if the counterpart client terminal cannot interpret the attached file even if the counterpart client terminal cannot interpret the attachment, the client terminal converts the original attachment into a substitute file that the counterpart client terminal can interpret. To the other client terminal device.

As described above, the present invention has an advantage of preventing unnecessary file transmission and reception between the client terminal devices because the inquiry service and the response for the file interpretation capability are transmitted and received between the client terminal devices in the messenger service system.

In addition, the present invention is configured to regenerate and transmit by modifying the attachment in the messenger service system so that the client terminal device can be interpreted by the counterpart client terminal device. Accordingly, unnecessary file transfer between the client terminal devices can be prevented.

1 is a diagram illustrating a system for communication between a general terminal device and a server;

2 is a signal flow diagram illustrating an instant messaging process in a messenger system;

3 is a signal flow diagram illustrating a message transaction performed between client terminal devices and a server prior to file transmission according to an embodiment of the present invention;

4 is a control flowchart when a terminal transmits a file to a counterpart terminal through a messenger service according to the first embodiment of the present invention;

5 is a control flowchart when a terminal transmits a file to a counterpart terminal through a messenger service according to a second embodiment of the present invention.

Claims (12)

In a system for providing a messenger service, If the user requests a file transfer to the counterpart client terminal device, the receiver transmits a receiver capability request message inquiring whether the counterpart client terminal device can interpret the file, and interprets the corresponding file of the counterpart client terminal device. A client terminal device that determines whether to send the corresponding file according to a result of the file interpretation capability of the counterpart client terminal when receiving a receiver capability response message including information about the receiver; When receiving the file interpretation capability query message from the client terminal device, the information on the file interpretation capability is received from the counterpart client terminal device, and the information on the interpretation capability of the corresponding file of the counterpart client terminal device is provided in the receiver response message. System comprising a server to include and transmit to the client terminal device. The system of claim 1, wherein the receiver capability request message includes information on a file to be transmitted to the counterpart client terminal device. The method of claim 1, wherein if the client terminal device determines that the other client terminal device can interpret the file to be transmitted based on a receiver capability response message, the client terminal device transmits a message transmission request message with a predetermined file to the server. System characterized in that. The method of claim 1, wherein if the client terminal determines that the counterpart client terminal cannot interpret the file to be transmitted, based on the receiver capability response message, the client terminal apparatus cannot interpret the attached file to the user. A system characterized by informing. The client terminal device of claim 1, wherein the client terminal device may interpret the original attachment file, if the counterpart client terminal device cannot interpret the attachment, even if the counterpart client terminal device cannot interpret the attachment. The system characterized in that the modification to the replacement file and transmits to the other client terminal device. 6. The system of claim 5, wherein the recipient capability response message includes information regarding an alternate interpretation capability that is an overall capability associated with the attachment. In the method for transmitting and receiving files between client terminal devices in a system providing a messenger service, When the first client terminal apparatus requests a file transfer from the first client terminal apparatus to the second client terminal apparatus, the server of the messenger service sends a receiver capability request message for inquiring whether the second client terminal apparatus can interpret the file. Sending to, Determining whether to transmit the corresponding file according to a result of the file interpretation capability of the second client terminal device when receiving a receiver capability response message including information on the interpretation capability of the corresponding file of the second client terminal device from the server; Method comprising a. 8. The method of claim 7, wherein the receiver capability request message includes information about a file to be sent to a second client terminal device. The server of claim 7, wherein when the first client terminal device determines that the second client terminal device can interpret the file to be transmitted based on a receiver capability response message, the server transmits a message transmission request message to which the predetermined file is attached. The method further comprises the step of transmitting. 8. The method of claim 7, wherein if the first client terminal determines that the second client terminal cannot interpret the file to be transmitted based on the receiver capability response message, the second client terminal interprets the attachment to the user. And notifying that the user cannot. The method of claim 7, wherein the client terminal device can interpret the original attachment file can be interpreted by the other client terminal device, even if the counterpart client terminal device can not interpret the attachment file, the client terminal device can interpret the original attachment file. And converting the file into a substitute file and transmitting the same to the counterpart client terminal device. 12. The method of claim 11, wherein the recipient capability response message includes information regarding an alternate interpretation capability that is an overall capability associated with the attachment.