KR20120128021A - System and method for providing push service using routing based on id - Google Patents

Abstract

PURPOSE: A push service providing system using ID(Identification) based routing and method thereof are provided to effectively execute the ID based routing by issuing a token to a client using client ID. CONSTITUTION: A push service apparatus(300) allocates client ID to a client(400). The push service apparatus issues a token to the client using the allocated client ID. The push service apparatus transmits the push message and token received from the service providing apparatus to space between an interworking unit(310,330) and a control unit(320) according to an ID based routing table. The push service apparatus transmits the transmitted push message to the client corresponding to the client ID of the transmitted token. [Reference numerals] (100) Service provider; (310) SP interworking unit; (320) Control unit; (330) Client interworking unit; (340) Load dispersion unit; (400) Client

Description

System and method for providing push service using ID-based routing {SYSTEM AND METHOD FOR PROVIDING PUSH SERVICE USING ROUTING BASED ON ID}

The present invention relates to a push service providing system and method using ID-based routing, and more particularly, assigns a client ID to the client, issues a token to the client using the assigned client ID, and receives the received service from the service providing apparatus. By sending push messages and tokens along an ID-based routing path and sending push messages to clients corresponding to the delivered tokens, it is possible to reduce the number of internal messages queried through routers while decentralizing push service devices. A push service providing system and method using ID-based routing that can reduce message processing delay.

With the spread of smart phones and the emergence of various applications due to the smart phone environment, the use of wireless resources has increased significantly. In particular, there are always applications (Always-On) that are always connected to receive real-time push messages (or push notifications) from the network, such as IM (Instant Messaging), Web, and Widget services. It is increasing rapidly. Always-On type applications have a problem of causing excessive traffic and speeding up battery consumption because each is preparing to receive a push service while maintaining a connection with a service provider.

For this reason, conventionally, the service provider and the client are not directly connected, but the connection is maintained with the push server through a daemon built in the client, and the service provider pushes a push message or push notification. The central push server receives the data and sends it to the client.

1 is a view showing the configuration of a conventional push service providing system.

According to the related art, the gateway 20 and the career 30 are established between the plurality of service providers 10 and the plurality of terminals 40 so that an application program installed in the plurality of terminals 40 is connected to the service provider 10. It shows a structure in which the service provider 10 is connected by connecting to the career 30 and the gateway 20 without separately connecting.

The gateway 20 is a relay device for connecting with the plurality of service providers 10, and the career 30 is an apparatus for connecting with the plurality of terminals 40, and the increase of the service provider 10 and the terminal 40 is performed. It is an extensible structure.

However, in the prior art according to FIG. 1, a push server may be distributed and managed to manage the plurality of service providers 10 and the plurality of terminals 40. In distributed operation, an internal message between the gateway 20 and the career 30 may occur. Internal messages must be queried each time the router finds a routing path for each distributed server. In addition, since internal messages must go through a router that manages routing, processing delays for processing internal messages may occur at the router.

Therefore, if the push server that provides the push service is distributed, it is necessary to effectively reduce the internal messages generated by the server and reduce the message processing delay.

The present invention has been invented by the above necessity, assigns a client ID to a client, issues a token to the client using the assigned client ID, and pushes a message and a token received from the service providing apparatus to an ID-based routing path. By forwarding and sending push messages to clients corresponding to the tokens delivered, ID-based, which can reduce the number of internal messages queried through the router and reduce the delay in processing messages due to the router while decentralizing push service devices. An object of the present invention is to provide a push service providing system and method using routing.

To this end, the system according to the first aspect of the present invention includes a service providing apparatus for receiving a token from the client and transmitting the received token and the push message to send a push message to the client; And managing the interconnection of the service providing device and the client through each interworking unit, assigning a client ID to the client, issuing a token to the client using the assigned client ID, and a push message received from the service providing device. And a push service device configured to transmit a token by performing routing between the interworking unit and the control unit according to an ID-based routing table, and to transmit the delivered push message to the client corresponding to the client ID in the transferred token. Characterized in that.

