KR100592881B1 - Method and device for providing multimedia messaging service using open service platform - Google Patents

Abstract

The present invention relates to a method and apparatus for providing a multimedia messaging service (MMS) between an application server (AS) and an end user terminal (UA) subscribed to a particular operator's multimedia messaging service relay server (MMSRS).

 An apparatus for providing a multimedia messaging service using an open service platform according to the present invention includes an OSA API processing unit (OAMSB) for processing a notification message for a multimedia messaging service (MMS) received from at least one application server (AS); A multimedia service controller (MSMSB) for managing the transmission status of the multimedia message (MM) and location information of the MMSRS to which the user terminal (UA) belongs, and for analyzing and generating protocol messages; Storage means for storing the multimedia message (MM) and a predetermined control table generated for the multimedia messaging service (MMS); and transmitting and receiving the multimedia message (MM) to the MMSRS to which the user terminal (UA) belongs. It characterized in that it comprises an MM7 protocol management unit (MPMSB) for processing the MM7 protocol.

AS, MMS, MM, MMS RS, Parlay API

Description

Method and device for providing multimedia messaging service using open service platform {METHOD AND DEVICE FOR PROVIDING MULTIMEDIA MESSAGING SERVICE USING PARLAY X GATEWAY SYSTEM}             

1 is a block diagram of a conventional multimedia message service network.

2 is a block diagram of a multimedia message service network according to an embodiment of the present invention.

3 is a detailed configuration diagram of an open service platform (Parlay X Gateway System) according to an embodiment of the present invention.

4 is a diagram showing the structure of a database (DB) configured in an open service platform (Parlay X Gateway System) according to an embodiment of the present invention.

5 is a diagram illustrating a process of providing a multimedia messaging service using an open service platform according to an embodiment of the present invention.

* Description of the symbols for the main parts of the drawings *

100: user terminal (UA)

110: Multimedia Message Service Relay Server (MMSRS)

120: application server

130: home location register (HLR)

200: Open Service Platform (Parlay X Gateway System)

210: Parlay API

301 to 308: interface

310: OSA API processing unit (OAMSB)

320: multimedia service control unit (MSMSB)

330: storage means

331: Local file system (File)

332: Database

340: MM7 protocol management unit (MPMSB)

400: Multimedia Messaging Service (MMS) Control Table

410: multimedia content table

420: MMSRS log table

430: state lookup table

440: AS information table

TECHNICAL FIELD The present invention relates to a multimedia messaging service (MMS), and in particular, to a multimedia messaging service (MMS) between any application server (AS) and an end user terminal (UA) subscribed to a particular operator's multimedia messaging service relay server (MMSRS). It relates to a method and an apparatus for providing a.

In general, a multimedia messaging service (MMS) is a new multimedia message (MM) for personalized content such as text, picture, video, and music through various mobile communication networks. It is configured as, refers to a third generation (Third Generation) multimedia messaging service linked to wired and wireless that can be delivered in a variety of services.

1 is a block diagram of a conventional multimedia message service network.

The conventional multimedia message service network shown in FIG. 1 is for a multimedia messaging service (MMS) and has a network structure that complies with general standards. The conventional multimedia message service network 100 may transmit and receive a multimedia message (MM) and collects and processes a multimedia message and multimedia content, and a user agent (UA) 100 serving as a user terminal. Multimedia message service relay server (MMSRS) 110, which is responsible for routing messages to another multimedia message service relay server (MMSRS), and logic for providing various types of multimedia services. Application Server (AS) (120) having a) and a Home Location Register (HLR) 130 that manages user information and location.

In such a conventional multimedia message service network, a multimedia message service relay server (MMSRS) (eg, MMSRS2 112) that is not directly connected to any application server (AS) (eg, AS1 121). The transmission of the multimedia message (MM) between the subscriber station (UA) 100 (for example, UA5 105) to which it belongs is performed as follows. First, the multimedia message MM addressed from the AS1 121 is transmitted to the MMSRS1 111 directly connected to the AS1 121 using the MM7 interface (MM7 protocol). The MMSRS1 111 then analyzes the content of the received multimedia message MM and processes the information about the receiving user terminal 105. At this time, if the information on the receiving user terminal 105 does not exist specifically in the MMSRS1 (111), the receiving user terminal 105 by using the MAP interface (MAP protocol) in the home location register (HLR) 130 The location information and the terminal information of the query are queried to update the information of the receiving user terminal 105. As a result of inquiring information on the receiving user terminal 105 as described above, when the terminal is connected to another multimedia message service relay server (MMSRS) (for example, MMSRS2 112), the MMSRS1 111 is connected to the MM4. Delegate authority for message transmission to the MMSRS2 112 via an interface (MM4 protocol). Finally, the multimedia message (MM) arriving at the MMSRS2 112 passes through a message analysis process and is then transmitted to the receiving user terminal 105 through the MM1 interface (MM1 protocol), thereby ending the basic transmission process. Here, the specific communication protocols of the MM1 and MM4 interfaces will be briefly described since they are not directly related to the present invention. The MM7 interface, which is a network protocol between the multimedia message service relay server (MMSRS) 110 and the application server (AS) 120, is typically implemented by the protocol (IP protocol) of the Internet network. These include, for example, TCP / IP, HTTP, and SOAP protocols.

