KR101527196B1 - Bi-directional service system for push message and Control method for the system - Google Patents

Abstract

Disclosed is a bidirectional push message service system for preventing meaningless retransmission and improving transmission reliability. The system comprises: a client having a messaging application installed therein; a push server for receiving a push message from a transmission-side client, generating a unique message ID to the push message, and transmitting the push message including the message ID to a reception-side client; a control server for receiving a reception logging of the reception-side client including the message ID, and requesting retransmission of the push message to the push server in accordance with predetermined retransmission policy in case that reception is dropped by referring to the reception logging.

Description

[0001] The present invention relates to a bi-directional push message service system and a control method,

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a bi-directional push message service system and a control method thereof, and more particularly to a bi-directional push message service technique for preventing a meaningful retransmission and improving transmission reliability.

The way to send and receive messages between mobile phones can be roughly classified into a pull method and a push method. The pull method is a method in which the mobile receives information from the information provider from time to time. In the case of a smart phone, for example, the data is updated by polling in the foreground or background. On the other hand, the push method is a method of forcibly transmitting information from a publisher or a server to a mobile device, and maintains a continuous connection state with the push support service in the operating system, thereby transmitting a message from the server side to the smartphone.

As a push message service system, for example, Korean Patent Registration No. 1165746, by authenticating and managing a plurality of push message services each provided by a plurality of providers, various push message services provided by the respective providers can be provided regardless of the operating system It is very easy to manage and extend the message service by integrating it. It identifies and manages heterogeneous devices based on the user ID. By using the service provided by the provider, the message is transmitted to the push server based on various operating systems It is possible to transmit a simultaneous message even when a single user has a plurality of user terminals having operating systems different from each other, thereby greatly enhancing the convenience of the user, and a service server that requests a push of a message performs multiple transmission, retransmission, and utilization of statistics by doing A push message service system is disclosed in which the service server itself secures a transmission guarantee rate and utilizes the message in various marketing to further increase the service utilization of the push message.

Also, Korean Patent Registration No. 1241365 discloses a content distribution system including a plurality of content providing servers for generating and transmitting push data; A specific operating system dedicated push service server for transmitting the push data to a user device installed with a specific operating system; And a first path for receiving the push data from the content providing server and transmitting the push data to the user device via the specific operating system dedicated push service server according to the operating system of the user device, And an integrated push service server for selectively performing any one of a second path for transmitting the service request to the user device without passing through the service server.

However, in the above patent, if the actual mobile or user device normally receives the push message from the push server, but the push server is mobile or user If the acknowledgment message is not received from the device, there is a problem that repeated retransmission is performed without meaning.

There is also a problem that there is an error in the push server itself, but there is no function of managing and monitoring the push server.

Also, there is a problem that the push message transmitted by the originating client may be broken and delivered to the receiving client, but this can not be confirmed at all.

Accordingly, it is an object of the present invention to provide a bi-directional push message service system and a control method that do not repeatedly transmit a message even if the push server does not receive acknowledgment from a client.

It is another object of the present invention to provide a bi-directional push message service system and a control method capable of managing and monitoring a push server against an error of the push server itself.

Another object of the present invention is to provide a bi-directional push message service system and a control method capable of retransmitting a push message by confirming whether a push message transmitted by an originating client is broken and delivered to a receiving client.

According to an aspect of the present invention, there is provided a communication system including a client having a messaging application installed therein; A push server for receiving a push message from an originating client, generating a unique message ID for the push message, and including the message ID in the push message to a receiving client; And a control server for receiving the reception log of the reception client including the message ID and requesting retransmission of the push message to the push server according to a preset retransmission policy when there is a reception missing by referring to the reception log A push-to-talk message service system is provided.

According to another aspect of the present invention, there is provided a communication system including a client having a messaging application installed therein; A push server for receiving a push message from an originating client, generating a unique message ID for the push message, and including the message ID in the push message to a receiving client; And a receiving module for receiving the receiving log of the receiving client including the message ID and the sending log of the sending client and the message ID including the message ID and the push message, And a control server for retransmitting the received push message according to the received push message.

According to another aspect of the present invention, there is provided a method comprising: receiving a push message from an originating client, generating and storing a message ID and sending the push message to the originating client; The originating client logging origination to the control server based on the message ID; The push server including the message ID in the push message and transmitting the push message to the receiving client; The receiving client logging in to the control server based on the message ID; And if the reception logging is not performed, determining that the control server is missing a reception and retransmitting the push message to the reception client according to a preset retransmission policy.

