KR20130050202A - Push server and mobile unit - Google Patents

Abstract

PURPOSE: A push server and a terminal thereof are provided to offer a push service for enabling a user to effectively execute a push application by reducing packet signaling with a keep alive messenger. CONSTITUTION: A reception unit(210) receives a push message from an application server. The push message requests the push of a message in an originating terminal. The application server supplies a push service to the originating terminal executed in a push application. A generation unit(230) generates a short text message including the telephone number of a reception terminal and the name of the push application, and the push message. A transmission unit(250) transmits the short message to an SMS(Short Message Service) server. [Reference numerals] (200) Push server; (210) Reception unit; (230) Generation unit; (250) Transmission unit

Description

Push server and terminal {PUSH SERVER AND MOBILE UNIT}

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a push server and a terminal, and relates to a push application technology for providing a push service to notify an application user of a notification message or an event.

A push application mainly installed in a smartphone is an application that provides a push service to notify an application user of a notification message or an event. For example, the push application refers to an application such as KakaoTalk, Skype, and Nate-on-Talk.

Such a push application establishes a Transmission Control Protocol / Internet Protocol (TCP / IP) connection with an application server to receive push messages from the application server. In detail, when a push message to be transmitted to the terminal is generated, the application server transmits the push message to the terminal through a TCP / IP connection that is continuously maintained.

Therefore, the terminal continuously transmits a keep alive message to the application server in order to increase the push message reception rate of the push application to maintain the TCP / IP connection. That is, when the terminal transmits a keep-alive message to the application server, the TCP / IP connection is maintained between the terminal and the application server through the application server responds with a confirmation message.

At this time, if the terminal periodically transmits the keep-alive message, the terminal attempts to wirelessly connect to the network by changing the wireless connection state from the idle state to the connected state. The terminal periodically sends a keep-alive message, which varies from application to application, for example, once every 10 minutes.

As such, the transmission period of the keep-alive message is the same as the number of attempts to connect wirelessly. Was found to be approximately 75 times / hr. In the case of the Skype application, the iPhone was confirmed 30 times and the Android phone 93 times. In the case of the MBCmini application, the iPhone was confirmed 3 times and the Android phone was 285 times.

In a crowded area due to frequent wireless access attempts caused by this particular push application, packet signaling increases rapidly, causing severe network load. For example, in the vicinity of Gangnam station, packet signaling increased by 1,160% in 2011 to 2.15 million in 2011, compared to 1.13 million in 2010.

Therefore, frequent wireless access attempts are a serious problem causing network load.

In addition, when a push message is received, the push application pops up only a partial content of the push message on the screen. Then, the user recognizes that the push message has arrived and executes the push application to check the entire contents of the push message.

Therefore, a process of searching the terminal screen is needed to find a push application to be executed by the user.

An object of the present invention is to provide a push server and a terminal for reducing packet signaling due to a keep alive message and providing a push service for a user to easily execute a push application.

According to an aspect of the present invention, a push server is a receiving unit for receiving a push message for requesting a push of a message requested by the originating terminal from an application server, wherein the application server provides a push service to the originating terminal on which the push application is executed. ; A generator configured to generate a short message including the push message, a name of the push application, and a phone number of a called terminal; And a transmitter for requesting a short message service server to transmit the short message to the called terminal .

In this case, the push message includes the telephone number of the called terminal transmitted by the calling terminal.

The generation unit may include the name of the push application in a header portion of the short message or the name of the push application in a tag portion of the short message.

In addition, the application server is a plurality of application servers for controlling different compatible push applications,

The push server further includes an application DB for storing application information compatible with each other,

The generation unit may check the name of one or more push applications that are compatible with the push application operated by the application server transmitting the push message from the application DB and add the names of the one or more push applications to the short message. .

In addition, among the names of one or more push applications included in the short message, the names of the push applications executed in the called terminal may be different push applications although they are mutually compatible with the names of the push applications executed in the calling terminal.

According to another feature of the present invention, a terminal is a terminal for transmitting a message to a called party through a push application, the storage unit storing a push application for providing a push service in conjunction with an application server; And an execution unit for calling and executing a push application from the storage unit and executing a call application from the storage unit and requesting the application server to transmit the generated message by including the called party's telephone number in the message generated through the push application. Include.