On the other hand, the apparatus according to the second aspect of the present invention, a service provider (SP) interworking unit for connecting to the service providing apparatus; A client interworking unit for connecting with the client; A load balancer for designating a linkage unit to which the service providing device or the client can connect, with reference to load information on the SP linkage unit or the client linkage unit; And when the client is connected through the client interlocking unit, generates a client ID to the connected client through the client interlocking unit, generates a token for a push message service using the assigned client ID, and generates the client ID through the client interlocking unit. And a controller for issuing to the client.

The control unit may generate the client ID by including a national ID for identification of the national company, a control ID for identifying the controller, and a user ID, and assign the generated client ID to the client.

The controller may be configured to generate a random number corresponding to each of the plurality of devices in the client ID when the device corresponding to the user ID is a plurality of devices.

The control unit may generate and include the assigned client ID and application ID in the token and issue the same to the client through the client interworking unit.

The SP interworking unit may extract a client ID, a controller ID, and an application ID from the token received from the service providing apparatus, and transfer the extracted client ID, the controller ID, and the application ID to the controller.

The SP interworking unit may transmit a push message and a token to a control unit corresponding to the extracted control unit ID.

The controller may store routing information of the client interworking unit for each client ID in an ID-based routing table through a registration message or a keep-alive message of the client.

The client interworking unit may manage a session with the client for each client ID.

The ID-based routing table may include routing information about an SP interlocking unit ID, a control unit ID, and a client interlocking unit ID mapped to the client ID.

On the other hand, the method according to the third aspect of the present invention, the interlocking unit designation step of designating each of the interlocking unit that the service providing apparatus or the client can connect; A service providing device access step of connecting to a service providing device through the designated SP interlocking unit; A client access step of connecting to a client through the designated client interlocking unit; A client ID assignment step of generating and assigning a client ID to the connected client; And issuing a token for generating a token for a push message service using the assigned client ID and issuing the token to the client.

The method comprises the steps of: receiving a message and a token from the connected service providing apparatus; A message and token delivery step of transmitting the received push message and token to the designated client interworking unit through a control unit according to an ID-based routing table; And transmitting the push message to the client corresponding to the client ID in the token through the designated client interworking unit.

In the client ID assignment step, the client ID may be generated by including a national ID for identifying a national company, a controller ID for identifying the controller, and a user ID, and assigning the generated client ID to the client.

The client ID assigning step may include generating a random number corresponding to each of the plurality of devices in the client ID when the device corresponding to the user ID is a plurality of devices.

The token issuing step may be generated by including the assigned client ID and application ID in the token and issuing it to the client.

The client access step is characterized in that for managing the session with the client for each client ID.

The receiving of the message and the token may include extracting a client ID, a controller ID, and an application ID from the received token.

The message and token delivery step may include delivering a push message and a token to a controller corresponding to the extracted controller ID.

The ID-based routing table may include routing information about an SP interlocking unit ID, a control unit ID, and a client interlocking unit ID mapped to the client ID.

According to the present invention, ID-based routing can be easily performed by assigning a client ID to the client and issuing a token to the client using the assigned client ID.

In addition, the present invention, by transmitting the push message and the token received from the service providing device according to the ID-based routing path and transmits the push message to the client corresponding to the delivered token, the router service distribution while operating the push service device Through this, it is possible to reduce internal messages that are queried and to reduce message processing delays caused by routers.

1 is a view showing the configuration of a conventional push service providing system.
2 is a diagram illustrating a network configuration of a push service providing system using ID based routing according to the present invention.
3 is a detailed configuration diagram illustrating a push service device of FIG. 2 according to the present invention.
4 is a flowchart illustrating a method of accessing a service providing apparatus according to the present invention.
5 is a flowchart illustrating a method of issuing a client ID according to a client's connection according to the present invention.
6 is a flow diagram of an embodiment of a method for allocating tokens to a client according to the present invention.
7 is a flowchart illustrating a push service providing method using ID based routing according to the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. The configuration of the present invention and the operation and effect thereof will be clearly understood through the following detailed description. Prior to the detailed description of the present invention, the same components will be denoted by the same reference numerals even if they are displayed on different drawings, and the detailed description will be omitted when it is determined that the well-known configuration may obscure the gist of the present invention. do.

