KR102079222B1 - Method and apparatus for optimizing notification message of multimedia message - Google Patents

Abstract

Provided are a method and an apparatus for transmitting a notification message of a multimedia message. The method for transmitting a notification message notifying reception of a multimedia message by a multimedia message service center (MMSC), comprises the steps of: receiving a multimedia message from a transmission terminal; recording notification data of notifying reception of the multimedia message to a plurality of fields configuring a notification message; determining whether a size of the notification message recorded with the notification data is less than or equal to a predefined maximum size; adjusting the size of the notification data to be less than or equal to the predefined maximum size if the size of the notification data is not the predefined maximum size; and transmitting the notification message which is less than or equal to the predefined maximum size to a reception terminal.

Description

METHOD AND APPARATUS FOR OPTIMIZING NOTIFICATION MESSAGE OF MULTIMEDIA MESSAGE}

The present invention relates to a method and an apparatus for optimizing a notification message transmitted to notify a receiving terminal of an arrival of a multimedia message service (MMS).

Multimedia Message Service (MMS) is a service defined in International Standard Recommendation 3GPP (3rd Generation Partnership Project) Technical Specification TS 22.140 and TS 23.140. MMS enables to transmit and receive various multimedia data such as voice, image, audio, video data as well as text messages between terminals.

The MMS presented in the aforementioned international standard recommendation adopts a store and forward method as a message transmission method.

Since the MMS message has a considerably large size, the MMS message is not directly transmitted to the receiving terminal like a short message service (SMS), which is generally used, but is transmitted to the receiving terminal through an MMSC (Multimedia Message Service Center).

The MMSC first transmits a notification message (M-Notification.Ind) informing the receiving terminal of the MMS reception, and this notification message is transmitted using SMS.

At the beginning of MMS service provision, the notification message (M-Notification.Ind) was transmitted in one SMS because the length of the message was less than 140 bytes.

However, in recent years, in order to increase MMS traffic and enhance stability, the number of MMSCs has increased, and MMSCs are distributed and deployed in various offices, such as MMS message ID, MMS message receiving URL (Uniform Resource Locator), etc. Was further encoded. Accordingly, the lengths of the MMS message ID, the MMS message reception URL, and the like have increased.

In addition, the size of the fields in the notification message (M-Notification.Ind) has increased due to the tendency to include more than 10 bytes before the body content in the MMS title.

For example, the X-Mms-Transaction-ID field, the X-Mms-Content-Location field, and the Subject field have increased in size. Here, the X-Mms-Transaction-ID field is a field in which a message identifier (MsgID) for distinguishing an MMS message is stored. The X-Mms-Content-Location field is a field that contains a connection URL address for a receiving terminal to receive an MMS message. The Subject field is a field that contains the subject of the MMS message.

For this reason, since the total length of the notification message M-Notification.Ind exceeds 140 bytes, which is the maximum SMS size, the notification message M-Notification.Ind is divided into two SMSs and transmitted.

Since two SMS transmissions per MMS incoming message (M-Notification.Ind) occur, the load on the MMSC and SMSC is increased to handle this. In addition, since the number of MMSCs and SMSCs has to be increased to solve the load, there is a problem that the cost of expansion increases.

One problem to be solved by the present invention is a method and apparatus for optimizing a notification message so that a notification message for a multimedia message service (MMS) can be transmitted to one short message service (SMS). To provide.

Another object of the present invention is to provide a method and apparatus for optimizing the length of a notification message within an SMS maximum size by reducing the length of fields contained in the notification message for the MMS.

According to one aspect of the present invention, a method for transmitting a notification message is a method for transmitting a notification message for notifying the reception of a multimedia message by a multimedia message service center (MMSC), which receives the multimedia message from a calling terminal. Step, recording each of the notification data for the arrival of the multimedia message in a plurality of fields constituting the notification message, determining whether the size of the notification message containing the notification data is less than a predefined maximum size, If not the defined maximum size, adjusting the size of the notification data to be less than or equal to the predefined maximum size, and transmitting a notification message that is less than or equal to the predefined maximum size to the receiving terminal.