At this time, the push application is linked with the terminal address book,

The execution unit may check the telephone number of the called party of the message generated by the push application from the terminal address book and include it in the generated message.

According to another feature of the present invention, the terminal is a terminal that receives a message from a caller through a push application, and executes a push application in which an execution command is input, the push application providing a push service in association with an application server. part; And receiving a short message including the push message from the push server, the push server receiving a push message requesting a message push of the sender from the application server, and selecting a name of a push application included in the short message. When clicked, a short message client for inputting an execution command of a push application corresponding to a name of the push application to the execution unit.

The display device may further include a display unit configured to output a short message in which the name of the push application is displayed in a message header or a short message in which the name of the push application is displayed in a message tag.

In addition, the short message client searches for whether a push application corresponding to the name of the push application clicked by the user exists, and if present, transmits the execution command, and if it does not exist, outputs a not executable notification to the screen.

In addition, when the execution command is input, the execution unit executes one push application from a plurality of different push applications,

The short message client outputs an execution command corresponding to the name of the push application clicked by the user among the names of one or more push applications included in the short message to the execution unit.

According to the embodiment of the present invention, since the PUSH message is transmitted in the form of a short message (SMS) used in a mobile communication network, there is no need to continuously connect the radio. In other words, it does not use TCP / IP connection and transmits only when there is a message. Therefore, it does not induce a separate network signaling so that no load occurs.

In addition, in the short message, a name of a push application to be driven is displayed, and when such a name is clicked, the corresponding push application is immediately executed and communication is possible.

1 is a diagram illustrating a network configuration according to an embodiment of the present invention.
2 is a network configuration diagram according to another embodiment of the present invention.
3 is a block diagram showing the configuration of a push server according to an embodiment of the present invention.
4 is a block diagram illustrating a configuration of a push server according to another exemplary embodiment of the present invention.
5 is a block diagram showing the configuration of a calling terminal according to an embodiment of the present invention.
6 is a block diagram showing the configuration of a called terminal according to an embodiment of the present invention.
7 and 8 are views showing the configuration of a short message according to an embodiment of the present invention.
9 is a flowchart illustrating the operation of a called terminal according to an embodiment of the present invention.
10 is a flowchart illustrating a push message delivery process according to an embodiment of the present invention.
11 is a flowchart illustrating a push message delivery process according to another embodiment of the present invention.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

Throughout the specification, when an element is referred to as "comprising ", it means that it can include other elements as well, without excluding other elements unless specifically stated otherwise.

Also, the terms " part, "" module," and " module ", etc. in the specification mean a unit for processing at least one function or operation and may be implemented by hardware or software or a combination of hardware and software have.

Hereinafter, a push server and a terminal according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

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

Referring to FIG. 1, an application server 100 and a push server 200, and a push server 200 and a short message service (hereinafter, referred to as SMS) server 300 are dedicated networks (not shown) or It is connected to each other via a network (not shown).

In addition, the application server 100 is connected to the calling terminal 400 and the called terminal 500. The destination terminal 500 receives a push message from the SMS server 300 that the originating terminal 400 requests transmission through the push application 401.

Here, the application server 100 controls the push applications 401 and 501 respectively installed in the calling terminal 400 and the called terminal 500, and may be, for example, a KakaoTalk application server or a skype application server. . In this case, the push applications 401 and 501 are the same applications.

Here, the push applications 401 and 501 are applications that use a push service to inform an application user of any notification message or event.

The application server 100 manages subscriber information of the push applications 401 and 501, and may manage phone numbers of terminals for each subscriber. For example, when the calling terminal 400 establishes a TCP / IP (Transmission Control Protocol / Internet Protocol) connection with the application server 100, the application server 100 uses the subscriber information to establish a telephone number of the calling terminal 400. You can check.

The push server 200 receives a push message requesting a push of a message transmitted from the originating terminal 400 from the application server 100. The push message is generated as a short message and transmitted to the SMS server 300.

In this case, the push message includes the telephone number of the called terminal 500 transmitted by the calling terminal 400. In addition, the application server 100 may further include a phone number of the calling terminal 400 recorded.

The SMS server 300 is a system in which a communication provider transmits a text message for a subscriber, and transmits a short message to the called terminal 500 at the request of the push server 200.

