KR20040022363A - Method and System for Successive Uploading of Multimedia Messages - Google Patents

Abstract

PURPOSE: A system for uploading multimedia messages of an MMS(Multimedia Messaging Service) is provided to generate and add new temporary headers using more than one header, and to upload enormous multimedia messages by using the added temporary headers, thereby reducing time for accessing a communication network. CONSTITUTION: Client terminals(100) support uploading functions of multimedia messages. A mobile communication network(110) is connected with the client terminals(100), and transceives the multimedia messages. An MMS center(120) receives/stores the multimedia messages, responds to uploading-related messages transmitted from the client terminals(100), and transmits the responded messages to the client terminals(100). A user database(130) stores MINs(Mobile Identification Numbers) and ESNs(Electronic Serial Numbers) of the client terminals(100), user profile information, available service information, and location registration information.

Description

METHOD AND SYSTEM FOR SUCCESSIVE UPLOADING OF MULTIMEDIA MESSAGES IN MULTIMEDIA MESSAGE SERVICES

The present invention relates to a method and system for inheriting a multimedia message from a multimedia messaging service (MMS). More specifically, create and add new temporary headers using one or more headers used for the message retrieval function supported by the HTTP (HyperText Transfer Protocol) protocol for the Transmission Control Protocol / Internet Protocol (TCP / IP) environment, The present invention relates to a method and system for carrying a large amount of multimedia messages using the added new temporary headers.

Since the Internet communication service, which is symbolized by the World Wide Web, has been in the spotlight, communication service has already made a big difference in human life in all aspects of society, economy and politics. It is hard to imagine life without the Internet, and the Internet is a part of life. Therefore, in recent years, the use of various high-speed communication networks, such as in order to use a variety of communication services in a better environment has increased significantly.

However, communication services such as the Internet using a computer have advantages in that the transmission speed is high and data input is convenient. However, when the communication service is no longer available, communication services cannot be used anymore. It has a disadvantage to use.

Therefore, in recent years, in order to provide communication services such as the Internet without restriction of places, many companies are spurring the development of new technology called wireless Internet. Wireless Internet refers to an environment and technology that enables users to use Internet services through a wireless network while the user is on the move. The development of technology related to mobile communication terminals and the rapid increase in the penetration rate of mobile communication terminals further promoted the development of this wireless Internet environment.

In such a wired and wireless Internet environment, a user transmits and receives data in various formats such as text, voice, image, and video using a mobile communication terminal. However, in the conventional wired and wireless Internet environment, data of various formats is not integratedly provided in one system and transmitted and received using different systems for each data format. For example, the short message is a system environment having a Short Message Service Center (SMSC), and the e-mail is a structure in which services are separately provided according to system environments having a mail server. Accordingly, a need has arisen for a system that integrally supports and manages all data regardless of the format of data transmitted and received, which has made MMS possible.

MMS refers to a messaging service that enables the transmission and reception of multimedia information by processing, converting, and selecting data in various formats to be suitable for various multimedia service environments. MMS provides a function of transmitting and receiving multimedia information and email to various devices desired by the user, away from the limited integrated services based on text or voice provided by the conventional Unified Messaging Service (UMS).

In addition, MMS supports the transmission and reception of data in various formats such as text, voice, image, and video regardless of the type of the terminal, and also supports the priority and validity period setting of data and a streaming service. When the MMS is applied, various and differentiated services such as real-time securities service, business meeting, telemedicine service, and movie watching are possible by using a mobile communication terminal.

MMS that provides such various functions can transmit and receive data in various formats using a number of commands related to sending and receiving messages defined in the HTTP protocol used in the TCP / IP environment. Here, HTTP is a communication protocol that enables information exchange between distributed servers and clients of the World Wide Web. A basic unit of data transmission and reception in a communication using the HTTP protocol is called an HTTP message. The HTTP message is composed of a sequence of octets and has a predetermined syntax.

The HTTP message includes a request message sent from the client to the server and a response message sent from the server to the client in response to the request message. Therefore, MMS implements the function of sending and receiving HTTP message between client and server by using METHOD including POST, GET, HEAD, etc. with Request message and Response message.