Advantageously, said missing omission is a result of a) the receiving client is powered off or in a non-communicable area, b) the messaging application installed on said receiving client has been deleted or not activated, or c) And a case where an error occurs in transmission of the push message to the client.

Preferably, the control server checks a keep-alive log time that the receiving client is last connected to the push server, and if the reception logging is not performed for a predetermined period of time or longer, If it is determined that the connection is established within the predetermined time, it can be determined that the connection corresponds to the step c).

Preferably, in accordance with the retransmission policy, the control server stops retransmission in the cases of a) and b), requests the push server to retransmit the push message in case of c), or requests the push server to retransmit the push message The message can be resent.

Preferably, in the origination logging, the originating client transmits the message ID, the origination time, the identification ID of the originating client, the identification ID of the receiving client, and the push message to the control server, The receiving client may transmit the message ID, the receiving time, the identification ID of the originating client, the identification ID of the receiving client, and the push message to the control server.

Advantageously, the originating client may not perform the origination logging if the message ID is not received from the push server.

Preferably, the control server checks the message ID stored in the push server, and if there is no message ID, the push server may determine that an internal error has occurred, including not storing the message ID .

Preferably, the control server compares the push message received at the origination logging with the push message received at the reception logging to determine whether the contents of the message match or not. When the control server determines that the message contents do not match, the control server determines that the message is broken, It may request to retransmit the message.

According to the above configuration, the push server performs only a push message transfer function, and the control server takes charge of omission due to the message ID, so that the push server does not repeatedly transmit the message even if the push server does not receive the acknowledgment from the client have.

In addition, if a push message is not received due to an error of the push server itself, the receiving client can receive the push message again through retransmission.

In addition, if the push client confirms whether the push message transmitted is broken and delivered to the receiving client, the push message can be retransmitted if the push message is broken.

1 is an exemplary diagram of a bi-directional push message service system of the present invention.
2 is a configuration diagram of a bi-directional push message service system of the present invention.
3 is a data flow diagram of a bi-directional push message control method of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will now be described in detail with reference to the accompanying drawings.

1 is an exemplary diagram of a bi-directional push message service system of the present invention.

The bi-directional push message service system comprises clients 100 and 110, a push server 300 and a control server 400, and is connected through a data network including the Internet and a public telephone network.

The client 100 or 110 may be a mobile device such as a smart phone, a smart terminal, or a tablet PC, and may be a device embedded in a mobile operating system and configured in a car, a home appliance, a home networking, a personal computer have.

Messaging applications 102 and 112 are installed in the clients 100 and 110. The messaging applications 102 and 112 request registration and authentication of the clients 100 and 110 to the push server 300, Transmits the created push message to the push server 300 in a predetermined format and performs reception logging notifying that the push message has been transmitted to the control server 400 or that the push message has been received .

The push server 300 registers and authenticates the clients 100 and 110 and sends a push message to the receiving client according to the originating client request.

The control server 400 receives and manages the outgoing and incoming logs from the clients 100 and 110, checks the status of the push messages, requests the push server 300 to retransmit the push messages according to the retransmission policy, Resend the push message.

The control server 400 may include a database 460 for storing information received at the time of transmission logging and reception logging.

2 is a configuration diagram of a bi-directional push message service system of the present invention.

The push server 300 includes a client registration unit 310, a client authentication unit 320, a message sending unit 330, and a message ID generating unit 340.

The client registration unit 310 performs a registration (subscription) procedure of the clients 100 and 110, and the client authentication unit 320 performs an authentication procedure.

For example, the client registration unit 310 receives an identification ID, e.g., a telephone number and a device ID, from the clients 100 and 110, and the client authentication unit 320 verifies the validity of the clients 100 and 110, For example, using a resident registration number and a telephone number, or using an I-PIN.

When the authentication is completed, the client registration unit 310 matches and stores the identification IDs of the clients 100 and 110.

The message sending unit 330 transmits the push message received from the clients 100 and 110 to the requesting party, manages the time stamp related to the sending and receiving of the message, and transmits the generated message to the clients 100 and 110, ID.

