KR100594107B1 - Meltimedia message service system and method for transmitting and receiving file between mobile communication terminals - Google Patents

Abstract

The present invention provides a system and method for file transmission and reception between terminals in a messenger service system. To this end, the present invention is a system for providing a multimedia message service (MMS), if a file transfer request to a counterpart MMS terminal by the user, whether or not the counterpart MMS terminal can interpret the file; An MMS terminal that transmits an information request message for inquiring and receives an information request response message including specification information of the other party's MMS terminal, and determines whether to send the corresponding file according to the specification information of the other party's MMS terminal, and from the MMS terminal. The MMS center may be configured to transmit the information request response message including the specification information of the counterpart MMS terminal to the MMS terminal upon receiving the information request message.

MMS

Description

METHOD AND METHOD FOR MULTIMEDIA MESSAGE SERVICE SYSTEM AND METHOD FOR TRANSMITTING AND RECEIVING FILE BETWEEN MOBILE COMMUNICATION TERMINALS}             

1 is a signal flow diagram illustrating an MMS messaging process in a multimedia message service (MMS) system;

2 is a diagram showing an MMS system to which the present invention is applied.

3 is a signal flow diagram when a terminal transmits a file to a counterpart terminal through an MMS service according to an embodiment of the present invention;

4 is a control flowchart when a file is transmitted from a mobile communication terminal to a counterpart mobile communication terminal through an MMS service according to an embodiment of the present invention.

The present invention relates to a multimedia message service (MMS) system, and more particularly, to a system and method for file transmission and reception when a terminal is connected through an MMS service.

In general, a user of a mobile communication terminal transmits and receives a message with a user of a counterpart mobile communication terminal using a short message service (SMS). This short message service allows only text messages of limited size to be sent. This is because the SMS message is transmitted through the signaling channel of the mobile communication network.

Over the years, the Internet has allowed information and messages to be shared among computer users. Communication between computers connected to the Internet has been accomplished by Transmission Control Protocol / Internet Protocol (TCP / IP). And e-mail communication has spread through the Internet. Email messages are routed over the Internet using the Electronic Mail Transfer Protocol (SMTP) and email addresses. Email messages can attach files of a size that are typically not limited. This attachment may be a voice file, a video file, or a file in which the voice file and the video file are combined. As a result, the e-mail user can attach the multimedia file to his e-mail message and send it.

Recently, with the development of mobile communication technology, it is possible to send and receive e-mail via the Internet even in the mobile communication terminal period. However, the e-mail transmission and reception procedure in the mobile communication terminal was complicated.

In addition, due to the development of mobile communication technology, the bandwidth in the mobile communication network has been greatly increased. This increased bandwidth enables the transmission of large multimedia messages between users of mobile communication terminals. In addition, the mobile communication terminal can process and store multimedia messages with improved functions and memory capacity. In order to enable such a multimedia message transmission, a mobile communication network provides an MMS. MMS is a standard for sending and receiving multimedia messages, which may include any combination of formatted text, pictures, photos, audio, and video clips. For example, the picture can be in any standard format, such as GIF and JPEG. Video formats such as MPEG4 and audio formats such as MP3 and MIDI are also supported by MMS. Next, the MMS messaging process in the MMS system will be described with reference to FIG. 1.

1 is a signal flow diagram illustrating an MMS messaging process in a multimedia message service (MMS) system. As shown in Fig. 1, the originating MMS terminal 1 and the receiving MMS terminal 3 connect to the MMS center 2 via an access network which is a mobile communication network. The originating MMS terminal 1 transmits a message transmission request (SendMessage Request) of the MMS message created in step 5 to the MMS center 2. When the MMS center 2 receives the message transmission request signal from the originating MMS terminal 1, the MMS center 2 checks the originating MMS terminal 1 that has requested the message transmission. If the originating MMS terminal 1 is a legitimate terminal, the MMS center 2 transmits a SendMessage Response signal in step 7.

