KR102134552B1 - System and method for transmitting message capable of seperate accounting - Google Patents

Abstract

Disclosed are a message sending system, a method, and a recording medium which are capable of separately charging a message capable of obtaining separate charging data for each user group belonging to an agent without generating individual agent module information for a plurality of clients belonging to the same agent. According to an embodiment of the present invention, the message sending system capable of separate charging comprises: a database including a message table and a separate charging table; an exchange module configured to receive a message including a separate charging ID and store the message in the message table; a sending module configured to receive the message from the exchange module and transmit the message to a communication company; and a separate charging module configured to extract message data including the separate charging ID from the message table and store the message data in the separate charging table.

Description

System and method for sending message that can be separated and billed{SYSTEM AND METHOD FOR TRANSMITTING MESSAGE CAPABLE OF SEPERATE ACCOUNTING}

The present invention relates to a message sending system and a message sending method, and more specifically, to a message sending system and method capable of separating billing that can generate segregated billing data for each group of users of the agent for a plurality of clients belonging to the agent. It is about.

A corporate messaging service has been provided to transmit text messages to a mobile phone of a user that a business customer trades using a wireless communication network of a mobile communication company. These corporate messaging services cannot be aggregated by subdividing the number of message transmissions for each user group (for example, department) belonging to a corporate customer, making it difficult to grasp the current status of message transmission service usage for each user group. Agent module information must be generated for each user group in order to understand the number of messages sent per user group. In this case, it is difficult to manage since multiple member IDs must be generated to generate individual agent module information even though they are the same corporate customer. This may lead to an increase in the cost of using the message sending service, such as inefficient management points. On the other hand, the corporate messaging service needs to send a large number of advertisement messages, messages for providing information or messages for authentication, to users of corporate customers. As such, when a large number of messages are simultaneously sent, a bottleneck may occur in a server providing a corporate messaging service, and message transmission may be delayed frequently.

The present invention provides a separate billable message sending system and method, recording medium capable of obtaining separate billing data for each user group belonging to the agent, without generating individual agent module information for multiple clients belonging to the same agent. It is to provide.

In addition, the present invention is to provide a message sending system and method, a recording medium capable of quickly sending a message by minimizing a delay in sending a message by preventing a bottleneck even when a large number of message sending requests are received from a client.

A separate billable message sending system according to an embodiment of the present invention includes a database including a message table and a separate billing table; An exchange module configured to receive a message including a separate charging ID and store the message in the message table; A sending module, configured to receive the message from the exchange module and transmit it to a communication company; And a separate billing module configured to extract message data including a separate billing ID from the message table and store it in the separate billing table.

The separation charging module includes: a message data monitoring unit configured to periodically check the message table to check message data that is successfully transmitted and has not generated separation charging data; And a separate billing data storage unit configured to store the message data extracted by the message data monitoring unit in the separate billing table including the separate billing ID.

The sending module includes: a transmission result processing unit configured to receive a message transmission result from the communication company and store the message transmission result in the message table; And a message transmission unit configured to extract a message to be transmitted to the communication company and transmit the extracted message to the communication company.

The exchange module may be configured to perform pre-processing for sending a message using a message queue before storing information about the message in the database. The exchange module includes a receiving unit for receiving a request to send a message from a client; A first message queue for receiving and storing message data included in the message sending request from the receiving unit; A message thread unit receiving message data from the first message queue, extracting information about the message from the message data, and transmitting the message data to the sending module; A second message queue for receiving and storing information about the extracted message from the message thread unit; And a message storage thread unit that receives information about a message from the second message queue and stores it in the database.

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

The message thread unit: delivers second message information including message content extracted from message data to the second message queue, and the message storage thread unit: transmits 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 calling number and a receiving number extracted from message data in the database, and the database: a key unique to the message sending request for the second and third message information It can be stored by matching the value.

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

The method for sending a separate billable message according to an embodiment of the present invention includes: receiving, by an exchange module, a message including a separate charging ID, and storing the message in a message table in a database; Receiving, by the sending module, the message from the exchange module and transmitting it to a communication company; And extracting message data including a separate billing ID from the message table by the separate billing module and storing the message data in the separate billing table of the database. The method for sending a separate billable message according to an embodiment of the present invention further includes, by the exchange module, performing pre-processing for sending a message using a message queue before storing information about the message in the database. can do. The step of executing the pre-processing includes: receiving, by the receiving unit, a message sending request from a client; Receiving and storing message data included in the message sending request from the receiving unit by a first message queue; Receiving, by the message thread unit, message data from the first message queue, extracting information about the message from the message data and transmitting the message data to the sending module; Receiving and storing information about the extracted message from the message thread unit by a second message queue; And receiving, by the message storage thread unit, information about the message from the second message queue and storing the message in the database.