In such a conventional multimedia message service network, an application server (AS) 121 is always operated in conjunction with a multimedia message service relay server (MMSRS) 111 of a specific operator. In addition, the application server (AS) 121 transmits a multimedia message (MM) to a specific service subscriber station (UA) 105. The message service relay server (MMSRS) 112 to which the subscriber station (UA) 105 belongs. ), One interface can be set and only a single service can be provided through the communication path. However, in this case, if the application server (AS) 121 sends a message to the service subscriber station (UA) 100 via any other message service relay server (MMSRS) 112, the communication server of the same type is additionally added. It should be set to provide a service or transmit a message through an interworking message between the message service relay servers (MMSRS) 111 and 112. In this case, however, as the types of multimedia messaging services provided by the application server (AS) 120 increase and the number of subscribers belonging to various service providers increases, the application server (AS) 120 and the plurality of multimedia message service relays are increased. In addition to the MM7 interface with the server (MMSRS) 110, the MM4 interface between the multimedia message service relay server (MMSRS) 110 increases, thereby causing a problem of duplication of interface investment and waste of resources for maintenance. . In addition, when a particular element of the interface related to the multimedia message service relay server (MMSRS) 110 is added, deleted or changed in the communication path during service operation, it is difficult to maintain and modify various interfaces. There is a problem that impedes the development of the application server (AS) 120 to provide a service.

In addition, Korean Patent Registration No. 10-0455132 'Message Delivery Method in Multimedia Messaging Service' includes a terminal of a wireless environment that receives a notification that a multimedia message (MM) has been received from an MMS server in a multimedia messaging service (MMS). A method of delivering the original message to another user's terminal or e-mail account without receiving only the information and downloading the entire body of the original message and attachments is disclosed. However, the preceding invention also requires an additional interface in order for the MMS server to provide a multimedia message to a subscriber belonging to another operator, which causes a problem of waste of resources for redundant investment and maintenance of the interface.

An object of the present invention for solving the above problems is to duplicate the investment and maintenance of the interface that can occur when the multimedia message service relay server (MMSRS) operated by a specific operator in the multimedia message service network To provide a method and apparatus that can reduce the waste of resources for.

Another object of the present invention is to provide a multimedia message service network that can efficiently provide various services in an application server (AS).

In order to achieve the above object, a method of providing a multimedia messaging service using an open service platform according to the present invention includes a notification message including a multimedia message (MM) for a multimedia messaging service (MMS) from at least one application server (AS). A first step of collecting; A second step of generating a predetermined control table for managing the multimedia messaging service (MMS) from header information included in the notification message; A third step of obtaining information on a multimedia messaging service relay server (MMSRS) to which the receiving user terminal (UA) belongs, using the information on the receiving user terminal (UA) included in the notification message; and the A fourth step of transmitting the multimedia message (MM) to the receiving user terminal (UA) via the multimedia messaging service relay server (MMSRS) based on the obtained information on the multimedia messaging service relay server (MMSRS). It is characterized by including.

In addition, a method for providing a multimedia messaging service using another open service platform according to the present invention for achieving the above object is transmitted from a user terminal UA through a multimedia messaging service relay server MMSRS in an open service platform. Collecting a notification message including a multimedia message (MM); A second step of generating a predetermined control table for managing the multimedia messaging service (MMS) from header information included in the notification message; and using information on a receiving side application server (AS) included in the notification message. And a third step of transmitting the multimedia message MM to the receiving side application server AS based on the web service.

