KR101337398B1 - Method and system for comprising user interface page - Google Patents

Abstract

The present invention relates to a method and system for constructing a user interface page. In the method of constructing a user interface page according to the present invention, a plurality of content registration windows having an input activation state in which a user input is permitted and an input inactivation state in which the user input is not allowed are disposed in a plurality of specific positions of the user interface page. Wow; If there is content input from the user in the input activation state window among the arranged content registration windows, the contents input from the user are matched with the corresponding content registration window to register and display the contents and the corresponding content registration window is switched to the input inactive state. Steps; And individually switching the input activation state to the input activation state when a preset time elapses from the time when the user input is registered for each of the input deactivation windows.

Description

METHOD AND SYSTEM FOR COMPRISING USER INTERFACE PAGE}

The present invention relates to a method and system for constructing a user interface page. More particularly, the present invention relates to a method and system for constructing a user interface page that can be input by a user while providing predetermined information to a user.

Recently, due to the development of communication technology, various information and opinions are exchanged online.

For example, netizens can leave various information or personal daily life on their blogs, post on each other's bulletin boards for discussion, or register a short message on Twitter using a communication terminal. In this case, various forms such as reply or comment may be used for mutual communication.

As such, online, especially on the web, a variety of opinions and information can be viewed and users can directly enter the pages. These pages can be operated by the user to register information or to register information registered by other users. It is a kind of 'user interface page' in that it is browsed.

In other words, each user inputs his or her desired content on the user interface page so that others can view it, while other users check the registered contents.

An example of a user interface page is the blog mentioned earlier.

A blog has its own owner (e.g. the blog administrator) who registers specific content so that visitors can view the registered content and has a 'comment' system so that visitors can comment on their comments in the form of comments. It allows you to register on the page.

For this purpose, the blog page is provided with a 'comment input window' and visitors can enter and register contents through the comment input window.

However, in a conventional user interface page such as a blog, visitors' comments are registered in almost the same way. For example, when a visitor enters contents through a comment input window, the input contents are displayed in the order in which they are registered in the preset area. Will be displayed on.

In other words, visitors who enter comments through the comment input window could not prevent their comments from being pushed back (down) if they were registered at the top level when the comments were entered, but later entered by other visitors. .

This conventional method is not only limited to comments, but also used when visitors (or users) register their opinions, information, advertisements, etc. on various user interface pages.

However, such a conventional method (how the display position on the page of the input content is continuously changed) may not be a problem when visitors merely express their opinions as in the above-described example, but the contents of the advertisement may be This is a big problem or inconvenience for visitors who want to register.

That is, the change of the display position according to the content (advertisement) registration of another visitor's content has a problem in that the advertisement effect cannot be predicted, and the inconvenience of having to register repeatedly to maximize the advertisement effect.

On the other hand, a blog owner or a visitor who visits the blog may not like to see the advertising comments. Advertisement comments may be useful information or spam advertisements depending on the person, so it is desirable to process the advertisement comments by the choice of the blog owner or the blog visitor.

However, in the related art, spam processing was performed using a method of blocking an IP address or an ID of a user (visitor) who inputs an advertisement comment, and thus the same advertisement contents could not be completely blocked from being repeatedly registered. For example, if a visitor who enters an advertising comment enters an advertising comment using a computer with a different IP address or enters an advertising comment by signing up with a different ID, the new IP will not be blocked immediately. There is a hassle to block the address or ID.

In addition, if you block the IP address or block ID, there is a problem that all the comments of the computer or the user are spammed at once.

In particular, conventionally, the function of selectively blocking such advertising comments for each visitor of a blog has not been presented.

Patent Publication No. 2011-51678

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned conventional problems, and an object thereof is to allow a location of contents registered by users on a user interface page to be fixed, and also to select a user interface page manager or a visitor to the interface page. Accordingly, the present invention provides a method and system for constructing a user interface page to prevent registration of the same or similar advertisement content.

In order to achieve the above object, the user interface page configuration system according to the present invention provides a content registration window having an input activation state in which user input is allowed and an input inactivation state in which user input is not allowed. An arrangement unit arranged in plural in a position; A content registration unit that registers content input from the user by registering the content input window with the corresponding content registration window when there is content input from the user in the input activation state of the content registration window arranged by the batch unit; A display controller configured to control the registered contents to be included in the corresponding contents registration window and displayed; The contents registration window in which the contents registration has been registered is switched to the input deactivation state, and the input registration state is individually switched to the input activation state when a preset time elapses from the time when the user input is registered for each of the input deactivation windows. It is configured to include a state switching unit.

