KR102184004B1 - System and method for transmitting message capable of parallel processing per transmission group - Google Patents

Abstract

Disclosed are a message transmission system capable of quickly transmitting a message in real time by minimizing a message transmission delay when receiving a request for transmitting a large quantity of messages from a client through parallel processing in transmission group units, and a method thereof, and a recording medium. According to an embodiment of the present invention, the message transmission system includes: an actual transmission message database formed to store messages requested to be transmitted by a client; and a transmission module formed to extract the messages from the actual transmission message database, and deliver information about the messages to a web agent module to transmit the extracted messages. The transmission module is formed to update messages, which can be processed by the actual transmission message database, into a transmittable state, create a processing process for each of a plurality of transmission groups with respect to the processable messages, and perform message processing in parallel with respect to the plurality of transmission groups.

Description

Message delivery system and method capable of parallel processing per dispatch group {SYSTEM AND METHOD FOR TRANSMITTING MESSAGE CAPABLE OF PARALLEL PROCESSING PER TRANSMISSION GROUP}

The present invention relates to a message sending system and a message sending method, and more particularly, to a message sending system and method capable of parallel processing in units of sending groups.

A corporate messaging service is provided in which a text message is transmitted to a user's mobile phone that a corporate customer transacts using a wireless communication network of a mobile communication company. This corporate messaging service needs to send advertisement messages, messages for information provision, or authentication messages in large quantities to users of corporate customers.

As such, when a large number of messages are simultaneously sent by a specific customer, a bottleneck occurs in the server providing the corporate messaging service, and messages sent to customers sent after that time may be delayed frequently. In addition, the conventional corporate messaging service has a problem in that real-time performance is deteriorated by processing data in a sequential serial manner when multiple customers send messages at the same time.

The present invention is to provide a message sending system and method, and a recording medium capable of quickly sending a message in real time by minimizing a message sending delay even when a large number of message sending requests are received from a client through parallel processing in a sending group unit. .

A message sending system according to an embodiment of the present invention includes: an actual sending message database configured to store a message for which message transmission is requested by a client; And a sending module configured to extract a message from the actual sending message database and transmit information about the message to the web agent module to send the extracted message.

The sending module updates a message that can be processed in the actual sending message database to a sendable state; Generating a processing process for each of the plurality of sending groups for the message that can be processed; It may be configured to perform message processing for the plurality of sending groups in parallel.

A message sending system according to an embodiment of the present invention includes: a temporary sending message database configured to store a message created by the client in a sending standby state; And a moving module configured to extract the message requested to be sent by the client from the temporary sending message database and store it in the actual sending message database.

The moving module includes: a temporary sending DB interworking unit configured to access the temporary sending message database to change a status value of message data or extract pending message data; A first sending group processing unit configured to perform message processing for a plurality of temporary sending groups in parallel, changing a message extracted from the temporary sending message database into a processable state, and storing it in the actual sending message database; And a first real sending DB linking unit configured to store the message processed by the first sending group processing unit in the real sending message database.

The first sending group processing unit includes: a first process management unit configured to check an idle process that is not currently operating in the temporary sending message database, and change the waiting status message to a processable status for each idle process; And a plurality of first processing units controlling the temporary sending DB linking unit to store messages that can be processed in the temporary sending message database in the actual sending message database, and then deleting message information waiting to be sent from the temporary sending message database. It may include. The plurality of first processing units may be configured to perform message processing for the plurality of temporary dispatch groups in parallel.

The sending module includes: a second real sending DB interworking unit configured to access the real sending message database and configured to change a message data state value of the real send message database or extract and delete pending message data; A second dispatch group processing unit configured to perform message processing for a plurality of dispatch groups in parallel, and to change a pending message state value of the actual dispatch message database to a final dispatchable state for each idle state; And a message transmission unit configured to transmit the message processed by the second transmission group processing unit to the web agent module.

The second dispatch group processing unit may include a second process management unit monitoring a process in an idle state that is not currently operating, and changing a pending message state value of the actual dispatch message database to be processed for each idle state; And a plurality of second processing units configured to change processable data among the message data of the actual transmission message database to a state capable of being finally transmitted, and to perform message processing for the plurality of transmission groups in parallel.

A message sending system according to an embodiment of the present invention includes: a database storing information on a message; It may further include an exchange module that performs pre-processing for message transmission using a message queue before storing information about the message in the database. The sending module may transmit information about a message to a communication company in order to send a message processed and received by the exchange module.