The calling terminal 400 and the called terminal 500 are terminals in which the push applications 401 and 501 which operate in conjunction with the application server 100 are installed, and a smart phone, a tablet PC, and the like are provided. Can be.

In this case, the push server 200 includes the name of the push application in the short message, and when the user of the called terminal 500 clicks the name of the push application included in the short message, the push application 501 is executed. Then, the push applications 401 and 501 of the calling terminal 400 and the called terminal 500 are connected to the application server 100 to communicate with each other.

2 is a diagram illustrating a network configuration according to another embodiment of the present invention, and descriptions of the same components as those of FIG. 1 will be omitted.

Referring to FIG. 2, unlike the configuration of FIG. 1, the push server 200 may control each application server 100, that is, the application server A 101 and the application server B 103, which control a plurality of compatible push applications. ).

Here, two compatible push applications are illustrated as two examples, but may be more than this.

At this time, the calling terminal 400 is provided with a push application A (401) controlled by the application server A (101). The destination terminal 500 is provided with a push application A 501 controlled by the application server A 101 and a push application B 503 controlled by the application server B 103. In this case, the push application A 501 and the push application B 503 are applications that are compatible with each other.

Accordingly, the push server 200 includes the name of the push application A executed in the calling terminal 400 and the name of the push application B compatible with the push application A in the short message. Then, the user of the called terminal 500 may select one of the name of the push application A or the name of the push application B.

In this case, the calling terminal 400 may be connected to the application server A 101 and the called terminal 500 may be connected to the application server B 103.

3 is a block diagram showing the configuration of a push server according to an embodiment of the present invention, which is a block diagram showing the configuration of the push server 200 of FIG.

Referring to FIG. 3, the push server 200 includes a receiver 210, a generator 230, and a transmitter 250, and the functions of each component are as follows.

The receiver 210 receives a push message for requesting a push of a message requested by the originating terminal 400 from the application server 100 interoperating with the push application executed in the originating terminal 400.

In this case, the message that the originating terminal 400 requests transmission includes the Mobile Station International ISDN Number (MSISDN) of the called terminal 500, and the MSISDN is composed of a country code, a network code, and a directory number.

The generation unit 230 generates a short message including a push message received from the application server 100, a name of a push application controlled by the application server 100, and a phone number of the called terminal 500. Here, the telephone number of the called terminal 500 is included in the push message received from the application server 100.

At this time, the generation unit 230 may include the name of the push application in the header portion of the short message, or may include the name of the push application in the tag portion of the short message.

Here, the short message may be a CP-DATA message transmitted when there is an SMS message to be sent to the user in the core network (not shown). At this time, the CP-DATA message has a CP_User Data Element, which includes a message to be transmitted to the actual user and the name of the push application in the CP_User Data Element.

The transmitter 250 requests the SMS server 300 to transmit the short message generated by the generator 230 to the called terminal 500. Then, the SMS server 300 transmits the short message to the telephone number of the called terminal 500 contained in the short message.

4 is a block diagram showing the configuration of a push server according to another embodiment of the present invention, which is a block diagram showing the configuration of the push server 200 of FIG.

Referring to FIG. 4, the push server 200 includes a receiver 210, a generator 230, a transmitter 250, and an application DB 270. The functions of each component are as follows.

In this case, the receiver 210, the generator 230, and the transmitter 250 are the same as those of FIG. 3. However, the generation unit 230 checks from the application DB 270 the names of one or more push applications that are compatible with the push application operated by the application server 100 that transmitted the push message. The name of one or more push applications is added to the short message.

Here, the application DB 270 stores application information compatible with each other.

5 is a block diagram showing the configuration of a calling terminal according to an embodiment of the present invention.

Referring to FIG. 5, the calling terminal 400 includes a storage unit 410, an execution unit 430, and a communication unit 450.

Here, the storage unit 410 stores a push application 401 that provides a push service in cooperation with the application server 100.

When the execution command is input, the execution unit 430 calls and executes a push application from the storage unit 410, and transmits the message to the application server 100 by including the called party's telephone number in the message generated through the push application. request.

In this case, the push application is linked with the terminal address book, and the execution unit checks the telephone number of the called party of the message generated in the push application from the terminal address book and includes it in the generated message.