In addition, an apparatus for providing a multimedia messaging service using an open service platform according to the present invention for achieving the above object includes an OSA API for processing a notification message for a multimedia messaging service (MMS) received from at least one application server (AS). A processing unit OAMSB; A multimedia service controller (MSMSB) for managing the transmission status of the multimedia message (MM) and location information of the MMSRS to which the user terminal (UA) belongs, and for analyzing and generating protocol messages; Storage means for storing the multimedia message (MM) and a predetermined control table generated for the multimedia messaging service (MMS); and transmitting and receiving the multimedia message (MM) to the MMSRS to which the user terminal (UA) belongs. It characterized in that it comprises an MM7 protocol management unit (MPMSB) for processing the MM7 protocol.

In addition, a multimedia messaging service network using an open service platform according to the present invention for achieving the above object, at least one application server (AS) having logic for providing various types of multimedia services; A multimedia message service relay server (MMSRS) for collecting and routing multimedia messages (MM); At least one user terminal (UA) capable of transmitting and receiving a multimedia message (MM); A home location register (HLR) for managing user information and location; and connected to the application server (AS) via the Parlay API, and connected to the multimedia message service relay server (MMSRS) and the MM7 interface, based on web services. And an open service platform for processing a multimedia message MM transmitted between the application server AS and the user terminal UA.

DETAILED DESCRIPTION A detailed description of preferred embodiments of the present invention will now be described with reference to the accompanying drawings. It should be noted that reference numerals and like elements among the drawings are denoted by the same reference numerals and symbols as much as possible even though they are shown in different drawings. In the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

2 is a block diagram of a multimedia message service network according to an embodiment of the present invention.

2, the multimedia message service network according to an embodiment of the present invention is an open service platform (Parlay X Gateway System) between a multimedia message service relay server (MMSRS) 110 and an application server (AS) 120. 200 is newly configured. The application server (AS) 120 and the open service platform (Parlay X Gateway System) 200 are connected through a Parlay API (210). The Parlay API 210 refers to a standard application program interface (API) provided by Open Service Architecture (OSA). The open service platform (Parlay X Gateway System) 200 and the multimedia message service relay server (MMSRS) 110 are connected by an MM7 interface. The multimedia message service relay server (MMSRS) 110 is connected to the user terminal (UA) 100 by an MM1 interface. In addition, a home location register (HLR) 130 is coupled to the open service platform (Parlay X Gateway System) 200 via a MAP interface.

Unlike the prior art illustrated in FIG. 1, in the multimedia message service network according to the present invention, a plurality of application servers (AS) 120 are connected to each other by an open service platform (Parlay X Gateway System) 200. The 210 transmits and receives a notification message for processing a multimedia message (MM) to an open service platform (Parlay X Gateway System) 200 through 210. The method of transmitting / receiving the parlay API 210 according to the present invention is provided based on a web service. In addition, the open service platform (Parlay X Gateway System) 200, in order to provide flexibility and independence in its own operating system (OS: Operating System), is made in the Java language and includes a basic mechanism for providing a web service. The detailed configuration of the open service platform (Parlay X Gateway System) 200 is described in detail with reference to FIG. 3.

In a multimedia message service network according to an embodiment of the present invention, an open service platform that receives a multimedia message (MM) by calling a parlay API 210 through a web service from an application server (for example, AS1 121) ( The Parlay X Gateway System (200) may inquire information of a receiving user terminal (for example, UA5 105) through a database configured internally, or as a result of information inquiry, there is no corresponding tuple. If the user terminal UA5 105 receives the information of the multimedia messaging service relay server (for example, MMSRS2 112) to which the receiving user terminal (UA5) 105 belongs through the interface with the home location register (HLR) 130, the corresponding MMSRS2 The information of 112 is updated. In addition, an open service platform (Parlay X Gateway System) 200 uses the Parlay API 210 message and creates an MM7 message through a protocol mapping process for the MM7 interface with the MMSRS2 112. When the creation of the MM7 message is completed, a process of exchanging a message through an interface with the MMSRS2 112 to which the corresponding user terminal UA5 105 belongs is performed through a TCP connection.

3 is a detailed configuration diagram of an open service platform (Parlay X Gateway System) 200 according to an embodiment of the present invention.

Referring to FIG. 3, an open service platform (Parlay X Gateway System) 200 according to an embodiment of the present invention includes an OSA API Management System (OAMSB) 310 and a Multimedia Service Controller (MSMSB). A storage means 330 having an SCF Management System Block (320), a Local File System (331) and a Database (DB) 332, and an MM7 Protocol Management System Block (MPMSB) (340). ) And a number of interfaces 301-308.