The exchange module may include: a receiver configured to receive a message transmission request from the client; A first message queue for receiving and storing message data included in the message transmission request from the receiver; A message threading unit that receives message data from the first message queue, extracts information about a message from the message data, and delivers it to the sending module; A second message queue for receiving and storing information on the extracted message from the message thread unit; And a message storage thread unit receiving information about a message from the second message queue and storing it in the database.

The message threading unit: extracts the originating number of the sender sending the message, the recipient number of the recipient of the message, and the message contents constituting the message from the message data, and includes the extracted originating number, the recipient number, and the message content Message information can be delivered to the sending module.

The message thread unit: transfers second message information including message content extracted from message data to the second message queue, and the message storage thread unit: transfers second message information received from the second message queue to the database Can be saved.

The message thread unit: stores third message information including a source number and a destination number extracted from the message data in the database, and the database: a key unique to the message transmission request for the second and third message information It can be saved by matching the value.

The message thread unit performs a first task of delivering first message information to the sending module, a second task of delivering second message information to the second message queue, and a third task of delivering third message information to the database. Run independently of each other; For each individual message data received from the first message queue, the third task may be executed first, then the first task may be executed, and then the second task may be executed.

A method for sending a message according to an embodiment of the present invention includes, by a sending module, extracting a message from an actual sending message database storing a message requested to be sent by a client; And transmitting, by the sending module, information on the message extracted from the actual sending message database to the web agent module.

The step of extracting the message may include: updating a message that can be processed in the actual transmission message database to a state in which it can be sent; Generating a processing process for each of a plurality of dispatch groups for the message that can be processed; And performing message processing for the plurality of sending groups in parallel.

A message sending method according to an embodiment of the present invention includes the steps of storing a message created by the client in a temporary sending message database while waiting for sending; And extracting the message requested to be sent by the client from the temporary sending message database and storing it in the actual sending message database.

According to an embodiment of the present invention, there is provided a computer-readable recording medium in which a program for executing the message sending method by a computer is recorded.

According to an embodiment of the present invention, even when a large number of message transmission requests are received from a client through parallel processing in a transmission group unit, a message transmission delay can be minimized and a message can be quickly transmitted in real time.

1 is a diagram for explaining a process in which a message sending system according to an embodiment of the present invention receives a message sending request from a client and sends a message to a user.
2 is a block diagram showing in more detail a message sending system according to an embodiment of the present invention.
3 is a flowchart illustrating a process of sending a message to a user 50 by receiving a message sending request from a client by a message sending system according to an embodiment of the present invention.
4 and 5 are flow charts illustrating a process performed by a mobile module according to an embodiment of the present invention.
6 and 7 are flow charts of a process performed by a sending module according to an embodiment of the present invention.
8 is a block diagram illustrating a configuration of a message transmission system according to another embodiment of the present invention.
9 is a block diagram illustrating the configuration of an exchange module constituting the message sending system according to the embodiment of FIG. 8.
10 is a block diagram illustrating a configuration of a sending module constituting the message sending system according to the embodiment of FIG. 8.
11 is a flowchart illustrating a process in which the message sending system according to the embodiment of FIG. 8 receives a message sending request from a client and sends a message to a user.

Other advantages and features of the present invention, and a method of achieving them will become apparent with reference to the embodiments to be described later in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms. It is provided to completely inform the scope of the invention to the possessor, and the invention is only defined by the scope of the claims.

Even if not defined, all terms (including technical or scientific terms) used herein have the same meaning as commonly accepted by universal technology in the prior art to which this invention belongs. Terms defined by general dictionaries may be construed as having the same meaning as the related description and/or the text of this application, and not conceptualized or excessively formalized, even if not clearly defined herein. Won't.

The terms used in the present specification are for describing exemplary embodiments and are not intended to limit the present invention. In this specification, the singular form also includes the plural form unless specifically stated in the phrase. As used in the specification,'includes' and/or various conjugated forms of this verb, for example,'includes','includes','includes','includes', etc. refer to the mentioned composition, ingredient, component, Steps, operations and/or elements do not preclude the presence or addition of one or more other compositions, components, components, steps, operations and/or elements. In the present specification, the term'and/or' refers to each of the listed components or various combinations thereof.

Meanwhile, terms such as'~ unit' and'~ module' used throughout this specification may refer to a unit that processes at least one function or operation. For example, it can mean software, hardware components such as FPGAs or ASICs. However,'~ unit' and'~ module' are not meant to be limited to software or hardware. The'~ unit' and the'~ module' may be configured to be in an addressable storage medium, or may be configured to reproduce one or more processors.