The communication unit 450 performs a TCP / IP connection with the application server 100 and transmits a message generated by the execution unit 430 to the application server 100.

6 is a block diagram showing a configuration of a called terminal according to an embodiment of the present invention, Figures 7 and 8 are views showing the configuration of a short message according to an embodiment of the present invention.

Referring to FIG. 6, the called terminal 500 includes a storage unit 510, an execution unit 520, a short message client 530, a display unit 540, an input unit 550, and a communication unit 4560.

Here, the storage unit 510 stores a push application. As described with reference to FIG. 2, the storage unit 510 may store one or more push applications that are compatible with each other.

The execution unit 520 loads and executes the push application to which the execution command is input from the storage unit 510. The software logic and data corresponding to the result of the executed push application are rendered and parsed to generate a display screen of the push application and output the generated display screen to the display unit 540.

In this case, the executed push application is the same as the push application 401 executed in the calling terminal 400 as described with reference to FIG. 1.

In addition, the executed push application may be another application that is compatible with the push application 401 executed in the calling terminal 400 as described with reference to FIG. 2.

The short message client 530 receives the short message from the push server 200 and outputs the short message to the display unit 540. When the user clicks on the name of the push application included in the short message, the execution command of the push application corresponding to the name of the push application is output to the execution unit 520.

In this case, the short message client 530 searches the storage unit 510 to determine whether there is a push application corresponding to the name of the push application clicked by the user, and if so, outputs an execution command. You can print it on the screen.

The display unit 540 outputs information according to the operation of the called terminal 500 on the screen, and for example, a liquid crystal display (LCD), which is currently commercialized, may be used.

The display unit 540 outputs a short message received by the short message client 530 on the screen, and the short message to be output may be configured as shown in FIGS. 7 and 8.

Referring to FIG. 7, the short message 600 may include a name of the push application and a message content 603 included in the message header 601.

Referring to FIG. 8, the short message 600 may include a name of the push application and a message content 603 included in the message tag 605.

The input unit 550 is a means for the user to select or input one name from among names of one or more push applications displayed in the short message. Various input means such as a touch pad, an optical pointing device, a keypad, and the like may be adopted.

The communication unit 4560 performs a TCP / IP connection with the application server 100 that controls the executed push application.

The operation of the called terminal 500 is the same as FIG. 9 is a flowchart illustrating the operation of a called terminal according to an embodiment of the present invention.

Referring to FIG. 9, when a short message is received (S101), the short message client 530 pops up a short message on the screen (S103).

When the user selects one of the one or more push application names included in the short message (S105), the storage unit 510 is searched to determine whether or not the terminal exists in the terminal (S107).

At this time, if installed, the short message client 530 transmits an execution command to the execution unit 520 (S109).

Then, the execution unit 520 executes the push application to which the execution command is input (S111), and outputs the push message included in the short message (S113).

In addition, if it is not installed, the short message client 530 pops up a notification that the execution is impossible (S115).

The process of delivering the push message based on the configuration described so far is as follows.

10 is a flowchart illustrating a push message delivery process according to an embodiment of the present invention, which is a flowchart according to the embodiment of FIG. 1.

Referring to FIG. 10, the calling terminal 400 executes a push application in which an execution command is input from a user (S201). The executed push application is connected to the corresponding application server 100 with a TCP / IP connection (S203).

Then, when a user writes a message to a specific called party and requests transmission, the execution unit 430 of the calling terminal 400 requests the application server 100 to include the MSISDN of the called party terminal in the message created by the user. (S205).

Then, the application server 100 transmits a push message requesting the push of the message requested to be transmitted from the originating terminal 400 to the push server 200 (S207).

The push server 200 generates a short message (SMS) including the name of the corresponding push application and the MSISDN of the called terminal 500 included in the push message (S209). The SMS server 300 requests a short message transmission (S211).

Then, the SMS server transmits the short message requested in step S211 to the called terminal 500 (S213).

The called terminal 500 pops up the received short message on the screen (S215). In this case, the short message displays the name of the push application executed in the calling terminal 500.

Then, when the called person clicks the push application name displayed in the short message (S217), the push application is executed (S219) and is connected to the application server 100 and TCP / IP (S221).

11 is a flowchart illustrating a push message delivery process according to another embodiment of the present invention, which is a flowchart according to the embodiment of FIG. 2.