The step of storing in the separate billing table may include: checking, by the message data monitoring unit, the message table by periodically monitoring the message table to successfully transmit a message and generating no separate billing data; And storing, by the separate billing data storage unit, the message data extracted by the message data monitoring unit in the separate billing table including the separate billing ID.

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

According to an embodiment of the present invention, separate billing data can be obtained for each user group belonging to the agent without generating individual agent module information for a plurality of clients belonging to the same agent.

In addition, according to an embodiment of the present invention, even when a large number of message sending requests are received from a client, a message can be rapidly transmitted by reducing a bottleneck and minimizing delay in sending a message.

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

Other advantages and features of the present invention and methods for achieving them will be made clear by referring to embodiments described below 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, and only the present embodiments allow the disclosure of the present invention to be complete, and the common knowledge in the technical field to which the present invention pertains. It is provided to fully inform the holder of the scope of the invention, and the invention is only defined by the scope of the claims.

If not defined, all terms (including technical or scientific terms) used herein have the same meaning as generally accepted by universal technology in the prior art to which this invention belongs. Terms defined by general dictionaries can be interpreted as having the same meaning as meaning in the text of the present application and/or related descriptions, and are not conceptualized or over-formally interpreted, even if not explicitly defined herein. Will not.

The terminology used herein is for describing the embodiments and is not intended to limit the present invention. In the present specification, the singular form also includes the plural form unless otherwise specified in the phrase. As used herein,'includes' and/or various conjugations of this verb, such as'includes','includes','includes','includes', etc. The steps, operations and/or elements do not exclude the presence or addition of one or more other compositions, ingredients, components, steps, operations and/or elements. The term'and/or' used herein refers to each of the listed configurations or various combinations thereof.

Meanwhile, terms such as'~ unit' and'~ module' used throughout the specification may mean a unit that processes at least one function or operation. For example, it can mean a hardware component such as software, FPGA or ASIC. However,'~unit','~module', etc. are not limited to software or hardware. The'~unit' and'~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','~module' are components such as software components, object-oriented software components, class components and task components, processes, functions, and attributes. Fields, 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','~module' are combined with a smaller number of components and'~unit','~module', or additional components and'~unit', It can be further separated into'~modules'.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. 1 is a view for explaining a process for sending a message to the user 50 by receiving a message sending request from the client 20, the message sending system 10 according to an embodiment of the present invention. The client 20 may be a lower customer belonging to the agent 30.

Referring to FIG. 1, the message sending system 10 may include an exchange module 100, a sending module 200, a separate charging module 300 and a database 400. The exchange module 100, the sending module 200, and the separate charging module 300 are computer devices including a processing device for processing data and a memory for storing data, and can process data according to a pre-installed computer program. have.

The database 400 may include a message table 410 and a separate billing table 420. The database 400 is a storage device for storing message information, and may include, for example, an HDD, an SSD, but is not limited thereto.

When the client 20 corresponding to the lower customer of the agent 30 requests to send a message to the agent 30, the agent 30 checks the information of the client 20 requesting the sending of the message and the corresponding separate billing ID Check to request the sending of a message to the message transmission system 10, including the corresponding separated billing ID.

The separated billing ID may be set in units of a lower customer group of the agent 30 (eg, a department belonging to the agent), but is not limited thereto. The separated billing ID may be used without being particularly limited as long as it can identify the client 20 in units of user groups belonging to the agent 30.

The exchange module 100 stores the message data received from the agent 30 in the message table 410 of the database 400 and transmits the message data to the sending module 200. The sending module 200 transmits the message received from the exchange module 100 to the communication company (relay company) 40.

The message sent by the sending module 200 may be transmitted through the communication company 40 and received by the user 50. The sending module 200 receives the transmission result from the communication company 40 and stores it in the message table 410.

The segregation billing module 300 periodically monitors the message table 410 to complete transmission (message transmission is successful), and the segregation billing (CDR) table includes the segregation billing ID of message data that is not generated in CDR (Call Data Raw). (420).

The segregation billing module 300 stores information on the total number of message transmissions and the raw data (Raw data) for which message transmission is successfully requested by sending a message from the agent 30, and each segregation billing ID through the segregation billing ID field. Each message can be stored separately.