2 is a diagram illustrating a network configuration of a push service providing system using ID based routing according to the present invention.

As shown, the push service providing system according to the present invention includes a plurality of service providing devices 100-1 to 100 -N: 100, a push service device 300, and a plurality of clients 400-1 to 400 -K: 400, the plurality of service providing apparatuses 100 and the plurality of clients 400 are connected to each other via the central push service apparatus 300.

The plurality of clients 400 may include, for example, a PC, a notebook computer, a smart phone, a PDA, a notebook computer, a navigation device, a PMP, an electronic dictionary, an MP3, and the like as a terminal that can be connected to the communication network 200. The plurality of clients 400 are installed with a client application that connects to the communication network 200 and transmits and receives predetermined data (particularly, push messages).

The plurality of service providing apparatuses 100 refers to a server or a terminal that provides a service by transmitting a push message to the plurality of clients 400. To this end, the plurality of service providing apparatus 100 receives a token from the client 400 for transmitting the push message, and transmits the received token and the push message to the push service apparatus 300.

The push service device 300 basically collects the push messages transmitted from the plurality of service providing devices 100 and transmits them to the corresponding client 400.

In this case, the push service device 300 manages the interconnection of the service providing device 100 and the client 400 between each of the plurality of service providing devices 100 and the plurality of clients 400 through each interworking unit. The push service device 300 allocates a client ID to the client 400 and issues a token to the client 400 using the assigned client ID. The push service device 300 transmits the push message and the token received from the service providing device 100 by performing routing between each interworking unit and the control unit according to the ID-based routing table. The push service device 300 transmits a push message to the client 400 corresponding to the client ID in the transferred token.

3 is a detailed configuration diagram illustrating a push service device of FIG. 2 according to the present invention.

The push service device 300 according to the present invention includes an SP interlocking unit 310, a control unit 320, a client interlocking unit 330, and a load balancer 340.

In order to provide a push service, the push service device 300 according to the present invention first issues a token to the client 400 so that the token between the client 400 and the service providing device 100 is shared. In addition, the push service device 300 provides a push service between the service providing device 100 and the client 400 by using the issued token.

Hereinafter, the first embodiment of the push service device 300 for issuing an ID-based token to the push service device 300 according to the present invention, and the push service device 300 for providing a push service using ID-based routing. Will be divided into a second embodiment of the present invention.

Referring to the first embodiment of the push service device 300, the SP interlocking unit 310 is connected to the service providing device 100 to receive new information from the plurality of service providing devices (100). Here, the new information includes new information or update information, event information, and the like. The SP interlocking unit 310 may perform an authentication process of the connected service providing apparatus 100.

The client interworking unit 330 connects with the plurality of clients 400. The client interworking unit 330 designates the control unit 320 to the connected client 400. The client interworking unit 330 receives the number of subscribers accommodated by each control unit 320 from each control unit at a predetermined period and designates the control unit 320 by using the transferred number of subscribers. The client interworking unit 330 receives the token from the control unit 320 and transmits the token to the client 400.

Each SP interlocking unit 310 or client interlocking unit 330 may be provided in plural numbers according to the number of the plurality of service providing apparatuses 100 or the clients 400 connected. In general, each linking unit (310, 330) is the number of terminals that can be accommodated can be expanded based on this.

The load balancer 340 may refer to the previously stored load information when the connection request is received from the plurality of service providing apparatuses 100 or the plurality of clients 400 to the service providing apparatus 100 or the client 400. Specify each one.

When the client 400 is connected through the client interlocking unit 330, the controller 320 generates a client ID to the connected client 400 and assigns the generated client ID through the client interlocking unit 330. The controller 320 generates a token for a push message service using a client ID and issues the token to the client 400 through the client interworking unit 330. As described above, the client 400 transmits the issued token to the service providing apparatus 100 to receive the push service.