Referring to FIG. 11, the calling terminal 400 executes a push application in which an execution command is input from a user (S301). The executed push application is connected to the corresponding application server A 101 by TCP / IP (S303).

Then, when a user writes a message to a specific called party and requests transmission, the execution unit 430 of the calling terminal 400 includes the MSISDN of the called party terminal in the message created by the user and requests the transmission to the application server A 101. (S305).

Then, the application server A (101) transmits a push message requesting the push of the message requested to be transmitted from the originating terminal 400 to the push server 200 (S307).

The push server 200 searches for one or more push applications compatible with the push application of the application server A 101 from the application DB 370 (S309).

Then, the push server 200 includes the name of the push application of the application server A (101), the name of one or more push applications retrieved in step S309, and the MSISDN of the called terminal 500 contained in the push message received in step S307. A short message SMS is generated (S311). The SMS server 300 requests a short message transmission (S313).

Then, the SMS server 300 transmits the short message requested in step S313 to the called terminal 500 (S315).

Then, the called terminal 500 pops up the received short message on the screen (S317). In this case, the short message includes a name of a push application executed in the calling terminal 400 and names of one or more push applications compatible with the push application A.

Then, when the called person clicks the name of the push application displayed in the short message (S319), the push application is executed (S321).

In this case, when the called party selects the push application B that is compatible with the push application A, there is a TCP / IP connection with the application server B 103 controlling the push application B (S323).

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

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, It belongs to the scope of right.

Claims (12)

A receiving unit for receiving a push message for requesting a push of a message requested by the calling terminal from an application server, wherein the application server provides a push service to a calling terminal on which a push application is executed;
A generator configured to generate a short message including the push message, a name of the push application, and a phone number of a called terminal; And
Sender for requesting the short message service server to send the short message to the called terminal
Push server comprising a. The method of claim 1,
The push message,
Push server including the telephone number of the called terminal transmitted by the calling terminal. The method of claim 1,
Wherein the generation unit comprises:
And a name of the push application in a header portion of the short message or a name of the push application in a tag portion of the short message. 4. The method according to any one of claims 1 to 3,
The application server is a plurality of application servers for controlling different compatible push applications, respectively,
The push server,
Further comprising an application DB for storing application information compatible with each other,
Wherein the generation unit comprises:
And a name of at least one push application compatible with the push application operated by the application server transmitting the push message from the application DB, and adding the name of the at least one push application to the short message. 5. The method of claim 4,
The push server name of the push application executed in the called terminal among the names of one or more push applications included in the short message are compatible with the name of the push application executed in the calling terminal but may be different push applications. A terminal for transmitting a message to a called party through a push application,
A storage unit for storing a push application that provides a push service in association with an application server; And
When the execution command is input, the execution unit for calling and executing the push application from the storage unit, and requesting the transmission of the generated message to the application server by including the telephone number of the called party in the message generated through the push application
. The method according to claim 6,
The push application is linked with the terminal address book,
The execution unit may include:
The terminal confirms the telephone number of the called party of the message generated by the push application from the terminal address book to include in the generated message. A terminal that receives a message from a sender through a push application,
An execution unit configured to execute a push application in which an execution command is input, wherein the push application provides a push service in association with an application server; And
Receives a short message including the push message from the push server, the push server receives a push message for requesting the push of the sender's message from the application server, and the user clicks on the name of the push application included in the short message. If so, the short message client for inputting the execution command of the push application corresponding to the name of the push application to the execution unit
. 9. The method of claim 8,
A display unit for outputting a short message in which the name of the push application is displayed in a message header or a short message in which the name of the push application is displayed in a message tag.
Terminal further comprising. 9. The method of claim 8,
The short message client,
Searching for the existence of the push application corresponding to the name of the push application clicked by the user, if present, delivers the execution command, and if not present, a terminal for outputting an execution disable notification on the screen. 11. The method according to any one of claims 8 to 10,
The execution unit may include:
When an execution command is input, one push application is executed among a plurality of different push applications,
The short message client,
The terminal outputs an execution command corresponding to the name of the push application clicked by the user among the names of one or more push applications included in the short message to the execution unit. The method of claim 11,
The push application executed according to the execution command of the short message client may be another application compatible with the push application installed in the caller's terminal.

Images