KR20240030226A - Distributed processing technology based corporate IMessage mass sending method and system - Google Patents

Abstract

The present invention relates to a method for mass sending corporate iMessages based on distributed processing technology. The present invention includes the steps of the client server inputting message data including the recipient, message body, client identifier, message purpose, and whether to send it first; the client server requesting transmission of message data to a relay designated by the service providing server; A step where the providing server receives a request to send the message data through an API, a step where the service providing server verifies the received message data, and the service providing server requests the client server to send the message data and determines whether the verification is successful. It includes a step of responding to and a step of the service providing server storing the verified message data. Through mass sending of corporate iMessages based on distributed processing technology, a corporate messaging sending environment can be provided based on standardization.

Description

{Distributed processing technology based corporate IMessage mass sending method and system}

The present invention relates to a method and system for mass sending corporate iMessages based on distributed processing technology. In particular, it provides convenience and common services to users by providing a messenger service that provides high capacity and high quality based on common message standards. This is about a method and system for mass sending corporate iMessages based on distributed processing technology.

In the case of conventional SMS, LMS, and MMS (hereinafter referred to as xMS), they correspond to the standard protocol for text messages, but have the disadvantage of low capacity for sending according to the protocol specified in 1992. In order to compensate for this, the RCS protocol that supports high capacity and high definition was established, but as of 2022, it is only supported on Android and some mobile communication device terminals, and has the disadvantage of not being supported by Apple's iPhone.

Separately from this, various messengers such as KakaoTalk, Line, WhatsApp, and WeChat, which are push apps, provide services in the form of services, but if the user does not install them, there are restrictions on the use of the services.

Lastly, in the case of iMessage, although it is similar to RCS, it does not provide corporate services and has the disadvantage of being only provided on Apple's mobile communication devices.

Prior art includes Domestic Patent No. 10-2156298 (message sending system and method using message queue and database post-processing), but pre-processing for sending uses message queue before storing information about the message in the database. It only discloses a method of executing and transmitting information about the message to the telecommunication company.

The problem that the present invention aims to solve is to provide a technology for providing rich content messages based on Apple's iMessage, and to provide a corporate iMessage based on distributed processing technology that enables mass sending of corporate iMessages based on common message standards. The goal is to provide mass shipping methods and systems.

In addition, the problem to be solved by the present invention is to quickly process a large amount of iMessages and provide a mass corporate iMessage based on distributed processing technology that can utilize the integrated corporate messaging service of mobile communication devices including RCS and the present invention in the corporate messaging market. The purpose is to provide a shipping method and system.

The method of mass sending corporate iMessages based on distributed processing technology according to an embodiment of the present invention includes the steps of the client server inputting message data including the recipient, message body, client identifier, message purpose, and whether to send priority, and the client server A step of requesting message data to be sent to a relay designated by the service providing server, a step of the service providing server receiving the message data sending request through an API, and a step of the service providing server verifying the received message data. It includes a step of the service providing server responding to a message data transmission request to the client server and whether verification is successful, and a step of the service providing server storing the verified message data.

According to the present invention, it is possible to provide a faster corporate messaging sending environment through mass sending of standardized corporate iMessages based on distributed processing technology using iMessage, Apple's Rich Contents Message standard.

In addition, corporate messaging can provide sending by purpose by distributing the sending method into information and advertising.

In addition, by providing statistics and results of sending details, additional responses (detour sending or follow-up response due to sending failure) can be made depending on whether the message has arrived.

Figure 1 is a diagram illustrating a corporate iMessage mass sending system based on distributed processing technology according to an embodiment of the present invention.
Figure 2 is a configuration diagram of a service providing server according to an embodiment of the present invention.
Figure 3 is a diagram illustrating a method for mass sending corporate iMessages based on distributed processing technology according to an embodiment of the present invention.

Specific structural or functional descriptions of the embodiments according to the concept of the present invention disclosed in this specification are merely illustrative for the purpose of explaining the embodiments according to the concept of the present invention, and the embodiments according to the concept of the present invention are It may be implemented in various forms and is not limited to the embodiments described herein.

Since the embodiments according to the concept of the present invention can make various changes and have various forms, the embodiments will be illustrated in the drawings and described in detail in this specification. However, this is not intended to limit the embodiments according to the concept of the present invention to specific disclosed forms, and includes all changes, equivalents, or substitutes included in the spirit and technical scope of the present invention.

The terms used in this specification are merely used to describe specific embodiments and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, terms such as “comprise” or “have” are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in this specification, but are not intended to indicate the presence of one or more other features. It should be understood that this does not exclude in advance the possibility of the existence or addition of elements, numbers, steps, operations, components, parts, or combinations thereof.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings attached to this specification.