In addition, in order to achieve the above object, the user interface page configuration method according to the present invention comprises a content registration window having an input activation state in which user input is allowed and an input inactivation state in which user input is not allowed. Placing a plurality in a specific position of the; If there is content input from the user in the input activation state window among the arranged content registration windows, the contents input from the user are matched with the corresponding content registration window to register and display the contents and the corresponding content registration window is switched to the input inactive state. Steps; And individually switching the input activation state at the time when a preset time elapses from the time at which the user input is registered for each of the input deactivation windows.

As described above, according to the present invention, the content registration window is displayed in a fixed position on the user interface page and has an input activation or input deactivation status individually so that visitors who want an advertisement can check in advance where their advertisement is displayed. do. In other words, the content registration window that visitors select and input becomes an advertisement area.

In addition, the same or similar contents may not be registered in the content registration window according to the blind or blocking request of the administrator, thereby preventing the same spam advertisement from being registered differently.

1 is a functional block diagram of a system for constructing a user interface page according to an embodiment of the present invention.
2 is a detailed block diagram of a content register of FIG. 1;
3 is an example of configuration of a blog page according to an embodiment of the present invention.
4 to 5 are control flowcharts of a system for constructing a user interface page according to an embodiment of the present invention.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

The user interface page configuration system according to the first embodiment of the present invention includes a layout unit 110, a content registration unit 120, a display control unit 130, and a state switching unit 140 as shown in FIG. 1. do. In addition, the user interface page configuration system may further include a request receiver 150 and a filtering register 160.

In this case, the user interface page includes all pages having a state in which each user can input specific contents. For example, the user interface page may correspond to various online bulletin boards and individual web pages such as blogs.

The arranging unit 110 performs a function of arranging a plurality of content registration windows at a specific position of the user interface page. Here, the content registration window may perform a function of inputting predetermined contents (user opinion, information, advertisement, etc.) by the user, and may also perform a function of displaying the input contents.

The content registration window has an input activation state in which a user input is allowed and an input inactivation state in which a user input is not allowed. The arrangement unit 110 uses a plurality of content registration windows arranged in a user interface page to deactivate the input. Alternatively, the placement order remains fixed regardless of whether the input is active or not.

When the content registration window is in an input activation state, content input is possible from the user. When the content registration window is in an input inactive state, content input is not possible from the user. A detailed description thereof will be described later.

Here, the content registration window in an active state may correspond to a comment window in which a visitor of a blog may leave a post.

The content registration unit 120 performs a function of registering the content input from the user by registering it with the corresponding content registration window when there is a content input from the user in the input activation window among the content registration windows arranged by the placement unit 110. do.

That is, as described above, the contents registration window in the input activation state can be input by the user, and the contents registration unit 120 performs the function of registering the contents input by the user to the corresponding contents registration window. .