The OSA API processing unit (OAMSB) 310 provides a web service for processing a Parlay API with the application server 120 and provides a plurality of application servers in multiple threads. A block for processing the notification message from 120. The OSA API processing unit (OAMSB) 310 basically not only provides the web service logic, but also processes and stores the contents of the multimedia message (MM) from the received Parlay API in the local file system (File) 331. Information is stored in a database (DB) 332.

The multimedia service control unit (MSMSB) 320 is a basic control block for processing a multimedia message (MM), and manages information regarding a current state of the multimedia message (MM), that is, a transmission state, a failure state, and a transmission completion state. It is also responsible for the location information processing function of the multimedia messaging service relay server (MMSRS) 110 to which the receiving user terminal (UA) 100 belongs. In addition, the multimedia service control unit (MSMSB) 320 is in charge of the interface processing functions of message analysis and message generation, parsing API (210), analysis and generation of MM7 protocol messages.

The MM7 protocol manager (MPMSB) 340 is responsible for processing the MM7 protocol, and is responsible for a detailed protocol processing function for network communication with the multimedia messaging service relay server (MMSRS) 110. The MM7 protocol manager (MPMSB) 340 is responsible for a protocol generation function according to the MM7 protocol and a transmission method using the MM7 data structure generated by the multimedia service controller (MSMSB) 320. In addition, the MM7 protocol manager (MPMSB) 340 is responsible for the overall protocol mapping and conversion process for HTTP, SOAP, MM7.

In addition, the open service platform (Parlay X Gateway System) 200 has internal / external interfaces 301 to 308 for processing a multimedia messaging service (MMS).

The interface 301 is an interface for transmitting the Parlay API 210 connecting the OSA API processing unit (OAMSB) 310 and the application server (AS) 120, and is a web service serviced over a SOAP / HTTP / TCP protocol. Interface.

The interface 302 stores a multimedia message (MM), which is primarily processed by the OSA API processing unit (OAMSB) 310, in a local file system (File) 331 and stores related information in a database (DB) 332. Create

An interface 303 is an interface connecting the OSA API processor (OAMSB) 310 and the multimedia service controller (MSMSB) 320. The interface 303 is an open service platform (Parlay X Gateway System) 200, to transmit the API message, via RMI (Remote Message Invocation) communication of the Java language, selected for operating independently of the operating system (OS) This is the interface for

The interface of reference numeral 304 indicates that the multimedia service control unit (MSMSB) 320 refers to a local database (DB) 332 for the MMSRS 110 to which the receiving user terminal (UA) 100 belongs. Interface for determining nothing.

The interface 305 indicates that MMSRS 110 information is received from an external home location register (HLR) 130 when the multimedia service controller (MSMSB) 320 does not find the corresponding information in the internal local database (DB) 332. Interface using MAP protocol to query.

An interface 306 denotes a data structure for generating the MM7 message generated by the multimedia service control unit (MSMSB) 320 to an MM7 protocol management unit (MPMSB) 340 that processes MM7 protocol mapping. Protocol) Interface to transmit through communication.

The interface 307 indicates that the MM7 protocol management unit (MPMSB) 340 stores the local file when a multimedia message (MM) stored and managed in the local file system (File) 331 is finally transmitted through the MM7 protocol. An interface for inquiring a system (File) 331 to process a multimedia message (MM).

Finally, the interface 308 connects the MM7 protocol management unit (MPMSB) 340 and the multimedia messaging service relay server (MMSRS) 110 and the MM7 message to the MMSRS 110 over the SOAP / HTTP / TCP communication protocol. Interface to transmit.

4 is a diagram illustrating a structure of a database (DB) 332 configured in an open service platform (Parlay X Gateway System) 200 according to an embodiment of the present invention.

Referring to FIG. 4, in accordance with an embodiment of the present invention, an open service platform (Parlay X Gateway System) 200 manages internally to provide a multimedia messaging service (MMS). Messaging service (MMS) control table (MMS_Control_Table) 400, multimedia content table (MMS_Contents_Table) 410, MMSRS log table (MMS_MMSRS_Table) 420, status lookup table (MMS_Status_Table) 430, and AS information A table (As_RegSvc_Table) 440 is included.

