KR101606319B1 - Method of push messages management using database - Google Patents

Abstract

The disclosed technology relates to a push message management method using a database. The push message management method comprises the steps of: receiving a plurality of push messages transmitted through a wireless communication network in a mobile terminal; transmitting the push messages to a collection server connected to a manager terminal; having the collection server receive one or more keywords by an input unit of the manager terminal, and search a partial push message including the keyword; and storing the searched partial push message in a database of the collection server. Thus, storage and deletion can be easily executed depending on the need of the push message, and the push message can be easily searched later by mapping metadata on an important push message.

Description

[0001] METHOD OF PUSH MESSAGES MANAGEMENT USING DATABASE [0002]

The disclosed technique relates to a method for managing push messages sent to a mobile terminal using a database.

With the development of smartphones, modern people have used a much wider range of services than ever before. With the development of applications such as SNS, modern people can enjoy various services accordingly, and a large amount of data is accumulated.

The push messages naturally transmitted to the smart phone are piled up. As time passes, these push messages are piled up so much that they can not be handled, and the number of push messages is increasing so that they can not be processed on the terminal.

The push message has a form different from conventional SMS, MMS, or e-mail, and includes a connection link such as a URL in a message, so that users can receive a push message and access the web page desired by the sender of the push message A message that leads to action.

Of course, such a push message does not occupy a large amount of data capacity. However, when a large number of such push messages accumulate, there is a great inconvenience in processing the push messages, and there is a possibility that there is a message required among a plurality of push messages . For example, many of the push messages are spam or phishing, but some of them may need to be managed effectively because they may contain a mix of messages that the user must receive.

In addition, since smart terminals are gradually becoming wearable devices, there is a prospect that more push messages will be used than in the past. Therefore, there is a need to effectively manage these push messages, to easily delete unnecessary messages, and to store separately the required messages so that they can be easily browsed later.

Korean Patent Laid-Open No. 10-2004-0035277 (entitled " invention of push message management and connection method of mobile communication terminal ") relates to managing push messages.

The disclosed technique is to provide a method for easily managing a push message using a database.

According to a first aspect of the present invention, there is provided a method for transmitting a push message to a mobile terminal, the method comprising: collecting a plurality of push messages transmitted to a mobile terminal through a wireless communication network; Receiving at least one keyword, retrieving a partial push message including the keyword, and storing the retrieved partial push message in a database of the collection server. have.

Embodiments of the disclosed technique may have effects that include the following advantages. It should be understood, however, that the scope of the disclosed technology is not to be construed as limited thereby, since the embodiments of the disclosed technology are not meant to include all such embodiments.

According to an embodiment of the disclosed technology, a push message management method using a database can delete a push message transmitted to a smartphone according to whether a push message is required by using a database, store an important push message for a predetermined period, Provides a management effect.

Also, there is an advantage that the metadata can be mapped to an important push message so that it can be easily found later.

1 is a flowchart of a push message management method using a database according to an embodiment of the disclosed technology.
2 is a diagram illustrating a collection server that receives a push message in accordance with one embodiment of the disclosed technique.
3 is a diagram illustrating a database for storing push messages in accordance with one embodiment of the disclosed technique.
4 is a diagram illustrating the creation of metadata for a push message in one embodiment of the disclosed technique.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

The terms first, second, A, B, etc., may be used to describe various components, but the components are not limited by the terms, but may be used to distinguish one component from another . For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

It is to be understood that the singular < RTI ID = 0.0 > terms < / RTI > used herein should be interpreted to include a plurality of representations unless the context clearly dictates otherwise. And "comprises ", when used in this specification, specify the presence of stated features, numbers, steps, operations, elements, parts, or combinations thereof, Or combinations thereof, as a matter of course.

Before describing the drawings in detail, it is to be clarified that the division of constituent parts in this specification is merely a division by main functions of each constituent part. That is, two or more constituent parts to be described below may be combined into one constituent part, or one constituent part may be divided into two or more functions according to functions that are more subdivided.

In addition, each of the constituent units described below may additionally perform some or all of the functions of other constituent units in addition to the main functions of the constituent units themselves, and that some of the main functions, And may be carried out in a dedicated manner. Accordingly, the presence or absence of each component described in this specification should be interpreted as a function.

1 is a flowchart of a push message management method using a database according to an embodiment of the disclosed technology. Referring to FIG. 1, a push message management method using a database includes receiving (110) a plurality of push messages transmitted through a wireless communication network at a mobile terminal, transmitting the push message to a collection server connected to an administrator terminal 120), the collection server receives at least one keyword through the input means of the administrator terminal, and retrieves (130) a part of the push message including the keyword, and a step (130) And storing (140) in a database.

In step 110, the mobile terminal receives a plurality of push messages transmitted through a wireless communication network. In step 110, the mobile terminal receives push messages. The push message includes a connection link such as a URL in a message, which means a message that induces a recipient of a push message to connect to the web page via the link. That is, it can be said that it is a kind of advertisement containing the intention of the sender of the push message. Therefore, it is often transmitted from an application maker, a mobile communication company, or advertisers.

Meanwhile, the push message may be less than 10 or more than 30 times a day, depending on the number of applications installed by the user of the mobile terminal and the frequency of use. Each of the push messages does not occupy a large capacity. However, when a plurality of push messages are transmitted while using the mobile terminal, inconvenience arises and it takes a predetermined time to process them.