In detail, the control unit 320 generates the token by including the client ID and the application ID and issues the same to the client 400 through the client interworking unit 330. The controller 320 generates a client ID by including a national ID for identification of the national company, a controller ID for identifying the controller, and a user ID, and assigns the generated client ID to the client 400. In addition, when the device corresponding to the user ID is a plurality of devices, the controller 320 may generate a random number corresponding to each of the plurality of devices in the client ID.

The controller 320 manages the SP interlocking unit 310 and the client interlocking unit 330 that are built in the push service device 300, and in particular, manages routing information for the client interlocking unit 330 that can be accessed for each client. The client interlocking unit 330 that can be accessed by each client means a client interlocking unit in which each client maintains a connection state, and may include a client interlocking unit designated through the load balancer 340.

Hereinafter, a second embodiment of a push service device 300 that provides a push service using ID based routing will be described.

The SP interlocking unit 310 connects with the service providing apparatus 100 and receives a push message and a token from the connected service providing apparatus 100. The SP interlocking unit 310 transmits the received push message and the token to the controller 320 according to the ID-based routing table. Here, the SP interworking unit 310 performs the routing of the push message using the ID-based routing table. In detail, the SP interworking unit 310 extracts a client ID, a controller ID, and an application ID from the received token, and transfers the extracted client ID, application ID, and a push message to the controller 320. The SP interlocking unit 310 transmits a push message and a token to the control unit 320 corresponding to the extracted control unit ID.

The controller 320 receives the push message and the token from the SP interlocking unit 310, and transfers the push message and the token according to the ID-based routing table. Here, the client interworking unit 330 performs the routing of the push message using the ID-based routing table. In detail, the controller 320 receives a client ID, a controller ID, and an application ID from among the tokens from the SP interlocking unit 310 and transmits the same to the client interlocking unit 330. The controller 320 may store routing information of the client interworking unit 330 for each client ID in an ID-based routing table through a registration message or a keep alive message of the client 400. Therefore, when receiving the push message from the SP interlocking unit 310, the control unit 320 extracts the client interlocking unit 330 accessible by the corresponding client with the client information contained in the push message, and extracts the extracted client interlocking unit 330. Deliver push messages.

The client interworking unit 330 connects with the client 400. In addition, the client interworking unit 330 receives the push message and the token from the control unit 320 and transmits the transferred push message to the client 400 corresponding to the client ID in the token. The client interworking unit 330 stores an ID-based routing table. The client interworking unit 330 manages a session with the client 400 for each client ID.

The load balancer 340 refers to load information on the SP interlocking unit 310 or the client interlocking unit 330 and designates an interlocking unit to which the service providing apparatus 100 or the client 400 can connect.

The ID-based routing table includes routing information about the SP interlocking unit ID, the control unit ID, and the client interlocking unit ID mapped to the client ID.

The method for providing a push message using the push service device 300 configured as described above may specifically include a method of connecting the service providing device 100, a method of allocating a client ID to the client 400, and a token to the client 400. It is divided into an issuing method and a push service providing method using ID based routing, which will be described with reference to FIGS. 4 to 7.

4 is a flowchart illustrating a method of accessing a service providing apparatus according to the present invention.

First, when the service providing device 100 makes a connection request to access the push service device 300 (S402), the load balancer 340 checks the load information of each SP linkage unit and connects to the SP linkage unit 310. Specify (S404).

The load balancer 340 provides the service providing apparatus 100 with the information of the corresponding SP interlocking unit 310 specified in step S404 (S406).

Then, the service providing apparatus 100 attempts to access the designated SP interlocking unit 310 (S408).

When the SP interworking unit 310 transmits an approval response message to the service providing device 100, a session between the service providing device 100 and the push service device 300 is connected through the SP interlocking device 310 (S410). ). In the above process, the SP interlocking unit 310 performs an authentication process for the service providing apparatus 100 (S412).

5 is a flowchart illustrating a method of issuing a client ID according to a client's connection according to the present invention.