2 is a block diagram showing a message sending system according to an embodiment of the present invention in more detail. 1 and 2, the exchange module 100 may perform a function of storing a message in the database 400 and delivering a message to the sending module 200. The exchange module 100 may include a data processing unit 110 and a first message transmission unit 120.

The data processing unit 110 may include a message data storage unit 111 that stores message data in the database 400. The message data storage unit 111 may store the message data received from the agent 30 in the message table 410 including a separate charging ID.

The first message transmission unit 120 is a first message data receiving unit 121 that receives a message from the agent 30, and a first message that stores the received message in the message queue of the sending module 200 (Message Queue) It may include a data transmission unit 122.

The sending module 200 may transmit the message received from the exchange module 100 to the communication company 40 and receive and store the transmission result from the communication company 40. The sending module 200 may include a transmission result processing unit 210 and a message transmission unit 220.

The transmission result processing unit 210 is a transmission result receiving unit 211 for receiving a message transmission result from the communication company 40, and a transmission result storage unit 212 for storing the transmission result received from the communication company 40 in the message table 410 ).

The second message transmission unit 220 may extract a message to be transmitted to the communication company 40 and transmit the extracted message to the communication company 40. The second message transmission unit 220 may include a message data extraction unit 221 for extracting a message to be transmitted from the message queue, and a second message data transmission unit 222 for transmitting the extracted message to the communication company 40. .

The separate charging module 300 may include a separate charging data processing unit 310 that stores data in the message table 410 in a separate charging (CDR) table 420. The separated billing data processing unit 310 may include a message data monitoring unit 311 and a separate billing data storage unit 312.

The message data monitoring unit 311 monitors the message table 410 and extracts data having a successful message transmission and not generating a CDR. The separated charging data storage unit 312 may store the message data extracted by the message data monitoring unit 311 in the CDR table 420 including the separated charging ID.

According to the above-described embodiment of the present invention, it is possible to generate charging data for each separated charging ID by using the separated charging ID in units of user groups belonging to the agent. Accordingly, it is possible to generate separate billing data for each user group without individually creating an agent module for each user group based on the separate billing ID.

According to an embodiment of the present invention, it is possible to view billing statistics for a plurality of separate billing IDs under one corporate member ID, and according to the user's group corresponding to the separate billing ID and the billing history according to the entire message sent by the customer (agent). You can check the billing history.

According to an embodiment of the present invention, for example, after contracting with a messaging system in the name of a customer company, the customer company provides a message sending UI to a lower customer, and when sending a message from the lower customer, sets the information of the lower customer to a separate billing ID Therefore, it is possible to generate separate billing data in the unit of the sub-customer (user group) of the agent based on the separate billing ID, and it is possible to process the billing to the lower customer based on the separate billing data.

3 is a flowchart of a method for sending a separate billable message according to an embodiment of the present invention. 4 is a flowchart illustrating a process performed in an exchange module constituting a separate billable message sending system according to an embodiment of the present invention.

3 and 4, the exchange module 100 receives a request for sending a message from the client 20 from the agent 30 (S110), and extracts message data received from the agent 30 (S111). . When there is a message received from the agent 30, the exchange module 100 determines whether the data includes a separate charging ID.

If the separation module ID is not included in the message received from the agent 30, the exchange module 100 stores the message information in the message table without storing the separation fee ID (S113, S114), and the sending module ( Message message is stored in the message queue of 200) (S115).

If, when the message received from the agent 30 includes a separate charging ID, the exchange module 100 stores the data including the separate charging ID in the message table 410 of the database 400 (S120) ), message data is stored in the message queue of the sending module 200 (S130).

5 is a flowchart illustrating a process performed by a sending module constituting a message sending system according to an embodiment of the present invention. 3 and 5, the sending module 200 extracts the message data to be transmitted from the message queue (S210), and transmits the message data to the carrier if there is a message (S211, S220). When the transmission result is received from the carrier, the sending module 200 stores the received transmission result in the message table 410 of the database 400 (S230, S240).

6 is a flowchart illustrating a process performed in a separate charging module constituting a message sending system according to an embodiment of the present invention. Referring to FIGS. 3 and 6, the separation charging module 300 may monitor the message table 410 and extract data having a successful message transmission and not generating a CDR (S310).

If there is a message in which CDR data has not yet been generated after the successful message transmission, the separation charging module 300 determines whether the data includes a separate charging ID, and if the data does not contain the separated charging ID, stores the separated charging ID. Instead, the message transmission result is stored in the separate billing table 410 (S311, S312, S313), and the CDR generation complete state is stored in the message table (S330).