As mentioned above, since the push message has many characteristics of the advertisement, a large part of a large amount of push messages received at the mobile terminal is often not necessary to the user. However, some of them are necessary for users. For example, there may be a case where an alarm is pushed in accordance with a schedule of a user in the scheduler application.

As described above, if the push messages are collectively deleted, important push messages can be deleted together, and there are many inconveniences to check each push message. Therefore, it is disclosed in the disclosed technology a method of easily managing such push messages.

In step 120, the mobile terminal transmits the push message to a collection server connected to the administrator terminal. The manager terminal is connected to the pre-established collection server. The collection server receives the push message received by the mobile terminal.

Meanwhile, the collection server is turned on or off according to a control signal transmitted from the administrator terminal. That is, if the OFF signal for downing the server is received from the administrator terminal, the push message is not received. Accordingly, in order for the user to transmit the push message to the collection server, the collection server must be turned on via the administrator terminal.

Also, the collection server permits connection through a predetermined IP, which has been transmitted from the administrator terminal in advance, and restricts access through an IP different from the IP. In other words, the collection server permits only the connection to the predetermined terminal through the administrator terminal. This is a solution for solving the security problem of storing the push message transmitted to the mobile terminal in a separate database.

Meanwhile, the manager terminal and the mobile terminal may be the same. For example, a user's mobile terminal may be an administrator terminal, set an access right to the collection server as an administrator terminal, and then transmit push messages received as a mobile terminal to a collection server.

In step 130, the collection server receives at least one keyword through the input means of the manager terminal, and retrieves a part of the push messages including the keyword. The collection server receives at least one keyword from the administrator terminal. Here, the keyword includes the sender of the push message, the date of sending the push message, and the text included in the push message content. And retrieves a push message including the keyword.

In one embodiment, if a push message about health care is searched, text such as health, health, or body management may be entered as a keyword. Then, a part of the push messages including the texts can be retrieved from among the collected push messages. Naturally, since the push message thus retrieved is a push message required by the user of the mobile terminal, the retrieved push message is stored in the following step.

Meanwhile, the collection server is linked to a web site having a predetermined interface. The push message can be searched based on the keyword transmitted from the website. Accordingly, the user can access the web site using the mobile terminal, and can input a keyword into a search window or an interface provided in the web site.

In step 140, the retrieved push messages are stored in the database of the collection server. The collection server includes a database for storing push messages. The database is used as a space for storing the retrieved push messages.

The step 140 further includes generating metadata for the retrieved push message and mapping the retrieved push message and the retrieved metadata. The metadata includes at least one of a date of retrieving the push message, a text included in the push message, and a provider of the push message.

The user saves the retrieved push message to retrieve the push message retrieved by the user. Therefore, the user can input the metadata in order to more easily find and memorize the push message. The metadata is mapped to the retrieved push message and stored together. Thus, the user of the mobile terminal can easily find the push message stored later.

2 is a diagram illustrating a collection server that receives a push message in accordance with one embodiment of the disclosed technique. And Figure 3 is a diagram of a database that stores push messages in accordance with one embodiment of the disclosed technique. Referring to FIGS. 2 and 3, it can be seen that a collection server is opened using PUTTY. The collection server is interlocked with a pre-built database.

In general, the collection server collects push messages in the order that they are transmitted from the mobile terminal. And may be displayed on the screen in reverse order to provide the user of the mobile terminal with readability.

2, a collection server is opened using PUTTY, but other programs may be used.

4 is a diagram illustrating the creation of metadata for a push message in one embodiment of the disclosed technique. Referring to FIG. 4, the metadata includes at least one of a date of retrieving a push message, a text included in the push message, and a provider of the push message. It is also possible to tag as shown in Fig.

Meanwhile, in the disclosed technology, not only the metadata of the retrieved push message is mapped, but also the contents of the retrieved push message itself can be modified and stored. For example, it is possible to distinguish the portion of the message from the portion containing the information, and the portion of the message that does not include the message. Only the part of the message required can be deleted, or the user can create new contents in the push message. Therefore, there is an advantage that higher readability and utilization can be expected.

Although the push message management method using the database according to an embodiment of the disclosed technology has been described with reference to the embodiments shown in the drawings for the sake of understanding, it is only an example and it will be understood by those skilled in the art It will be understood that various modifications and equivalent embodiments are possible. Accordingly, the true scope of protection of the disclosed technology should be determined by the appended claims.

110: Push message collection 120: Transfer to collection server
130: Search by Keyword 140: Save push message to DB

Claims (6)

Receiving a plurality of push messages transmitted through a wireless communication network at a mobile terminal;
Transmitting the push message to a collection server connected to an administrator terminal;
Receiving, by the collection server, at least one keyword through the input means of the manager terminal and searching for a part of the push message including the keyword; And
And storing the retrieved push messages in a database of the collection server. The system according to claim 1,
A push message management unit configured to allow a connection via a predetermined IP which has been previously transmitted from the administrator terminal according to a control signal transmitted from the administrator terminal and to permit connection via an IP different from the IP, Way. The method according to claim 1,
A push message management method using a database including a sender of a push message, a send date of a push message, and text contained in the push message content. The system according to claim 1,
A push message management method using a database interlocked with a website having a predetermined interface and searching for a push message based on a keyword transmitted from the website. 2. The method of claim 1, wherein storing in a database of the collection server comprises:
Further comprising: generating metadata for the retrieved push message and mapping the retrieved push message and the retrieved metadata. 6. The method according to claim 5,
Wherein the push message comprises at least one of a date when the push message was retrieved, a text included in the push message, and a provider of the push message.

Images