First, when the client 400 requests a connection to access the push service device 300 (S502), the load balancer 340 checks load information of each client interlocking unit 330 and designates a client interlocking unit that can be connected. (S504). The load information of each client linkage unit 330 is a value calculated based on the number of subscribers connected to each client linkage unit 330 and the data throughput, similar to the SP linkage unit, and each client linkage unit 330 at predetermined intervals. Can be renewed by receiving from

The load balancer 340 provides information of a client interlocking unit designated to the corresponding client 400 (S506).

The client 400 tries to access the designated client interlocking unit 330 (S508).

Subsequently, when the client interworking unit 330 transmits an approval response message to the client 400, a session between the client 400 and the push service device 300 is connected through the client interlocking unit 330 (S510).

Thereafter, the client interworking unit 330 designates the control unit 320 to the connected client 400 and transmits the information of the designated client 400 to the control unit 320 (S512).

The controller 320 allocates a client ID corresponding to the client 400 (S514).

The controller 320 transmits the assigned client ID to the client interworking unit 330 (S516).

Subsequently, the client interworking unit 330 transmits the transmitted client ID to the client 400 and allocates the client ID to the client 400 (S518).

6 is a flow diagram of an embodiment of a method for allocating tokens to a client according to the present invention.

As described above, the client 400 is assigned a client ID to receive the push service through FIG. 5.

After receiving the client ID, the client 400 transmits the client ID and the application ID to the client interworking unit 330 and requests for token issuance (S602).

In addition, the client interworking unit 330 transmits the client ID and the application ID transmitted from the client 400 to the controller 320 and requests for issuance of the token (S604).

Subsequently, the controller 320 issues a token using the client ID and the application ID transmitted from the client interworking unit 330 (S606).

Thereafter, the controller 320 transmits the issued token to the client interworking unit 330 (S608). The client interworking unit 330 transmits the transferred token to the client 400 (S610).

The client 400 transmits the token to the service providing apparatus 100 in order to share the issued token (S612).

7 is a flowchart illustrating a push service providing method using ID based routing according to the present invention.

The service providing apparatus 100 connects to the designated SP interlocking unit 310 through the load balancer 340 and connects the session.

After the session connection, the SP interlocking unit 310 receives a push message and a token from the service providing apparatus 100 (S702).

The SP interlocking unit 310 decrypts the received push message and the token to extract the client ID, the controller ID, and the application ID (S704).

The SP interlocking unit 310 transmits the push message, the client ID, and the application ID to the controller 320 corresponding to the controller ID (S706). In this case, the controller 320 may be provided in plural. In this case, since the correspondence relationship between the SP interlocking unit 310 and the control unit 320 is set in advance in the token, each SP interlocking unit 310 is set to the preset control unit 320. It can deliver push messages.

The controller 320 transmits a push message to the client interworking unit 330 (S708).

The client interworking unit 330 transmits a push message to the client 400 corresponding to the client ID (S710).

The client 400 confirms the push message by transferring the push message to the application corresponding to the application ID transmitted from the client interworking unit 330 (S712).

The foregoing description is merely illustrative of the present invention, and various modifications may be made by those skilled in the art without departing from the spirit of the present invention. Accordingly, the embodiments disclosed in the specification of the present invention are not intended to limit the present invention. The scope of the present invention should be construed according to the following claims, and all the techniques within the scope of equivalents should be construed as being included in the scope of the present invention.

The present invention assigns a client ID to a client, issues a token to the client using the assigned client ID, delivers a push message and a token received from the service providing device along an ID-based routing path, and corresponds to the transferred token. By sending a push message to a client, the internal message that is queried through the router can be reduced while the push service device is distributed and operated, and the message processing delay caused by the router can be reduced. In this regard, the invention is useful as it is industrially available because the possibility of construction and sales of the applied server as well as the use of related technology is not only sufficient for the use of related technologies, but also practically clearly implemented. to be.

100-1 to 100-N: service providing apparatus 1 to service providing apparatus N
400-1 to 400-K: Client 1 to Client K
100: service providing device 200: communication network
300: push service device 400: client
310: SP interlocking unit 320: control unit
330: client interworking unit 340: load balancer