If the message containing the separate charging ID among the messages that have not yet generated CDR data after the successful transmission of the message, the separate charging module 300 stores the data including the separated charging ID in the separate charging table 410 (S320) ), the CDR generation complete state is stored in the message table (S330).

According to the above-described embodiment of the present invention, it is possible to generate charging data for each separated charging ID by using the separated charging ID in units of user groups belonging to the agent. Accordingly, it is possible to generate separate billing data for each user group without individually creating an agent module for each user group based on the separate billing ID.

In addition, according to an embodiment of the present invention, it is possible to reduce the management cost by viewing the billing statistics for a plurality of separate billing IDs under one corporate member ID, and the billing history of the entire message sent by the customer (agent), You can check the billing history for each user group corresponding to the separate billing ID.

According to an embodiment of the present invention, for example, after contracting with a messaging system in the name of a customer company, the customer company provides a message sending UI to a lower customer, and when sending a message from the lower customer, sets the information of the lower customer to a separate billing ID Therefore, it is possible to generate separate billing data in the unit of the sub-customer (user group) of the agent based on the separate billing ID, and it is possible to process the billing to the lower customer based on the separate billing data.

7 is a block diagram illustrating the configuration of a message sending system according to another embodiment of the present invention. Referring to FIG. 7, the exchange module 100 may include a receiving unit 130, a first message queue 140, a message thread unit 150, a second message queue 160, and a message storage thread unit 170. Can.

The receiving unit 130 may receive a message sending request from the agent 30. The first message queue 140 may receive and store message data included in the message sending request from the receiving unit 130. The message thread unit 150 may receive message data from the first message queue 140, extract information about the message from the message data, and deliver the message data to the sending module 200. The second message queue 160 may receive and store information about the extracted message from the message thread unit 150. The message storage thread unit 170 may receive information about a message from the second message queue 160 and store it in the database 400.

8 is a block diagram illustrating the configuration of the exchange module 100 constituting the message sending system according to the embodiment of FIG. 7. Referring to FIG. 8, in the exchange module 100, the receiving unit 130 may include a message sending request receiving unit 131 and a first message queue message data storage unit 132.

The message sending request receiving unit 131 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 132 may extract message data included in the message sending request and input the message data into the first message queue 140.

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

In the exchange module 100, the message thread unit 150 includes a message information extraction unit 154, a sending module delivery unit 152, a second message queue message information storage unit 153, and a database storage unit 151. It can contain.

The message thread unit 150 may receive message data from the first message queue 140, extract information about the message from the message data, and transmit the message data to the sending module 200.

According to an embodiment of the present invention, the message information extraction unit 154 may receive message data from the first message queue 140 and extract information about the message. In addition, the sending module delivery unit 152, the second message queue message information storage unit 153, and the database storage unit 151 respectively store information about the message extracted by the message information extraction unit 154. The delivery module 200, the second message queue 160 and the database 400 may be transmitted and stored.

Specifically, in the message thread unit 150, the message information extracting unit 154 may extract from the message data, the sender's calling number to send a message, the recipient's receiving number to receive the message, and message content constituting the message. . Then, in the message thread unit 150, the sending module delivery unit 152 may deliver the first message information including the extracted calling number, receiving number, and message content to the sending module 200.

Further, in the message thread unit 150, the second message queue message information storage unit 153 may transmit second message information including message content extracted from message data to the second message queue 160. .

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

In the message storage thread unit 170, the second message queue message information receiving unit 171 may retrieve second message information from the second message queue 160. In addition, the database post-processing storage unit 172 may store second message information retrieved from the second message queue 160 in the database 400.

Further, in the message thread unit 150, the database storage unit 151 may transmit and store third message information including the calling number and the receiving number extracted from the message data to the database 400.

That is, according to an embodiment of the present invention, the message sending system stores information about a message in the database 400 in the process of performing a process for sending a client's message to a user via a carrier, but for sending a message Processing and processing for storing information on the message in the database 400 are separated from each other and executed independently.

As a result, it is possible to send a message smoothly and quickly even if a large number of message sending requests are received from the client by minimizing the sending delay caused in the process of storing information about the message in the database when sending the message.

7 and 8, the database 400 receives and stores second message information including message content from the message storage thread unit 170 of the exchange module 100, and stores the exchange module ( The third message information including the calling number and the receiving number from the message thread unit 150 of 100) may be received and stored.