The predefined maximum size may be a maximum size of a short message service (SMS).

The notification data may include a title of a multimedia message included in a subject field of the notification message, and the adjusting may include a value obtained by adding up sizes of fields of which the size cannot be changed among the plurality of fields. Setting a threshold by subtracting from the predefined maximum size, cutting a subject of the multimedia message so that the size of the subject field is within the threshold, and including the cut subject in the subject field; Can be.

The notification data includes caller information contained in a caller information field of the notification message, wherein the caller information is obtained from a multimedia message received from the caller terminal, and the adjusting of the caller information includes a caller number in the caller information. Cutting the remaining information except for, and may further include the step of including only the calling number in the caller information field.

The notification data includes content type information contained in a content type field of the notification message, and the adjusting includes changing the content type information from string type information to code type information and recording the same in the content type field. It may further comprise a step.

The receiving terminal may not be in a roaming state.

Before the determining, the method may further include determining whether the receiving terminal is a terminal capable of receiving a notification message that is less than or equal to the predefined maximum size using an optimization setting table. The determining may include determining that the size of the notification message including the notification data is less than or equal to the predetermined maximum size when the receiving terminal is a terminal capable of receiving a notification message less than or equal to the predetermined maximum size. In the configuration table, whether to receive the notification message adjusted to the predetermined maximum size or less may be set for each terminal model.

Monitoring the throughput of the notification message adjusted to the predetermined maximum size or less after the transmitting; based on the monitoring result, an optimization completion rate based on the number of processing of the adjusted notification message for each terminal model; Comprising the step of calculating, and if the optimization completion rate is less than the threshold value, may further comprise the step of changing whether to allow the reception of the corresponding terminal model in the optimization setting table from allow to disallow.

According to another feature of the invention, the notification message transmission device is connected to a communication network, a communication device for transmitting and receiving data, a memory for storing a program for optimizing the notification message of the multimedia message for informing the reception terminal of the multimedia message, and And at least one processor for executing the program, wherein the program includes notification data for notifying reception of the multimedia message in a plurality of fields constituting the notification message, and the size of the notification message including the notification data. If is not less than the maximum size of the Short Message Service (SMS), instructions for adjusting the notification data to adjust the size of the notification message to be less than the maximum size (Instructions).

The apparatus for transmitting a notification message may further include a storage device configured to store an optimization setting table configured to allow reception of a notification message adjusted to a predetermined maximum size or less for each terminal model, and wherein the receiving terminal roams. Determine whether or not the reception permission is set in the optimization setting table as a reception permission, and when the information is roaming or not, the notification message is divided into at least two short messages and transmitted to the reception terminal. If the reception is not in the roaming state and the reception is allowed, the mobile terminal may include instructions for transmitting a notification message adjusted to be less than or equal to the maximum size of the short message to the receiving terminal.

The program collects the number of transmission of the adjusted notification message, the number of completion of reception of the adjusted notification message and the number of incoming text message requests received from the receiving terminal for each terminal model, and the number of transmission of the adjusted notification message. An original message request received from the receiving terminal relative to the received completion number of the adjusted notification message, the transmission completion rate of the adjusted notification message calculated as a ratio of the received completion number of the adjusted notification message to the terminal model; Computing the received request completion rate of the adjusted notification message calculated by the ratio of the number of incoming by the terminal model, and if one of the transmission completion rate and the received request completion rate of the adjusted notification message is less than a threshold, for the corresponding terminal model Do not allow receipt of the adjusted notification message. Command may comprise a.

According to the embodiment, by sending a notification message for the MMS to one SMS, it is possible to reduce the load and expansion cost of the MMSC and SMSC by transmitting the notification message to the two SMS in the prior art. In addition, the transaction until the MMS is received by the receiving terminal is reduced, which can solve the problem of deterioration of the MMS reception quality, thereby improving the MMS reception quality.