As such, the originating MMS terminal 1 may request the MMS center 2 to transmit a message for the receiving MMS terminal 2. A file may be attached when the message is transmitted, which is the case when the user of the originating MMS terminal 1 transmits the file to the receiving MMS terminal 3. For example, if a user selects a desired file on the originating MMS terminal 1 or accessible to the originating MMS terminal 1 to send a file to the other party, the user's MMS terminal 1 sends a message (SendMessageRequest). Attaches the predetermined file selected by the user while sending the message to the MMS center 2. Accordingly, if there is an attachment in the MMS message, the attachment is transmitted together with the MMS message. The MMS center 2 then interoperates with the receiving MMS terminal 3 and transmits an MMS message from the originating MMS terminal 1 to the receiving MMS terminal 3.

However, the receiving MMS terminal 3 may not be able to interpret the attached file transmitted by the originating MMS terminal 1. For example, when the user of the originating MMS terminal 1 wants to play music or show an image to the counterpart, the user transmits the music file or image file to the counterpart along with the MMS message. At this time, there is a case where the transmitted music file or image file is a file that cannot be executed in the receiving MMS terminal 3. If the music file is an MP3 format music file, the receiving MMS terminal 3 may not have software for executing the MP3 file. In general, when the software is installed in the terminal, the format of the file that can be interpreted by the installed software is registered in the terminal. Thus, the receiving MMS terminal 3 can know whether or not the corresponding music file can be executed. In this way, the originating MMS terminal 1 does not consider the processing capability of the receiving MMS terminal 3. That is, the originating MMS terminal 1 transmits the attachment with the MMS message regardless of whether the receiving MMS terminal 3 can comment on the attachment. In this case, not only the time taken by the originating MMS terminal 1 to transmit the file to the receiving MMS terminal 3 but also the radio resources occupied for transmitting the file was wasted.

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

Another object of the present invention is to provide an MMS system and method capable of preventing traffic consumption due to unnecessary file transfer between MMS terminals.

The present invention for achieving the above object provides a system and method for file transmission and reception between terminals in a messenger service system. To this end, the present invention is a system for providing a multimedia message service (MMS), if a file transfer request to a counterpart MMS terminal by the user, whether or not the counterpart MMS terminal can interpret the file; An MMS terminal that transmits an information request message for inquiring and receives an information request response message including specification information of the other party's MMS terminal, and determines whether to send the corresponding file according to the specification information of the other party's MMS terminal, and from the MMS terminal. The MMS center may be configured to transmit the information request response message including the specification information of the counterpart MMS terminal to the MMS terminal upon receiving the information request message.

In addition, the present invention for achieving the above object is a method in which a MMS terminal transmits and receives a file in a system including an MMS center for providing a multimedia message service (MMS), the first MMS terminal is a user; Sending, by the MMS center, an information request message inquiring whether the second MMS terminal can interpret the file if there is a file transfer request to the second MMS terminal by the second MMS terminal; Transmitting an information request response message including specification information of the terminal to the first MMS terminal; and transmitting the file according to the specification information of the second MMS terminal when the first MMS terminal receives the information request response message. Determining whether or not.

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.

According to the present invention, in order to prevent unnecessary file transmission and reception between MMS terminals in the MMS system, the originating MMS terminal generates a primitive asking whether the receiving MMS terminal can interpret the file before actually performing the file transmission. Send to the Multimedia Message Service Center (hereinafter referred to as MMSC). The MMSC then generates and sends a primitive asking whether the file to be transmitted to the receiving MMS terminal can be interpreted, and receives a result of whether the corresponding file can be interpreted from the receiving MMS terminal. Finally, when the MMSC sends the result of the file interpretation capability of the receiving MMS terminal to the originating MMS terminal to which the file is to be sent, the client terminal determines whether to send the file according to the result of the file interpretation capability of the counterpart client terminal. do.

First, the system for communication between the MMS terminal and the MMSC will be described with reference to FIG. 2. The MMS terminal includes all mobile communication terminals capable of providing an MMS service such as a mobile phone terminal and a personal digital assistant (PDA).