The multimedia messaging service (MMS) control table 400 is a table for managing a multimedia message (MM) received from a user terminal (UA) 100 or a specific application server (AS) 120. The multimedia messaging service (MMS) control table 400 includes a transaction ID for processing a multimedia message, a sender and a receiver terminal number (Sender Address, Receiver Address), content information (Count of Contents, TableName for Contents Info. ), MM Priority Code (AS Priority Code), AS Registration Code and AS Service registered in the Parlay X Gateway System 200 if the sender or called party is an application server (AS). Manages information about code (AS Service Code), MM7 Message Linked ID, MM Control Date, and MM Status Reference Id.

In addition, the multimedia messaging service (MMS) control table (MMS_Control_Table) 400 is, as shown in Figure 4, the multimedia content table (MMS_Contents_Table) 410, MMSRS log table (MMS_MMSRS_Table) 420, state lookup table (MMS_Status_Table) 430, and AS information table (As_RegSvc_Table) 440 may be linked to and referred to them.

The multimedia contents table (MMS_Contents_Table) 410 indicates details of contents included in the multimedia message (MM), and includes a content file name (FileName), a content file type (FileType), a content file size (FileSize), and content storage. Contains information about the location (FileURL). Since the open service platform (Parlay X Gateway System) 200 manages all contents except the external interfaces 301, 305, and 308 with the local file system (File) 331 and the database (DB) 332, The multimedia messaging service (MMS) control table 400 is configured to manage basic information of content and information about a storage location (URL).

The MMSRS log table (MMS_MMSRS_Table) 420 is the MMSRS 110 to which the user terminal (UA) 100 belongs when the multimedia message (MM) is transmitted from the application server (AS) 120 to the user terminal (UA) 100. In order to obtain the information, the information about the MMSRS 110 to which the receiving application server (AS) 120 once serviced by the service request belongs is maintained. Therefore, when a message requesting transmission to the same receiving side user terminal (UA) 100 is received later, the MMSRS log table 420 may refer to the MMSRS 110. As a result, unnecessary interface with the home location register (HLR) 130 may be reduced, thereby reducing waste of network resources. The MMSRS log table 420 has information about a receiving terminal number RecvAddr, an MMSRS identifier (MMSC ID), and an MMSRS IP address (IPAddr).

In addition, in the present invention, even if the tuple of the multimedia messaging service (MMS) control table 400 is deleted, the application server (AS) 120 may later query the status of the multimedia message (MM). MMS_Status_Table) 430 is maintained. The state lookup table 430 is a table existing for the parlay API 210 in which the application server AS periodically checks the state information, and includes a reference identifier TransId for the multimedia message MM and a state reference identifier. (StatusId), a status code (StatusCode) and a status text (StatusText).

In order for the application server (AS) 120 to use the parlay API 260 provided by the Parlay X Gateway System 200, the application server AS goes through an off-line registration process. In this case, an information table (As_RegSvc_Table) 440 of an application server (AS) to use a web service is created. The AS information table 440 is used to transmit a message to the user terminal (UA) 101 by changing the calling address to an identification code value that can be recognized by the receiving terminal. The AS registration code (asRegCode) is used. And information about an AS service code (asSvcCode) and an AS code (asUACode) for a user terminal (UA).

5 is a diagram illustrating a process of providing a multimedia messaging service using an open service platform according to an embodiment of the present invention.

Referring to FIG. 5, an application server (AS) 120 transmits a multimedia message (MM) to a user terminal (UA) 100, and a specific application server (AS) in the user terminal (UA) 100. A process of transmitting the multimedia message MM to 120 will be described in detail.

An open service platform (Parlay X Gateway System) 200 according to the present invention provides a parlay API in a web service environment for interfacing with an application server (AS) 120. The application server (AS) 120 performs a registration procedure of the application server (AS) 120 to provide multimedia services to the open X platform (Parlay X Gateway System) (200) offline. To generate an AS registration table 440. In an embodiment of the present invention, the application server (AS) 120 may transmit a multimedia message (MM) to the user terminal (UA) belonging to any service provider through the Parlay API as follows through initial web service registration.