1 is a diagram illustrating a network providing an MMS according to an embodiment of the present invention.
2 is a flowchart illustrating an MMS transmission method including an MMS optimization process according to an embodiment of the present invention.
FIG. 3 is a flowchart specifically illustrating an MMS optimization process of FIG. 2.
4 is a flowchart illustrating a process of determining whether an optimization condition of FIG. 2 is satisfied.
5 is a flowchart illustrating a process of updating an optimization setting for each model of a terminal according to an embodiment of the present invention.
6 is a block diagram showing a hardware configuration of the MMSC according to an embodiment of the present invention.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

Throughout the specification, when a part is said to "include" a certain component, it means that it can further include other components, except to exclude other components unless specifically stated otherwise.

In addition, the terms “… unit”, “… unit”, “module”, etc. described in the specification mean a unit that processes at least one function or operation, which may be implemented by hardware or software or a combination of hardware and software. have.

The devices described in the present invention are composed of hardware including at least one processor, a memory device, a communication device, and the like, and a program executed in combination with the hardware is stored in a designated place. The hardware has the configuration and performance to implement the method of the present invention. The program includes instructions implementing the method of operation of the present invention described with reference to the drawings, and executes the present invention in combination with hardware such as a processor and a memory device.

In the present invention, the terminal is a mobile station (MS), a mobile terminal (MT), a subscriber station (SS), a portable subscriber station (PSS), a user equipment (UE) It may also refer to an access terminal (AT) and the like, and may include all or some functions of a mobile station, a mobile terminal, a subscriber station, a portable subscriber station, a user device, an access terminal, and the like.

The terminal may be a base station (BS), an access point (AP), a radio access station (RAS), a node B (Node B), an advanced node B (evolved NodeB, eNodeB), a base transceiver station ( A network device such as a base transceiver station (BTS), a mobile multihop relay (MMR) -BS, a 5G NB (gNB), and the like may be connected to a remote server.

Embodiments of the present invention are standard documents related to the international standard Open Mobile Alliance (OMA) -Multimedia Messaging Service (hereinafter referred to as MMS) standard (International Standard Recommendation 3GPP (3rd Generation) Partnership Project) Technical Specification TS 22.140 and TS 23.140). That is, steps or parts which are not described to clearly reveal the technical spirit of the present invention among the embodiments of the present invention may be supported by the above document. In addition, all terms disclosed in the present document can be described by the above standard document.

A method and apparatus for optimizing a notification message of an MMS according to an embodiment of the present invention will be described with reference to the drawings.

1 is a diagram illustrating a network providing an MMS according to an embodiment of the present invention.

Referring to FIG. 1, an originating terminal 100 and a receiving terminal 200 are connected to a mobile communication network 300 to transmit and receive a mobile communication message service. In the present specification, the mobile communication message service includes an MMS and a short message service (hereinafter, referred to as SMS).

The calling terminal 100 and the receiving terminal 200 are terminals connected to the mobile communication network 300 to enable wired and wireless communication. For example, a digital broadcasting terminal, a personal digital assistant (PDA), a smart phone, and long term evolution (LTE) ) Terminal and the like.

The mobile communication network 300 may include a communication network such as an LTE network, a 5G network, a variety of wireless networks such as a Wi-Fi network, and a combination thereof.

The mobile communication network 300 is connected to the Multimedia Message Service Center (MMSC) 400 and the Short Message Service Center (SMSC) 500, and the calling terminal 100 and the interworking between the MMSC 400 and the SMSC 500. A mobile communication message service is provided between the receiving terminals 200.

The receiving terminal 200 may set the MMS receiving mode. The MMS reception mode includes an automatic reception mode (Immediate Retrieval) and a manual reception mode (Deferred Retrieval).

When the MMS reception mode is set to the automatic reception mode, when the reception terminal 200 receives the notification message from the MMSC 400, the reception terminal 200 requests transmission of the MMS message to the MMSC 400 immediately.