Thus, as an example,'~ unit' and'~ module' are components such as software components, object-oriented software components, class components, and task components, processes, functions, and properties. S, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays and variables. The functions provided within the components and'~ unit' and'~ module' are combined into a smaller number of elements and'~ unit' and'~ module', or additional components and'~ unit', It can be further divided into'~modules'.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. 1 is a diagram for explaining a process in which a message sending system 10 according to an embodiment of the present invention receives a message sending request from a client 20 and sends a message to a user 50.

Referring to FIG. 1, a message sending system 10 according to an embodiment of the present invention includes a temporary sending message database (DB) 100, a move module 200, an actual sending message database 300, and It may include a Send module (400).

When a message to be transmitted through the web is created by the client 20, the message is stored in the temporary transmission message DB 100 in a state of waiting for transmission. The temporary sending message DB 100 is a storage device for storing message information, and may include, for example, an HDD or SSD, but is not limited thereto. The temporary sending message DB 100 stores information on a sending group related to sending a message (eg, recipient group information).

The mobile module 200 is a computer device including a processing device for processing data and a memory for storing data, and may process data according to a computer program installed in advance.

Each sending group (temporary sending group) of the mobile module 200 may be defined as recipient number information of message recipients. Each temporary dispatch group may include recipient number information of one or more recipients.

The number of temporary dispatch groups (N) may be preset in the message sending system 10 or may be set by a client. Alternatively, it is possible to increase the number of temporary dispatch groups each time a dispatch group addition is requested by the client.

The content of the message created by the client 20 may not be stored in the temporary transmission message DB 100. After the message content is created by the client 20, when the client 20 finally requests the message to be sent, the message content may be stored in the actual sending message DB 300.

If necessary, the content of the message created by the client 20 is stored in the temporary sending message DB 100 in real time even before the client 20 finally requests the message to be sent, or the temporary sending message DB The content of the message can also be stored in (100).

The moving module 200 may include a first process management unit 221 and a plurality of first processing units 222. The first process management unit 221 may check a process in an idle state that is not currently operating, and change a message in a waiting state to a state capable of being processed for each idle state.

The plurality of first processing units 222 take a message that can be processed from the temporary sending message DB 100 and store it in the actual sending message DB 300, and then delete the message information waiting to be sent from the temporary sending message DB 100. I can.

For each temporary dispatch group, the first processing unit 222 may be provided in a one-to-one correspondence and configured to execute the process, and a process for sending a message is performed by the first processing unit 222 equal to or greater than the number of temporary dispatch groups. Can be implemented.

The first processing unit 222 corresponding to each temporary dispatch group may include a plurality of processing units 2221 and 222N. Therefore, processing for sending messages to a plurality of temporary sending groups can be performed in parallel, and at the same time, a parallel process is possible by a plurality of process units 2221 and 222N for each temporary sending group. Bottlenecks and delays in sending messages can be more effectively prevented.

The sending module 400 is a computer device including a processing device for processing data and a memory for storing data, and may process data according to a computer program installed in advance.

The sending module 400 may include a second process management unit 421 and a plurality of second processing units 422. The second process management unit 421 may check a process in an idle state that is not currently operating, and change a message in a waiting state to a processable state for each idle state.

The plurality of second processing units 422 may take a message that can be processed from the actual delivery message DB 300, update the actual delivery message DB 300 to a state that can be finally sent, and then transmit the message information to the web agent module 30. have.

The actual sending message DB 300 is a storage device that stores message information, and may include, for example, an HDD or SSD, but is not limited thereto. The message transmitted through the web agent module 30 may be received by the user 50 through the gateway 40.

The second processing unit 422 may be configured to execute a process by providing a one-to-one correspondence for each actual dispatch group, and a process for sending a message is performed by the second processing unit 422 having a number equal to or greater than the number of actual dispatch groups. Can be implemented.

The second processing unit 422 corresponding to each thread dispatch group may include a plurality of processing units 4221 and 422N. Therefore, processing for sending messages to a plurality of real sending groups can be performed in parallel, and at the same time, a parallel process is possible by a plurality of process units 4221 and 422N for each real sending group, Bottlenecks and delays in sending messages can be more effectively prevented.