2 is a diagram illustrating an MMS system to which the present invention is applied. Referring to FIG. 2, the MMS system includes one or more MMS terminals 10 and 20 and a mobile communication network 30 connecting the MMS terminals 10 and 20 to the MMSC 40. The mobile communication network 30 may be a second generation mobile communication network such as a GSM network, a third generation mobile communication network such as a UMTS network, or a wireless LAN network. The MMS system also includes an Internet server (or other Internet Protocol (IP) network) 70 connected to an external server such as a mailbox 80 and a wired email client 90. The mailbox 80 is connected to the Internet network 70 to store a message in an email system. The wired e-mail client 90 is connected to the Internet network 90 to perform e-mail transmission and reception on the wire.

The MMSC 40 also includes an MMS server 42, an MMS relay 44, and a user database 60. The MMS server 42 is in charge of processing and storing MMS messages transmitted and received. MMS relay 44 performs message transfer between different message systems. The user database 60 stores information related to the user, such as user subscription and addressing information.

Specifically, the sending MMS terminal 10 transmits a primitive signal to see if the receiving MMS terminal 20 can interpret the attached file to the MMSC 40, if there is an attachment when transmitting the MMS message. That is, when the sending MMS terminal 10 has a message transmission request with a predetermined file attached, the receiving MMS terminal 20 interprets the file to the MMSC 40 before transmitting the message transmission request to the MMSC 40. It generates and sends a primitive signal to inquire whether or not it can. The MMSC 40 then provides the originating MMS terminal 10 with information about the interpretation capabilities of the receiving MMS terminal 20 with respect to the attachment sent from the originating MMS terminal 10. That is, the MMSC 40 transmits a response primitive signal including information on the corresponding file interpretation capability of the receiving MMS terminal 20 to the calling MMS terminal 10. After the originating MMS terminal 10 receives the response primitive from the MMSC 40, the originating MMS terminal 10 determines whether to transmit the file according to the result of the file interpretation capability of the receiving MMS terminal 20.

Then, a message transaction is made between the MMS terminal 10 and the MMSC 40 so that the originating MMS terminal 10 may inquire the MMSC 40 of the file interpretation capability of the receiving MMS terminal 20 and receive the result. This will be described with reference to FIG. 3.

3 is a signal flow diagram illustrating a message transaction performed between an MMS terminal and an MMSC prior to file transmission according to an embodiment of the present invention. First, if the originating MMS terminal 10 is instructed to send an MMS message with a file attached by the user, the MMSC 40 sends a message transmission request with the predetermined file attached to the MMSC 40 in step 110. It requests the specification (processable media information) information of the receiving MMS terminal 20 as a primitive signal for inquiring whether the receiving MMS terminal 20 can interpret the file. In other words, the originating MMS terminal 10 requests the MMSC 40 the specification of the receiving MMS terminal 20 with an information request message having the header field information of Table 1 below (Information Message Request or m-info req). Is transmitted to the MMSC 40 as a primitive signal.

Field name Field value Explanation X-Mms-Message-Type Message-type-value = m-info-req Mandatory item PDU type definition X-Mms-Transaction-ID Transaction-id-value Identifier for Mandatory Item PDU The transaction ID is valid only for m-info-req and the corresponding m-info-conf. X-Mms-MMS-Version MMS-version-value Mandatory item MMS version number Follow the MMS version to which m-info-req applies. Date Date-value Information on when the optional item m-info-req is sent From From-value Mandatory Item Sender Terminal Number requesting m-info-req To To-value Mandatory Item Terminal number to receive requesting terminal specification information

Then, the MMSC 40 retrieves the specification information of the receiving MMS terminal 20 from the user database 60 in step 120. In another embodiment, the MMSC 40 may inquire the receiving MMS terminal 20 about the interpretation capability of the corresponding file and request and receive information on the interpretation capability of the corresponding file from the receiving MMS terminal 20. Subsequently, the MMSC 40 transmits an information message response message (Information Message Response or m-info-conf) having header field information of Table 2 below to the originating MMS terminal 10. This information request response message (m-info-conf) includes specification information of the receiving MMS terminal 20.

Field Name Field Value Explanation X-Mms-Message-Type message-type-value = m-info-conf Mandatory item PDU type definition X-Mms-Transaction-ID Transaction-id-value Identifier for Mandatory Item PDU The transaction ID is valid only for m-info-req and the corresponding m-info-conf. X-Mms-MMS-Version MMS-version-value Mandatory item MMS version number Follow the MMS version to which m-info-req applies. X-Mms-Response-Status Response-Status-value Mandatory item related response status X-Mms-Response-Text Response-Text-value A more detailed description of the optional item response status X-Mms-Contents-Info Contents-Info-value Mandatory Items Contents specification information that can be processed by the receiving terminal

