WO2020040341A1 - Hashtag correction service method for improving marketing effectiveness and system therefor - Google Patents

Abstract

The present invention relates to an SNS service largely used as a marketing tool and, specifically, to a hashtag correction service method and a system therefor, wherein when a user uploads a post with a wrongly typed hashtag, a correction guide for the hashtag is provided to guide the user to correct the hashtag.

Description

Hashtag correction service method for improving marketing effect and system for same

The present invention relates to an SNS service that is widely used as a means of marketing. Specifically, when a user uploads a post and incorrectly writes a hash tag, the present invention can induce correction to a correct hash tag by providing a correction guide. Hashtag correction service method and system for the same.

As the spread of smart terminals expands, the use of social network services (SNS) also increases. A hashtag is introduced to efficiently classify posts uploaded to a social network service (SNS). The hashtag includes various information such as a summary of uploaded posts or keywords related to the posts.

Hash tag can also be used as a marketing means, service providers that provide a product or service is used to enhance the marketing effect by exposing a lot of hash tags related to the product or service online.

On the other hand, the service subject who uses SNS service as a marketing means hopes that the object they want to promote is entered with the correct name and exposed online, but since the hashtag input is entirely made by the user who uploads it, the user Incorrectly inputting a hashtag, ie, a character is mistakenly entered incorrectly, or a wrong name is entered frequently causes an incorrectly displayed name to be exposed online.

Considering that a large number of keyword search results are based on hashtags, if a mistyped product name or service name is entered as a hashtag as described above, even if a user searches for a keyword, it will not be included in the search results. The marketing effect may be halved, and if a wrong brand name or service name is frequently exposed, many consumers may experience confusion about what the actual brand name or service name is and thus may also cause a problem that the marketing effect is halved.

Thus, in order to solve the problem of half the marketing effect caused by a wrongly inputted hashtag by a user's mistake or misunderstanding, it is necessary to induce a user to notify and correct a wrong hashtag input. We propose a method for providing hashtag correction service and a system for the same.

In the present invention, when a user uploads an SNS post, the user first specifies which service subject corresponds to the post, and then determines whether the hash tag corresponding to the service subject is correctly inputted, and determines that the post is not correctly inputted. If the purpose is to deliver a calibration guide message to the user.

The purpose of this is to induce the user to correct the hash tag by mistake or misunderstanding, so that the service subject can fully enjoy the marketing effect through SNS.

In order to solve the above problems, a method of providing a hash tag correction service according to the present invention includes the steps of: the user terminal forwarding the upload request for the post, the post includes at least one hashtag; And determining, by the SNS server, whether or not correction is necessary for the hash tag included in the post.

In addition, the method for providing a hash tag correction service, after the SNS server determines whether the hash tag needs to be corrected, if it is determined that the hash tag needs to be corrected, the SNS server sends a calibration guide message to the user terminal. Sending a; may further include.

In addition, the hash tag calibration service providing method, the step of determining whether the SNS server needs to calibrate the hash tag, the step of specifying a service principal corresponding to at least one information in the post; And comparing a hash tag in the post with a keyword corresponding to a service subject to determine whether the hash tag needs to be corrected.

Meanwhile, according to another embodiment of the present invention, a method for providing a hash tag correction service by an SNS server includes: receiving an upload request from a user terminal for a post, wherein the post includes at least one hashtag; And determining whether or not correction is necessary for the hashtag included in the post.

The hash tag calibration service providing method may further include transmitting a calibration guide message to the user terminal when it is determined that the hash tag needs to be calibrated after determining whether to calibrate the hash tag. .

In the hash tag calibration service providing method, determining whether the calibration is necessary may include: specifying a service principal corresponding to at least one information in the post; And comparing a hash tag in the post with a keyword corresponding to a service subject to determine whether the hash tag needs to be corrected.

In the hash tag correction service providing method, specifying a service principal corresponding to at least one information in the post may include comparing reference data previously provided from the service principal with at least one information in the post. It may include a step. In this case, the reference data includes at least one of location information, reference image, or reference text.

On the other hand, a method for providing a hash tag correction service according to another embodiment of the present invention comprises the steps of: the user terminal forwarding the upload request for the post, the post includes at least one hashtag; Determining whether the SNS server is a notification target for the post, and if it is determined that the notification target is a notification target, transmitting an upload notification to a service server; And determining, by the service server, whether correction is necessary for the hash tag included in the post.