On the other hand, the HTTP protocol supports the function of re-sending data after aborting or failing in case of interruption or failure of message transmission when a large amount of multimedia messages are transmitted (downloaded) from server to client. . However, when a message transmission interruption or transmission failure occurs when a large amount of multimedia messages are transmitted from a client to a server, a function of subsequent transmission such as download is not supported.

Therefore, in the wireless communication network, which is relatively slow in data transmission rate and expensive in service, compared to wired communication network, the essential functions such as a rollover function when using MMS are not supported. It is also causing economic damages, resulting in high costs.

In order to solve the above-described problem, the present invention creates and adds new temporary headers using one or more headers used in the message inheritance function supported in the HTTP protocol for the TCP / IP environment, and adds the new temporary headers. It is an object of the present invention to provide a method and system for aggregating a large amount of multimedia messages by using the same.

1 is a block diagram schematically showing an MMS system according to a preferred embodiment of the present invention;

2A to 2C are exemplary screens of a request message used for retrieving a multimedia message according to an embodiment of the present invention;

3A to 3D are exemplary screens of a response message used for rolling up a multimedia message according to an embodiment of the present invention;

4 is a flowchart illustrating a process of rolling up a multimedia message according to an embodiment of the present invention.

<Description of Symbols for Main Parts of Drawings>

100: client terminal 110: mobile communication network

112: base station transmitter 114: base station controller

120: multimedia messaging service center 130: user database

140: public switched telephone network 150: voice mail / fax server

160: Internet 170: Email Server

180: Short Message Service Center

To this end, the present invention provides a multimedia messaging service system for transmitting and receiving multimedia messages having various formats, comprising: a client terminal capable of using a multimedia messaging service for supporting a function of uploading a multimedia message; A mobile communication network connected to the client terminal to transmit and receive the multimedia message; A multimedia messaging service center that receives and stores the multimedia message transmitted to the client, converts the multimedia message into a format suitable for a receiving device, and transmits a response message to the client terminal in response to the roll-up related message transmitted from the client terminal. (MMSC); And a user database interworking with the multimedia messaging service center and storing and updating information related to MIN, ESN, user profile information, available service information and location registration of the client terminal. Provide a system for uptake.

According to another object of the present invention, there is provided a client terminal capable of using a multimedia message service, a multimedia messaging service center for transmitting and receiving a multimedia message to and from the client terminal through a communication network, and a user database storing various information related to the client terminal. A multimedia message service environment, comprising: (a) uploading the multimedia message from the client terminal to the multimedia messaging service center; (b) the multimedia messaging service center receiving and storing the multimedia message and checking whether the upload is normally completed, but notifying the client terminal of an upload failure when the upload is not normally completed; (c) the client computer sending the query message to the multimedia messaging service center to query the range of the multimedia message to be followed up; (d) the multimedia messaging service center notifying the client terminal of the range of the multimedia message stored; And (e) the client terminal determining a range of the multimedia message to be uploaded and uploading the multimedia message to the multimedia messaging service center.

Hereinafter, with reference to the accompanying drawings will be described in detail a preferred embodiment of the present invention.

1 is a block diagram schematically showing an MMS system according to a preferred embodiment of the present invention.

Hereinafter, the MMS system according to the preferred embodiment of the present invention uses the HTTP message transmission / reception protocol of HTTP1.1 (RFC2616).

MMS system according to a preferred embodiment of the present invention is a voice mail / connected to a plurality of client terminals 100, mobile communication network 110, MMSC (MMS Center) 120, the user database 130 and the MMSC (120) And a fax server 150, an e-mail server 170, and a short message service center 180.

The client terminal 100 refers to a terminal capable of using the wired / wireless internet and MMS having a function of transmitting, receiving or deleting a multimedia message through an MMS system. Accordingly, the user may upload the multimedia message to the MMSC 120 using the client terminal 100 or download the multimedia message from the MMSC 120. The client terminal 100 includes all communication terminals using a network of TCP / IP, for example, hand-held computers, desktop computers, and notebooks such as mobile phones, PDAs, and Pocket computers. (Notebook) A computer, etc. may be possible.