To this end, the content registration unit 120 may include a storage unit 121, a reception unit 122, and a registration control unit 125, as shown in FIG. 2, and furthermore, a payment page providing unit for payment processing ( 123 and the payment processing unit 124 may be further included.

Here, the storage unit 121 is a space in which various data are stored. As described below, the content input by the user may be matched with the input content registration window and stored in the storage unit 121. The storage unit 121 is preferably composed of a nonvolatile memory that retains the stored data even when power is cut off.

The receiver 122 performs a function of receiving (receiving) content (comment, information, advertisement, etc.) from the user. That is, the receiver 122 performs a function of receiving the content input by the user through the content registration window.

The registration controller 125 matches the content received by the receiver 122 with a corresponding content registration window and stores (registers) the content in the storage 121.

On the other hand, when payment processing is required for content registration through the content registration window, the payment page providing unit 123 and the payment processing unit 124 perform the function.

That is, the payment page providing unit 123 performs a function of providing a payment page to a corresponding user when content is received by the receiving unit 122. The payment page may include various input windows (or input fields) for inputting information required for payment processing.

When the user inputs payment method information (for example, card number, expiration date, CVS value, etc.) for payment processing on the payment page, and the payment method information is received in the receiving unit 122, the payment processing unit 124 is the corresponding payment method. The payment process is performed using the information.

Herein, the payment processing includes not only directly performing payment processing through a built-in database but also communicating with an external financial institution server to perform payment processing.

Since the payment process is performed online, the method itself corresponds to a known technology, and thus a detailed description thereof will be omitted.

The display controller 130 controls the registered contents to be included in the corresponding contents registration window and displayed. As described above, the content registration window may perform a function of receiving content from a user or display a content received from the user. The display control unit 130 may include a content registration window. It is to perform the function that is displayed in.

The state switching unit 140 switches the content registration window in which content registration is made to the input inactivation state, and individually at the time when a preset time elapses from the time when the user input is registered for each window of the input inactivation state. To switch to the input activation state.

That is, the state switching unit 140 switches the content registration window, which has already been registered, to an input deactivation state so that a new input is not made from another user.

However, the state switching unit 140 does not allow the content registration window that has been switched to the input inactive state to maintain its state, but sets a separate time for each content registration window to enter the input activation state when the corresponding time elapses. Control to switch.

This will be described with reference to FIG.

3 illustrates a blog page as an example of a user interface page. The blog page includes an area (first area) in which a post written by the blog owner is displayed, and a blog visitor can register and display the registered content. It is divided into an area (second area).

In the second area, a plurality of content registration windows that can be input by the visitor are fixedly arranged. For convenience, alphabets such as A, B, and C may be attached in order.

Although not shown, the registration request button and the blind button may be provided around each content registration window. That is, the registration request button may be displayed in the content registration window in the input activation state, and the blind button may be displayed in the content registration window in the input inactivation state because the content is already registered.

Initially, A, B, and C assume that input is active, and if a visitor requests registration by entering content in A (that is, clicking the Request Registration button after entering the information), the requested content is registered. In addition to being displayed, A switches to input inactivity. Switching the content registration window to the input inactive state can be done in various ways, for example, by switching the content registration window into a form of display window so that new content cannot be registered, or by making the registration request button invisible or inactive. Can be done.

If another visitor enters / registers the contents in C after 10 minutes, the registered contents are displayed and C is deactivated.

A and C are now inactive and B is inactive.

In this case, a blog visitor can enter new contents only in B at this time, but not in other contents registration windows A and C.

However, if the same time (for example, 5 hours) is set as so-called state recovery time for both A and C, A is switched to the input activation state 5 hours after the content registration time, and 10 After minutes (i.e., 5 hours from the time when the contents are registered in C), C is also switched to the input activation state.

Here, switching to the input activation state means that the registered contents are deleted and new contents can be input.

As such, each content registration window occupies a fixed area of the blog page regardless of whether the content is registered or whether the input is activated.

This approach can appeal to the visitors who wish to register advertising text on the blog page, for example, that their advertisement display position is fixed regardless of whether other visitors register the advertisement.

Here, the specific blog page in which an advertisement is displayed at a fixed specific location (that is, a content registration window is displayed) may correspond to a separate page separated by a Uniform Resource Locator (URL). In this case, separate content registration windows may be displayed for each URL.

For example, the first page and the second page of the blog may display different content registration windows.

As another example, specific blog pages in which a content registration window is displayed at a fixed specific location may be distinguished from each other even with the same Uniform Resource Locator (URL).

Recently, web pages displayed on a client terminal (web browser) can communicate with a web server while maintaining a URL, so that some contents of the web page can be changed. In this case, each specific content is called a separate page. Can be.

For example, even if the web page has the same URL, a page having different information may be displayed on the client terminal (user terminal) according to the visitor's selection. In this case, the pages displayed on the client terminal have the same URL. Even though it may be referred to as a separate page, in this case, different content registration windows may be separately managed for each separate page having the same URL.

Meanwhile, the request receiving unit 150 performs a function of receiving a blind processing request according to the administrator's selection of the corresponding user interface page for at least one of the content registration windows having the input deactivation state included in the user interface page.

For example, referring to FIG. 3, if a blog owner (blog page manager) thinks that a content registered in a content registration window by a visitor is a spam advertisement, a blind processing request (for example, a blind button click) is applied to the content registration window. The request receiving unit 150 may perform a function of receiving a request of the blog owner.

The filtering registration unit 160 performs a function of analyzing the contents, which are previously registered in the content registration window for which the blind processing is requested, in units of at least one word and then registering the contents as blind target contents.

For example, the filtering registration unit 160 may extract content registered in the content registration window for which the blind processing is requested, in sentence units or as a series of word bundles, and register the content as a blind target content. The hash value can also be calculated and registered as the content of the blind.

At this time, the display control unit 130 blindly processes the content registration window for which the blind processing is requested. In addition, the display control unit 130 newly registers the content registered by the content registration unit 120 according to a user's input when the content is similar to the blind target content registered by the filtering registration unit 160 or within the preset range. The blind process is also performed for the registered content registration window.

In this case, the blind processing means that the registered contents are not shown. For example, a blank image may be displayed on the registration display window so that the registered contents are not displayed, or only the message that the blind processing is performed is displayed on the content registration window. It can also be displayed.

In the blind processing of the present embodiment, since the content registration state is maintained as it is, that is, the content registration window keeps the input deactivation state, and thus, new content is added to the content registration window by another user (blog visitor) within a preset time. Although this cannot be registered, the present invention is not limited thereto.

The user interface page configuration system according to the second embodiment of the present invention may include the same configuration as the first embodiment described above. The registration content window is displayed at a fixed position on the user interface page and each registration content window is input. The function of individually controlling activation is the same, but there may be differences in the functions related to filtering.

That is, the request receiving unit 150 ′ of the user interface page configuration system according to the second embodiment of the present invention may manage an administrator of the corresponding user interface page for at least one of content registration windows having an input deactivation state included in the user interface page. Performs a function of receiving a block processing request according to selection of a.

The filtering registration unit 160 ′ analyzes the content previously registered in the content registration window for which the blocking process is requested in units of at least one word and registers the content as the blocking target content.

At this time, the content registration unit 120 'rejects the registration of the content input from the user when the newly input content has the same or similarity within the preset range as the blocking target content registered by the filtering registration unit 160'. do. For example, the content register 120 'may generate an error message (a message informing that it cannot be registered) and provide the user without registering the content input from the user in the storage 121'.

That is, in the first embodiment, the contents input by the user are registered and then blindly processed, whereas in the present embodiment, the contents input by the user are not even registered.

If not registered in this way, the corresponding content registration window is kept in the input activation state, and new content can be immediately input from other visitors.

In the above-described example, the components of the present invention have been described with specific examples, but each component may be divided into a plurality of devices rather than being implemented in any one hardware device.

For example, some of the above components may be configured in the user terminal, and others may be configured in the web server.

Hereinafter, with reference to FIG. 4, the control and signal flow will be described under the premise that the system for constructing a user interface page according to the first embodiment of the present invention comprises a visitor terminal and a web server. Here, the visitor terminal may correspond to, for example, a terminal manipulated by a visitor visiting a blog of another person, and the web server may correspond to a server that provides a blog service for each individual.

When the visitor terminal requests a blog page from a web server (step S1), the web server transmits a blog page of a specific individual provided to the visitor terminal (step S3).

The visitor terminal displays the received blog page (step S5), and if it detects a content input from the visitor to a predetermined content registration window (step S7), it transmits a content registration request signal to the web server (step S9).

When the web server transmits a payment page for content registration to the visitor terminal (step S11), the visitor terminal displays a payment page (step S13), and when the input of payment means information is detected from the visitor (step S15) Transfer to a web server (step S17).

Here, the payment amount may vary depending on the time when the registered contents are displayed (posted). For example, the visitor may set a time for which his / her registered contents are maintained in a corresponding content registration window, and the payment amount may be changed in real time according to the set time.

The web server performs payment processing using the received payment method information (step S19), matches the received content with a corresponding content registration window and registers it (step S21), and registers the content including the registered content. The blog page, i.e., the updated blog page which has changed the window to the input deactivation state, is transmitted to the visitor terminal (step S25).

Accordingly, the visitor terminal displays the updated blog page including the content registration window in which the content input by the visitor is displayed and the input is deactivated (step S27).

Of course, even when there is a request for a blog page of another visitor, the web server transmits the blog page in which the above-described content registration window is inactivated to the visitor terminal.

On the other hand, the web server determines whether the predetermined time has elapsed from when the content registration window is switched to the input inactive state at the request of the visitor (step S29), and if the predetermined time has elapsed, the web server matches the content registration window. The registered content is deleted (step S31) and the content registration window is switched to the input activation state (step S33).

Here, the web server may dynamically display the time remaining until the input activation state is changed for each content registration window in the input deactivation state of the blog page.

At this time, the web server may transmit the updated blog page (that is, the page whose content registration window is switched to the input activation state) to the visitor terminal (step S36), and thus, the visitor terminal switches to the state where the content registration window is waiting for new input. The displayed blog page is displayed (step S37).

Of course, even when there is a request for a blog page of another visitor, the web server transmits the blog page in which the above-described content registration window is activated to the visitor terminal.

Hereinafter, a process performed when the blog manager sets the blind process for a specific content registration window in the blog page will be described with reference to FIG. 5.

First, in the present embodiment, a terminal operated by an administrator is called an administrator terminal, and other web servers and visitor terminals are the same as those mentioned in FIG.

It is assumed that the administrator is currently receiving and viewing his blog page from the web server.

In this state, when the administrator requests blind setting for a content registration window in which an unused advertisement, for example, a spam advertisement, is registered among the content registration windows included in the blog page (step S51), the administrator terminal blinds the web server. The process request signal is transmitted (step S53).

The blind processing request signal may include information about a content registration window designated by the user for blind processing.

The web server blinds the corresponding content registration window (step S55). For example, the web server may delete the content registered in the corresponding content registration window or overwrite the blank image so that the content is not visible.

In addition, the web server analyzes the contents already registered in the content registration window for which the blind processing is requested, extracts the contents of the blind target, and registers them (step S57). The blind object content registered here is necessary to prevent re-registration of the same content later.

The web server transmits the blinded blog page, that is, the updated blog page to the manager terminal (step S59) according to the administrator's request (step S59), so that the manager terminal displays the blinded blog page on the content registration window designated by the manager. (Step S61).

On the other hand, when the visitor terminal requests the transmission of the blog page corresponding to the administrator described above (step S63), the web server transmits the blog page to the visitor terminal (step S65).

If the visitor terminal displays the received blog page (step S67) and detects content input by the visitor in any of the content registration windows included in the blog page (i.e., any of the input-enabled content registration windows). (Step S69) The content registration request signal is sent to the web server (step S71).

Here, the content registration request signal includes content input by the visitor to the content registration window.

Although the payment processing is omitted in the present embodiment, the payment processing may be performed as in the previous embodiment.

The web server determines whether the content received from the visitor terminal and the content registered as the blind target are the same (step S73). Here, if a plurality of contents registered as blind targets may be compared with each other, of course. The same can be done by comparing hash values.

If it is determined that at least one of the contents received from the visitor terminal and the contents registered as the blind target is the same, the web server transmits an error message indicating that the user cannot be registered as the new contents as the blind target in the visitor terminal (step S75). ).