First, the application server (AS) 120 transmits the multimedia message (MM) to the user terminal (UA) 100 in steps S501 to S507 as follows. The application server (AS) 120 opens a notification message (API_sendMessage) including the multimedia message (MM) through a web service in order to send the multimedia message (MM) to a user terminal (UA) 100 belonging to a specific operator. Transfer to the service platform (Parlay X Gateway System) (200) (S501). The header of the notification message API_sendMessage includes information on the sender and the called party, and the content part includes a multimedia message MM. In an open service platform (Parlay X Gateway System) 200, an OSA API processing unit (OAMSB) 310 for processing a web service is generated as a thread and transmitted to a multimedia service control unit (MSMSB) 320. The OSA API processing unit (OAMSB) 310 separates the notification message (API_sendMessage) into a header portion and a content portion, and delivers the header portion to the multimedia service controller (MSMSB) 320 through an RMI. The corresponding multimedia message (MM), the contents related to the multimedia messaging service (MMS) and the control information on the called party are stored in the predetermined storage means 330. At this time, the multimedia message (MM) is stored in the local file system 331, and the contents related to the multimedia messaging service (MMS) and control information for the called party are stored in the database 332. The multimedia service control unit (MSMSB) 320 generates a control table 400 for the multimedia messaging service (MMS), and the internal MMSRS log table 420 when the called party address is the number of the user terminal (UA) 100. Query the multimedia messaging service relay server (MMSRS) information corresponding to the user terminal number. In this case, when there is no tuple corresponding to the user terminal number as a result of the information search for the MMSRS log table 420, the specific user terminal UA through the interface (MAP_Search, MAP_Response) with the home location register (HLR) 130. In step S502, information about the multimedia messaging service relay server (MMSRS) 110 to which the 100 belongs is obtained.

In this way, the multimedia service control unit (MSMSB) 320 is based on the information of the multimedia messaging service relay server (MMSRS) 110 inquiring through interworking with the internal MMSRS log table 420 or the home location register (HLR). Create a data structure of a SubmitReq message of the MM7 protocol for interfacing with the multimedia messaging service relay server (MMSRS) 110 to which the user terminal (UA) 100 belongs. When the sender's address is a registration code of the application server (AS) 120, the AS service code and the AS terminal code are queried from the AS registration table 440. The AS terminal code means a caller code that can be recognized by the user terminal. The data structure of the MM7_SubmitReq message generated as described above is transferred to the MM7 protocol management unit (MPMSB) 340. The MM7 protocol manager (MPMSB) 340 then generates the MM7 protocol using the data structure of the SubmitReq message and the content information attached from the local file system 331 and the database 332. In addition, the MM7 protocol management unit (MPMSB) 340 is based on the information of the multimedia messaging service relay server (MMSRS) 110 to which the user terminal (UA) 100 belongs, the multimedia messaging service relay server (MMSRS) 110 and TCP. The message is transmitted to the multimedia messaging service relay server (MMSRS) 110 through interworking, and a response thereof is received (MM7_Submit.REQ, MM7_Submit.RES) (S503).

Subsequently, the MMSRS 110 notifies the user terminal (UA) 100 that a message has arrived (MM1_notification.REQ, MM1_notification.RES), and the user terminal (UA) 100 takes a multimedia message (MM) (MM1_retrieve). .REQ, MM1_retrieve.RES) It forwards the response (MM1_acknowledgement.REQ) (S504).

As such, when the message delivery process between the MMSRS 110 and the user terminal (UA) 100 is completed, the MMSRS 110 notifies that the message has been delivered to the open service platform (Parlay X Gateway System) 200, and Respond (MM7_DeliveryReport.REQ, MM7_DeliveryReport.RES) (S506). In addition, when the multimedia content delivered from the user terminal (UA) 100 is read, the result is transmitted to the open service platform (Parlay X Gateway System) 200 through the MMSRS 110 (MM1_read_reply_recipient). REQ, MM7_read_reply_report.REQ, MM7_read_reply_report.RES) (S507). In addition, the application server (AS) 120 may inquire the status information of the multimedia message (MM) transmitted by using the API_getMessageDeliveryStatus message to inquire about the result of requesting the delivery of the multimedia message (MM) (S506). . The status information is maintained by managing the multimedia status table 430 so that the message control database 400 can be deleted later even if it is deleted. The open service platform (Parlay X Gateway System) 200 may inform the application server AS 120 of the reference code for status inquiry of the multimedia message MM as a response value of the notification message. The reference code is generated as a unique key and can be used as a key for referencing a mode message.

In addition, the multimedia message MM may be transmitted from the user terminal UA 100 to the application server AS 120 by the following steps S511 to S514.