The message ID generating unit 340 generates a message ID that is unique to the push message, that is, a message ID that can identify the corresponding message when the push request message transmission request is received from the clients 100 and 110, ) And the push message.

There is no particular restriction on the structure of the message ID, but it is possible to use a combination of the character generated by the algorithm using the originating client ID and the server timestamp as keys and the time stamp itself.

The control server 400 includes an originating logging management unit 410, a reception logging management unit 420, a message state management unit 430, a retransmission management unit 440, and a setting unit 450.

The outbound logging management unit 410 receives and manages the outbound logging from the clients 100 and 110 and manages it. Here, the 'outgoing logging' is a record of a state in which the client 100 or 110 transmits a push message to the push server 300, and includes a message ID, a sending client ID, a receiving client ID, a message, do.

The reception logging management unit 420 receives and manages the reception logs from the clients 100 and 110, and manages the received logs. Herein, 'reception logging' is a record of a state in which the client 100 or 110 receives a push message from the push server 300, and includes a message ID, a sending client ID, a receiving client ID, a message, do.

The message state management unit 430 manages the state of a message, such as an internal error or a missing message, or a message content is broken.

The retransmission management unit 440 determines the status of the offline client that has not received the reception log and performs the operation according to the predetermined scheduling. In the case of the clients 100 and 110 located in the power off state or the communication disablement area, If the push server 300 fails, the push message is retransmitted.

The retransmission management unit 400 may be implemented as a daemon module that performs a retransmission algorithm, for example, and the scheduling related to the operation of the daemon module may be changed.

The setting unit 450 sets the operation of the control server 400. For example, when the retransmission management unit 440 checks the offline clients 100 and 110, the time stamp associated with transmission and reception of all the messages is pushed Whether to manage the server 300 separately or not.

Hereinafter, a control method in the bi-directional push message service system having the above configuration will be described with reference to FIGS. 2 and 3. FIG.

3 is a data flow diagram of a bi-directional push message control method of the present invention.

First, the registration and authentication processes of the clients 100 and 110 will be described.

The messaging application 102 installed in the client 100 transmits the identification ID of the client 100, such as the telephone number and the device ID, to the push server 300 to request registration.

In the case of the client 100 having no telephone number, only the device ID is transmitted. As the device ID, for example, an international mobile equipment identity (IMEI) may be used.

The client registration unit 310 of the push server 300 stores the identification ID and notifies that the registration is completed.

After the messaging application 102 installed in the client 100 receives the notification of the completion of the registration and then requests authentication, the client authentication unit 320 performs the authentication process. When the validity of the client 100 is confirmed, .

The authentication by the client authentication unit 320 may be performed using the resident registration number and the telephone number of the owner of the client 100 or using the I-PIN.

The registration and authentication process of the client 110 is also performed in the same manner as the client 100.

When the registration and authentication process is completed, the push message can be delivered to the other party. The client 100 can be regarded as a sender (hereinafter referred to as a 'originating client') and the client 110 as a receiver And transmits the push message.

When the originating client 100 creates a push message and sends it to the push server 300 together with the identification ID of the recipient client 110, the message ID generator 340 of the push server 300 responds to the received push message And the message sending unit 330 transmits the generated message ID, the identification ID of the originating client 100, and the push message to the receiving client 110 by referring to the identification ID of the receiving client 110 .

Here, the message ID may be formed by combining the character ID generated by the algorithm using the identification ID of the originating client 100 and the time stamp of the push server 300, and the time stamp itself as described above.

Then, the message sending unit 330 of the push server 300 delivers the generated message ID to the originating client 100.

The originating client 100 transmits the message ID, the origination time, the identification ID of the originating client 100, the identification ID of the recipient client 110, and the push message to the control server 400, Ali performs outgoing logging.

Here, if any of the information for the outgoing logging is missing, the outgoing client 100 does not perform outgoing logging to the control server 400.

The transmission log management unit 410 of the control server 400 stores and confirms the received information and checks the message ID stored in the push server 300 with reference to the received information. If there is no message ID, It is determined that an error has occurred because the message ID transmitted from the originating client 100 to the originating client 100 is not stored.

The reception client 110 receives the message ID, the identification ID of the originating client 100 and the push message from the push server 300 and transmits the message ID, the reception time, The identification ID, the identification ID of the receiving client 110, and the push message to the control server 400 to perform reception logging indicating that the push message has been received.