That is, when at least one of the contents received from the visitor terminal and the contents registered as the blind target is the same, the web server performs error processing without registering the newly input contents. Of course, the registration process can be blinded.

Here, the web server may be configured to transmit an error message when there is similarity within a preset range even if it is not identical, for example, when 90% of the words are the same according to a preset condition.

5 illustrates that the blind processing request for the content registration window is made according to a request of a blog page owner, that is, an administrator. However, the blind processing request may be made according to a request of a visitor who visits a blog.

This example is shown in FIG. 6.

In FIG. 6, a visitor who visits a blog is divided into a first visitor (first visitor terminal) and a second visitor (second visitor terminal) for convenience of description. After the first visitor makes a blind request, the second visitor Shows the process of newly registered contents.

When the first visitor terminal transmits a blind processing request signal for a specific content registration window to the web server according to the request of the first visitor (step S81), the web server blinds the requested content registration window to the first visitor. To be processed (step S3). That is, the web server matches and registers the blind target content with the first visitor (step S84), and transmits the updated blog page with the corresponding content registration window to the first visitor terminal (step S85).

In this case, the web server matches the blind target with the visitor who requested the blind process. When the first visitor is logged in, the web server acquires first visitor information (user ID, name, email address, etc.) obtained by the login process. The blind target contents may be matched and registered. If the first visitor is not logged in, the blind target contents may be matched with the blind session contents (first visitor terminal IP address) and registered.