When the multimedia message (MM) is transmitted from the user terminal (UA) 100 to a specific application server (AS) 120, the user terminal (UA) first transmits the multimedia message (MMSRS) 110 to the multimedia messaging service relay server (MMSRS) 110. A notification message with MM) is transmitted (MM1_Submit.REQ), and a response thereto is received (MM1_Submit.RES) (S511). The multimedia messaging service relay server (MMSRS) 110 recognizes the destination address of the received message as the service code of the application server (AS) 120 and transmits the message to the open service platform (Parlay X Gateway System) 200. (MM7_Deliver.REQ), and receives a response thereto (MM7_Deliver.RES) (S512). The multimedia messaging service relay server (MMSRS) 110 notifies that the message has been transmitted to the user terminal (UA) 100 (MM1_Deliver_report.REQ) (S513). Subsequently, the MM7 protocol management unit (MPMSB) 340 in the open service platform (Parlay X Gateway System) 200 separates the received MM7 message into a header part and a content part, and the header part is a multimedia service control unit (MSMSB). The multimedia message MM transmitted to the content part 320 and the content related to the multimedia messaging service MMS and control information about the called party and the called party are stored in the predetermined storage means 330. At this time, the multimedia message (MM) is stored in the local file system 331, and the contents related to the multimedia messaging service (MMS) and control information for the called party are stored in the database 332.

The multimedia service control unit (MSMSB) 320 recognizes the service registration number of the application server (AS) 120 from the called party number included in the header information of the MM7_Deliver.REQ received from the MM7 protocol management unit (MPMSB) 340. In the AS register registration table 430, the application server (AS) 120 finds a number registered with the open service platform (Parlay X Gateway System) 200. Subsequently, an API_notifyMessageReception message is transmitted to the application server 120 through a web service logic. The application server (AS) 120 receiving the message is directly received the multimedia message (MM) received through API_getMessage (S514). In order to deliver the multimedia message (MM) to the application server (AS) as described above, the open service platform (Parlay X Gateway System) 200 uses the API_notifyMessageReception message directly to the application server (AS) 120 to send content directly. Can provide. In addition, the application server (AS) can be configured to check the API_getReceivedMessage message periodically to the open service platform (Parlay X Gateway System) 200 by polling (Polling) method to receive the content.

The method for providing a multimedia messaging service using an open service platform according to the present invention may be embodied as computer readable codes on a computer readable recording medium. The computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer system is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and the like, and also include those implemented in the form of carrier waves such as transmission over the Internet. The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the claims below, but also by those equivalent to the claims.

According to the present invention as described above, the multimedia message (MM) provided from a plurality of application server (AS) is transmitted through the Parlay API using a single window called an open service platform (Parlay X Gateway System) based on web services. Done. Therefore, even if a multimedia message service relay server (MMSRS) operated by a specific operator is changed or added, the application server and the multimedia messaging service relay server (MMSRS) may only interface with an open service platform (Parlay X Gateway System). Since it can be maintained, there is an advantage to efficiently use network resources.

In addition, according to the present invention, since the location information of the multimedia messaging service relay server (MMSRS) to which the user terminal (UA) belongs can be found by using a control table configured inside of an open service platform (Parlay X Gateway System), There is an advantage that can increase the efficiency of network resources by reducing the unnecessary location lookup process with the home location register (HLR).

Claims (22)