The reception logging management unit 420 of the control server 400 stores the received information and checks the received information.

Here, when the reception logging is not performed even after a certain period of time has elapsed even though it is determined that the transmission logging is normally performed by the transmission log management unit 410, the reception log management unit 420 determines that the reception is missed in the following cases do.

First, the power of the receiving client 110 is turned off or is located in a non-communicable area.

Second, the messaging application 112 installed in the receiving client 110 is deleted or not activated.

Third, there is a case where an error occurs in transmission of a push message from the push server 300 to the receiving client 110. [

The reception log management unit 420 confirms the keep-alive log time that the receiving client 110 is last connected to the push server 300, and if the reception logging is not performed for three minutes or more, It is determined to be the first or the second, whereas if it is confirmed that it is connected within the predetermined time, it is determined to be the third.

The reception logging management unit 420 notifies the retransmission management unit 440 of 'missing reception', and the retransmission management unit 440 performs an operation according to a preset retransmission policy.

For example, when it is determined that the 'reception missing' corresponds to the first and second cases, the retransmission management unit 440 may suspend the retransmission according to the retransmission policy. If it is determined that the push message corresponds to the third case, the retransmission management unit 440 transmits a message ID to the push server 300 according to the scheduling to request retransmission of the push message or retransmits the stored push message .

Accordingly, in the past, if the push server 300 does not receive the acknowledgment from the receiving client 110, the push server 300 repeatedly transmits the push message without repetition until the push server 300 receives the acknowledgment. However, Since the mobile station 300 retransmits only in response to a request from the control server 400, it can prevent the retransmission of unconditional messages.

Furthermore, by analyzing the cause of the reception confirmation failure in various ways, it is possible to surely retransmit when retransmission is necessary.

Meanwhile, the message state management unit 430 compares the push message received at the time of call logging with the push message received at the time of reception logging to determine whether the contents of the message match or not. If the message content does not match, the message state management unit 430 determines that the message is broken, Notify.

Similarly, in this case as well, the retransmission management unit 440 may request the push server 300 to retransmit the push message corresponding to the message ID.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. Accordingly, the scope of the present invention should not be construed as being limited to the embodiments described above, but should be construed in accordance with the following claims.

100, 110: Client
102, 112: messaging application
300: push server
400: control server

Claims (10)

delete delete The push server receiving a push message from an originating client, generating and storing a message ID and sending the message ID to the originating client;
The originating client logging origination to the control server based on the message ID;
The push server including the message ID in the push message and transmitting the push message to the receiving client;
The receiving client logging in to the control server based on the message ID; And
If the reception logging is not performed, determining that the control server is missing a reception and retransmitting the push message to the reception client according to a preset retransmission policy,
When the control server confirms the keep-alive log time that the receiving client is last connected to the push server, the control server determines that the received response is a first missing omission when the reception logging is not performed for a predetermined time or more, And if it is confirmed that the connection is made within the set time, it is determined that the second reception omission corresponds to the omission. The method of claim 3,
The method of claim 1, wherein the first missing message is a message that indicates that a) the receiving client is powered off or in an unreachable area, or b) the messaging application installed on the receiving client has been deleted or not activated,
Wherein the second missing reception is c) when an error occurs in transmission of the push message from the push server to the receiving client. delete The method of claim 4,
Wherein the control server, in accordance with the retransmission policy,
In the case of a) and b), retransmission is stopped,
Wherein the push message is requested to be retransmitted to the push server or the push message stored in the push server is retransmitted in case of c). The method of claim 3,
The originating client transmits the message ID, the origination time, the identification ID of the originating client, the identification ID of the receiving client, and the push message to the control server,
Wherein the receiving client transmits the message ID, the receiving time, the identification ID of the originating client, the identification ID of the receiving client, and the push message to the control server at the time of the reception logging. . The method of claim 3,
And does not perform the origination logging if the originating client does not receive the message ID from the push server. The method of claim 3,
Wherein the control server checks the message ID stored in the push server and determines that an internal error has occurred in the push server including not storing the message ID in the absence of the message ID. A method of controlling a push message. The method of claim 3,
The control server compares the push message received at the time of the origination logging with the push message received at the time of the reception logging to determine whether the contents of the message match or not, and if it does not match, the control server determines that the message is broken and retransmits the push message to the push server The method comprising the steps of:

Images