KR20180006548A - Push service management method and apparatus thereof - Google Patents

Abstract

The present invention relates to an apparatus and a method for managing a push service. The apparatus for managing a push service according to an embodiment of the present invention comprises: a storage unit which stores a push service target URL and a push message corresponding to the push service target URL; a traffic analysis unit which analyzes user traffic generated from a user device, and confirms whether a traffic URL of the user traffic is the push service target URL; and a push message transmission unit which transmits the push message to the user device when the traffic URL is the push service target URL. According to embodiments of the present invention, since a push message which does not correspond to the intention of a user is not transmitted, it is possible to reduce stress of the user caused by an unnecessary push message.

Description

[0001] Push service management method and apparatus [

Embodiments of the present invention are directed to an apparatus and method for managing a push service.

With the spread of various user devices such as smart phones, users are using various services. Among them, push services provided by service providers are widely used, and accordingly the amount of push messages is gradually increasing.

Such an increase in push messages has a problem of increasing the burden on network operators, and there is also a problem in that users are exposed to various frauds such as smsing and hacking because the subject managing the push service is not clear.

Korean Patent Publication No. 2004-0035277 (Push Message Management and Connection Method of Mobile Communication Terminal)

Embodiments of the present invention provide a way to prevent transmission of unnecessary push messages.

Embodiments of the present invention provide a way to prevent push messages that are not consistent with the user's intentions from being transmitted.

A push service management apparatus according to an embodiment of the present invention includes: a storage unit for storing a push service target URL and a push message corresponding to the push service target URL; A traffic analyzing unit analyzing user traffic generated from the user device and verifying that the traffic URL of the user traffic is a push service target URL; And a push message forwarding unit for forwarding the push message to the user device when the traffic URL is a push service target URL.

In one embodiment, the push service target URL and the push message corresponding to the push service target URL may be received from a service providing server that manages the push service target URL.

In one embodiment, the traffic analyzing unit confirms from the service providing server whether or not the user device sets up a push notification for the traffic URL identified as the push service target URL, and the push message forwarding unit transmits the push message to the user device The push message may be transmitted to the user device when there is a push notification setting of the push message.

In one embodiment, the storage further stores information on a push notification time corresponding to the user device, and the traffic analysis is performed such that, if the user traffic occurs within the push notification allowable time, URL.

In one embodiment, the push notification time may be set by a request of the user device.

In one embodiment, the storage further stores information on a push notification permitted service provider corresponding to the user device, and the push message forwarding unit transmits, when the traffic URL is a URL managed by the push notification permitted service provider, Push message to the user device.

In one embodiment, the information about the push notification allowed service provider may be set by a request of the user device.

In one embodiment, the storage unit further stores an identifier of a push service target device corresponding to the push service target URL, and the traffic analysis unit further verifies whether the identifier of the user device is an identifier of the push service target device, The push message forwarding unit may transmit the push message to the user device when the traffic URL is the push service target URL and the identifier of the user device is the identifier of the push service target device.

In one embodiment, the push service target URL, the push message corresponding to the push service target URL, and the identifier of the push service target device corresponding to the push service target URL are transmitted from a service providing server managing the push service target URL Lt; / RTI >

According to an embodiment of the present invention, there is provided a push service management method comprising: receiving a push service target URL managed by the service providing server and a push message corresponding to the push service target URL from a service providing server; Analyzing the user traffic generated from the user device and confirming whether the traffic URL of the user traffic is a push service target URL; And transmitting the push message to the user device if the traffic URL is a push service target URL.

In one embodiment, the method further comprises confirming, from the service providing server, whether to set up the push notification of the user device for the traffic URL identified by the push service target URL, and transmitting the push message to the user device The transmitting step may include transmitting the push message to the user device when there is a push notification setting of the user device for the traffic URL.

In one embodiment, the method further comprises setting a push notification time corresponding to the user device in response to a request from the user device, wherein the step of verifying that the traffic URL is the push service target URL comprises: And confirming that the traffic URL is the push service target URL when traffic occurs within the push notification allowable time.

In one embodiment, the method further comprises setting push notifying service provider information corresponding to the user device in response to a request from the user device, the step of transmitting the push message to the user device And transmitting the push message to the user device when the traffic URL is a URL managed by the push notification permitted service provider.

In one embodiment, the method includes receiving an identifier of a push service target device corresponding to the push service target URL from the service providing server; And confirming whether the identifier of the user device is an identifier of the push service target device, wherein the step of transmitting the push message to the user device comprises: determining whether the traffic URL is a push service target URL and the identifier of the user device And transmitting the push message to the user device when the identifier is the identifier of the push service target device.

According to the embodiments of the present invention, since unnecessary push messages are not generated, burden on the network provider can be reduced.

According to embodiments of the present invention, a push message that does not match the intention of the user is not transmitted, thereby reducing a user's stress due to unnecessary push messages.

According to the embodiments of the present invention, since the subject of the push service management is clear, the security related to the push service can be easily improved, thereby preventing users from being exposed to various frauds such as smsing and hacking.

1 is an exemplary view for explaining a push service management system to which embodiments of the present invention are applied;
FIG. 2 is a flowchart illustrating a push service management method according to an embodiment of the present invention. FIG.
3 is an exemplary view for explaining a first URL-specific mapping table according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating a push service management method according to another embodiment of the present invention. FIG.
FIG. 5 is an exemplary view for explaining a category-specific mapping table according to an embodiment of the present invention;
FIG. 6 is a flowchart illustrating a push service management method according to another embodiment of the present invention. FIG.
FIG. 7 is an exemplary view for explaining a second URL-specific mapping table according to another embodiment of the present invention;
FIG. 8 is an exemplary diagram illustrating a push notification time according to an exemplary embodiment of the present invention;
FIG. 9 is an exemplary diagram illustrating a push notification service provider according to an embodiment of the present invention;
10 is a block diagram illustrating a push service management apparatus to which embodiments of the present invention are applied.

In the following description of the embodiments of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

1 is an exemplary diagram illustrating a push service management system to which embodiments of the present invention are applied.

Referring to FIG. 1, a push service management system to which embodiments of the present invention are applied includes a user device 100, a push service management apparatus 200, and a service provision server 300. Depending on the embodiment, at least one of the components shown in Fig. 1 may be omitted.

The user device 100 may be various electronic devices such as a smart phone, a tablet, and a notebook computer. The user device 100 can perform communication according to various communication protocols and can be connected to the Internet through an ISP (Internet Service Provider).

The push service management apparatus 200 may be operated by an ISP or may be operated by a separate provider (for example, a provider who professionally manages push message transmission). The push service management apparatus 200 can monitor user traffic generated from the user device 100 and analyze the traffic. The push service management apparatus 200 may bypass the monitored user traffic to the Internet section. The analysis of the user traffic can be made on the HTTP request message. The push service management apparatus 200 can acquire a traffic URL (Uniform Resource Locator) of user traffic and a device identifier (e.g., a telephone number) of the user device 100 from a HyperText Transfer Protocol (HTTP) . The traffic URL may refer to the URL the user device 100 intends to access.

The service providing server 300 is a server operated by a service providing company, and can provide various services related to travel, shopping, and books through the Internet.

2 is a flowchart illustrating a push service management method according to an embodiment of the present invention. Depending on the embodiment, at least one of the steps shown in Fig. 2 may be omitted.

In step 201, the service providing server 300 can manage the first URL-specific mapping information. The first URL-specific mapping information may include at least one push service object corresponding to the URL and each push service target URL. The push service target URL may refer to a URL to which a push message corresponding to the push service is set. Accordingly, the push message corresponding to the push service target URL may mean a push message to be provided to the user device 100 when the user device 100 accesses the corresponding push service target URL.

The first URL-specific mapping information may be managed in the form of a table. FIG. 3 shows an example of the first URL-specific mapping table. Referring to FIG. 3, it can be seen that the push service target URL and the push message corresponding to each push service target URL are mapped.

The service providing server 300 may update the first URL-specific mapping information when the push service target URL or the push message is generated, modified or deleted. The creation, modification, or deletion of the push service target URL or the push message may be performed by an operator (e.g., a service provider or a server administrator) who operates the service providing server 300.

The service providing server 300 can provide the first URL-specific mapping information managed by the service providing server 300 to the push service managing apparatus 200. [ Such provision may be made periodically, at the operator's request, or automatically when a push service URL or push message is created, modified or deleted.

The push service management apparatus 200 can store the first URL-specific mapping information received from the service providing server 300 and manage the same. The push service management apparatus 200 may also store and manage the first URL-specific mapping information in the form of a table as shown in FIG.

The push service management apparatus 200 analyzes the user traffic to acquire the traffic URL of the user traffic and the device identifier of the user device 100 when the user traffic is generated from the user device 100 can do.

The push service management apparatus 200 can confirm that the obtained traffic URL is the push service target URL. This confirmation may be made by referring to the first URL-specific mapping information managed by the push service management apparatus 200. [

When it is determined that the acquired traffic URL is the push service target URL, the push service management apparatus 200 refers to the first URL-specific mapping information and provides a push message corresponding to the traffic URL to the user device 100 can do.

4 is a flowchart illustrating a push service management method according to another embodiment of the present invention. Depending on the embodiment, at least one of the steps shown in Fig. 4 may be omitted.

In step 401, the service providing server 300 can manage the mapping information for each category. The category-specific mapping information includes at least one category related to the service provided by the service providing server 300, a push service target URL corresponding to each category, a device identifier corresponding to each push service target URL, And at least one of push messages corresponding to the target URL.

The mapping information for each category can be managed in the form of a table. FIG. 5 shows an example of a category-specific mapping table. Referring to FIG. 5, it can be seen that the service category, the push service target URL corresponding to each category, the device identifier corresponding to each push service target URL, and the push message corresponding to each push service URL are mapped .

In step 403, the service providing server 300 receives the push notification setting request from the user device 100 that desires to receive the push message, and sets the push notification setting corresponding to the user device 100 in accordance with the received request And update the mapping information for each category. The push notification setting request may include a device identifier of the user device 100 and a push message reception condition (for example, a category for which a push message is desired to be received). The category-specific mapping information may be updated whenever the creation, modification, or deletion of at least one of the category, the push service target URL, and the push message is made.

The service providing server 300 transmits mapping information for each first URL (at least one push service target URL and at least one push message corresponding to each push service target URL) among the category-specific mapping information managed by the service providing server 300 to the push service Management apparatus 200 according to the present invention. This provision may be made periodically, at the operator's request, or when at least one of the category, the push service URL, the device identifier, and the push message is created, modified or deleted.

The push service management apparatus 200 can store the first URL-specific mapping information received from the service providing server 300 and manage the same. Like the embodiment described with reference to FIG. 2, the first URL-specific mapping information can be managed in the form of a table shown in FIG.

In step 405, when the user traffic is generated from the user device 100, the push service management apparatus 200 analyzes the user traffic to acquire the traffic URL of the user traffic and the device identifier of the user device 100 can do.

The push service management apparatus 200 can confirm that the obtained traffic URL is the push service target URL. This confirmation may be made by referring to the first URL-specific mapping information managed by the push service management apparatus 200. [

In step 407, when the traffic URL is a push service target URL, the push service management apparatus 200 provides the traffic URL and the device identifier of the user device 100 to the service providing server 300, The user device 100 may request confirmation of whether or not the push notification is set. Accordingly, the service providing server 300 refers to the mapping information for each category managed by the service providing server 300, confirms whether the push notification of the user device 100 is set for the traffic URL, and transmits the confirmation result to the push service management apparatus 200).

When it is determined that the user device 100 has set a push notification for the traffic URL, the push service management apparatus 200 refers to the first URL-specific mapping information, and transmits a push message corresponding to the traffic URL to the user To the device (100).

6 is a flowchart illustrating a push service management method according to another embodiment of the present invention. Depending on the embodiment, at least one of the steps shown in Fig. 6 may be omitted.

In step 601, the service providing server 300 can manage the mapping information for each category. The category-specific mapping information includes at least one category related to the service provided by the service providing server 300, a push service target URL corresponding to each category, a device identifier corresponding to each push service target URL, And at least one of push messages corresponding to the target URL. Like the embodiment described with reference to FIG. 4, the category-specific mapping information can be managed in the form of a table shown in FIG.

In step 603, the service providing server 300 receives the push notification setting request from the user device 100 desiring to receive the push message, and sets the push notification setting corresponding to the user device 100 in accordance with the received request And update the mapping information for each category. The push notification setting request may include a device identifier of the user device 100 and a push message reception condition (for example, a category for which a push message is desired to be received). The category-specific mapping information may be updated whenever the creation, modification, or deletion of at least one of the category, the push service target URL, and the push message is made.

The service providing server 300 receives the second URL-specific mapping information (at least one push service target URL, at least one push message corresponding to each push service target URL, and each push And at least one device identifier corresponding to the service target URL) to the push service management apparatus 200. This provision may be made periodically, at the operator's request, or when at least one of the category, the push service URL, the device identifier, and the push message is created, modified or deleted.

The push service management apparatus 200 may store the second URL-specific mapping information received from the service providing server 300 and manage the second URL-specific mapping information. The second URL-specific mapping information can be managed in the form of a table. FIG. 7 shows an example of the second URL-specific mapping table. Referring to FIG. 7, it can be seen that a push service target URL, a device identifier corresponding to each push service target URL, and a push message corresponding to each push service target URL are mapped.

The push service management apparatus 200 analyzes the user traffic when the user traffic is generated from the user device 100 and acquires the traffic URL of the user traffic and the device identifier of the user device 100 can do.

The push service management apparatus 200 can confirm that the obtained traffic URL is the push service target URL. This confirmation can be made by referring to the second URL-specific mapping information managed by the push service management apparatus 200. [

When the traffic URL is the push service target URL, the push service management apparatus 200 can check whether the device identifier of the user device 100 is mapped to the corresponding push service target URL. That is, the push service management apparatus 200 can confirm whether or not the push notification of the user device is set for the corresponding push service target URL. This confirmation can be made by referring to the second URL-specific mapping table managed by the push service management apparatus 200. [

When the traffic URL is the push service target URL and the identifier of the user device is mapped to the corresponding push service target URL, the push service management apparatus 200 provides the push message corresponding to the traffic URL to the user device 100 can do.

2 to 6, the push service management apparatus determines whether to transmit a push message based on information received from the service providing server.

On the other hand, the user of the user device may not want to receive the push message at a specific time, or may not want to receive the push message provided by the specific service providing server. Collaboration between the user device and the push service management device can be achieved so that the intent of such a user can be easily achieved.

For example, the user device may request the push service management device to set the push notification time. For example, the user device can request the push service management apparatus to prevent a push message corresponding to the push service target URL from being received during a specific time period, even if the push service target URL is a push notification. Thereby, the push service management apparatus can manage the push notification permission time information corresponding to the user device. The information on the allowable push notification time can be managed in the form of a table, and an example thereof is shown in FIG. Referring to FIG. 8, it can be seen that the push notification allowable time for each device identifier is set. The push service management apparatus can confirm whether or not the user traffic has occurred within the push notification permission time before confirming that the traffic URL described with reference to Figs. 2 to 6 is the push service target URL. If the user traffic has occurred within the push notification permitted time, it is confirmed that the traffic URL is the push service target URL, and if not, the procedure for transmitting the push message can be terminated.

Also, for example, the user device may request the push service management device to set up push notifying service provider information (e.g., URL). For example, even if the push service target URL is provided with a push notification, if the push service target URL is provided by a specific service provider, the user device does not receive a push message corresponding to the URL provided by the corresponding service provider To the push service management apparatus. Accordingly, the push service management apparatus can manage the URL of the push notification permitted service provider corresponding to the user device. The push notification permitted service provider information can be managed in the form of a table, and an example thereof is shown in FIG. Referring to FIG. 9, it can be seen that the URL of the push notifying service provider per device identifier is set. The push service management apparatus can confirm whether or not the traffic URL corresponds to the URL of the push notification permitted service provider before the step of providing the push message to the user device described with reference to Figs. If the traffic URL corresponds to the URL of the push notification permitted service provider, a push message may be provided to the user device, and if not, the push message transmission procedure may be terminated.

FIG. 10 is a block diagram illustrating a push service management apparatus to which embodiments of the present invention are applied.

Referring to FIG. 10, a push service management apparatus 200 to which embodiments of the present invention are applied includes a traffic analysis unit 210, a storage unit 220, and a push message forwarding unit 230. Depending on the embodiment, at least one of the aforementioned components may be omitted.

The traffic analysis unit 210 may monitor user traffic generated from the user device and analyze the user traffic. Monitored user traffic can be bypassed to the Internet section. In one embodiment, the traffic analysis unit 210 may perform analysis on the HTTP request message. The traffic analysis unit 210 can obtain the device identifier and the traffic URL of the user device through analysis of the user traffic.

The traffic analysis unit 210 can check whether the traffic URL is the push service target URL by referring to the first URL-specific mapping information. The traffic analyzing unit 210 can inquire the service providing server about whether or not the user device sets up the push notification of the traffic URL confirmed to the push service target URL and receive the result.

The traffic analysis unit 210 can check whether the traffic URL is the push service target URL by referring to the second URL-specific mapping information, and confirm that the device identifier is the push service target device.

According to the embodiment, the traffic analyzing unit 210 may check whether the traffic URL is the push service target URL only when the user traffic occurs within the push notification allowable time.

The storage unit 220 may store first URL-specific mapping information (at least one push service target URL and a push message corresponding to each push service target URL). The first URL-specific mapping information may be received from the service providing server.

The storage unit 220 stores second URL-specific mapping information (at least one push service target URL, at least one push message corresponding to each push service target URL, and at least one device corresponding to each push service target URL Identifier) can be stored. The second URL-specific mapping information may be received from the service providing server.

The storage unit 220 may store information on a push notification permission time corresponding to the user device. Information on the push notification allowable time can be set by a request of the user device.

The storage unit 220 may store information on a push notification permitted service provider corresponding to the user device. Information about the push notification permitted service provider can be set by a request of the user device.

The push message forwarding unit 230 may transmit a push message to the user device if the traffic URL is the push service target URL.

According to the embodiment, the push message forwarding unit 230 may transmit a push message to the user device only when the user device sets a push notification for the traffic URL.

According to the embodiment, even if the user device sets up the push notification for the traffic URL, the push message forwarding unit 230 transmits the push message only if the traffic URL is a URL managed by the push notification permitted service provider To the user device.

The embodiments of the invention described above may be implemented in any of a variety of ways. For example, embodiments of the present invention may be implemented using hardware, software, or a combination thereof. When implemented in software, it may be implemented as software running on one or more processors using various operating systems or platforms. Additionally, such software may be written using any of a number of suitable programming languages, and may also be compiled into machine code or intermediate code executable in a framework or virtual machine.

Also, when embodiments of the present invention are implemented on one or more processors, one or more programs for carrying out the methods of implementing the various embodiments of the invention discussed above may be stored on a processor readable medium (e.g., memory, A floppy disk, a hard disk, a compact disk, an optical disk, a magnetic tape, or the like).

Claims (14)

A storage unit for storing a push service target URL and a push message corresponding to the push service target URL;
A traffic analyzing unit analyzing user traffic generated from the user device and verifying that the traffic URL of the user traffic is a push service target URL; And
A push message forwarding unit for forwarding the push message to the user device if the traffic URL is a push service target URL,
The push service management apparatus comprising:
The method according to claim 1,
Wherein the push service target URL and the push message corresponding to the push service target URL are received from a service providing server managing the push service target URL
Push service management device.
3. The method of claim 2,
Wherein the traffic analyzing unit checks from the service providing server whether or not the push notification of the user device is set for the traffic URL confirmed as the push service target URL,
Wherein the push message forwarding unit transmits the push message to the user device when there is a push notification setting of the user device for the traffic URL
Push service management device.
The method according to claim 1,
Wherein the storage unit further stores information on a push notification permission time corresponding to the user device,
The traffic analysis is performed to determine whether the traffic URL is the push service target URL when the user traffic occurs within the push notification permission time
Push service management device.
5. The method of claim 4,
The push notification permission time is set by a request of the user device
Push service management device.
The method according to claim 1,
Wherein the storage further stores information on a push notification service provider corresponding to the user device,
Wherein the push message forwarding unit transmits the push message to the user device when the traffic URL is a URL managed by the push notification permitted service provider
Push service management device.
The method according to claim 6,
Wherein the information about the push notification permitted service provider is set by a request of the user device
Push service management device.
The method according to claim 1,
Wherein the storage unit further stores an identifier of a push service target device corresponding to the push service target URL,
The traffic analyzer further verifies whether the identifier of the user device is an identifier of the push service target device,
Wherein the push message forwarding unit transmits the push message to the user device when the traffic URL is the push service target URL and the identifier of the user device is the identifier of the push service target device
Push service management device.
9. The method of claim 8,
The push service target URL, the push message corresponding to the push service target URL, and the identifier of the push service target device corresponding to the push service target URL are received from a service providing server managing the push service target URL
Push service management device.
CLAIMS 1. A method for a push service management apparatus to manage a push service,
Receiving a push service target URL managed by the service providing server and a push message corresponding to the push service target URL from a service providing server;
Analyzing the user traffic generated from the user device and confirming whether the traffic URL of the user traffic is a push service target URL; And
Transmitting the push message to the user device if the traffic URL is a push service target URL
Gt;
11. The method of claim 10,
Further comprising confirming, from the service providing server, whether the push notification of the user device is set for the traffic URL identified by the push service target URL,
Wherein forwarding the push message to the user device comprises transmitting the push message to the user device when there is a push notification setting of the user device for the traffic URL
How to manage push services.
11. The method of claim 10,
Further comprising setting a push notification allowable time corresponding to the user device in response to a request from the user device,
Wherein the step of verifying that the traffic URL is the push service target URL comprises checking if the traffic URL is the push service target URL if the traffic occurs within the push notification permission time
How to manage push services.
11. The method of claim 10,
Further comprising setting, in response to a request from the user device, push notifying service provider information corresponding to the user device,
Wherein the step of transmitting the push message to the user device comprises transmitting the push message to the user device if the traffic URL is a URL managed by the push notifying service provider
How to manage push services.
11. The method of claim 10,
Receiving an identifier of a push service target device corresponding to the push service target URL from the service providing server; And
Further comprising: confirming whether the identifier of the user device is an identifier of the push service target device,
Wherein the step of transmitting the push message to the user device comprises transmitting the push message to the user device when the traffic URL is a push service target URL and the identifier of the user device is an identifier of the push service target device Included
How to manage push services.

Images