The mobile communication network 110 transmits the multimedia messages transmitted from the plurality of client computers 100 to the MMSC 120, and transmits the multimedia messages transmitted from the MMSC 120 to the corresponding client terminal 100. Here, the protocol used for transmitting the multimedia message between the client terminal 100 and the MMSC 120 is HTTP.

The mobile communication network performing such a function includes a base transceiver station (BTS) 112, a base station controller (BSC) 114, and a mobile switching center (MSC) 116. do.

The MMSC 120 is a core component of the MMS system according to an embodiment of the present invention and performs a message transfer function between different messaging systems. That is, the multimedia message transmitted from the client terminal 100 or one or more separate messaging systems is received and interpreted, and then converted into a multimedia message format suitable for the corresponding receiving terminal device and transmitted.

In addition, the MMSC 120 notifies the client terminal 100 or the messaging system of the success or failure of the storage and transmission function of the multimedia message received from the client terminal 100 or one or more messaging systems, and transmits the message from the receiving terminal device. You are notified of the success and failure associated with the receipt of a message.

On the other hand, according to an embodiment of the present invention, in the case where the transmission failure occurs during the upload of the multimedia message from the client terminal 100 to the MMSC 120, the uploading of the multimedia message in the conventional multimedia message to take over function Add new headers defined by extending the functionality of one or more headers used. According to an embodiment of the present invention, a newly defined header begins with a header letter 'X'. Of course, a different identifier may be used for the newly defined header according to an embodiment of the present invention.

In more detail with respect to the succession of the multimedia message according to an embodiment of the present invention, the client terminal 100 is uploaded in preparation for the interruption of the upload of the multimedia message that may occur while uploading the multimedia message to the MMSC 120 The multimedia message is transmitted with a new header for identifying each of the multimedia messages. Therefore, if a transmission failure occurs during the upload of the multimedia message, the client terminal 100 transmits the identification information of the corresponding multimedia message to the MMSC 120 and at the same time inquires the data range up to the point where the upload is completed, and sends an answer message to the query. Received from the MMSC 120 will continue to upload the rest of the data from the point where the transmission is stopped.

The type and function of a header newly defined and used according to an embodiment of the present invention will be described in detail with reference to FIG.

The user database 130 may register a location for supporting mobile identification number (MIN) and ESN (Electronic Serial Number), user profile information, available service information, and mobility of the client terminal 100 that can use MMS. The relevant information is stored. That is, when the MMSC request from the specific client terminal 110 occurs, the MMSC 120 authenticates whether the corresponding client terminal 100 is a terminal that can use the MMS by using the user database 130, and authenticates the user. And to check the location information of the client terminal 100 to support mobility.

The voice mail / fax server 150 uses a gateway (not shown) and a public switched telephone network (PSTN) 140 to perform a function of transmitting voice mail and fax data to the client terminal 100 using MMS. Is connected to the MMSC 120.

Like the voice mail / fax server 150, the e-mail server 170 is connected to the MMSC 120 through the Internet 160 to perform a function of transmitting an e-mail to the client terminal 100 using the MMS. The e-mail server 170 sends and receives e-mails using SMTP (Simple Mail Transfer Protocol), which is a type of TCP / IP protocol, for e-mail transmission.

The short message service center 180 is also connected to the MMSC 120 through a communication network to perform a function of transmitting a short message to the client terminal 100 using the MMS.

2A to 2C are exemplary screens of a request message used for resuming a multimedia message according to an embodiment of the present invention.

A request message according to an embodiment of the present invention comprises 1. Request Line (command), 2. Message Headers (General Headers, Request Headers, Entity Headers), 3. BlankLine (blank line), and 4. Message Body (message body). Follow the HTTP1.1 protocol. Of course, the technical spirit of the present invention is not necessarily limited to the HTTP 1.1 protocol, and may be applied to the HTTP protocol that is version-up in the future.