2 is a block diagram showing in more detail a message sending system according to an embodiment of the present invention. 1 and 2, a message created by the client 20 and transmitted through the web may be stored in the temporary sending message DB 100.

When a message transmission is requested from the client 20 through the web, the mobile module 200 temporarily sends the recipient group information (sending group information) related to the requested message, for example, recipient numbers belonging to the recipient group. It can be extracted from the DB (100) and stored in the actual sending message DB (300).

The moving module 200 may include a temporary sending DB linking unit 210, a first sending group processing unit 220, and a first real sending DB linking unit 230. The temporary sending DB linking unit 210 may access the temporary sending message DB 100 to change or extract message data.

The temporary sending DB linking unit 210 may include a first message data changing unit 211 and a first message data extracting unit 212. The first message data change unit 211 may change or delete a message data state value of the temporary transmission message DB 100. The first message data extracting unit 212 may extract message data waiting for the temporary transmission message DB 100.

The first dispatch group processing unit 220 may include a first process management unit 221 performing process management and a plurality of first processing units 222 performing a DB data movement process.

As described above, the first process management unit 221 may monitor an idle process that is not currently operating, and change the pending message status value of the temporary sending message DB 100 to be processed for each idle process. have.

The plurality of first processing units 222 take the data that can be processed among the message data of the temporary sending message DB 100 and store them in the real sending message DB 300 by the first real sending DB linking unit 230, and temporarily send them. The message data of the temporary sending message DB 100 may be deleted by the DB linking unit 210.

When a client requests to send a message, the actual sending message DB 300 may store sender information, sending group information (recipient group information) received from the temporary sending message DB 100, and message contents.

The sending module 400 may perform a function of transmitting a message of the actual sending message DB 300. The sending module 400 may include a second actual sending DB linking unit 410, a second sending group processing unit 420, and a message transmitting unit 430.

The second actual delivery DB interworking unit 410 may access the actual delivery message DB 300. The second actual sending DB interworking unit 410 may include a second message data changing unit 411 and a second message data extracting unit 412.

The second message data change unit 411 may change or delete a message data state value of the actual sending message DB 300. The second message data extracting unit 412 may extract the queued message data of the actual sending message DB 300.

The second sending group processing unit 420 may include a second process management unit 421 performing process management and a plurality of second processing units 422 performing a message transmission process.

The second process management unit 421 may monitor a process in an idle state that is not currently operating, and change a pending message state value of the actual sending message DB 300 to be processed for each idle state.

The plurality of second processing units 422 take the data that can be processed among the message data of the actual sending message DB 300 and open the actual sending message DB 300 in a state that can be finally sent by the second real sending DB interlocking unit 410. After updating, message information may be transmitted to the web agent module 30 by the message transmission unit 430.

The message transmission unit 430 may include a web agent interworking unit 431 interlocking with the web agent module 30 to transmit a message, and a message data transmission unit 432 transmitting message information to the web agent module 30. I can.

According to the message sending system 10 according to the embodiment of the present invention, a plurality of first processing units 222 of the first sending group processing unit 220 and a plurality of second processing units of the second sending group processing unit 420 ( 422), multiple processes are processed in a parallel manner to prevent bottlenecks, thereby minimizing dispatch delays.

The number of first processing units 222 and the number of second processing units 422 may be generated as many as the number of dispatch groups (temporary dispatch groups, actual dispatch groups), or greater numbers. Therefore, even if a large amount of messages is requested by the client 20, a large amount of messages can be simultaneously and quickly and smoothly transmitted in real time.

In addition, the first processing unit 222 and the second processing unit 422 in a unit of sending group perform processing for sending messages to a plurality of sending groups in parallel, and at the same time, each of the first iron tooth units 222 If the and the second processing unit 422 are configured with a plurality of processing units 2221, 222N, 4221, 422N, it is possible to increase the message processing speed and more effectively prevent a bottleneck and message transmission delay in mass message transmission.

In addition, according to the message sending system 10 according to an embodiment of the present invention, processing such as changing/deleting a message of the client 20 is performed by the temporary sending message DB 100 and the moving module 200. , It is possible to perform a process of actually sending a message by the actual sending message DB 300 and the sending module 400.

Accordingly, even when a client frequently modifies a message or changes a recipient before requesting a message to be sent, there is no need to change the actual message DB 300, thereby reducing the load on the actual message DB 300, and The burden of the DB 300 may be shared with the temporary sending message DB 100. Accordingly, even when a large number of messages are requested by the client 20, a bottleneck in the actual transmission message DB 300 is reduced, and a large number of messages can be processed more quickly, thereby minimizing message transmission waiting and delay.