When the MMS reception mode is set to the manual reception mode, when the reception terminal 200 receives the notification message from the MMSC 400, the reception terminal 200 transmits a response message to the MMSC 400. The receiving terminal 200 requests transmission of the MMS message to the MMSC 400 according to a user input signal for selecting whether to receive the original MMS message.

At this time, the notification message for the MMS is transmitted in the form of SMS.

The MMSC 400 performs MMS delivery, media conversion, MMS notification message transmission, MMS management function, and the like. MMSC 400 includes Simple Mail Transfer Protocol (SMTP), Multipurpose Internet Mail Extensions (MIUA), Internet Mail Access Protocol (IMAP), Short Message Peer to Peer (SMPP), Wireless Application Protocol (WAP), HyperText Transfer Protocol (HTTP). It performs MMS delivery function through many protocols such as Notifies each terminal (100, 200) of a message such as arrival of a new MMS or MMS delivery status, recipient message search, or message delivery error through SMS.

The SMSC 500 interoperates the SMS and the MMS with a short message peer to peer (SMPP) protocol, and transmits various information generated in the MMS process to the originating terminal 100 and the receiving terminal 200.

2 is a flowchart illustrating an MMS transmission method including an MMS optimization process according to an embodiment of the present invention. At this time, Figure 2 shows the MMS transmission process defined in the MMS standard.

Referring to FIG. 2, the calling terminal 100 transmits an MMS request message (M-Send.req) including the message contents created by the caller to the MMSC 400 (S101).

The MMSC 400 transmits a response message (M-Send.conf) to the originating terminal 100 in response to the MMS request message (S103).

The MMSC 400 determines whether the receiving terminal 200 satisfies the optimization condition (S105). Here, the determining of whether the optimization condition is satisfied will be described later with reference to FIG. 5.

If it is determined in step S105 that the receiving terminal 200 does not meet the optimization condition, the MMSC 400 generates a notification message (M-Notification.ind) informing of the MMS reception as two SMS messages and generates the SMSC 500. Through the transmission to the receiving terminal 200 (S107, S109, S111, S113).