2A to 2C are exemplary screens of a request message used for resuming a multimedia message according to an embodiment of the present invention.

The request message according to the embodiment of the present invention includes 1. Request Line (command), 2. Message Headers (General Headers, Request Headers, Entity Headers), 3. Blank Line, and 4. Message Body. It follows the HTTP1.1 protocol. Of course, the technical spirit of the present invention is not necessarily limited to the HTTP 1.1 protocol, and may be applied to the HTTP protocol that is version-up in the future.

2A is an exemplary screen of a request message used to upload a multimedia message from the client terminal 100 to the MMSC 120 from the beginning.

The command used in the request message of FIG. 2A is POST. The POST command is a command used by the client terminal 100 to upload a multimedia message to the MMSC 120 and deliver it to the final target server. Also, SP = Space, CRLF = Carriage Return LineFeed.

On the other hand, various commands and header fields such as POST, GET, HEAD, etc. used in the embodiment of the present invention are those defined in the HTTP 1.1 protocol, and thus, detailed descriptions thereof will be omitted.

Referring to the header field of FIG. 2A, the definition of the header field of the request message is newly defined in addition to the information of the language (Accept-Language), the operator (User-Agent), the host, and the byte size (Contents-Length) of the entire data to be transmitted. It can be seen that an additional header field named X-Upload-Etag is included.

X-Upload-Etag is a header field of type Int and functions as a unique identifier of the multimedia message body uploaded from the client terminal 100 to the MMSC 120. That is, it is used to identify an uploaded message body that has already been uploaded when a situation in which future function is required due to the interruption of the transmission when uploading a multimedia message occurs. X-Upload-Etag is used in the form of X-Upload-Etag: MIN_MMDDHHMMSS [CRLF], where MMDDHHMMSS represents month, day, hour, minute, and second information. For example, if it is used as X-Upload-Etag: 0114261166_0515232012, the client terminal uploading the multimedia message has a MIN of 011-426-1166, indicating that the upload time is 23:20:12 seconds on May 15. Therefore, the MMSC 120 can identify the multimedia message that is being uploaded, the upload is interrupted or completed by checking the information in the X-Upload-Etag. The blank line is used to indicate the end of the header field, and the message body includes multimedia message data to be uploaded.

2B is an example screen of a request message for inquiring the MMSC 120 of a portion to carry out when a transmission failure occurs during upload of a multimedia message.

The command used in the request message of FIG. 2B is GET. The GET command is a command used by the client terminal 100 to receive a multimedia message from the MMSC 120. Here, the HEAD instruction having a similar function to the GET instruction can also be used. While the GET command is used to receive multimedia messages with various formats, the HEAD command is simply used to receive information from the header field of a particular multimedia message from the MMSC 120.

Referring to the header field of FIG. 2B, it can be seen that a header field named X-Upload-if-Match is additionally included in addition to the header field of the normal request message. X-Upload-if-Match is also an Int type header field used to check whether there is a message body in which transmission interruption has occurred during uploading of a multimedia message from the client terminal 100 to the MMSC 120. The X-Upload-if-Match header field is also used in the X-Upload-if-Match: MIN_MMDDHHMMSS [CRLF] format similarly to the X-Upload-Etag header field described in FIG. 2A.

Accordingly, the MMSC 120 receiving the request message including the X-Upload-if-Match from the client terminal 100 indicates that the MIN_MMDDHHMMSS [CRLF] of the X-Upload-if-Match and the upload from the client terminal 100 are uploaded. The MIN_MMDDHHMMSS [CRLF] of the X-Upload-Etag of the suspended multimedia messages is compared and searched for a match. The MMSC 120 transmits a status code 503 indicating the internal server error to the corresponding client terminal 100 when the multimedia message corresponding to the search result does not exist. Otherwise, if there is a matching multimedia message as a result of the search, the range of multimedia messages to be followed up with 200, which is a status code indicating the success of the request message in the response message, is specified and sent to the corresponding client terminal 100. send. This will be described in more detail with reference to FIG. 3C.