3 is a flowchart for explaining a process in which the message sending system 10 according to an embodiment of the present invention receives a message sending request from the client 20 and sends a message to the user 50. When a message to be transmitted through the web is created by the client 20, the message is stored in the temporary transmission message DB 100 in a state of waiting for transmission.

4 and 5 are flow charts illustrating a process performed by a mobile module according to an embodiment of the present invention. 3 to 5, the moving module 200 extracts an idle process that is not currently running (S210), and if there is an extracted process, the temporary sending message DB 100 for each extracted process is in a standby state. It can be determined whether or not there is a message in a waiting state by checking the message data (S211, S212, S213). There is a message in a waiting state, and the moving module 200 may change the state to be processed for each idle state (S220).

The mobile module 200 may extract a message that can be processed from the temporary transmission message DB 100 and determine whether there is a message in a processing state (S230, S231). If there is a message in a processable state, the mobile module 200 may store the message in the actual sending message DB 300 (S240), and then delete the message information in the sending standby state from the temporary sending message DB 100 (S250). ).

6 and 7 are flow charts of a process performed by a sending module according to an embodiment of the present invention. 3, 6, and 7, the sending module 400 monitors and extracts a process in an idle state that is not currently operating (S410), and if there is an extracted process, the actual sending message DB for each extracted process ( 300), it is possible to check whether there is message data in a waiting state (S411, S412, S413).

If there is a message in the waiting state in the actual transmission message DB 300, the sending module 400 may change the pending message state value of the actual transmission message DB 300 to be processed for each idle state (S420). The sending module 400 extracts data in a processable state from the data of the actual sending message DB 300 (S430), and if there is a processable message, it may transmit the message data to the web agent (S431, S440).

8 is a block diagram illustrating a configuration of a message transmission system according to another embodiment of the present invention. Referring to FIG. 8, the message sending system according to an embodiment of the present invention may include an exchange module 500 instead of or together with the mobile module. The exchange module 500 may include a receiving unit 510, a first message queue 520, a message thread unit 530, a second message queue 540, and a message storage thread unit 550.

The receiving unit 510 may receive a message transmission request from the client 20. The first message queue 520 may receive and store message data included in the message transmission request from the receiving unit 510. The message thread unit 530 may receive message data from the first message queue 520, extract information about a message from the message data, and transmit it to the sending module 400. The second message queue 540 may receive and store information about the extracted message from the message thread unit 530. The message storage thread unit 550 may receive information about a message from the second message queue 540 and store it in the database 600.

9 is a block diagram for explaining the configuration of the exchange module 500 constituting the message sending system according to the embodiment of FIG. Referring to FIG. 9, in the exchange module 500, the receiving unit 510 may include a message sending request receiving unit 511 and a first message queue message data storage unit 512.

The message sending request receiving unit 511 may receive a message sending request for sending a message to the user 50 from the client 20. The first message queue message data storage unit 512 may extract message data included in a message transmission request and input it to the first message queue 520.

The first message queue 520 may receive and store message data from the first message queue message data storage unit 512. According to an embodiment of the present invention, the first message queue 520 may be configured to operate in a FIFO (First In First Out) method so that first input message data is first output and processed.

In the exchange module 500, the message thread unit 530 includes a message information extracting unit 534, a sending module delivery unit 532, a second message queue message information storage unit 533, and a database storage unit 531. Can include.

The message threading unit 530 may receive message data from the first message queue 520, extract information about a message from the message data, and transmit it to the sending module 400.

According to an embodiment of the present invention, the message information extracting unit 534 may receive message data from the first message queue 520 to extract information about a message. In addition, the sending module delivery unit 532, the second message queue message information storage unit 533, and the database storage unit 531 each store information on the message extracted by the message information extraction unit 534, respectively. The transmission module 400, the second message queue 540, and the database 600 may be transferred to and stored.

Specifically, in the message threading unit 530, the message information extracting unit 534 may extract a calling number of a sender sending a message, a recipient number of a recipient who receives the message, and message contents constituting the message from the message data. . Then, in the message thread unit 530, the sending module transfer unit 532 may transfer first message information including the extracted source number, receiving number, and message content to the sending module 400.

Further, the second message queue message information storage unit 533 from the message thread unit 530 may transfer second message information including message content extracted from message data to the second message queue 540. .