The rules for the message header fields as described above are as described below, which are based on the 7.2 Encoding Rules of the MMS Specification OMA-WAP-MMS-ENC-v1_1-xxx.

Header-field = MMS-header | Application-header

MMS-header = MMS-field-name MMS-value

Application-header = Token-text Application-specific-value

Token-text = Token End-of-string

MMS-field-name = Short-integer

Application-specific-value = Text-string

Wherein MMS-value includes a value as described in Table 3 below.

Field name Explanation Bcc-value Bcc Cc-value Reference Content-location-value Location kept on the server for messages you want to receive Content-type-value Content type of the message Date-value Message transfer time Previously-sent-by-value Sender who previously sent the message Previously-sent-date-value Time the message was previously sent Delivery-report-value Sender requests delivery report to recipient Delivery-time-value Message Delivery Scheduled Time Expiry-value Message expiration time From-value Message sender Message-class-value Message class (Info, Advertisement, personal, Auto) Message-ID-value Message identifier Message-type-value Message type (m-send-req, m-send-conf…) MMS-version-value MMS Protocol version Message-size-value Message size you want to receive Priority-value Message importance (high, normal, low) Read-replyreport-value Whether caller requests Read report from recipient Report-allowed-value | Allow delivery report, read report Response-status-value Status of the message sent Response-text-value State description of sent message Sender-visibility-value Whether the receiver is notified of the sender Status-value Status of the message notified to the receiver Subject-value Message subject To-value Message recipient Transaction-id-value Each transaction identifier X-Mms-Retrieve-Status-value Status of the received message X-Mms-Retrieve-Text-value Description of the status of the received message Read-status-value Receipt of received message Reply-charging-value Is there a charge for the message to the recipient Reply-charging-deadline-value Effective billing validity time of the message Reply-charging-ID-value Message billing identifier Reply-charging-size-value Message billing size

In addition, the header field values and assigned numbers shown in Table 2 are defined only for header fields additionally defined in relation to m-info-req and m-info-conf. In the X-Mms-Contents-Information field of Table 2, the Contents-Info-value has a value of length-content-type-value. In the X-Mms-Message-Type field, the Message-type-value is m-send-req | m-send-conf | m-notification-ind | m-notifyresp-ind | m-retrieve-conf | m-acknowledge-ind | m-delivery-ind | m-read-rec-ind | m-read-orig-ind | m-forward-req | m-forward-conf | m-info-req | It has the value of m-info-conf . Where m-info-req | You can see that m-info-conf has been added.

Each of these messages has a location defined in the MMS message as follows.

m-send-req = <Octet 128>

m-send-conf = <Octet 129>

m-notification-ind = <Octet 130>

m-notifyresp-ind = <Octet 131>

m-retrieve-conf = <Octet 132>

m-acknowledge-ind = <Octet 133>

m-delivery-ind = <Octet 134>

m-read-rec-ind = <Octet 135>

m-read-orig-ind = <Octet 136>

m-forward-req = <Octet 137>

m-forward-conf = <Octet 138>

m-info-req = <Octet 139>

m-info-conf = <Octet 140>

Also, in the X-Mms-Response-Status field of <Table 2>, Response-status-value has OK value and error value.

Error-unspecified |

Error-service-denied |

Error-message-format-corrupt |

Error-sending-address-unresolved |

Error-message-not-found |

Error-network-problem |

Error-content-not-accepted |

Error-unsupported-message |

Error-Info-not-found |

Error-transient-failure |

Error-transient-sending-address-unresolved |

Error-transient-message-not-found |

Error-transient-network-problem |

Error-permanent-failure |

Error-permanent-service-denied |

Error-permanent-message-format-corrupt |

Error-permanent-sending-address-unresolved |

Error-permanent-message-not-found |

Error-permanent-content-not-accepted |

Error-permanent-reply-charging-limitations-not-met |

Error-permanent-reply-charging-request-not-accepted |