On the other hand, when the second visitor terminal transmits the blog page transmission request signal according to the operation of the second visitor (step S87), the web server transmits the blog page to the second visitor terminal (step S88).

The second visitor terminal displays the received blog page (step S89). At this time, the blog page displayed on the second visitor terminal displays a state in which the content registration window for which the first visitor requests blind processing is not blind processed.

This point is different from the process of blind processing request by the blog page manager in FIG. That is, the content registration window that is requested to be blinded by the blog page manager is blinded to all visitors who visit the blog page. However, as shown in the present embodiment, the content registration window that is requested to be blinded by the first visitor is created. Only one visitor is blinded and another visitor, that is, the second visitor, is not blinded.

When the second visitor terminal transmits a content registration request signal to the web server according to the operation of the second visitor (step S90) (step S91), the web server matches the received content with the content registration window and registers it (step S92).

At this time, when the first visitor terminal requests the transmission of the blog page (step S93), the web server blindly processes the first newly registered content with the first visitor by the second visitor terminal (i.e., previously blinded by the first visitor). Judge whether the content of the blind is the same, and if the determination result is the same (step S94), the content registration window newly registered by the second visitor terminal is blinded to the first visitor (step S95), and the blind processing is performed. The transmitted blog page to the first visitor terminal (step S96).

