WO2013105809A1

WO2013105809A1 - Communication system and method for providing push service in said communication system

Info

Publication number: WO2013105809A1
Application number: PCT/KR2013/000241
Authority: WO
Inventors: 손중제
Original assignee: 삼성전자 주식회사
Priority date: 2012-01-13
Filing date: 2013-01-11
Publication date: 2013-07-18
Also published as: KR20130083667A

Abstract

The present invention relates to a communication system and to a method for providing a push service in said communication system. The method comprises: the steps of enabling a terminal to make a request for a registration to a push server upon installation of an application; enabling the terminal to transmit a registration confirmation to an application server upon receipt of a registration response from the push server; enabling the application server to make a request for a server registration to the push server; enabling the push server to make a request for a server registration to a public authentication server and receive a server registration response from the public authentication server; enabling the application server to make a request for push to the push server upon triggering of a message for a push server; and enabling the push server to transmit a push notification based on the push request to the terminal. Thus, traffic overload can be prevented and the data communication environment can be optimized through a network connection to a provider server.

Description

Communication system and method of providing push service in the communication system

The present invention relates to a communication system and a method for providing a push service in the communication system. The present invention provides a push service by easily changing a registration procedure between servers constituting the communication system to transmit a push message to a terminal. A method and a communication system for performing the same.

Two methods are typical for receiving data based on the Internet network. One is the pull based communication method, and the other is the push based communication method.

The pull based communication method is performed through the following process. First, the terminal connects to an application server provided by the data service provider. The terminal periodically performs keep alive with the application server. In this case, the terminal periodically transmits an uplink request for data retrieval to the application server. In the pull based communication method, there are many overloads according to connection management and uplink request.

Push based communication method is performed by the following process. First, the terminal registers with the application server provided by the data service provider. The terminal then connects to a push server connected to the application server. Next, the push server periodically transmits a push notification to the terminal. The terminal periodically performs connection management with the push server.

1 is a diagram illustrating a push service providing method according to the prior art.

Referring to FIG. 1, the application server transmits a server registration request to a push server in step 110 to provide a push service. The server registration request includes address information indicating the location of the push server and information on the providing application. In operation 115, the push server stores address information of the corresponding application server and information on the application. The push server then sends a server registration response to the application server. Here the push server carries the server authentication code together.

In step 120, the terminal installs an application from an app market or an operator server. In step 125, the terminal requests an application registration from the push server. In this case, the terminal transmits all or part of the application ID, the terminal ID, and the user ID to the push server. In operation 130, the push server transmits a registration response to the terminal along with the registration ID.

When the registration response is received from the push server, the terminal transmits a registration confirmation including the registration ID transmitted from the push server to the application server in step 135. The application server receiving this checks the registration ID in step 140 and completes the registration. The application server triggers a message due to application update or data change in step 145. In operation 150, the application server transmits a push request including a server authentication code, a registration ID, and data for triggering to the push server. In operation 160, the push server transmits a push notification including the application ID and data corresponding to the registration ID to the terminal.

In an open operating system (OS) such as Android, there is a push server that provides various push alarm services. The push server is configured by various push service providers. Apple, for example, offers a separate push server called Apple Push Notification Service (APNS). And in the case of goolge's Android, it provides a push server called C2DM (Android Cloud To Device Messaging Framework). In addition, a push server may be provided for each mobile service provider server providing a service to a terminal.

In the case of APSN, only an application used in a specific terminal provided by Apple can provide a push service. In the case of C2DM, the data that can be transmitted is limited, and the number of uses is limited. When a push server is configured for a specific mobile operator server, the push service is provided only to a specific application that is contracted with the corresponding operator server.

As there is a push server for each push service provider or mobile carrier, push messages provided to the terminal are also applied only to a specific application that is contracted with the corresponding push service provider. Therefore, it is necessary to develop a separate software for the application service provider to connect to the push server for each region or for each push service provider or mobile service provider. In addition, the push service of the corresponding application is provided only in the mobile communication provider in which the terminal is registered. That is, when the terminal roams to another country, there is a problem that the push service of the application is not provided.

Accordingly, the present invention proposes a mobile communication system and a method for providing an efficient push service when there are multiple push service providers in the mobile communication system.