At this time, two SMS-type notification messages (M-Notification.ind # 1, M-Notification.ind # 2) include fields defined as shown in Table 1 and Table 2 below.

M-Notification.ind # 1 Header name Field name in header size UDH UDH Length One WSP Port 6 Service IEI 3 Concatenated IEI 5 WSP Header Transaction ID One PDU Type One Length One WSP Content Type 32 X-Wap-Application-Id One X-Wap-Application One OMA MMS Header X-Mms-Message-Type 2 X-Mms-Transaction-ID 17 X-Mms-MMS-Version 2 X-Mms-Message-Class 2 X-Mms-Message-Size 3 X-Mms-Expiry 7 X-Mms-Content-Location 48

M-Notification.ind # 2 Header name Field name in header size UDH UDH Length One WSP Port 6 Service IEI 3 Concatenated IEI 5 OMA Header From 7-54 Subject 5 ~ 44

On the other hand, if it is determined in step S105 that the message optimization condition is satisfied, the MMSC 400 performs optimization of the notification message (M-Notification.ind) (S115).

The MMSC 400 transmits the optimized notification message (M-Notification.ind) to the receiving terminal 200 via the SMSC 500 (S117 and S119). That is, it transmits in one SMS (S117, S119).

Among the fields included in the notification messages (M-Notification.ind) described in Table 1 and Table 2, the UDH header includes a UDH Length field, a WSP Port field, a Service IEI field, and a Concatenated IEI field. Is a Concatenated IEI field. Since the Concatenated IEI field contains an identifier indicating that two notification messages are related to each other when the notification message is divided into two, it is possible to remove the notification message because it is an unnecessary field.

Also, among the fields included in the notification messages (M-Notification.ind) described in Tables 1 and 2, the WSP header includes a Transaction ID field, a PDU Type field, a Length field, a WSP Content Type field, and an X-Wap-Application- Includes Id field and X-Wap-Application field, among which the adjustable field is WSP Content Type field.

The WSP Content Type field can be set to a String type and a Code type. The length of the code type is relatively smaller than the length of the string type. Therefore, the length can be reduced by setting the WSP Content Type field as a code type during optimization.

In addition, among the fields included in the notification messages (M-Notification.ind) described in Tables 1 and 2, the OMA MMS Header includes an X-Mms-Message-Type field, an X-Mms-Transaction-ID field, and an X-Mms. -MMS-Version field, X-Mms-Message-Class field, X-Mms-Message-Size field, X-Mms-Expiry field, X-Mms-Content-Location field, From field and Subject field. Each of these fields is defined in Table 3, according to the standard.

Field Name Description X-Mms-Message-Type Mandatory
Specifies the PDU type X-Mms-Transaction-ID Mandatory
Transaction ID identifying the notification message (M-Notification.ind) and notification response message (M-NotifyResp.ind) X-Mms-MMS-Version Mandatory
MMS version (According to this specification, the version is 1.2) X-Mms-Message-Class Mandatory
Class of the message.The MMS Proxy-Relay MUST provide the Personal message class if the original submission did not include the X-Mms-Message-Class field. X-Mms-Message-Size Mandatory-Size of the MM as defined in [TS23140] for 3GPP and [XS0016200] for 3GPP2. X-Mms-Expiry Mandatory
Length of time the message will be available.The field has only one format, relative. X-Mms-Content-Location Mandatory
This field defines the location of the MM to be retrieved. From Optional
The address of the end MMS client (the address of the last MMS client that processed the MM, that is, the address from which the MM was sent or forwarded). Subject Optional
Subject of the message

At this time, the length of the X-Mms-Transaction-ID field, the X-Mms-Content-Location field, the From field, and the Subject field can be adjusted among the fields of the OMA MMS Header during optimization. .ind) is shown in Table 4 below.

M-Notification.ind Header name Field name in header size UDH UDH Length One WSP Port 6 Service IEI 3 WSP Header Transaction ID One PDU Type One Length One WSP Content Type One X-Wap-Application-Id One X-Wap-Application One OMA MMS Header X-Mms-Message-Type 2 X-Mms-Transaction-ID 17 X-Mms-MMS-Version 2 X-Mms-Message-Class 2 X-Mms-Message-Size 3 X-Mms-Expiry 7 X-Mms-Content-Location 48 From 7-43 Subject 5 ~ 43

The receiving terminal 200 transmits a response message (M-NotifyResp.ind) in response to the notification message (M-Notification.ind) to the MMSC 400 (S121). The receiving terminal 200 transmits a message (M-Retrieve.req) requesting the reception of the MMS original message to the MMSC 400 (S123). Then, the MMSC 400 includes the MMS original message in the response message (M-Retrieve.conf) and transmits it to the receiving terminal 200 (S125).

Here, the response message (M-Retrieve.conf) is defined as shown in Table 5 below, and the data in the Subject field cut during optimization is stored in the Subject field of the response message (M-Retrieve.conf) to the receiving terminal 200. Is sent.

M-Retrieve.conf HTTP Header Header name Field name in header size OMA Header … Message-ID 17 Subject 40 … data

However, when data in the Subject field is cut through such optimization, a problem may occur in which the title of the original message is not transmitted to the receiving terminal 200. Therefore, although the notification message is optimized and transmitted, the subject field of the MMS received message (M-Retrieve.conf) according to the response message (M-Retrieve.conf) request of the receiving terminal 200 includes all the subjects of the original message. To record. Here, even if the original title is not included in the notification message, the receiving terminal 200 normally operates in an automatic receiving mode in which the user does not recognize the notification message.

3 is a flowchart specifically illustrating the MMS optimization process of FIG. 2, and FIGS. 4A and 4B are exemplary diagrams for describing an MMS optimization process according to an exemplary embodiment of the present invention.