The second message queue 540 may receive and store second message information from the second message queue message information storage unit 533. According to an embodiment of the present invention, the second message queue 540 may also be configured to operate in a FIFO method so that the first input second message information is first output and processed.

In the message storage thread unit 550, the second message queue message information receiving unit 551 may retrieve second message information from the second message queue 540. In addition, the database post-processing storage unit 552 may store second message information retrieved from the second message queue 540 in the database 600.

Furthermore, in the message thread unit 530, the database storage unit 531 may transmit and store third message information including a source number and a destination number extracted from the message data to the database 600.

That is, according to an embodiment of the present invention, the message sending system stores information about the message in the database 600 in the process of sending a message from a client to a user through a communication company. Processing and processing for storing information about a message in the database 600 are separated from each other and executed independently.

As a result, it is possible to send a message smoothly and quickly even when a request for sending a large number of messages from a client is received by minimizing the delay in sending that occurs in the process of storing information about a message in a database when sending a message.

8 and 9, the database 600 receives and stores second message information including message content from the message storage thread unit 550 of the exchange module 500, and stores the message, and the exchange module ( 500) from the message threading unit 530 may receive and store third message information including a source number and a destination number.

In this way, the process of storing the second message information including the message content in the database 600 and the process of storing the third message information including the calling number and the called number are separately executed in a separate thread. As mentioned, the process of transmitting the first message information to the sending module 400 is also performed separately.

According to an embodiment of the present invention, the database 600 may match and store the second message information and the third message information with a key value unique to a message sending request.

In other words, according to this embodiment, a message sending request received from a client is uniquely assigned a key value for each message sending request, and the database 600 includes the message storage thread unit 550 and the message thread unit. In the process of independently receiving and storing the second message information and the third message information from 530, the second and third message information are stored in association with each other by matching the key value uniquely assigned to the message sending request. I can.

According to an embodiment of the present invention, the message threading unit 530 is a first task of delivering the first message information to the sending module 400, and the second message information is delivered to the second message queue 540. The second task to perform and the third task of transmitting third message information to the database 600 may be independently executed.

In addition, the message thread unit 530 first executes the third task for each individual message data received from the first message queue 520 and stores the calling number and the receiving number in the database 600, Execute the first task to deliver the sender number, recipient number, and message content required for message transmission to the sending module 400, and then execute the second task to perform the second message queue 540 and the message. Message contents may be stored in the database 600 through the storage thread unit 550.

Further, according to an embodiment of the present invention, the message storage thread allocated to a task of receiving information about a message from the second message queue 540 in the exchange module 500 and storing it in the database 600 The number of units 550 is the number of the message thread unit 530 allocated to a task of receiving message data from the first message queue 520, extracting information about a message, and delivering it to the sending module 400. It can be set less than the number.

As described above, according to an embodiment of the present invention, a process for sending a message received from a client and a process for storing information about a message in the database 600 are separately executed, but the message is sent in the processing order and resource allocation. By prioritizing processing related to database storage, it is possible to send messages quickly and smoothly by minimizing bottlenecks and delays even when sending a large number of messages simultaneously.

Referring back to FIG. 8, the sending module 400 may include a third message queue 440 and a sending unit 450.

The third message queue 440 may receive and store first message information including a source number, a destination number, and message content from the message thread unit 530 of the exchange module 500. According to an embodiment of the present invention, the third message queue 440 may also be configured to operate in a FIFO manner so that the first message information input first is first output and processed.

10 is a block diagram for explaining the configuration of the sending module 400 constituting the message sending system according to the embodiment of FIG. 8. Referring to FIG. 10, the sending unit 450 may include a third message queue message receiving unit 451 and a message sending unit 452.

The third message queue message receiving unit 451 may retrieve first message information from the third message queue 440. In addition, the message sending unit 452 may transmit the first message information retrieved from the third message queue 440 to the communication service provider 3 to send a message to a user.

11 is a flowchart illustrating a process in which the message sending system according to the embodiment of FIG. 8 receives a message sending request from a client and sends a message to a user.

Referring to FIG. 11, the step of receiving, by the exchange module 500, a message sending request from a client (S11), and the message data included in the message sending request by the exchange module 500 to a first message queue 520 Storing (S12), the exchange module 500 fetching message data from the first message queue 520, extracting information about the message from the message data, and transmitting it to the sending module 400 ( S15), the sending module 400 storing information on the received message in the third message queue 440 (S21), the sending module 400 received from the exchange module 500 Delivering information about a message to a communication service provider (S22), storing information about the extracted message by the exchange module 500 in a second message queue 540 (S16), and the exchange module 500 ) May include a step (S17) of fetching information about the message from the second message queue 540 and storing it in the database 600.