In order to solve the above problems, in the present invention, a method of providing a push service of a communication system includes a process in which a terminal requests registration with a push server when an application is installed, and a registration response is received from the push server. Transmitting a registration confirmation to a server, the application server requesting a server registration to the push server, the push server requesting a server registration to a public authentication server, and receiving a server registration response from the public authentication server And when a message for a push service is triggered, the application server requesting a push to the push server, and the push server transmitting a push notification according to the push request to the terminal. It features.

To this end, the process of transmitting the registration confirmation in the present invention is characterized in that it comprises the step of transmitting the push server information stored in advance received from the operator server.

In the present invention, the process of requesting the server registration is characterized in that the application server comprises the step of transmitting a server authentication code received in advance from the public authentication server.

And in the present invention, the step of receiving the server registration response is characterized in that the push server comprises the step of transmitting the server authentication code received from the application server to the public authentication server.

In addition, in order to solve the above problems, the push service providing system according to the present invention requests a registration to a push server when an application is installed, and receives a registration response from the push server, and transmits a registration confirmation to an application server. Requesting server registration to the push server according to the registration confirmation, and if a message for a push service is triggered, transmitting the registration request to a public authentication server, the application server requesting push to the push server, and When a response according to the registration request is received from a public authentication server, the push server for transmitting a push notification to the terminal according to the push request received from the application server, and transmits a server authentication code to the application server, On server registration requests received from the push server Transmitting a different response is characterized by including the common authentication server.

To this end, in the present invention, the terminal is characterized in that it receives from the operator server to transmit previously stored push server information to the application server.

In the present invention, the application server is characterized in that for transmitting the server authentication code to the push server, when the server registration request.

In the present invention, the push server is characterized in that for transmitting the server authentication code received from the application server to the public authentication server.

According to the present invention, a push server may be configured for each mobile operator server providing a service to a terminal. Accordingly, the terminal may receive a push service while roaming to another mobile communication provider. In addition, by connecting the operator server and the network, it is possible to prevent traffic overload and optimize the data communication environment. In addition, since the procedures for using a push server of a mobile service provider or a push service provider are the same, it is possible to solve the difficulty of application development.

2 is a diagram illustrating a communication system configuration according to an embodiment of the present invention.

3 is a diagram illustrating a method for obtaining push server information according to an embodiment of the present invention.

4 is a diagram illustrating a push server authentication method according to an embodiment of the present invention.

5 is a diagram illustrating a push service providing method according to an embodiment of the present invention.

6 is a diagram showing a push service providing method according to another embodiment of the present invention.

7 is a diagram illustrating a push service providing method in a terminal according to an embodiment of the present invention.

'Push service' is a service in which the server automatically provides the data desired by the user. It is a webcasting service of two-way communication in which various information is provided according to an individual's interests by time zone and subject.

'Terminal' is an information processing apparatus that can process data transmitted and received from the outside, and includes a computer, a smartphone, a tablet PC, and the like.

Hereinafter, the operating principle of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, detailed descriptions of well-known functions or configurations will be omitted if it is determined that the detailed description of the present invention may unnecessarily obscure the subject matter of the present invention. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.

Referring to FIG. 2, the communication system includes a terminal, a push server, an application server, and a public authentication server. The terminal receives the push server information including the address indicating the location of the push server provided by the provider after the registration step or successful registration for use of the communication service provided by the mobile communication service provider.

The terminal installs the application, and requests the application registration and issuance of the registration ID installed in the corresponding push server through the received push server information. When the registration ID is issued from the push server, the terminal delivers the registration ID and the push server information issued to the application server.

When the push server receives a push request including a push message from the application server, the push server delivers it to the terminal. The push server issues a registration ID when a registration request is received from the terminal. When the push server receives a server registration request including a server authentication code from the application server, the push server transmits it to the public authentication server to confirm application authentication. Once the application server is authenticated, the push server receives the push request from the authenticated application server. The push server notifies the terminal of this.

An application server is a server managed by a provider that provides an application. The application server requests server registration from the public authentication server in advance. The application server stores the server authentication code received with the server registration response from the public authentication server. When the application server receives the push server information and the registration ID for the push server address from the terminal, the application server requests the server registration with the server authentication code to the push server. Next, when a push message for an application provided by the application provider is triggered, the application server sends a message requesting this to the push server.