Error-permanent-reply-charging-forwarding-denied |

Error-permanent-reply-charging-not-supported

Each of these messages has a location defined in the MMS message as follows.

Ok = <Octet 128>

Error-unspecified = <Octet 129> (obsolete)

Error- service-denied = <Octet 130> (obsolete)

Error-message-format-corrupt = <Octet 131> (obsolete)

Error-sending-address-unresolved = <Octet 132> (obsolete)

Error-message-not-found = <Octet 133> (obsolete)

Error-network-problem = <Octet 134> (obsolete)

Error- content-not-accepted = <Octet 135> (obsolete)

Error-unsupported-message = <Octet 136>

Error-Info-not-found = <Octet 137> (obsolete)

Error-transient-failure = <Octet 192>

Error-transient-sending-address-unresolved = <Octet 193>

Error-transient-message-not-found = <Octet 194>

Error-transient-network-problem = <Octet 195>

Error-permanent-failure = <Octet 224>

Error-permanent-service-denied = <Octet 225>

Error-permanent-message-format-corrupt = <Octet 226>

Error-permanent-sending-address-unresolved = <Octet 227>

Error-permanent-message-not-found = <Octet 228>

Error-permanent-content-not-accepted = <Octet 229>

Error-permanent-reply-charging-limitations-not-met = <Octet 230>

Error-permanent-reply-charging-request-not-accepted = <Octet 231>

Error-permanent-reply-charging-forwarding-denied = <Octet 232>

Error-permanent-reply-charging-not-supported = <Octet 233>

Header field names and assigned numbers in Table 2 include values as described in Table 4 below.

Name Assigned Number Bcc 0x01 Cc 0x02 X-Mms-Content-Location 0x03 Content-Type 0x04 Date 0x05 X-Mms-Delivery-Report 0x06 X-Mms-Delivery-Time 0x07 X-Mms-Expiry 0x08 From 0x09 X-Mms-Message-Class 0x0A Message-ID 0x0B X-Mms-Message-Type 0x0C X-Mms-MMS-Version 0x0D X-Mms-Message-Size 0x0E X-Mms-Priority 0x0F X-Mms-Read-Report 0x11 X-Mms-Read-Allowed 0x12 X-Mms-Response-Status 0x13 X-Mms-Response-Text 0x14 X-Mms-Seder-Visiblity 0x15 X-Mms-Status 0x16 Subject 0x17 To 0x18 X-Mms-Transaction-Id 0x19 X-Mms-Retrieve-Status 0x1A X-Mms-Retrieve-Text 0x1B X-Mms-Read-Status 0x1C X-Mms-Reply-Charging 0x1D X-Mms-Reply-Charging-Deadline 0x1E X-Mms-Reply-Charging-ID 0x1F X-Mms-Reply-Charging-Size 0x20 X-Mms-Previous-Sent-By 0x21 X-Mms-Content-Info 0x22

According to the header value as described above, according to the present invention, the information request message (m-info req) transmitted by the originating MMS terminal 10 to the MMSC 40 and the MMSC 40 are transmitted to the originating MMS terminal 10. Information Message Response or m-info-conf is configured.

Referring back to FIG. 3, when the originating MMS terminal 10 receives an information request response message from the MMSC 40, the user creates an MMS message by referring to information on media that the receiving MMS terminal 20 can process in step 140. Creates an MMS message conforming to the city receiving MMS terminal 20 specification. Alternatively, the originating MMS terminal 10 configures the MMS message so that the user of the receiving MMS terminal 20 can view the existing service that can view the message through the web portal service regardless of the specification of the receiving MMS terminal.

In operation 150, the originating MMS terminal 10 attaches a predetermined file selected by the user while transmitting a message transmission request (SendMessageRequest) to the MMS center 40 for transmission to the receiving MMS terminal 20. Accordingly, if there is an attachment in the MMS message, the attachment is transmitted together with the MMS message. In operation 160, the MMS center 40 transmits a response message (SendMessage Response) to the originating MMS terminal 10 in response to the message transmission request.

In operation 170, the MMS center 2 transmits an MMS message from the originating MMS terminal 10 to the receiving MMS terminal 20 in association with the receiving MMS terminal 20.