On the other hand, according to another embodiment of the present invention, a method for providing a hash tag correction service by a service server includes: receiving, from an SNS server, an upload notification indicating that a post has been uploaded from any user terminal; And determining whether or not correction is necessary for the hashtag included in the post.

According to the present invention, since the necessity of correcting the wrong input hashtag can be guided, there is an effect that the user can have an opportunity to correct the wrong input, and the service subject can enhance the marketing effect using SNS. It works.

1 is a view for explaining an example of input of a wrong hash tag.

2 is a flowchart illustrating a hash tag calibration service providing method according to a first embodiment of the present invention in order.

Figure 3 shows the detailed steps of the calibration necessity determination step.

4 is a view for explaining the use of the position information when determining whether or not correction is necessary.

5 is a view for explaining the use of a reference image when determining whether or not correction is necessary.

6 is a flowchart illustrating a hash tag correction service providing method according to a second embodiment of the present invention in order.

FIG. 7 illustrates an application example of a method for providing a hash tag correction service according to the present invention, and illustrates an embodiment in which the method for providing a hash tag correction service is provided within another service provision process.

8 is another application example of a method for providing a hash tag correction service according to the present invention.

Details of the object and technical configuration of the present invention and the resulting effects thereof will be more clearly understood by the following detailed description based on the accompanying drawings. With reference to the accompanying drawings will be described in detail an embodiment according to the present invention.

The embodiments disclosed herein should not be interpreted or used as limiting the scope of the invention. It is obvious to those skilled in the art that the description, including the embodiments herein, has a variety of applications. Accordingly, certain embodiments described in the detailed description of the invention are intended to illustrate the invention better and are not intended to limit the scope of the invention to the embodiments.

In the present specification, a terminal is a mobile station, a mobile terminal, a subscriber station, a portable subscriber station, a user equipment, an access terminal, a personal computer. It refers to all kinds of devices capable of data communication with an external device such as a personal computer and a phone, and may include all or some functions of the corresponding device.

The functional blocks shown in the figures and described below are only examples of possible implementations. Other functional blocks may be used in other implementations without departing from the spirit and scope of the detailed description. In addition, while one or more functional blocks of the present invention are represented by separate blocks, one or more of the functional blocks of the present invention may be a combination of various hardware and software configurations that perform the same function.

In addition, the expression "comprising" certain components merely refers to the presence of the components as an "open" expression, and should not be understood as excluding additional components.

Furthermore, when a component is referred to as being “connected” or “connected” to another component, it should be understood that there may be a direct connection or connection to that other component, but there may be other components in between. do.

First, the situation of a problem to be solved by the present invention will be briefly described with reference to FIG. 1.