Figure 1 is a diagram illustrating a corporate iMessage mass sending system 10 based on distributed processing technology according to an embodiment of the present invention.

Referring to Figure 1, the corporate iMessage mass sending system 10 based on distributed processing technology of the present invention is composed of a client server 100, a service providing server 200, and a user terminal 200.

The client server 100 can receive message data including the recipient, message body, client identifier, message purpose, and priority delivery in accordance with the provided API standards. The client server 100 may request transmission of the received message data to a relay designated by the service providing server 200.

The service providing server 200 can receive each message data transmission request sent from the client server 100 through an API endpoint, and can proceed with verification of the received message data. The service providing server 200 can simultaneously send message data that has completed verification to the user terminal and has been converted to suit the transmission protocol through a thread operation, and can respond to the client server 100 as to whether the message data transmission was successful. .

The user terminal 300 may receive message data sent from the service providing server 200 and transmit the sending processing status to the service providing server 200. At this time, the following methods can be used to track the iMessage sending processing status, but are not necessarily limited to this. First, the DB used in the Mac OS message app is searched to specify the GUID and sequence number of the currently requested message data based on the recipient (chat ID), sending time, and message content. Afterwards, the status is checked at regular intervals until the message transmission task is completed, and after completion, the message transmission status can be updated based on whether transmission was successful or not. At this time, if the message sending operation fails, fallback can be done to another message protocol, and the other message protocol can be at least one of xMS, RCS, and Notification Talk.

Figure 2 is a configuration diagram of the service providing server 200 according to an embodiment of the present invention.

Referring to Figure 2, the service providing server 200 of the present invention is composed of an API endpoint unit 210, a verification unit 220, a distributed processing unit 230, and a DB storage unit 240.

The API endpoint unit 210 can receive each message data transmission request sent from the client server 100 through the API endpoint. The message data can be received by a load-balanced service providing server through the API endpoint unit.

The verification unit 220 can verify the message data transmission request received from the API endpoint unit 210. The verification unit 220 can check whether the sending number of the message data is normal and analyze abnormal messages (spam) through relay. The verification unit 220 consists of a caller ID verification module 221, an abnormal message analysis module 222, and a data transmission module 223.

The calling number confirmation module 221 analyzes whether there are any abnormalities in the calling number among the message data received by the API endpoint unit 210, checks whether it is normal, and performs verification work. The calling number verification module 221 uses the main number authentication policy, which includes the mobile phone number (11 digits) used as the calling number, main numbers such as 1544, 1644, etc. (8 digits), and 02, General numbers (9 to 11 digits) such as 070 can be used for representative number authentication purposes, but are not necessarily limited to this. Additionally, an email address can also be used as a main number.

The abnormal message analysis module 222 may analyze abnormal messages (spam) among the message data received by the API endpoint unit 210 and perform verification work.

The data transmission module 220 may respond by transmitting to the client server 100 whether the message data transmission request was successful and whether the verification performed by the sender number confirmation module 221 and the abnormal message analysis module 222 was successful. there is.

The distributed processing unit 230 may receive message data from the verification unit 220 and send the message data to the user terminal 300. The distributed processing unit 230 consists of a distributed processing waiting module 231, a distribution module 232, a sending waiting module 233, a conversion module 234, a sending module 235, and a sending completion receiving module 236.

The distributed processing standby module 231 can receive and store message data that has been verified by the verification unit 230 and successfully verified.

The distribution module 232 can distribute the message data stored in the distributed processing standby module 231 through a distribution technology according to the amount of the message body, and can distribute it according to the purpose of the message and whether or not to send it first. At this time, in order to configure an efficient message sending agent, multiple accounts can be created on a single device to distribute the transmitted message data, but it is not necessarily limited to this.

The transmission waiting module 233 can sequentially distribute and store the message data distributed by the distribution module 232. In addition, the transmission waiting module 233 can transmit message data, status, and logs being processed to the DB storage unit 240.

The conversion module 234 can convert the message data distributed and stored in the transmission waiting module 233 to suit each transmission protocol.

The sending module 235 can send each message data converted by the conversion module 234 to the user terminal 300. The sending module 235 can work with a thread to simultaneously send together distributed message data. If the sending module 235 runs as a thread, a large number of messages can be sent simultaneously and quickly. In one embodiment, in the case of existing iMessage, it was possible to transmit message data from one device to one device, but using the technology of the present invention, message data distributed together can be collected and transmitted to one device using a virtualized account. You can send a large amount of message data at the same time. Additionally, the sending module 235 can transmit the transmission/reception status of the sent message to the DB storage by referring to the protocol response and the log of the message application DB.