Hereinafter, the overall flow for transmitting the file to the other MMS terminal 20 via the MMS terminal 10 according to the present invention will be described with reference to FIG.

4 is a control flow diagram 300 when an MMS terminal transmits an attached file through an MMS message to a counterpart MMS terminal 20 through a messenger service according to an embodiment of the present invention.

Referring to FIG. 4, first, the MMS terminal 10 determines whether the user has transmitted an MMS message in step 302. As described above, this MMS message is a message that the user sends to the counterpart MMS terminal through the MMS center. If the user attempts to transmit the MMS message, the MMS terminal 10 creates a SendMessageRequest message for transmitting the message. If the user transmits a file such as an audio file or an image file to the counterpart, the MMS terminal 10 generates a message transmission request (SendMessageRequest) to which a predetermined file is attached.

In operation 304, the MMS terminal 10 determines whether there is an attachment file in the corresponding MMS message. If a file is attached to the SendMessageRequest according to the present invention, the MMS terminal 10 asks the MMSC 40 whether the other party's MMS terminal 20 can interpret the file in step 306. It generates a message for sending to the MMSC (40). Then, the MMSC 40 transmits the specification information of the counterpart MMS terminal 20 to the MMS terminal 10. The MMS terminal 10 checks in step 308 whether it has received a response primitive signal from the MMSC 40 containing information about the media of the other MMS terminal.

The MMS center 40 is an information request response primitive signal having information on the overall capability related to JPEG image interpretation as well as whether or not the counterpart MMS terminal 20 is capable of interpreting JPEG images, for example. -info-conf) to the MMS terminal 10.

When the MMS terminal 10 receives the response primitive signal from the MMSC 40, the MMS terminal 10 proceeds to step 310 based on the specification information of the counterpart MMS terminal 20 and the other MMS terminal receives the file attached to the message transmission request (SendMessageRequest). Determine if it can be interpreted.

At this time, the specification information of the counterpart MMS terminal includes not only information on whether the attachment file to be transmitted can be interpreted but also information on whether there is an alternative interpretation capability for the attachment file. For example, when the MMS terminal 10 attempts to transmit a 65,000 color JPEG image having a resolution of 640 * 480 from the MMS terminal 20 to the counterpart MMS terminal 20 as an attachment, the counterpart MMS terminal 20 is transmitted by the MMS terminal 10. Even if you can't interpret the attachment you're trying to translate into 65,000 color JPEG images with a resolution of 640 * 480, it's possible to interpret 256 color JPEG images with a resolution of 640 * 480. Alternatively, the other MMS terminal 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. In the present invention, the overall capability related to the attachment of such an MMS message is called an alternative interpretation capability.

Accordingly, the MMS terminal 10 determines whether the counterpart MMS terminal 20 can interpret the replacement file based on the information on the alternative interpretation capability included in the specification information of the counterpart MMS terminal 20 that is the communication counterpart in step 312. To judge. If the counterpart MMS terminal 20 can interpret the replacement file, the MMS terminal 10 proceeds to step 314 to determine whether the counterpart MMS terminal 20 can generate a substitute file that can be interpreted. That is, the MMS terminal 20 has a 65,000 color JPEG image file of 640 * 480, for example, but does not generate a 256 color JPEG image file of 640 * 480 resolution that the other MMS terminal 20 can interpret. You may not be able to. If it is determined that the MMS terminal 10 can generate a substitute file that can be interpreted by the counterpart MMS terminal 20, the MMS terminal 10 generates a substitute file by modifying the attachment file originally intended to be transmitted. That is, the MMS terminal 10 changes the format, size, etc. of the attached file to generate a replacement file, that is, a new attached file. Alternatively, the MMS terminal 10 may change the attached file into a file of a new format by using predetermined software. The MMS terminal 10 then checks in step 318, for example, if the user chooses to send the attachment. At this time, the user of the MMS terminal 10 cannot generate and transmit the replacement file, or transmit the attachment to the counterpart MMS terminal 20 even when the counterpart MMS terminal 20 cannot interpret the original attachment or the replacement file. You can do that.