The common authentication server issues a server authentication code, which is an authentication key for transmitting a push message corresponding to the application, for each application server. Here, the public authentication server may be operated through an application market operation server such as google, Apple, WAC (Wholesale Application Community).

The terminal requests application registration installed by the push server in step 210. In this case, the terminal transmits a registration request message including a user ID, an ID assigned to the terminal, and an installed application ID. And the push server issues a registration ID for this to the terminal. Next, the terminal transmits the push server address and the registration ID to the application server in step 220. In this case, the push server address is push server information received from the operator server by the terminal and is included in the information on the push server transmitting the push message.

Next, the registration between the application server and the push server is performed in step 230. That is, the application server requests a server registration from the push server using the push server address received from the terminal. Here, the application server transmits the server authentication code received in advance through the public authentication server. Then, the push server transmits the server authentication code received from the application server in step 240 to the public authentication server. And the push server confirms the application server authentication requesting registration through the public authentication server.

3 is a diagram illustrating a method of obtaining push server information according to an embodiment of the present invention.

Referring to FIG. 3, the terminal needs to know the address of the push server in order to request an application registration installed by the push server. To this end, the terminal receives information related to the push server from the operator server.

The operator server refers to a server managed by an operator providing a communication service to a terminal. Here, the operator server delivers the push server information providing the push service to the terminal. In this case, the push server information includes information on an address of a push server and information on an application for which a push message is provided by the corresponding push server.

The terminal receives the push server information from the operator server in step 310 after the terminal authentication procedure for using a communication service from the mobile operator. The terminal checks the address of the corresponding push server using the push server information received from the operator in step 320. The terminal then requests registration and issuance of a registration ID for receiving a push message corresponding to the application to the confirmed push server. The push server then issues a registration ID of the terminal and delivers it to the terminal.

Referring to FIG. 4, in the present invention, the push server and the application server do not register and authenticate the application, but are performed between the application server and the public authentication server.

The common authentication server registers an application provided by an application server managed by an application provider, and issues a server authentication code, which is an authentication key for transmitting a push message corresponding to the corresponding application, for each application server. Here, the public authentication server may be operated through an application market operation server such as google, Apple, WAC (Wholesale Application Community).

The application server requests the application registration provided by the application server to the public authentication server in step 410. The public authentication server then issues a server authentication code, which is an authentication key for the application, and sends it to the application server.

Referring to FIG. 5, in step 510, the application server requests server registration with a public authentication server. The public authentication server then transmits a server registration response to the application server in step 515. At this time, the public authentication server authenticates the application server and transmits a server authentication code for transmitting a push message.

Next, the terminal installs the application. At this time, the terminal receives the push server information for transmitting a push message for the application from the operator server. At this time, the push server information includes information on the address of the push server.

The terminal stores the push server information received in step 520. The terminal requests registration with the push server of the address verified through the push server information received in step 525. Here, the terminal delivers the terminal ID, the user ID, and the installed application ID to the push server. The push server checks this in step 530 and transmits a registration response to the terminal. At this time, the push server issues a registration ID and delivers it to the terminal.

Upon receiving the registration response, the terminal transmits a registration confirmation message to the application server in step 535. The registration confirmation message includes the push server information including the registration ID received from the push server and the address of the push server. The application server receiving this is registered in step 540.

Next, the application server requests a server registration to the push server in step 545. At this time, the application server transmits the server authentication code received from the public authentication server together to the push server. In operation 550, the push server transmits a server registration request including a server authentication code received from the application server to the public authentication server. The public authentication server checks the server authentication code received from the push server in step 560 and transmits a response to the push server.

The application server triggers a message according to the application update or data change in step 565. In operation 570, the application server transmits a push request to the push server. At this time, the application server transmits the server authentication code received from the common authentication server, the registration ID received from the terminal and the data to push. In operation 575, the push server checks the registration ID to identify the corresponding terminal, and notifies the terminal of the push message including the application ID and data to be pushed to the checked terminal according to the received push request.

6 is a diagram illustrating a push service providing method according to another embodiment of the present invention.

Referring to FIG. 6, when the push server is changed through roaming or the like, the operator server transmits the push server information changed to the terminal to the terminal. Here, push server 1 is a push server that delivers a push message before roaming, and push server 2 represents a push server changed by roaming.