2C is an example screen of a request message informing the MMSC 120 of an identifier of an uplinking multimedia message and an upcoming portion after confirming a portion to carry out.

The command used in the Request message of FIG. 2C is POST. Referring to the header item of FIG. 2C, it can be seen that a header field named X-Upload-Content-Range is added together with the X-Upload-Etag header field described in FIG. 2A. X-Upload-Content-Range is also an Int-type header, which is a range of a multimedia message to be carried out after receiving a response message from which MMSC 120 should be continued for the query described in FIG. It has a function of notifying the MMSC 120 by displaying.

The X-Upload-Content-Range header field is used in the format X-Upload-Content-Range: 1001-1500 / 1500, where 1500 represents the size (in bytes) of the entire multimedia message to be uploaded. 1500 indicates the range (bytes) of the multimedia message to be additionally conveyed, which means that the client terminal 100 intends to increment from 1001 bytes to 1500 bytes. That is, after transmission is completed from 1 byte to 1000 bytes, it can be seen that a transmission failure occurred due to disconnection.

That is, the MMSC 120 receives and combines the multimedia message corresponding to the X-Upload-Content-Range at the end of the specific uploaded multimedia message identified as the X-Upload-Etag.

3A to 3D are exemplary screens of a response message used for rolling up a multimedia message according to an embodiment of the present invention.

The response message according to the embodiment of the present invention includes: 1. Status Line, 2. Message Headers (General Headers, Response Headers, Entity Headers), 3. Blank Line, and 4. Message Body. Follow the HTTP1.1 protocol. The response message is a message used by the MMSC 120 to respond after receiving and decrypting a request message transmitted from the client terminal 100.

3A illustrates an example of a response message transmitted from the MMSC 120 to the client terminal 100 when the multimedia message upload is normally completed.

Meaning that the next OK is the status code 200 of the status line, the MMSC 120 is a code that informs the client terminal 100 that the upload is normally completed.

Referring to the header field of FIG. 3A, a transmission date used for a normal response message, a server, a connection, a cache control, and a data size in a message body to be transmitted are shown. ) And the X-Upload-Etag header field described with reference to FIG. 2A. That is, the MMSC 120 loads the identification information of the client terminal 100 and the multimedia message in which the upload is normally completed in the X-Upload-Etag header field.

Two parameters are temporarily defined and used in the message body. One is X-Mms-Message-Type indicating the type of response message, and the other is X-Mms- indicating text actually included in the message body. Response-Text. X-Mms-Response-Text is a text that the MMSC 120 notifies the client terminal 100 of the upload result of the multimedia message in which the upload is normally completed. For example, the X-Mms-Response-Text may be expressed as, for example, "transmission is completed". Accordingly, the user may check the normal upload end message displayed on the client terminal 100 and confirm the normal upload of the corresponding multimedia message.

3B illustrates an example of a response message for notifying the fact to the client terminal 100 when a failure occurs due to a failure in a server or a terminal during uploading of a multimedia message.

In the HTTP 1.1 protocol, 5xx is defined as a status code when a failure occurs in the server, and 4xx is defined as a status code when a failure occurs in the client terminal. Referring to the status line of FIG. 3B, a status code 500 representing an internal server error and a status code 400 representing a bad request are illustrated. Since only the status line can notify the client terminal 100 of the upload failure of the multimedia message, the following header items and message body items can be omitted.

The client terminal 100 notified of the upload failure occurrence as illustrated in FIG. 3B by the MMSC 120 queries the MMSC 120 for a range of multimedia messages to be carried out using the request message described in FIG. 2B. .

3C is an exemplary screen illustrating a response message that the MMSC 120 receives a query request message related to the retrieval from the client terminal 100 in response thereto.

Receiving a query request message related to the rollover from the client terminal 100, if there is already uploaded partial data, the MMSC 120 assigns a status code 200 to the status line and the client together with the header item illustrated in FIG. 3C. Transmission to the terminal 100. Otherwise, if there is no partial data already uploaded, the MMSC 120 assigns a status code 503 meaning that the requested service is not available without having to send the header item together, so that only the status line is sent to the corresponding client terminal 100. Send it.