In this way, the process of storing the second message information including the message content and the process of storing the third message information including the calling number and the receiving number are executed separately from each other in a separate thread. As mentioned, the process of transmitting the first message information to the sending module 200 is also executed separately.

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

In other words, according to this embodiment, the message sending request received from the client is uniquely assigned a key value for each message sending request, and the database 400 includes the message storage thread unit 170 and the message thread unit In the process of receiving and storing the second message information and the third message information independently from the 150, 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. Can.

According to an embodiment of the present invention, the message thread unit 150 transmits first message information to the sending module 200 and second message information to the second message queue 160. The second task and the third task of transmitting third message information to the database 400 may be executed independently of each other.

In addition, the message thread unit 150 first executes the third operation for each individual message data received from the first message queue 140, stores the calling number and the receiving number in the database 400, Execute the first operation to transmit the sender number, the reception number and the content of the message necessary for sending the message to the sending module 200, and then execute the second operation to execute the second operation to the second message queue 160 and the message Message contents may be stored in the database 400 through the storage thread unit 170.

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 160 in the exchange module 100 and storing it in the database 400 The number of units 170 of the message thread unit 150 allocated to the task of receiving message data from the first message queue 140, extracting information about the message, and transmitting the message data to the sending module 200 It can be set to 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 on a message in the database 400 are separately executed, and the message is sent in the processing order and resource allocation. By performing processing on the database storage prior to processing, even if a large number of messages are simultaneously sent, messages can be sent quickly and smoothly by minimizing bottlenecks and delays.

Referring back to FIG. 7, the sending module 200 may include a third message queue 230 and a sending unit 240.

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

9 is a block diagram illustrating the configuration of the sending module 200 constituting the message sending system according to the embodiment of FIG. 7. Referring to FIG. 9, the sending unit 240 may include a third message queue message receiving unit 241 and a message sending unit 242.

The third message queue message receiver 241 may retrieve first message information from the third message queue 230. In addition, the message sending unit 242 may process the first message information retrieved from the third message queue 230 to be transmitted to the communication company 40 to send a message to the user.

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

Referring to FIG. 10, the message sending system including the database 400, the exchange module 100, and the sending module 200 includes the steps of receiving the message sending request from the client by the switching module 100 ( S11), the exchange module 100 stores the message data included in the message sending request in the first message queue 140 (S12), and the exchange module 100 sends the message data from the first message queue 140. Retrieving message data, extracting information about the message from the message data, and transmitting it to the sending module 200 (S15), and the sending module 200 receives information about the received message from the third message queue Step (S21) of storing in (230), step (S22) of transmitting information about a message received from the exchange module 100 by the sending module 200 to the communication company 40 (S22), and the exchange module 100 Storing the information on the extracted message in the second message queue 160 (S16), and the exchange module 100 retrieves the information on the message from the second message queue 160 to the database It may include the step (S17) of storing in (400).

According to an embodiment of the present invention, in the message sending method, the message thread unit 150 receives message data from the first message queue 140 and extracts information about the message from the message data (S13). It may include. The step of extracting information about the message (S13) may include extracting from the message data, the sender's calling number to send the message, the recipient's receiving number to receive the message, and message content constituting the message.

In step S15 of transmitting information about the message to the sending module 200, the step of delivering first message information including the extracted calling number, receiving number, and message content to the sending module 200 It can contain.

In the step of storing information on the extracted message in the second message queue 160 (S16), the second message information including the message content extracted by the message thread unit 150 from the message data is the second message. The method may include transmitting to a queue 160 and storing the second message information received from the second message queue 160 by the message storage thread unit 170 in the database 400.

According to an embodiment of the present invention, in the message sending method, the message thread unit 150 stores the third message information including the calling number and the receiving number extracted from the message data in the database 400 ( S14) may be further included.

Further, storing the third message information in the database 400 (S14), transmitting the first message information to the sending module 200 (S15), and the second message information to the second The step of storing in the message queue 160 (S16) may be executed independently of each other by the message thread unit 150.

Furthermore, the message thread unit 150 first executes the step (S14) of storing the third message information in the database 400 for each individual message data received from the first message queue 140, and then, The step (S15) of transmitting the first message information to the sending module 200 may be executed, and then the step (S16) of storing the second message information in the second message queue 160 may be executed. .

The method according to the above-described embodiment of the present invention may be manufactured as a program for execution on a computer and stored in a computer-readable recording medium. The computer-readable recording medium includes all kinds of storage devices for storing data that can be read by a computer system. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, 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 in combination with a computer.