Claims (19)

A service providing apparatus for receiving a token from the client and transmitting the received token and a push message to send a push message to a client; And
Manage the interconnection of the service providing device and the client through each interworking unit, assign a client ID to the client, issue a token to the client using the assigned client ID, push messages received from the service providing device, and A push service device for routing a token according to an ID-based routing table and performing routing between the interworking unit and the control unit, and transmitting the delivered push message to the client corresponding to a client ID in the transferred token.
Push service providing system using an ID-based routing comprising a. Service provider (SP) interworking unit for accessing the service providing device;
A client interworking unit for connecting with the client;
A load balancer for designating a linkage unit to which the service providing device or the client can connect, with reference to load information on the SP linkage unit or the client linkage unit; And
When the client is connected through the client interlocking unit, a client ID is generated to the connected client through the client interlocking unit, and a token for a push message service is generated by using the assigned client ID. Control issued to the client
Push service device comprising a. The method of claim 2,
The control unit,
And a client ID for identification of a national company, a controller ID for identifying the controller, and a user ID, and assigning the generated client ID to the client. The method of claim 3, wherein
The control unit,
And when the device corresponding to the user ID is a plurality of devices, generating a random number corresponding to each of the plurality of devices in the client ID. The method of claim 2,
The control unit,
And generating the token by including the assigned client ID and an application ID and issuing the generated token to the client through the client interworking unit. The method of claim 2,
The SP linkage unit,
And extracting a client ID, a control unit ID, and an application ID from the token received from the service providing device, and transferring the extracted client ID, control unit ID, and application ID to the control unit. The method according to claim 6,
The SP linkage unit,
And a push message and a token to a controller corresponding to the extracted controller ID. The method according to claim 6,
The control unit,
Push service device, characterized in that for storing the routing information of the client interlocking unit for each client ID through the registration message or the keep-alive message of the client in an ID-based routing table. The method according to claim 6,
The client interworking unit,
Push service device, characterized in that for managing the session with the client for each client ID. The method of claim 8,
The ID-based routing table,
Push service device, characterized in that the routing information for the SP interlocking unit ID, the control unit ID and the client interlocking unit ID mapped to the client ID. An interlocking unit specifying step of designating an interlocking unit to which a service providing device or a client can connect;
A service providing device access step of connecting to a service providing device through the designated SP interlocking unit;
A client access step of connecting to a client through the designated client interlocking unit;
A client ID assignment step of generating and assigning a client ID to the connected client; And
A token issuing step of generating a token for a push message service using the assigned client ID and issuing it to the client.
Push service providing method in a push service device comprising a. The method of claim 11,
A message and token receiving step of receiving a push message and a token from the connected service providing apparatus;
A message and token delivery step of transmitting the received push message and token to the designated client interworking unit through a control unit according to an ID-based routing table; And
Transmitting a push message to the client corresponding to the client ID in the token through the designated client interworking unit;
Push service providing method characterized in that it further comprises. The method of claim 11,
The client ID assignment step,
And generating the client ID by including a national ID for identifying a national company, a controller ID for identifying the controller, and a user ID, and assigning the generated client ID to the client. 13. The method of claim 12,
The client ID assignment step,
And generating a random number corresponding to each of the plurality of devices in the client ID when the device corresponding to the user ID is a plurality of devices. The method of claim 11,
The token issuance step,
The token service providing method, characterized in that generated by including the assigned client ID and the application ID in the token to the client. The method of claim 11,
The client connection step,
The push service providing method, characterized in that for managing the session with the client for each client ID. 13. The method of claim 12,
The message and token receiving step,
And extracting a client ID, a controller ID, and an application ID from the received token. 13. The method of claim 12,
The message and token delivery step,
The push service providing method, characterized in that for transmitting a push message and a token to the control unit corresponding to the extracted control unit ID. 13. The method of claim 12,
The ID-based routing table,
And a routing information about an SP interlocking unit ID, a control unit ID, and a client interlocking unit ID mapped to the client ID.

Images