Referring to the header item of FIG. 3C, in addition to the header field included in the normal response message, an X-Upload-Etag header field for identifying the multimedia message with the client terminal 100 and a header field named X-Upload-Range It can be seen that it is additionally included. X-Upload-Range is an Int-type header field used to inform the client terminal 100 of the range of the message body stored in the MMSC 120 until a failure occurs during the upload of the multimedia message. In the HTTP 1.1 protocol, Range is originally used for a request message. However, in the embodiment of the present invention, a range is newly defined as a header field called X-Upload-Range and used in a response message.

Referring to FIG. 3C, X-Upload-Range: 1-1000 / 1500 is indicated, indicating that only 1000 bytes of 1500 bytes, the size of the entire message body, are uploaded and stored in the MMSC 120. Accordingly, the client terminal 100 notified of the range of the message body to be continued through the response message from the MMSC 120 may upload the remaining message bodies using the request message described with reference to FIG. 2C.

3D is an example screen showing a response message when uploading of a multimedia message to which a roll-up is normally completed.

The status code 206 of the status line indicates a partial content and indicates that a successful operation on a request message including a Range header field is performed as shown in FIG. 2C. The header field item includes an X-Upload-Etag header field for identifying the multimedia message and the client terminal 100 that has performed the retrieval.

In addition, there are two parameters described in FIG. 3A in the message body, and among them, the X-Mms-Response-Text has a phrase indicating that the succession has been successfully performed. Accordingly, the user may check that the multimedia message is normally uploaded by looking at the normal termination message of the ear upload displayed on the client terminal 100.

4 is a flowchart illustrating a process of rolling up a multimedia message according to an embodiment of the present invention.

The client terminal 100 starts uploading the multimedia message to the MMSC 120 by loading the MIN and upload time information of the multimedia message on the X-Upload-Etag using the request message (S400).

The MMSC 120 receives and stores the multimedia message uploaded from the client terminal 100 (S402).

The MMSC 120 checks whether the upload of the multimedia message is normally uploaded (S404).

If it is determined in step S404 that the upload of the multimedia message is not normally completed, the MMSC 120 notifies the client terminal 100 of the upload failure of the multimedia message by putting a predetermined failure-related status code in the response message (S406). .

The client terminal 100 notified of the upload failure occurrence from the MMSC 120 adds an X-Upload-If-Match header field to the request message and inquires of the MMSC 120 of the range of the message body to be continued (S408). ).

The MMSC 120 adds an X-Upload-Range header field to the response message and transmits the message body range of the corresponding multimedia message, which is received and stored until the transmission failure occurs, to the client terminal 100 (S410).

Client terminal 100 receives the range of the message body successfully uploaded from the MMSC 120 determines the range of the remaining message body to be carried up to the MMSC (120) (S412).

The client terminal 100 adds an X-Upload-Content-Range header field to the request message and uploads the message body of the portion to be followed up to the MMSC 120 (S414).

After step S414 is performed, the process proceeds to step S402, and the MMSC 120 stores the message body to be recalled after the multimedia message already stored, and checks whether the resumption is normally completed as in step S404.

On the other hand, if the MMSC 120 determines that the resume of the multimedia message is normally terminated, it notifies that the resume is normally completed by using the response message (S416).

The above description is merely illustrative of the present invention, and those skilled in the art to which the present invention pertains may various modifications without departing from the essential characteristics of the present invention. Accordingly, the embodiments disclosed herein are not intended to limit the present invention but to describe the present invention, and the spirit and scope of the present invention are not limited by these embodiments. It is intended that the scope of the invention be interpreted by the following claims, and that all descriptions within the scope equivalent thereto shall be construed as being included in the scope of the present invention.

As described above, in the MMS using the conventional HTTP, the multimedia message retrieval function was not supported. However, according to the present invention, the multimedia message retrieval in the MMS is extended by newly defining the function of several headers used in the conventional HTTP. There is an advantage to being possible.