The transmission completion reception module 236 may receive the transmission processing status of the message data after the user terminal 300 receives the message data sent by the transmission module 235.

The DB storage unit 240 can receive and store message data, status, and logs being processed transmitted from the transmission waiting module 233. The DB storage unit 240 can transmit the transmission and reception status of the sent message to the DB storage unit by referring to the protocol response sent by the sending module 235 and the log of the message application DB. In addition, the DB storage unit 240 can store the sending processing status of the message data received by the sending completion receiving module 236 from the user terminal 300, and can manage the log by synchronizing the status of each message. .

Additionally, the DB storage unit 240 can make additional responses depending on whether the message has arrived based on statistics and results of the transmission details of the stored message data. At this time, the additional response may be at least one of bypass delivery or follow-up response following delivery failure, but is not necessarily limited thereto.

Figure 3 is a diagram illustrating a method for mass sending corporate iMessages based on distributed processing technology according to an embodiment of the present invention.

Referring to Figure 3, the client server 100 of the present invention inputs message data including the recipient, message body, client identifier, message purpose, and whether to send priority (S101). The client server 100 requests transmission of message data to the relay designated by the service providing server 200 (S103). The service providing server 200 receives the message data transmission request through the API (S105) and verifies the received message data (S107). When the verification task is completed, the service providing server 200 responds to the client server 100 with a message data transmission request and whether verification is successful (S109), and the service providing server stores the verified message data (S111).

Afterwards, the service providing server 200 distributes the stored message data according to the amount of the message body, message purpose, and priority sending (S113), and the service providing server 200 distributes the distributed message data and status and Save the log (S115). At this time, the service providing server 200 converts the distributed message data to fit the transmission protocol (S117) and sends the converted message data to the user terminal 300 (S119). The user terminal 300 completes sending the message data (S121) and transmits the sending processing status to the service providing server 200 (S123). The service providing server 200 stores and updates the sending processing status received from the user terminal 300 (S125), and the service providing server 200 responds to the client server 100 regarding whether message data was successfully sent. (S127).

Although the invention has been described with reference to the embodiments shown in the drawings, this is merely illustrative, and those skilled in the art will understand that various modifications and other equivalent embodiments are possible therefrom. Therefore, the true technical protection scope of the present invention should be determined by the technical spirit of the attached registration claims.

10; Corporate iMessage mass sending system based on distributed processing technology
100; client server 200; Service provision server
300; User terminal 210; API endpoint section
220; Verification Department 221; Caller ID verification module
222; Abnormal message analysis module 223; data transmission module
230; Distributed processing unit 231; Distributed processing standby module
232; Distribution module 233; Delivery standby module
234; conversion module 235; Shipping module
236; Delivery completion reception module 240; DB storage

Claims (5)

In the method of sending mass corporate iMessages based on distributed processing technology,
A client server inputting message data including the recipient, message body, client identifier, message purpose, and whether to send priority;
A step where the client server requests transmission of message data to a relay designated by the service providing server;
A service providing server receiving a request to send the message data through an API;
A service providing server performing verification of the received message data;
A step where the service providing server responds to a request to send message data to the client server and whether verification is successful or not; and
A corporate iMessage mass sending method based on distributed processing technology that includes the step of the service providing server storing verified message data.
According to paragraph 1,
A service providing server distributing the stored message data according to the amount of the message body, message purpose, and priority delivery; and
A method for mass sending corporate iMessages based on distributed processing technology, further comprising the step of the service providing server storing the distributed message data, status, and log.
According to paragraph 2,
A step where the service providing server converts message data to suit the transmission protocol; and
A corporate iMessage mass sending method based on distributed processing technology that further includes the step of the service providing server simultaneously sending converted message data to the user terminal through a thread operation.
According to paragraph 3,
A step where the user terminal completes sending message data and transmitting the sending processing status to the service providing server; and
A corporate iMessage mass sending method based on distributed processing technology, further comprising the step of the service providing server storing and updating the sending processing status received from the user terminal.
In a corporate iMessage mass sending system based on distributed processing technology,
A client server that inputs message data including the recipient, message body, client identifier, message purpose, and whether to send priority, and requests transmission of the message data to a relay designated by the service providing server;
Receives the message data transmission request sent by the client server through the API, verifies the received message data, stores the verified message data, and determines the amount of the message body, message purpose, and priority sending. It distributes according to the distribution, stores the distributed message data, status and log, converts the message data to suit the sending protocol, simultaneously sends the converted message data to the user terminal through thread work, and stores and updates the sending processing status. Service provision server; and
An enterprise-type iMessage mass sending system based on distributed processing technology that includes a user terminal that receives message data sent from the service providing server and transmits the sending processing status to the service providing server.