Referring to FIG. 3, the MMSC 400 selects at least one variable field from among header fields of a notification message (M-Notification.ind) shown in Table 1 and Table 2 (S201).

The MMSC 400 determines a field that can be removed from the selected variable fields (S203). The MMSC 400 excludes the removable field from the notification message (M-Notification.ind) (S205). For example, a removable field may be a Concatenated IEI field. Since the Concatenated IEI field is for identifying two notification messages (M-Notification.ind # 1 and M-Notification.ind # 2) related to each other, the Concatenated IEI field is deleted upon optimization to one notification message.

The MMSC 400 determines a field capable of adjusting the data size included in the selected variable fields (S207). At this time, it is determined whether the field whose data size is adjustable is the Subject field (S209), and if the Subject field is cut, the data of the Subject field is partially cut to reduce the size of the Subject field (S211).

At this time, the MMSC 400 only records up to a specific size s of the original title value of the MMS in the Subject field, and cuts thereafter. Here, s may be defined as in Equation 1 below.

That is, the subject field value length s is obtained by subtracting the length of the From field from the specific threshold k.

Here, the threshold value k is set to 140 bytes, that is, subtracted the size of the fields that cannot vary in the SMS maximum size. For example, if you use 48 bytes of X-Mms-Content-Location and 17 bytes of X-Mms-Transaction-ID, k is 33 bytes. In addition, if the calling number is 11 digits which is a general mobile number, the subject length may contain 33-11 = 22 bytes (7.33 characters since 1 Korean character is 3 bytes based on UTF-8, which is an MMS collator set). To prevent this, up to 7 Korean characters (21 bytes) are included.

The MMSC 400 determines whether the adjustable field size of the data contained in the selected variable field is the From field (S213). If the From field is present, the MMSC 400 cuts data except for the calling number from the data contained in the From field (S215).

The MMSC 400 determines whether the field capable of adjusting the data size included in the selected variable fields is a field in which content type information is stored (S217). If the content type field, the MMSC 400 changes the data type of the content type field to a code type (S219). Since the string type is string-based, changing it to the code type can reduce the size of the Content Type field.

The MMSC 400 determines whether the Transaction ID field and the Content-Location field are present (S221). The MMSC 400 may be formed of a single group or may be divided into an enterprise group and a general group.

In this case, when the MMSC 400 is divided into an enterprise type and a general type group, MMSCs of each group may be identified by a total of 36 identifiers of 0 to 9 and A to Z, respectively. However, if the MMSC 400 is a single group, it is difficult to identify the MMSC with 36 identifiers, and thus additional identifiers may be introduced. Therefore, the size of the Transaction ID field and the Content-Location field may vary depending on the structure of the MMSC. That is, the size of the data contained in the Transaction ID field and the Content-Location field is relatively adjusted (S223).

Through the above steps (S201 ~ S223) can be optimized to a single notification message as shown in Table 4.

5 is a flowchart illustrating a process of determining whether an optimization condition of FIG. 2 is satisfied.

Referring to FIG. 5, the MMSC 400 determines whether the receiving terminal 200 is in a roaming state (S301). While the receiving terminal 200 is roaming, the MMS reception mode is set to the MMS manual reception mode. Therefore, step S123 of FIG. 2 is performed only when the receiver clicks the download button. In this case, if the original title in the Subject field is truncated, inconvenience to the receiver occurs. Therefore, in the roaming state, without performing optimization, two SMS transmission methods, that is, steps S107 to S113 of FIG. 2 are performed (S303).

If the receiving terminal 200 is not in the roaming state, the MMSC 400 checks the optimization setting of the receiving terminal 200 based on the optimization setting table generated for each terminal model (S305).

The MMSC 400 determines whether the optimization setting of the receiving terminal 200 is activated (S307). If the optimization setting is activated, the MMSC 400 performs the optimization of FIG. 2 (S309). On the other hand, if the optimization setting is inactive, step S303 is performed.

On the other hand, the optimization of the notification message is a deviation from the MMS standard by changing some fields in the notification message (M-Notification.ind), MMS received message (M-Retrieve.conf), which causes the receiving terminal 200 to operate abnormally It may be.

Accordingly, in order to selectively optimize a notification message for a specific terminal model, optimization settings may be activated (On) or deactivated (Off) for each terminal model as shown in Table 6.

Terminal model name Optimization setting NOKIA-6210 On AIP-16 Off LUMIA710 On SK-S100 Off … …

6 is a flowchart illustrating a process of updating an optimization setting for each model of a terminal according to an embodiment of the present invention.

Referring to FIG. 6, the MMSC 400 generates the number of MMS notification optimization processing statistics for each terminal model (S401), and calculates an optimization completion rate based on this (S403), as shown in Table 7.

Terminal model name Optimization Processing Statistics Optimization completion rate Number of Transmissions of Optimization Notification Message (M-Notification.ind) The number of completion of reception of optimization notification message (M-Notification.ind) Number of incoming MMS received messages (M-Retrive.Req) Optimization notification sent completion rate Optimization Receive Request Completion Rate NOKIA-6210 … … … … … AIP-16 … … … … … LUMIA710 … … … … … SK-S100 … … … … … … … … … … …

Here, the transmission completion rate of the optimized notification message (M-Notification.ind) and the reception request completion rate of the optimization MMS reception message (M-Retrive.Req) are calculated through Equations 2 and 3, respectively. The optimized MMS received message (M-Retrive.Req) means an MMS received message after transmission of the optimized notification message (M-Notification.ind).

The MMSC 400 determines whether the optimization completion rate calculated in step S403 is less than the threshold (S405).

At this time, if less than the threshold, the optimization setting of the corresponding terminal model is changed from on to off (S407), which is reflected in Table 6.

When optimizing the notification message, since the title of the notification message (M-Notification.ind) and the title of the MMS reception message (M-Retrieve.conf) are different, abnormal operation may occur depending on the terminal model. Accordingly, statistics on the optimization processing number of the notification (M-Notification.ind) message are generated for each model of the receiving terminal 200, and the optimization completion rate is calculated based on the optimization completion rate of the notification (M-Notification.ind) message. Below this particular threshold, an operator can generate an audible alarm. The optimization setting of the corresponding terminal model may be changed from active (On) to inactive (Off). At this time, in the case of each number of statistics shown in Table 7, the optimization setting based on the optimization completion rate is changed when the predetermined number or more.

7 is a block diagram illustrating a hardware configuration of the MMSC according to an embodiment of the present invention, and illustrates the hardware configuration of the MMSC 400 described with reference to FIGS. 1 to 6.

Referring to FIG. 7, the MMSC 400 includes a communication device 601, a memory 603, a storage device 605, and at least one processor 607. The communication device 601 is connected to at least one processor 607 to transmit and receive data. The memory 603 is connected to at least one processor 607 and stores a program including instructions for executing the configuration and / or method according to the embodiments described with reference to FIGS. 1 to 6. The program implements the present invention in combination with hardware such as memory 603 and at least one processor 607.

The embodiments of the present invention described above are not only implemented through the apparatus and the method, but may also be implemented through a program for realizing a function corresponding to the configuration of the embodiments of the present invention or a recording medium on which the program is recorded.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

Claims (11)

A method of transmitting a notification message notifying the receipt of a multimedia message by a multimedia message service center (MMSC),
Receiving the multimedia message from a calling terminal,
Recording notification data for notifying reception of the multimedia message in a plurality of fields constituting the notification message, respectively;
Determining whether a size of a notification message including the notification data is less than or equal to a predefined maximum size,
Adjusting the size of the notification data to be less than or equal to the predefined maximum size, if not less than or equal to the predefined maximum size, and
Transmitting a notification message that is less than or equal to the predefined maximum size to a receiving terminal;
The adjusting step,
Setting a threshold by subtracting a value obtained by summing respective sizes of fields whose sizes cannot be changed among the plurality of fields from the predefined maximum size; and
Cutting the subject of the multimedia message included in the subject field so that the size of the subject field of the notification message is within the threshold, and recording the cut subject in the subject field.
The notification message transmission method comprising a. In claim 1,
The predefined maximum size is,
Method for sending a notification message, which is the maximum size of a Short Message Service (SMS). delete In claim 1,
The notification data includes caller information contained in a sender information field of the notification message,
The caller information is obtained from a multimedia message received from the caller terminal.
The adjusting step,
Cutting the remaining information other than the calling number from the calling party information, and storing only the calling number in the calling party information field
The notification message transmission method further comprising. In claim 1,
The notification data includes content type information contained in a content type field of the notification message,
The adjusting step,
Changing the content type information from string type information to code type information and storing the content type information in the content type field;
The notification message transmission method further comprising. In claim 1,
The receiving terminal,
How to send a notification message that is not roaming. In claim 1,
Before the determining step,
Determining whether the receiving terminal is a terminal capable of receiving a notification message that is less than or equal to the predefined maximum size using an optimization setting table;
Determining whether the size is less than or equal to the predefined maximum size,
If the receiving terminal is a terminal capable of receiving a notification message that is less than or equal to the predefined maximum size, it is determined whether the size of the notification message containing the notification data is less than or equal to the predefined maximum size,
The optimization setting table,
The notification message transmission method is set to allow the reception of the notification message adjusted to the predetermined size or less for each terminal model. In claim 7,
After the transmitting step,
Monitoring a throughput for a notification message adjusted to be less than or equal to the predefined maximum size,
Calculating an optimization processing completion rate based on the number of processing of the adjusted notification message for each terminal model based on the monitoring result, and
If the optimization completion rate is less than a threshold, changing whether to allow reception of a corresponding terminal model in the optimization setting table from allow to disallow
The notification message transmission method further comprising. A communication device connected to a communication network to transmit and receive data,
A memory for storing a program for optimizing a notification message of a multimedia message for notifying a reception terminal of a multimedia message; and
At least one processor for executing the program,
The program,
Each of the notification data for notifying the reception of the multimedia message is stored in a plurality of fields constituting the notification message,
If the size of the notification message containing the notification data is not less than the maximum size of the Short Message Service (SMS), the notification data is adjusted so that the size of the notification message is less than or equal to the maximum size,
A threshold value is set by subtracting a value obtained by adding up sizes of fields of which the size cannot be changed among the plurality of fields from the maximum size,
And instructions for cutting the title of the multimedia message contained in the subject field of the notification message to adjust the size of the subject field to be within the threshold. In claim 9,
The apparatus may further include a storage device configured to store an optimization setting table configured to allow reception of a notification message adjusted to a size less than or equal to the predefined maximum size for each terminal model.
The program,
Determine whether the reception terminal is in a roaming state or whether reception is allowed in the optimization setting table is set as reception permission;
If the roaming state or not receiving permission, divide the notification message into at least two short message and transmit to the receiving terminal,
And a notification message for transmitting to the receiving terminal a notification message adjusted to be less than or equal to the maximum size of the short message when the reception is not roaming and reception is allowed. In claim 10,
The program,
Collecting the number of transmission of the adjusted notification message, the number of completion of reception of the adjusted notification message and the number of incoming text message requests received from the receiving terminal for each terminal model;
Calculating a transmission completion rate of the adjusted notification message for each terminal model, which is calculated as a ratio of the received completion number of the adjusted notification message to the number of transmission of the adjusted notification message,
Calculating the reception request completion rate of the adjusted notification message for each terminal model, which is calculated as a ratio of the received number of original message requests received from the receiving terminal to the received completion number of the adjusted notification message,
And if one of the transmission completion rate and the reception request completion rate of the adjusted notification message is less than a threshold, setting disallowing reception of the adjusted notification message for a corresponding terminal model.

Images