In addition, there is a big disadvantage that the service usage fee is greatly required when the content is uploaded again from the beginning because MMS in the conventional wireless network environment is not supported. However, according to the present invention, only the remaining part that is not uploaded needs to be continued. The cost problem is also greatly improved.

Claims (16)

In a multimedia messaging service (MMS) system for transmitting and receiving multimedia messages having various formats, A client terminal capable of using a multimedia messaging service that supports the function of uploading the multimedia message; A mobile communication network connected to the client terminal to transmit and receive the multimedia message; A multimedia messaging service center that receives and stores the multimedia message transmitted to the client, converts the multimedia message into a format suitable for a receiving device, and transmits a response message to the client terminal in response to the roll-up related message transmitted from the client terminal. (MMSC); And A user database interworking with the multimedia messaging service center and storing and updating information related to a mobile identification number (MIN), an electronic serial number (ESN), a user profile information, available service information, and location registration of the client terminal. System for rolling up a multimedia message comprising a. The method of claim 1, And the multimedia messaging service system provides the multimedia messaging service using HTTP version 1.1 or future version-up HTTP. The method according to claim 1 or 2, And one or more new header fields are defined and added to the HTTP to support the rollback of the multimedia message. The method of claim 3, wherein And the new header field extends and redefines the function of one or more header fields used for the function of receiving the multimedia message in the HTTP. The method of claim 1, The client terminal includes a mobile phone, a PDA, a pocket computer, a desktop computer and a notebook computer. The method of claim 1, The receiving device for transmitting and receiving the multimedia message with the multimedia messaging service center includes a voice mail / fax server connected through a gateway and a public switched telephone network (PSTN), an email server connected through the Internet, and Short Message Service Center (SMSC) connected via a wired network includes a system for rolling over a multimedia message, characterized in that it comprises. In a multimedia message service environment in which a client terminal capable of using a multimedia message service, a multimedia messaging service center for transmitting and receiving a multimedia message with the client terminal through a communication network, and a user database storing various information related to the client terminal, (a) uploading the multimedia message from the client terminal to the multimedia messaging service center; (b) the multimedia messaging service center receiving and storing the multimedia message and checking whether the upload is normally completed, but notifying the client terminal of an upload failure when the upload is not normally completed; (c) the client computer sending the query message to the multimedia messaging service center to query the range of the multimedia message to be followed up; (d) the multimedia messaging service center informing the client terminal of the range of the multimedia message stored; And (e) the client terminal determining a range of the multimedia message to be uploaded and uploading the multimedia message to the multimedia messaging service center; Method for rolling up a multimedia message comprising a. 8. The method of claim 7, wherein in step (a) The header item of the multimedia message includes an extended ETag header field defined by extending an ETag header field defined in HTTP. The method of claim 8, The extended ETag header field includes a MIN of the client terminal and upload time information of the multimedia message. The method according to claim 7 or 8, And when the upload is normally completed, the multimedia messaging service center transmits a status code indicating that the requested operation is normally performed and the extended ETag header field to the client terminal. 8. The method of claim 7, wherein in step (c) The query message includes a MIN of the client terminal and upload time information of the multimedia message in an extended If-Match header field defined by extending an If-Match header field defined in HTTP. How to raise. 8. The method of claim 7, wherein in step (d) And a message transmitted to the client terminal includes an extended ETag header field and an extended range header field defined by extending a range header field defined in HTTP. The method of claim 12, And the extended Range header field includes range information of the multimedia message in byte units already stored in the multimedia messaging service center. 8. The method of claim 7, wherein in step (e) The multimedia message inherited from the client terminal includes an extended Etag header field and an extended Content-Range header field defined by extending the Content-Range header field defined in HTTP. Way. The method of claim 14, The extended Content-Range header field includes a range information of the multimedia message in the unit of a subsequent byte. The method according to claim 7 or 9, The multimedia messaging service center transmits a message including a status code indicating that the resume is normally completed and the extended ETag header field to the client terminal when the resume of the multimedia message is normally completed. How to pick up.