Accordingly, when the MMS terminal 10 is instructed to transmit the attachment, the MMS terminal 10 proceeds to step 320 and transmits to the MMSC 40 a message transmission request (SendMessageRequest) to which the predetermined file which is the original attachment or the replacement file is attached. . Subsequently, the MMS center 40 transmits an MMS message from the MMS terminal 10 to the counterpart MMS terminal 20 in association with the counterpart MMS terminal 20.

On the other hand, if the MMS terminal 10 is instructed not to transmit the attachment to the counterpart MMS terminal 20, for example, a message is displayed on the display that the user did not transmit the attachment to the counterpart MMS terminal 20 in step 322. Notify by marking. In addition, the MMS terminal 10 does not transmit the message transmission request (SendMessageRequest) to which the predetermined file is attached to the MMSC 40.

As described above, the MMS terminal may transmit the attached file even if the counterpart MMS terminal cannot interpret the transmitted file. In addition, even if the counterpart MMS terminal cannot interpret the attached file even if the counterpart MMS terminal cannot interpret the attachment, the MMS terminal transforms the original attachment into a substitute file that the counterpart client terminal can interpret, and the counterpart MMS. Can be sent to the terminal.

As described above, the present invention has an advantage of preventing unnecessary file transmission and reception between MMS terminals by providing specification information of each MMS terminal when MMS messages are transmitted and received between MMS terminals in an MMS system.

In addition, the present invention is configured to regenerate and transmit by modifying the attachment when the MMS terminal can not interpret the attachment in the MMS terminal in the MMS system. Accordingly, unnecessary file transfer between the MMS terminals can be prevented.

Claims (10)

In the system for providing a multimedia message service (MMS), If the user requests a file transfer to the counterpart MMS terminal, an information request message for inquiring whether the counterpart MMS terminal can interpret the file is transmitted, and the information request response message including specification information of the counterpart MMS terminal is transmitted. When receiving the MMS terminal and determines whether to send the file in accordance with the specification information of the other MMS terminal, And an MMS center for transmitting the information request response message including specification information of the counterpart MMS terminal to the MMS terminal upon receiving the information request message from the MMS terminal. The message transmission request message of claim 1, wherein the MMS terminal determines that the counterpart MMS terminal can interpret the file to be transmitted based on the information request response message received from the MMS center. System characterized in that the transmission to the MMS center. The method of claim 1, wherein the MMS terminal determines that the counterpart MMS terminal cannot interpret the file to be transmitted based on the information request response message received from the MMS center. A system characterized by announcing a number. The method of claim 1, wherein if the counterpart MMS terminal cannot interpret the attached file even if the counterpart MMS terminal cannot interpret the attachment, the MMS terminal can replace the original attachment file with the counterpart MMS terminal. Transforming the file to the other party's MMS terminal. The system as claimed in claim 4, wherein the information request response message includes processable media information of the counterpart MMS terminal. In a system including an MMS center for providing a multimedia message service (MMS) MMS terminal in the method for transmitting and receiving files, Sending, by the first MMS terminal to the MMS center, an information request message inquiring whether the second MMS terminal can interpret the file if a file transfer request is made by the user to the second MMS terminal; Transmitting, by the MMS center, an information request response message including specification information of a second MMS terminal to the first MMS terminal; And when the first MMS terminal receives the information request response message, determining whether to transmit the corresponding file according to the specification information of the second MMS terminal. The MMS center of claim 6, wherein when the first MMS terminal determines that the second MMS terminal can interpret the file to be transmitted based on the information request response message, the MMS center sends a message transmission request message with a predetermined file attached thereto. The method further comprises the step of transmitting. The method of claim 6, wherein if the first MMS terminal determines that the second MMS terminal cannot interpret the file to be transmitted based on the information request response message, the second MMS terminal can interpret the attachment to the user. The method further comprises the step of notifying. The method according to claim 6, wherein if the MMS terminal can interpret the replacement file modified from the attachment even though the MMS terminal cannot interpret the attachment, the MMS terminal converts the original attachment into a replacement file that can be interpreted by the other MMS terminal. Modifying and transmitting to the counterpart client terminal. The method of claim 6, wherein the information request response message includes receivable media information of the counterpart MMS terminal.

Images