Accordingly, even if the first visitor is registered in the other content registration window of the blog page by another visitor (second visitor), the same content as the content included in the content registration window for which the blind visitor is requested is also newly registered. You can see the page (blog page) in the blinded state.

Of course, other visitors who do not request the blind process (for example, the third visitor) may view the contents registered by the second visitor in the content registration window when visiting the blog page.

In the above-described example, a case in which the same content as the first visitor requests the blind processing is newly registered is described as an example. However, as described above, the first visitor may be extended to a similar range. .

For example, the web server may be blinded to all new contents whose content of the registered blind target content and the phrase have a similarity of 80% or more (filtering ratio).

This filtering rate can be changed depending on how many visitors the blind process is requested.

That is, when 10 visitors request blind processing for the same content registration window (that is, the specific content registration window in which the advertisement content is registered), the content having more than 90% similarity with the content registered in the content registration window is newly registered. If only 100 visitors can request blind processing for the same content registration window, new contents that have more than 70% similarity with the contents registered in the content registration window are newly registered. Only blind treatment can be performed.

Furthermore, the web server may disadvantage the user who registered the blinded content, such as restricting the comment registration.In this case, the more visitors requesting the blinded process, the longer the input period of the comment to the user who registered the content. It can be a big disadvantage.

In FIGS. 4 to 6, the web server performs state switching (input activation state or input inactivation state switching) and blind processing in the content registration window as an example. However, the client script (eg, JavaScript) included in the blog page is used to perform the blind process. It may be performed on an administrator terminal or a visitor terminal.

In particular, the fixed placement and display of the content registration window are also included in the web page. The markup data or JavaScript can be interpreted in the administrator terminal or the visitor terminal.

That is, the function implementation according to the present invention is not necessarily performed by a specific server but may be achieved by cooperation between a plurality of devices.

In addition, in the above-described embodiments, the user interface page is an example of a blog page, but the present invention is not limited thereto. That is, the user interface page may correspond to a bulletin board used by many, or a web page visited for information retrieval or the like, or may correspond to various service providing pages that provide a personalized page while being shared. In particular, the user interface page may correspond to a social networking service page.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the invention. It is to be understood that such variations and modifications are intended to be included in the scope of the appended claims.

110: placement unit 120: content registration unit
130: display control unit 140: state switching unit
150: request receiving unit 160: filtering register
121: storage unit 122: receiving unit
123: payment page provider 124: payment processing unit
125: registration control unit

Claims (13)