A first step of collecting a notification message including a multimedia message (MM) for the multimedia messaging service (MMS) from at least one application server (AS); A second step of generating a predetermined control table for managing the multimedia messaging service (MMS) from header information included in the notification message; A third step of obtaining information on a multimedia messaging service relay server (MMSRS) to which the receiving user terminal (UA) belongs, using the information on the receiving user terminal (UA) included in the notification message; And A fourth step of transmitting the multimedia message (MM) to the receiving user terminal (UA) through the multimedia messaging service relay server (MMSRS) based on the obtained information on the multimedia messaging service relay server (MMSRS). Method for providing a multimedia messaging service using an open service platform comprising a. The method of claim 1, wherein in the first step, the notification message is received using web service logic. The method of claim 1, wherein in the first step, the notification message is received through a Parlay API. The method of claim 1, wherein in the third step, when the information on the receiving user terminal (UA) is a receiving user terminal (UA) number, the user terminal (UA) is searched by searching the predetermined control table. Method for providing a multimedia messaging service using an open service platform, characterized in that to obtain information of the multimedia messaging service relay server (MMSRS) corresponding to the number. 5. The multimedia messaging service relay server (MMSRS) according to claim 4, wherein if there is no tuple corresponding to the user terminal (UA) number in the predetermined control table, a home location register (HLR) belongs to the multimedia messaging service relay server (MMSRS). Method of providing a multimedia messaging service using an open service platform, characterized in that to obtain information of. The method of claim 1, further comprising receiving a response from the multimedia messaging service relay server (MMSRS) as to whether or not a message has been received. The method of claim 1, further comprising receiving a response from the user terminal (UA) as to whether the message has been read. The method of claim 1, further comprising the step of the application server (AS) inquiring state information on the request for delivery of the multimedia message (MM). The method of claim 1, wherein the message transmitted to the multimedia messaging service relay server (MMSRS) uses an MM7 protocol. In an open service platform, a first step of collecting a notification message including a multimedia message (MM) transmitted from a user terminal (UA) via a multimedia messaging service relay server (MMSRS); A second step of generating a predetermined control table for managing the multimedia messaging service (MMS) from header information included in the notification message; and And transmitting the multimedia message (MM) to the receiving application server (AS) based on a web service by using the information on the receiving application server (AS) included in the notification message. Method for providing a multimedia messaging service using an open service platform, characterized in that. 12. The method of claim 10, wherein the third step is that the open service platform delivers the received multimedia message (MM) directly to the application server (AS). . The open service platform of claim 10, wherein the third step is that the application server (AS) periodically checks the open service platform by polling to receive the multimedia message (MM). Multimedia messaging service providing method using. An OSA API processing unit (OAMSB) for processing a notification message for a multimedia messaging service (MMS) received from at least one application server (AS); A multimedia service control unit (MSMSB) for managing the transmission status of the multimedia message (MM) and location information of the MMSRS to which the user terminal (UA) belongs, and for analyzing and generating protocol messages; Storage means for storing said multimedia message (MM) and a predetermined control table generated for a multimedia messaging service (MMS); and Apparatus for providing a multimedia messaging service using an open service platform, comprising an MM7 protocol management unit (MPMSB) for processing an MM7 protocol to transmit and receive the multimedia message (MM) to the MMSRS to which the user terminal (UA) belongs. . The apparatus of claim 13, wherein the OSA API processing unit (OAMSB) processes the notification message transmitted from the at least one application server (AS) in multiple threads. The method of claim 13, wherein the storage means, A local file system for storing the multimedia message (MM); and Apparatus for providing a multimedia messaging service using an open service platform, characterized in that it comprises a database for storing a predetermined control table generated for the multimedia messaging service (MMS). The multimedia apparatus of claim 13, wherein the OSA API processor OAMSB interfaces with the at least one application server AS using a Parlay API serviced over a SOAP / HTTP / TCP protocol. Messaging service providing device. The apparatus of claim 13, wherein an OSA API processor (OAMSB) interfaces with the multimedia service controller (MSMSB) through RMI (Remote Message Invocation) communication. The multimedia service of claim 13, wherein the multimedia service controller (MSMSB) interfaces with an external home location register (HLR) using a MAP protocol to obtain information about the MMSRS. Messaging service providing device. The apparatus of claim 13, wherein the multimedia service controller (MSMSB) interfaces with the MM7 protocol manager (MPMSB) through user datagram protocol (UDP) communication. The multimedia messaging service of claim 13, wherein the MM7 protocol management unit (MPMSB) interfaces with the multimedia messaging service relay server (MMSRS) using a MM7 protocol over a SOAP / HTTP / TCP communication protocol. Provision device. The method of claim 13, wherein the predetermined control table, A multimedia messaging service (MMS) control table for managing a multimedia message (MM) received from the user terminal (UA) or the application server (AS); A multimedia content table for managing details of content included in a multimedia message (MM); An MMSRS log table for maintaining information on MMSRS to which a receiving user terminal UA serviced by a service request once belongs; A status query table for enabling the application server AS to query the status of the multimedia message MM later, even if the tuple of the multimedia messaging service (MMS) control table is deleted; and Multimedia messaging service using an open service platform comprising an AS information table for managing the registration information so that the application server (AS) to the multimedia messaging service (MMS) through the Parlay API based on the web service Provision device. At least one application server (AS) having logic for providing various types of multimedia services; A multimedia message service relay server (MMSRS) for collecting and routing multimedia messages (MM); At least one user terminal (UA) capable of transmitting and receiving a multimedia message (MM); A home location register (HLR) for managing user information and location; and It is connected to the application server (AS) through the Parlay API, and is connected to the multimedia message service relay server (MMSRS) through the MM7 interface, between the application server (AS) and the user terminal (UA) on a web service basis A multimedia messaging service network using an open service platform, characterized in that it comprises an open service platform for processing the multimedia message (MM) to be transmitted.

Images