The present invention has been described through the above embodiments, but the above embodiments are only for explaining the spirit of the present invention and are not limited thereto. Those skilled in the art will understand that various modifications can be made to the above-described embodiments. The scope of the invention is defined only through the interpretation of the appended claims.

10: Message sending system
20: Client
30: Agent
40: carrier
50: user
100: exchange module
110: data processing unit
111: message data storage
120: first message transmission unit
121: first message data receiving unit
122: first message data transmission unit
200: shipping module
210: transmission result processing unit
211: transmission result receiving unit
212: transmission result storage unit
220: message transmission unit
221: message data extraction unit
222: second message data transmission unit
300: separate charging module
310: separate billing data processing unit
311: message data monitoring unit
312: separate billing data storage
400: database
410: message table
420: separate charging table

Claims (11)

A database including a message table and a separate billing table;
An exchange module configured to receive a message including a separate charging ID and store the message in the message table;
A sending module, configured to receive the message from the exchange module and transmit it to a communication company; And
And a separating billing module configured to extract message data including a separating billing ID from the message table and store it in the separating billing table,
The exchange module is configured to perform pre-processing for sending a message using a message queue before storing information about the message in the database,
The exchange module,
A receiving unit that receives a message sending request from a client;
A first message queue for receiving and storing message data included in the message sending request from the receiving unit;
A message thread unit receiving message data from the first message queue, extracting information about the message from the message data, and transmitting the message data to the sending module;
A second message queue for receiving and storing information about the extracted message from the message thread unit; And
And a message storage thread unit for receiving information about a message from the second message queue and storing the message in the database. The method according to claim 1,
The separation charging module,
A message data monitoring unit configured to periodically check the message table and check message data for which message transmission was successful and no separate billing data was generated; And
And a separate billing data storage unit configured to store the message data extracted by the message data monitoring unit in the separate billing table including the separate billing ID. The method according to claim 1,
The sending module,
A transmission result processing unit configured to receive a message transmission result from the communication company and store the message transmission result in the message table; And
And a message transmission unit configured to extract a message to be transmitted to the communication company and to transmit the extracted message to the communication company. delete The method according to claim 1,
The message thread section:
From the message data, the caller's calling number to send the message, the recipient's receiving number to receive the message, and the contents of the message constituting the message are extracted,
A separate billable message sending system that delivers the first message information including the extracted calling number, receiving number and message content to the sending module. The method according to claim 5,
The message thread section:
The second message information including the message content extracted from the message data is delivered to the second message queue,
The message storage thread part:
Separate billable message sending system that stores the second message information received from the second message queue in the database. The method according to claim 6,
The message thread section:
The third message information including the calling number and the receiving number extracted from the message data is stored in the database,
The database is:
A separate billable message sending system for storing the second and third message information by matching a key value unique to the message sending request. The method according to claim 6,
The message thread portion,
The first operation of delivering the first message information to the sending module, the second operation of delivering the second message information to the second message queue, and the third operation of delivering the third message information to the database are executed independently of each other, ;
A separate billable message sending system that executes the third operation first for each individual message data received from the first message queue, then executes the first operation, and then executes the second operation. Receiving, by the exchange module, a message including a separate billing ID, and storing the message in a message table in a database;
Receiving, by the sending module, the message from the exchange module and transmitting it to a communication company; And
And extracting message data including the separated billing ID from the message table by the separate billing module and storing the message data in the separate billing table of the database.
Further comprising, by the exchange module, performing pre-processing for sending a message using a message queue before storing information about the message in the database,
Step of executing the pre-processing,
Receiving, by the receiving unit, a message sending request from a client;
Receiving and storing message data included in the message sending request from the receiving unit by a first message queue;
Receiving, by the message thread unit, message data from the first message queue, extracting information about the message from the message data and transmitting the message data to the sending module;
Receiving and storing information about the extracted message from the message thread unit by a second message queue; And
And receiving, by the message storage thread unit, information about the message from the second message queue and storing it in the database. The method according to claim 9,
The step of storing in the separate billing table,
Checking, by the message data monitoring unit, the message table by periodically monitoring the message table to successfully transmit a message and not generating separate charging data; And
And storing, by the separate billing data storage unit, the message data extracted by the message data monitoring unit in the separate billing table including the separate billing ID. In a computer-readable recording medium,
A recording medium in which a program for executing a method for sending a detachable billable message according to claim 9 or 10 with a computer is recorded.

Images