FIG. 1 illustrates a process in which a user takes a picture of a visited restaurant and uploads it to a post after visiting a restaurant. For example, a user can visit a restaurant named [MOLINA's] (left of FIG. 1) and then create and upload a post to leave it on SNS. For example, a user can create and upload a post like the right side of FIG. have. 1 is an example of a post editing window 10 provided by an SNS server or provided by an application for using an SNS service, and includes a first input area for inputting an image or a video. (11) and a second input area 12 for inputting text. A user may input a hash tag 13 in the second input area 12. FIG. 1 illustrates an example in which a user attempts to input a restaurant name #MOLINA as a hash tag, but mistakenly enters #MOLIMA. will be.

Hashtag typos such as these occur quite often among users, for example, if you just typed a typo, as in the above example, you misunderstood the name of the restaurant or the name of the food provided by the restaurant. In addition, these examples are not limited only to restaurants, but there may also be misinputs resulting from not knowing general tourist attractions such as mountains, seas and river names.

The present invention intends to provide an opportunity for hash tag correction by determining whether a correction is necessary for a hash tag that is incorrectly input by a user mistake or a misunderstanding, and guiding the user when the correction is necessary.

2 illustrates a hash tag correction service providing method according to a first embodiment of the present invention.

First, a configuration of the entire system for providing a hash tag correction service according to the present invention will be described with reference to FIG. 2. Referring to FIG. 2, the system may include a user terminal and an SNS server in a basic configuration, and may additionally include a service server.

First, a user terminal is a device including a memory capable of storing instructions for executing a program, and a central control unit (CPU) that actually executes the instructions. The user terminal referred to in the present specification edits and uploads a post. It can be understood as generic to devices with the ability to make requests. The type of the user terminal may be preferably portable such as a smartphone, a tablet PC, a laptop. However, the type of user terminal is not necessarily limited to a portable device.

Next, the SNS server refers to a server operated by a self-providing SNS service to a plurality of users. The SNS server provides a basic SNS service by receiving a post upload request directly from a user and storing the uploaded post in the server. Since the process and the type of SNS service is well known to those skilled in the art can be easily understood, a detailed description thereof will be omitted.

The hashtag correction service providing method according to the first embodiment may be basically performed by the user terminal and the SNS server, but additionally, the service server may be further included in the system configuration. The service server refers to a device operated by a service entity that provides a product or a service, and the device also includes a central control unit and a memory. For reference, the service subject mentioned in the detailed description may include a subject that provides a product or a service, such as a restaurant operator, a tourist manager, a festival operating in a tourist destination, a business entity selling goods, and the like.

Referring to FIG. 2 again, a process of providing a hash tag correction service will be described. In the method of providing a hash tag correction service according to the first embodiment, when a user uploads a post to an SNS server through a user terminal, the SNS server determines whether the hash tag in the post needs to be corrected and needs correction. If it is determined, the calibration guide message is transmitted to the user terminal. This will be described in detail below.

The hashtag correction service providing method according to the first embodiment may be started by sharing reference data between the service server and the SNS server in advance. The reference data may include various pieces of information for identifying the service subject, for example, location information of the service subject, name of the service subject, and the like, and reference images related to goods or services provided by the service subject. , Reference images, and the like, and further, reference texts previously designated by the service subject may be further included. For example, assuming that the service subject is a particular restaurant, reference data includes the restaurant's location information (address or GPS / GIS information), the restaurant's name, the image of the food sold in the restaurant, the image of the restaurant's exterior (signboard), The reference data may include a plate image provided, a table setting image when a food is provided to a consumer in the restaurant, a plurality of food names predefined in the restaurant, abbreviations of the restaurant name, and the like. For reference, the location information may be displayed as a range of a range including a specific location of the corresponding service subject. For example, when the location point of a restaurant is P, a radius of 50m around the point P may be represented as location information. have.

On the premise that the above reference data is shared, the method for providing a hash tag correction service according to the first embodiment uploads a post to a SNS server after the user edits a post and inputs a hash tag on the user terminal (S220). It can be started from the step of making a request. (S230) Steps S220 and S230 may be understood as a step in which a user edits a post by using an SNS application installed in his terminal and requests an upload of the post to the SNS server by pressing an upload button. May include content such as an image (picture), audio, video, etc., and may also include hashtags and other texts directly input by the user, location information of the corresponding user terminal upon request for uploading the post, and terminal identifier. have. In this case, the terminal identifier may include a telephone number of the user terminal, an ID of the user, a product number of the user terminal, and the like, and other types of letters, numbers, letters and numbers for identifying the user terminal or the user. Combinations, biometrics, and the like.

After step S230, the SNS server may determine whether the hash tag needs to be corrected for the post that has been the upload request. Referring to FIG. 3, in more detail, a process of determining whether a correction is necessary is described. In step S241, a service subject corresponding to at least one information in the post is specified (S241). The hash tag in the post may be divided into a step S242 of determining whether a correction is necessary by comparing whether or not the service principal is the same as a keyword previously shared or requested.

First, in step S241, before deciding directly whether a hashtag in a post needs to be corrected, it is a step of specifying which service subject the post is written to, which service subject corresponds to. This step may be performed by utilizing reference data provided by the service entity in advance, and typically, location information, reference image, and reference text may be utilized.

First, referring to an embodiment using location information with reference to FIG. 4, as mentioned above, a service principal may share location information in advance, and the SNS server may include location information of a service principal in the post. By comparing it with the information, you can specify which service entity the post corresponds to. For example, if the location information previously shared by the service subject is P and the location information included in the post is also P, the SNS server may determine that the post corresponds to the service subject. Alternatively, when the location information shared by the service entity in advance is a specific range centering on P and P, and the location information included in the post is P 'included in the range, the SNS server indicates that the post is the service. It may be determined that it corresponds to the subject.

Next, an embodiment using a reference image will be described with reference to FIG. 5A, and the SNS server may specify a service subject by comparing a reference image previously shared with a content image included in the post. This process may be a variety of known image analysis methods, such as image analysis method for separating the objects in the image, image analysis method for determining the similarity by comparing the RGB values in the image may be used. That is, in this step, the similarity between the reference image and the content image in the post may be compared, and if the similarity value is greater than or equal to the threshold value, it may be specified that it corresponds to the service subject.

5 (b) is an embodiment for better understanding of the present invention. It is assumed that a menu sold by a particular restaurant is shared as a reference image. When the user uploads a post, the user may take a picture of a menu eaten at a restaurant and upload it. In this case, the same menu provided in the same restaurant may have a high similarity when analyzing an image. In particular, the color or shape of an object within the image, such as the color of the food, the color and shape of the plate on which the food is placed, the shape of the table on the plate or silverware, and the shape of the object on the table. When compared to the main part can be compared, accordingly, the SNS server can specify that the target corresponding to the post is the service subject.

For reference, FIG. 5 (b) has been described as only an image including a menu (food) sold by the service entity for the purpose of understanding the invention, but as mentioned above, the reference image may include various objects, For example, it may be a picture of the exterior and signboard of a restaurant, an interior space of a restaurant (arrangement of furniture and furniture), and a photograph of an entrance to a tourist attraction if the service principal is a person who operates a tourist site (not a restaurant). If the image includes an object for analyzing an image that can identify the subject of the service, such as a picture of a main attraction in a tourist spot or a picture of a festival banner hanging in the tourist spot, the reference image may be included without limitation.

In addition to the location information and the reference image, the SNS server may specify the service subject by using the reference text. The post requested to upload may include text, which may include a plurality of hashtags and content texts other than hashtags (text entered by the user in addition to the hashtag). The SNS server may determine whether the post corresponds to the service subject by comparing hashtags in the post or content text other than the hashtag with reference texts previously shared from the service subject. For example, the SNS server may determine the similarity based on how many keywords match the plurality of hashtags and the reference texts in the post, or how many keywords match the content text and the reference texts in the post. Can be. On the other hand, the SNS server may separately calculate the similarity for each of the keywords when comparing the hash tag or the content text with the reference text. For example, in the example of MOLINA's of FIG. 1, if the SNS server has previously shared MOLINA as the reference text and the hashtag included in the post is MOLIMA, it is recognized that 5 out of 6 characters have the same arrangement and alphabet. Can be used to determine similarity.

As described above, in step S241, the SNS server can identify the service subject corresponding to the post by comparing the information included in the post with the reference data previously shared from the service subject. Meanwhile, in the above description, only the example in which the location information, the reference image, and the reference text are used to separately specify a service subject are described. However, the step S241 is not performed based on any one reference data. It should be understood that several of these can be used in combination. For example, in the above embodiment, the SNS server refers to all the location information, the reference image, and the reference text, calculates the probability that the post corresponds to the service subject for each reference data, and then averages or sums these values. Finally, the service subject to which the post corresponds may be specified. In this case, in particular, the probability operation based on location information may function to greatly reduce the candidate group of service subjects corresponding to the post, and in addition, when additional calculations such as reference images and reference texts are performed, You will be able to specify the service principal more accurately.

On the other hand, after the service subject corresponding to the post is specified in step S241, the SNS server compares the keywords shared from the service subject in advance with the hash tag in the post, so that the hash tag is incorrectly input, that is, correcting the hash tag. Determine if it is necessary. If a service subject is specified, keywords corresponding to the service subject, that is, reference texts shared in advance from the service subject may also be specified, so that these keywords may be compared with hash tags in the post. In this comparison process, it is possible to determine whether or not the hashtag in the post is incorrectly input.

With reference to FIG. 3, the SNS server has been described in the step S240 of determining whether a correction is necessary for a hash tag of an uploaded post.

Referring back to FIG. 2, when it is determined that the hashtag does not need correction in step S240, that is, when it is determined that the hashtag is input with the correct name, the SNS server does not take any special action on the post. On the contrary, if it is determined that the hashtag needs to be corrected, the SNS server may transmit a calibration guide message to the user terminal that has made the upload request. (S250) The calibration guide message may include information indicating which hashtags of the hashtags input by the user are incorrectly input, and furthermore, whether the service subject corresponding to the post matches the service subject originally intended by the user, The post may further include information asking whether there is a willingness to modify the hashtag in the post.

On the other hand, the user who receives the calibration guide message from the SNS server can edit the posts, that is, modify the hash tag using his user terminal and can request a re-upload to the SNS server for the modified post. (S260, S270)

Afterwards, the SNS server may again determine whether or not a correction is required for the post that has been requested to be uploaded again (S280). The determination of the necessity of correction in this step may be performed by the same process as in the previous step S240, or By comparing the modified hashtag with the reference texts of the specified service subject, it is possible to confirm only that the hashtag that needs to be corrected is correctly corrected.

On the other hand, the SNS server may report the calibration results to the service server side to inform the service subject of the calibration contents, calibration results, and the like. (S290)

The method for providing a hash tag correction service according to the first embodiment and a system therefor have been described above with reference to FIGS. 2 to 5.

6 is a flowchart illustrating a hash tag correction service providing process according to a second embodiment. When comparing the first embodiment and the second embodiment, the first embodiment in the first embodiment, if the calibration necessity determination is made by the SNS server, the second embodiment is that the calibration server needs to determine whether calibration is necessary. That is, the subject who determines whether or not correction is necessary is different. Hereinafter, a hash tag correction service providing process according to the second embodiment will be described in detail.

The second embodiment may be started from a step in which a user edits a post and inputs a hash tag on a user terminal (S610) and then uploads a request to the SNS server for the post. At this time, the post requested to be uploaded may include a content image, a hash tag, and a content text, and may also include location information of the user terminal at the time of upload.

After step S620, the SNS server determines whether the post is a post corresponding to a service subject that has been contracted in advance, instead of determining whether the post is requested to be corrected for the uploaded post, and determined to correspond to the service subject. In this case, the upload notification may be transmitted to the service server (S630). In this case, the SNS server may use the location information in the post as a criterion. That is, if the location information uploaded from the post and the location information previously shared from the service subject are the same or within the range, the service server is notified of the upload of the post. The upload notification transmitted by the SNS server to the service server may include at least one of location information, content image, content text, hashtag, and terminal identifier of the user terminal included in the post.

After the step S630, the service server itself determines whether or not the correction necessary for the hash tag in the post (S640), at this time, the determination of the need for calibration may proceed in the same process as the step S240 described in the first embodiment. have. However, since this step is performed directly by the service server, unlike the SNS server of the first embodiment using reference data shared in advance from the service server, the service server utilizes reference data stored directly by the service server. There is a difference. In the same context, in the first embodiment, a separate step in which the service server and the SNS server share the reference data in advance may be included, but in the second embodiment, it is understood that the step of sharing the reference data is not necessary.

On the other hand, if the service server determines that the hash tag of the post does not need to be calibrated in particular at step S640, it may not take any further action.If it is determined that the hash tag needs to be calibrated to the user terminal, A calibration guide message can be sent. In operation S650, the calibration guide message may include information informing which hashtags of the hashtags input by the user are incorrectly input.

After the step S650, the user can edit the posts on the user terminal, that is, modify the hashtags, and can request the upload again to the SNS server for the modified posts. (S660, S670)

Thereafter, the SNS server may again transmit an upload notification to the service server for the post that has been requested to be uploaded again (S680), and the service server that has received the upload notification again determines whether the corrected hashtag needs to be corrected. (S690) can be.

With reference to the drawings, a method for providing a hash tag correction service according to the present invention and a system therefor have been described.

On the other hand, the hash tag correction service providing method described above may be provided in conjunction with other services. FIG. 7 illustrates an application example of a method for providing a hash tag correction service, and illustrates an embodiment in which a hash tag correction service providing method is included in a stamp service providing method for actively inducing a hash tag input of users. . Briefly describing the example of FIG. 7, when the visitor uploads an SNS post including a specific hash tag in a tourist destination, the SNS server 500 notifies the service server 300 of the visit, and the service server 300. Relates to a service for providing a stamp after determining whether to provide a stamp to the visitor, among which, when the service server 300 determines whether to provide a stamp to the visitor, whether the hash tag in the post needs to be corrected or not is required. Including the judging process enables the visitor to correctly upload the wrongly uploaded hashtag. For reference, the stamp referred to in this detailed description is a kind of compensation provided to the user terminal 100, and the stamp is used as a discount coupon when purchasing goods or services in the future according to the intention of the visitor, or several stamps. In the case of collecting and presenting the present, it can be used for the purpose of receiving souvenirs. In addition, in this detailed description, the term stamp is used to help understand the invention, and it should be understood that the stamp includes all types of rewards given for uploading a post that satisfies certain requirements.

Referring to FIG. 7, a system for implementing the above application example may include a user terminal 100, a service server 300, and an SNS server 500. Since each configuration has already been described above, a detailed description thereof will be omitted. However, in the above-described embodiments, the service server 300 has been described as being a server of a restaurant. In this example, the service server 300 is operated by a person who operates a park sightseeing spot including a mountain, the sea, a river, and the like. It is assumed that the server is maintained.

The service providing method of FIG. 7 may be started from the service server 300 sharing the condition for the post that is the target of the upload notification to the SNS server 500 in advance. (S10) This process may be implemented in such a way that the conditions determined by the contractual relationship between the person who operates the tourist site and the person who provides the SNS service are shared with the SNS server 500 from the service server 300. For example, the service server 300 may request the SNS server 500 to notify the service server 300 when posts including the corresponding location information are uploaded by transmitting location information corresponding to the area of the tourist destination. For example, when the service server 300 is operated by the natural park A, location information corresponding to each location within the range of the natural park A may be transmitted to the SNS server 500.

On the premise that location information sharing between the service server 300 and the SNS server 500 is completed, the above service providing method includes the step of requesting the user terminal 100 to upload a post to the SNS server 500 (S710). Can be started. S710 may be understood as a step in which a user requests a post editing and upload request using an SNS application installed in his terminal. For example, a user may print advertisements attached to a tourist destination (advertisement printed on a bulletin board or a banner, Posts can be uploaded voluntarily to obtain stamps after receiving advertisements for the stamp service from advertisement banners posted on web pages operated by tourist sites. On the other hand, the post may include a hash tag input by the user as well as the image, voice, video, location information of the user terminal 100 when the upload request, and the terminal identifier of the user terminal 100. In this case, the terminal identifier may include a telephone number of the user terminal 100, an ID of the user, a product number of the user terminal 100, and the like, and all other kinds of the user terminal 100 or the user who can specify the user. Letters, numbers, combinations of letters and numbers, biometrics may be included.

After operation S710, the SNS server 500 may store or register a post that has been uploaded, and then determine whether the uploaded post is a notification target. The notification subject refers to a post that satisfies a condition (condition for a post targeted for notification) received from the service server 300 in advance, for example, location information corresponding to a specific tourist destination. When the upload request for the post including the SNS server 500 may determine this as the notification target. Furthermore, the SNS server 500 may determine that the notification target is included even if a specific keyword is included as a hash tag in addition to the location information. For example, when a post requested to be uploaded by the user terminal 100 includes location information corresponding to A natural park, that is, location information (GPS information, etc.) included in the post is in the area of A natural park. In this case, it may be determined as a notification target.

When the post that is the notification target is uploaded in step S720, the SNS server 500 may notify the service server 300 that the post has been uploaded. In this step, the SNS server 500 may transmit the hash tag and the terminal identifier included in the post to the service server 300. The location information contained in the post is already selected by the SNS server 500 to satisfy the condition (location condition), so it will be less necessary to be delivered separately to the service server 300, but the configuration of the system In accordance with the SNS server 500 may also deliver the location information included in the post to the service server 300.

In operation S730, the service server 300 receiving the upload notification may determine whether the user terminal 100 that uploads the post satisfies a requirement to receive a reward, that is, meets a requirement to receive a stamp. In this step, the service server 300 may determine whether a stamp is provided after determining whether a specific keyword, that is, a specific hashtag is included in the post. For example, if a post includes a keyword related to a tourist destination, such as a tourist destination name, a tourist festival name, a tourist destination zone name, a tourist restaurant name, and the like as a hashtag, the service server 300 may determine that the post is to be provided with a stamp. have. On the contrary, although the posts selected as uploaded in the tourist destination are not included as hashtags as described above, the service server 300 may determine that the posts are not provided for stamps. For example, if the above post contains hashtags such as #keyword A, #keyword A_natural park, #keyword A_cherry blossom, etc., it can be determined that the stamp is provided, and the above hashtags are not included. If not, it may be determined that the stamp is not provided.

On the other hand, when determining whether or not to provide a stamp in step S740, it can also determine whether the hashtag in the post needs to be corrected. For example, although the post was selected as uploaded from a tourist spot, a hashtag that incorrectly printed the touristic name or a hashtag that incorrectly printed the touristic festival name was notified of the stamp. It can also be implemented to guide. The calibration necessity determination process may be performed in substantially the same process as step S240 described in the first embodiment. However, in the present application, since the service server directly determines whether it needs to be calibrated, it may utilize reference data stored directly by the service server as in the second embodiment described above.

Specifically, in step S740, the service server specifies which service subject the hashtag in the post corresponds to by using at least one of the location information, the reference image, and the reference text, and after the service subject is specified in advance, By comparing the stored hashtags with hashtags in the post, it is possible to determine whether a hashtag is incorrectly input, that is, whether the hashtag needs correction. For example, if a visitor enters a hash tag called #B Nature Park or #B_Cherry Blossom after visiting A Nature Park, the service server compares the content image in the post, the content text with the previously stored reference image, and the reference text. By doing so, it can be determined that the post is intended for A natural park, and through this, a service server (the service server is a server maintained by the operator of A natural park) can be specified as a service subject. Thereafter, the specified service server may determine that the hash tag needs correction by comparing the keyword (eg, A natural park) stored in advance with the hash tag in the post.

When it is determined in step S740 that the post is to be provided with a stamp, the service server 300 provides a reward, that is, a stamp to the corresponding user terminal 100 with reference to the terminal identifier received together when receiving the upload notification for the post. can do. The stamp provided at this time may be provided in various ways such as a text message, a chat application message, an application push message, and the form may be various forms such as numbers, letters, numbers and letters, QR codes, and barcodes. have.

On the other hand, if it is determined in step S740 that the stamp is not subject to the service, the service server 300 may transmit a message indicating that the post is not a stamp to be provided to the user terminal 100, and at this time to deliver a calibration guide message with Can be. (S750b)

When it is determined that the stamp is not provided and the calibration guide message is delivered, the user terminal may modify the hashtag according to the calibration guide message and request a reupload to the SNS server (S760). By notifying the service server of the re-upload again (S770), the service server may issue a stamp to the corresponding user terminal. (S780)

Meanwhile, the service method of FIG. 7 allows users to upload a large number of hashtags, that is, hashtags correctly input by calibration, and further adds a congestion calculation based on the uploaded hashtags. This starts from the step S790 in which the service server 300 requests information about posts including a specific hash tag. The service server 300 may request information on posts including a specific hash tag to the SNS server 500. For example, the service server 300 may be associated with a tourist destination such as a tourist destination name, a tourist festival name, an area name in a tourist destination, and a restaurant name in a tourist destination. You can request information about posts that contain keywords as hashtags. For example, the service server 300 may request information about posts including #A natural park, #A or #A_cherry blossoms as hashtags from the SNS server 500. The use of hashtags, that is, texts, for data collection for congestion calculation is to increase the efficiency of calculations compared to analyzing images when analyzing congestion in a conventional area. The density of crowds is analyzed by analyzing images in images or pictures. This is because identifying the congestion based on text is advantageous in terms of resource utilization and computation speed, compared to grasping.

After the information of the posts including the specific hash tag is received in operation S790, the service server 300 may collect location information of the corresponding posts. (S800) The information of the above posts may include the location information when the post was uploaded, the service server 300 is the location information of the posts uploaded from the corresponding tourist attractions among the posts containing the hashtag corresponding to the corresponding tourist attractions By collecting only the congestion can be calculated. (S810)

Steps S790 to S810 may be performed based on a predetermined period, for example, 10 minutes, and thus indirectly determine the congestion degree of the tourist destination based on the number of posts or hashtags uploaded in the tourist destination. Can be. For reference, the stamp providing service and the hash tag correction service of steps S710 to S780 described above may calculate the congestion degree by allowing the service server 300 to secure a larger number of post information and location information in steps S790 to S810. Is to increase the accuracy.

Meanwhile, step S810 of calculating a congestion degree based on the hash tag and the location information of the post including the hash tag may be implemented in various ways. For example, the first number of posts or hashtags uploaded in the tourist destination is preset. If the threshold value is exceeded, it can be displayed as [congestion], if it is less than the second threshold value, [free], and if it is equal to or less than the second threshold value, the value is [normal]. Alternatively, congestion can also be expressed numerically, for example, when 100 is defined as very congested, numbers less than 100 are less congested, and values greater than 100 are relatively congested. It can also be displayed to indicate status.

As another method, the service server 300 may calculate a congestion degree for each region after dividing the tourist spot into detailed regions. For example, if there are a total of five subdivisions (Zone A, Zone B, Zone C, Zone D, Zone E) in the tourist destination, the service server 300 hashtag corresponding to each subdivision in the SNS server 500. Can request information of the posts, and can calculate the congestion degree of each of the sub-zones based on the location information of the received posts. After the congestion degree for the zones A to E is calculated, the service server 300 may add up all of these congestion levels and then calculate the congestion degree at all tourist sites. For example, if the degree of congestion in each subdivision is calculated as a numerical value, the sum of the sums can be averaged and expressed as the degree of congestion in the entire tourist destination.

Meanwhile, the embodiment related to the above-mentioned congestion calculation and congestion indication is just one example, and the congestion calculation and congestion indication may be made based on a hashtag-based post information request and location information extracted from received post information. There is no limit to the way of finding the degree of congestion.

On the other hand, the service server 300 may further collect visual information as well as location information from the information of the posts received in step S790. That is, the service server 300 may grasp the congestion degree in the tourist spot by time zone by further collecting at what time the post including the hash tag is uploaded. For example, if you post posts containing the hashtag #ANature Park, uploaded within the area A and uploaded between 12:00 PM and 1:00 PM on August 2, 2018, You can indirectly grasp the congestion of the time zone within.

For reference, steps S790 to S810 are not necessarily performed continuously with steps S710 to S780, and it is understood that steps S790 to S810 may be performed independently regardless of steps S710 to S780.

With reference to FIG. 7, the embodiment in which the hash tag correction service is provided in the process of providing the stamp service by the service server has been described.

For reference, the application example of FIG. 7 has been described as including a process of providing a hash tag correction service at the same time in the process of providing a stamp service, the service server, the combined application of the stamp service and hash tag correction service is shown in FIG. In other words, the SNS server may be implemented as a subject to provide a hash tag correction service.

Specifically, referring to FIG. 8, steps S910 to S990 correspond to steps S210 to S290 of FIG. 2 described above. However, after the step S990, the service server receiving the calibration result report corrects the hash tag in the user terminal. By providing a stamp (S1000) as a reward for doing so, the user may be prompted to input a more accurate hashtag when uploading a post.

On the other hand, those skilled in the art will recognize that the present invention can be implemented in other specific embodiments without changing the technical spirit or essential features. Therefore, it should be understood that the above-described embodiments are merely exemplary and are not limitative in scope. In addition, the flowcharts shown in the drawings are merely exemplary sequential sequences shown in order to achieve the most desirable results in practicing the present invention, and other additional steps may be provided, or some steps may be omitted. .

The technical features and implementations described herein may be embodied in digital electronic circuitry, implemented in computer software, firmware, or hardware, including the structures and structural equivalents described herein, or a combination of one or more of these. It can be implemented. Also, an implementation implementing the technical features described herein is a module relating to computer program instructions encoded on a program storage medium of tangible type for controlling or by the operation of a computer program product, ie a processing system. It may be implemented.

The computer readable recording medium may be a machine readable storage device, a machine readable storage substrate, a memory device, a composition of materials affecting a machine readable propagated signal, or a combination of one or more thereof.

Claims (10)

In the method of providing a hashtag correction service, The user terminal forwarding an upload request to the SNS server for the post, the post including at least one hashtag; Determining, by the SNS server, whether a hash tag included in the post needs to be corrected; Containing, How to provide hashtag correction service. The method of claim 1, After the SNS server determines whether the hash tag needs correction, If it is determined that the hash tag needs to be corrected, an SNS server transmitting a calibration guide message to the user terminal; Further comprising, How to provide hashtag correction service. The method of claim 1, Determining whether or not the SNS server needs to correct the hash tag, Specifying a service principal corresponding to at least one information in the post; Comparing a hash tag in the post with a keyword corresponding to a service subject to determine whether the hash tag needs correction; Containing, How to provide hashtag correction service. In the SNS server provides a hash tag correction service, Receiving an upload request from a user terminal for a post, wherein the post includes at least one hashtag; And Determining whether the hash tag included in the post needs to be corrected; Containing, How to provide hashtag correction service. The method of claim 4, wherein After determining whether you need to calibrate, Transmitting a calibration guide message to the user terminal when it is determined that the hash tag needs to be corrected; Further comprising, How to provide hashtag correction service. The method of claim 4, wherein Determining whether the calibration is necessary, Specifying a service principal corresponding to at least one information in the post; Comparing a hash tag in the post with a keyword corresponding to a service subject to determine whether the hash tag needs correction; Containing, How to provide hashtag correction service. The method of claim 6, Specifying a service principal corresponding to at least one information in the post, Comparing the reference data previously provided from the service principal with at least one information in the post, How to provide hashtag correction service. The method of claim 7, wherein The reference data is, Including at least one of location information, reference image, or reference text, How to provide hashtag correction service. In the method of providing a hashtag correction service, The user terminal forwarding an upload request to the SNS server for the post, the post including at least one hashtag; Determining whether the SNS server is a notification target for the post, and if it is determined that the notification target is a notification target, transmitting an upload notification to a service server; And Determining, by the service server, whether the hash tag included in the post needs correction; Containing, How to provide hashtag correction service. In the method by which the service server provides hashtag correction service, Receiving an upload notification from the SNS server, indicating that the post has been uploaded from any user terminal; Determining whether a correction is necessary for the hashtag included in the post; Containing, How to provide hashtag correction service.

Images