In step 610, the terminal stores the changed push server information from the operator server. In step 615, the terminal requests registration with the push server 1. At this time, the terminal transmits the push server information including the user ID, the terminal ID and the push server address received from the operator server. Then push server 1 requests registration confirmation to push server 2 in step 620. Here, the push server 1 transmits a user ID and a device ID together.

In response to this, the push server 2 transmits a registration confirmation response to the push server 1 in step 625. The ID of the applications provided by the push server 2, the registration ID, and the ID of the application server registered on the push server 2 are transmitted together in the registration confirmation response.

The push server 1 transmits a registration response received from the push server 2 to the terminal in step 630. At this time, the push server 1 transmits the registration ID received from the push server 2 to the terminal. In step 635, the terminal receives the registration confirmation message to the application server. The registration confirmation message includes the registration ID sent from push server 2 and the push server information for the address of push server 2.

The application server triggers a push message according to the application change or data update in step 640. The application server then sends a push request to push server 2 in step 645. At this time, the application server transmits the server authentication code, registration ID, and data to be pushed together. Upon receiving this, the push server 2 notifies the terminal of the push message for the corresponding application in step 650. Here, the push server 2 transmits the application ID and the data to be pushed together to the terminal.

Referring to FIG. 7, in step 710, the terminal requests subscription and authentication for a mobile service provider to use a communication service. In operation 720, the terminal receives and stores push server information from the operator server. At this time, the push server information includes the address of the push server, and the operator server knows all of the addresses for each push server.

Next, the terminal requests registration with a push server in step 730. At this time, the terminal transmits the user ID using the terminal, the ID assigned to the terminal, and the address of the push server transmitted from the operator server together with the registration request.

In step 740, the terminal receives the registration ID from the push server. In operation 750, the terminal transmits a registration confirmation including the registration ID to the application server. At this time, the terminal transmits the address of the push server with registration confirmation. Next, the terminal receives a push message from the push server in step 760.

Through such processes, registration between the application server and the push server is managed through a common authentication server, so the push server does not need to register for each application server providing the application. In addition, when roaming by the operator server by the movement of the terminal, it is not necessary to download a new application, it is only necessary to change the address of the push server to notify the push message for the application.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by those equivalent to the scope of the claims.

Claims

In the push service providing method of the communication system,

The terminal, when the application is installed, the process of requesting registration with the push server,

When the registration response is received from the push server, the terminal transmits a registration confirmation to the application server;

The application server requesting server registration to the push server;

Requesting server registration from a public authentication server and receiving a server registration response from the public authentication server;

When a message for a push service is triggered, the application server requests a push to the push server;

The push server provides a push service comprising the step of transmitting a push notification according to the push request to the terminal.
The process of claim 1, wherein the registration confirmation is transmitted.

The terminal comprises a step of transmitting a push server information stored in advance received from the operator server.
The process of claim 1, wherein the requesting server registration is performed.

The application server is a push service providing method comprising the step of transmitting a server authentication code received in advance from the public authentication server.
4. The process of claim 3, wherein receiving the server registration response is

The push server provides a push service providing method comprising the step of transmitting the server authentication code received from the application server to the public authentication server.
The method of claim 2, wherein the push server information is

Push service providing method characterized in that the information on the address of the push server.
The process of claim 2, wherein the registration confirmation is transmitted.

The terminal further comprises the step of transmitting a registration ID received from the push server.
When the application is installed, request a registration to the push server, and if a registration response is received from the push server, the terminal for transmitting a registration confirmation to the application server,

The application server requesting a server registration to the push server according to the registration confirmation, and requesting push to the push server when a message for a push service is triggered;

The push server transmits the registration request to a public authentication server, and transmits a push notification to the terminal according to the push request received from the application server when a response according to the registration request is received from the public authentication server;

And a public authentication server which transmits a server authentication code to the application server and transmits a response according to a server registration request received from the push server.
The method of claim 7, wherein the terminal is

Push service providing system, characterized in that for receiving from the operator server to transmit previously stored push server information to the application server.
The method of claim 7, wherein the application server

And a server authentication code to the push server when a server registration request is made.
The push server of claim 9, wherein the push server comprises:

Push service providing system, characterized in that for transmitting the server authentication code received from the application server to the public authentication server.
The method of claim 8, wherein the push server information is

Push service providing system, characterized in that the information about the address of the push server.
The method of claim 8, wherein the terminal

And a registration ID received from the push server to the application server.