According to an embodiment of the present invention, in the message sending method, the message threading unit 530 receives message data from the first message queue 520 and extracts message information from the message data (S13). It may include. The step of extracting information about the message (S13) may include extracting a calling number of a sender, a recipient number of a recipient of the message, and message contents constituting the message from the message data.

The step (S15) of transmitting the information about the message to the sending module 400 includes the step of transferring first message information including the extracted source number, recipient number, and message content to the sending module 400. Can include.

In the step (S16) of storing information about the extracted message in the second message queue 540, the message threading unit 530 stores second message information including message content extracted from the message data. Transferring to the queue 540, and storing, by the message storage thread unit 550, the second message information received from the second message queue 540 in the database 600.

According to an embodiment of the present invention, the message sending method includes, by the message threading unit 530, storing third message information including a source number and a destination number extracted from the message data in the database 600 ( S14) may be further included.

Further, storing the third message information in the database 600 (S14), transferring the first message information to the sending module 400 (S15), and transferring the second message information to the second The storing of the message in the message queue 540 (S16) may be performed independently of each other by the message thread unit 530.

Further, the message threading unit 530 first executes the step (S14) of storing the third message information in the database 600 for each individual message data received from the first message queue 520, The step of transferring the first message information to the sending module 400 (S15) may be executed, and then the step of storing the second message information in the second message queue 540 (S16) may be performed. .

The message sending method according to the embodiment of the present invention described above may be produced as a program for execution in a computer and stored in a computer-readable recording medium. The computer-readable recording medium includes all types of storage devices that store data that can be read by a computer system. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tapes, floppy disks, and optical data storage devices. In addition, the message sending method may be implemented as a computer program stored in a medium for execution by being combined with a computer.

In the above, the present invention has been described through the embodiments, but the above embodiments are merely for explaining the spirit of the present invention and are not limited thereto. One of ordinary skill in the art will understand that various modifications may be made to the above-described embodiments. The scope of the invention is determined only through interpretation of the appended claims.

10: message sending system
20: client
30: web agent module
40: gateway
50: user
100: temporary sending message DB
200: move module
210: Temporary sending DB linkage unit
211: first message data change unit
212: first message data extraction unit
220: first sending group processing unit
221: first process management unit
222: first processing unit
230: First thread delivery DB linkage unit
300: actual sending message DB
400: sending module
410: second thread sending DB linkage unit
411: second message data change unit
412: second message data extraction unit
420: second dispatch group processing unit
421: second process management unit
422: second processing unit
430: message transmission unit
431: web agent interface
432: message data transmission unit

Claims (15)