In the user interface page configuration method performed by the system,
(a) disposing a plurality of content registration windows in a specific position of the user interface page having an input activation state in which user input is allowed and an input inactivation state in which the user input is not allowed;
(b) If there is a content input from the user in the input activation state window among the arranged content registration windows, the content input from the user is registered and displayed by matching the content registration window, and the corresponding content registration window is input inactive. Switching to;
and (c) individually switching the input activation state to the input activation state when a preset time elapses from when the user input is registered for each of the input deactivation windows. Way. The method of claim 1,
The plurality of content registration windows arranged on the user interface page maintain the arrangement order fixed regardless of whether the input registration window is switched to the input inactive state according to step (b) or the input activation state according to step (c). How to configure a user interface page, characterized in that. The method of claim 1,
Receiving a blind processing request according to a manager's selection of a corresponding user interface page for at least one of content registration windows having an input deactivation state included in the user interface page;
Performing blind processing on the content registration window for which the blind processing has been requested, and analyzing content previously registered in the blind content registration window in at least one word unit and registering the content as a blind target content;
And when the content having similarity within the preset range with the blind target content is newly input in the content registration window, performing blind processing on the newly input content registration window. Configuration method. The method of claim 1,
Receiving a blind processing request according to a visitor's selection of a corresponding user interface page for at least one of content registration windows having an input deactivation state included in the user interface page;
Blind-processing the content registration window for which the blind process is requested and analyzing the content previously registered in the blind content registration window in at least one word unit and registering the content as a blind target content;
And when the content having similarity within the preset range with the blind target content is newly input in the content registration window, blindly processing the newly entered content registration window for the visitor who visited later. How to configure user interface pages. The method of claim 1,
Receiving a block processing request according to an administrator's selection of a corresponding user interface page for at least one of content registration windows having an input deactivation state included in the user interface page;
Performing block processing on the content registration window of the block processing request and analyzing the content registered in the block content registration window in at least one word unit and registering the block content;
If a content having similarity within the preset range with the blocking target content is newly input in the content registration window, the user interface page configuration further comprises the step of blocking the content is newly registered in the content registration window. Way. The method of claim 1,
Registering the predetermined content in the content registration window in the step (b),
Detecting content input from the user;
Providing a payment page to the user;
Performing payment processing using the payment means information when the payment means information is received from the user;
And switching the content registration window in which the content input is made by the user to an input inactivation state and displaying the content input from the user in a corresponding content registration window. . A computer-readable recording medium having recorded thereon a program for implementing the method of any one of claims 1 to 6. In the user interface page composition system,
A disposition unit for disposing a plurality of content registration windows each having a input activation state in which a user input is permitted and an input deactivation state in which a user input is not allowed;
A content registration unit that registers content input from the user by registering the content input window with the corresponding content registration window when there is content input from the user in the input activation state of the content registration window arranged by the batch unit;
A display controller configured to control the registered contents to be included in the corresponding contents registration window and displayed;
The contents registration window in which the contents registration has been registered is switched to the input deactivation state, and the input registration state is individually switched to the input activation state when a preset time elapses from the time when the user input is registered for each of the input deactivation windows. User interface page configuration system comprising a state switching unit. 9. The method of claim 8,
The arrangement unit maintains a plurality of content registration windows arranged on the user interface page regardless of whether the input deactivation state or the input activation state is changed by the state switching unit. system. 9. The method of claim 8,
A request receiving unit configured to receive a blind processing request according to a manager's selection of a corresponding user interface page for at least one of content registration windows having an input deactivation state included in the user interface page;
A filtering registration unit for analyzing the content registered in the content registration window of the blind processing request at least one word unit and registering the content as blind target content;
The display control unit blinds the content registration window requested for the blind processing, and when the content newly registered by the content registration unit has similarity with the blind target content registered by the filtering registration unit within a preset range. And a blind process is performed on the content registration window where the newly registered content is matched. 9. The method of claim 8,
A request receiving unit which receives a blind processing request according to a visitor's selection of a corresponding user interface page for at least one of content registration windows having an input deactivation state included in the user interface page;
A filtering registration unit for analyzing the content registered in the content registration window of the blind processing request at least one word unit and registering the content as blind target content;
The display control unit blindly processes the content registration window requested for the blind processing for the visitor, and the content newly registered by the content registration unit is similar to the blind target content registered by the filtering registration unit within a preset range. And a blind process is performed on the visitor even for the content registration window in which the newly registered content is matched. 9. The method of claim 8,
A request receiving unit configured to receive a block processing request according to a manager's selection of a corresponding user interface page for at least one of content registration windows having an input deactivation state included in the user interface page;
The filtering processing unit may further include a filtering register configured to analyze content previously registered in the content registration window of the block processing request in at least one word unit and then register the content as blocking target content.
The content registration unit rejects the registration of the content input from the user when the content input from the user has a similarity within a preset range with the blocking target content registered by the filtering registration unit. Configuration system. 9. The method of claim 8,
The content registration unit,
A storage unit;
A receiving unit which receives contents input by the user and payment means information;
A payment page providing unit which provides a payment page to the user when contents are received in the receiving unit;
A payment processing unit which performs payment processing by using the payment means information when the payment means information is received in the receiving unit;
And a registration controller which matches the contents received from the user to a corresponding content registration window and stores the contents received from the user after the payment processing is performed by the payment processing unit.

Images