A database for storing information about the message;
An exchange module that performs pre-processing for message transmission by using a message queue before storing information about the message in the database;
An actual sent message database configured to store a message for which message transmission is requested by a client; And
And a sending module configured to extract a message from the actual sending message database and transmit information about the message to a web agent module in order to send the extracted message,
The sending module,
Updating a message that can be processed in the actual transmission message database to a state in which it can be sent;
Generating a processing process for each of the plurality of sending groups for the message that can be processed;
It is configured to perform message processing for the plurality of sending groups in parallel,
The exchange module,
A receiving unit for receiving a message transmission request from the client;
A first message queue for receiving and storing message data included in the message transmission request from the receiver;
A message threading unit that receives message data from the first message queue, extracts information about a message from the message data, and delivers it to the sending module;
A second message queue for receiving and storing information on the extracted message from the message thread unit; And
A message storage thread unit receiving information about a message from the second message queue and storing it in the database,
The message thread unit,
Extracting a source number of a sender who sends a message, a recipient number of a recipient who receives the message, and message contents constituting the message from the message data; And
Transferring first message information including the extracted source number, destination number, and message content to the sending module,
The message thread unit transfers second message information including message content extracted from message data to the second message queue,
The message storage thread unit stores second message information received from the second message queue in the database,
The message thread unit stores third message information including a source number and a destination number extracted from the message data in the database,
The message thread unit performs a first job of delivering first message information to the sending module, a second job of delivering second message information to the second message queue, and a third job of delivering third message information to the database. A standalone, messaging system. The method according to claim 1,
A temporary sending message database, configured to store the message created by the client in a sending standby state; And
And a moving module, configured to extract the message requested to be sent by the client from the temporary sending message database and store it in the actual sending message database. The method according to claim 2,
The moving module,
A temporary sending DB linking unit configured to access the temporary sending message database to change a status value of message data or extract pending message data;
A first sending group processing unit configured to perform message processing for a plurality of temporary sending groups in parallel, changing a message extracted from the temporary sending message database into a processable state, and storing it in the actual sending message database; And
A message sending system comprising a first real sending DB linking unit, configured to store a message processed by the first sending group processing unit in the real sending message database. The method of claim 3,
The first sending group processing unit,
A first process management unit configured to check an idle process that is not currently operating in the temporary sending message database, and change the waiting status message to a processable status for each idle process; And
A plurality of first processing units controlling the temporary sending DB linking unit to store messages that can be processed in the temporary sending message database in the actual sending message database, and then deleting message information in a status of waiting for sending from the temporary sending message database. Including,
And the plurality of first processing units are configured to perform message processing for the plurality of temporary dispatch groups in parallel. The method of claim 4,
The sending module,
A second real sending DB interworking unit configured to access the real sending message database and configured to change a message data state value of the real send message database or extract and delete pending message data;
A second dispatch group processing unit configured to perform message processing for a plurality of dispatch groups in parallel, and to change a pending message state value of the actual dispatch message database to a final dispatchable state for each idle state; And
And a message transmission unit configured to transmit a message processed by the second transmission group processing unit to the web agent module. The method of claim 5,
The second sending group processing unit,
A second process management unit that monitors an idle process that is not currently operating, and changes a pending message status value of the actual sending message database to be processed for each idle process; And
A message sending system comprising a plurality of second processing units configured to change processable data among the message data of the actual sending message database to a final sendable state, and to perform message processing for the plurality of sending groups in parallel . The method according to claim 1,
The sending module transfers information about a message to a communication company in order to send a message processed and delivered by the exchange module. delete delete delete The method according to claim 1,
The database is:
A message sending system for matching and storing the second and third message information with a key value unique to the message sending request. The method according to claim 1,
The message thread unit,
For each individual message data received from the first message queue, the third task is first executed, the first task is executed, and then the second task is executed. Receiving a message sending request from a client by a receiving unit of the exchange module;
Performing, by the exchange module, pre-processing for message transmission using a message queue before storing information on the message in a database;
Storing information about the message in the database;
Extracting, by the sending module, a message from an actual sending message database storing a message for which message transmission is requested by a client; And
And transmitting, by the sending module, information about the message extracted from the actual sending message database to a web agent module,
The step of extracting the message,
Updating a message that can be processed in the actual transmission message database to a state in which it can be sent;
Generating a processing process for each of a plurality of dispatch groups for the message that can be processed; And
Including the step of performing message processing for the plurality of sending groups in parallel,
The step of executing the pre-processing is:
Receiving message data included in the message transmission request from the receiving unit and storing it in a first message queue of the exchange module;
Receiving, by the message threading unit of the exchange module, message data from the first message queue, extracting information about the message from the message data, and transmitting it to the sending module; And
Receiving information on the extracted message from the message thread unit and storing it in a second message queue of the exchange module,
Storing information about the message in the database comprises:
Receiving, by the message storage thread unit of the exchange module, information about the message from the second message queue and storing it in the database,
The step of extracting information about the message and transferring it to the sending module includes:
Extracting, by the message threading unit, a calling number of a sender sending a message from the message data, a receiving number of a recipient who receives the message, and message contents constituting the message; And
And transmitting, by the message threading unit, first message information including the extracted source number, destination number, and message content to the sending module,
Storing in the second message queue of the exchange module includes:
Transmitting, by the message threading unit, second message information including message content extracted from message data to the second message queue,
Storing information about the message in the database comprises:
Storing the second message information received from the second message queue in the database by the message storage thread unit; And
And storing, by the message threading unit, third message information including a source number and a destination number extracted from the message data in the database,
A first task of delivering the first message information to the sending module, a second task of delivering the second message information to the second message queue, and a third task of delivering the third message information to the database are independent of each other. How to send a message. The method of claim 13,
Storing the message created by the client in a temporary transmission message database in a state of waiting for transmission; And
And extracting the message requested to be sent by the client from the temporary sending message database and storing it in the actual sending message database. In a computer-readable recording medium,
A recording medium in which a program for executing the message sending method according to claim 13 or 14 by a computer is recorded.

Images