KR101061189B1 - Visitor identifying method using identification image and web server performing the same - Google Patents

Abstract

PURPOSE: A connector recognizing method using a unique identification image and a web server for implementing the same are provided to renew a connection history in case of transmitting a require-message about a web document to a web server using different terminals. CONSTITUTION: A first terminal transmits a first require-message to a web server(S100). The web server creates a unique ID about the first terminal(S110). A unique identification image about the first terminal is created(S120). The web server provides a web document in which the unique identification image is inserted to the first terminal(S130). The unique identification image is delivered from the first terminal to a second terminal(S140). The second terminal transmits a second require-message with the web server(S150). The web server extracts a unique ID by receiving the second require-message(S160). A connection history of the second terminal is renewed by recognizing a connector of the second terminal(S170). The web server provides the web document to the second terminal(S180).

Description

Accessor recognition method using unique identification image and web server performing the same {VISITOR IDENTIFYING METHOD USING IDENTIFICATION IMAGE AND WEB SERVER PERFORMING THE SAME}

The present invention relates to a visitor recognition method using a unique identification image and a web server performing the same.

When an Internet user visits a specific website on the Internet, a web server that operates the website automatically stores information such as the visitor's IP address and the number of accesses. This is called log information.

The operator of the web site analyzes this log information so that the visitor's behavior on the web server, such as the number of visits, the number of visits, and the page views of his web site, that is, how many of the visitors were pure visitors, You can identify the characteristics and behaviors of users who visit your website, such as whether you have visited the site or not.

For example, for an e-commerce website, the number of visits that represent the number of visitors to the website and the number of purchase conversions that represent the number of buyers who purchase the item from the visitor are important to effectively manage the website. It is used as data.

On the other hand, in the prior art, when generating log information, the visitor is mostly recognized based on a login ID, or the visitor is recognized based on a cookie, an IP address, or the like of the access terminal.

Therefore, in the case where the same accessor connects a plurality of times without logging in from a specific terminal, it is not possible to recognize whether the same accessor is the same accessor. In addition, even in the case of recognizing the visitor based on the cookie, IP address, etc. of the access terminal, when the same accessor is connected through a plurality of different terminals (a personal PC, a mobile phone, etc.), whether or not the user is still the same accessor is recognized. I could not. Therefore, considering that a large number of Internet service users access the web server through a plurality of terminals, there is a problem that log information stored in the web server does not properly reflect the characteristics and behavior of the web service user.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned problems, and an object of the present invention is to provide a method for accurately recognizing the accessor and a web server using the same even when the same accessor accesses a web server through a plurality of different terminals.

A technical means for achieving the above-described technical problem, In the visitor recognition method using a personalized unique identification image according to the first aspect of the present invention, Receiving a first request message for a web document from the first terminal, Generating a unique ID for the first terminal, generating a unique identification image for the first terminal using the unique ID, and inserting the unique identification image as a response to the first request message. Providing a web document to the first terminal; receiving a second request message for the web document from a second terminal having the unique identification image; parsing a unique ID included in the second request message Extracting and recognizing an accessor of the second terminal using the unique ID, And updating and recording the access history for the accessor.

Further, in a web server providing a personalized unique identification image according to a second aspect of the present invention, a message receiving unit for receiving a first request message and a second request message for a web document from a first terminal and a second terminal, respectively A unique ID generating unit for generating a unique ID for the first terminal, a unique ID image generating unit for generating a unique ID image for the first terminal using the unique ID, and a response to the first request message. As a web document providing unit for providing a web document inserted with the unique identification image to the first terminal, a unique ID extraction unit for parsing and extracting a unique ID included in the second request message and using the unique ID A connection history for recognizing an accessor of a second terminal and updating and recording a connection history for the accessor of the second terminal; Including the bride.

According to any one of the problem solving means of the present invention described above, it is possible to recognize the accessor of each terminal based on the unique ID included in the request message, and update the access history for the recognized accessor.

In addition, according to any one of the problem solving means of the present invention described above, even when the same accessor sends a request message for the web document to the web server using a plurality of different terminals to recognize this as the same accessor to update the access history can do.

In addition, according to any one of the problem solving means of the present invention described above, the accessor can receive the same web service optimized for him through the other terminal.

1 is a block diagram illustrating a method for identifying a visitor according to an embodiment of the present invention.
2 is a flowchart illustrating a user recognition method according to an embodiment of the present invention.
3 is a diagram illustrating a connection history table according to an embodiment of the present invention.
4 is a block diagram illustrating a web server according to an embodiment of the present invention.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

Throughout the specification, when a part is "connected" to another part, this includes not only "directly connected" but also "electrically connected" with another element in between. . In addition, when a part is said to "include" a certain component, which means that it may further include other components, except to exclude other components unless otherwise stated.

1 is a block diagram illustrating a method for identifying a visitor according to an embodiment of the present invention.

The accessor recognition method according to an embodiment of the present invention may be performed by one or more terminals 100 and 150 and the web server 200.

In addition, the first terminal 100, the second terminal 150, and the web server 200 may include a local area network (LAN), a wide area network (WAN), or a value added network (VAN). A wired network 300 such as a mobile communication network, a mobile radio communication network, a satellite communication network, Bluetooth, a wireless broadband Internet (Wibro), a high speed downlink packet access (HSDPA), and the like. 300).

The first and second terminals 100 and 150 load web documents provided by the web server 200 through the HTTP protocol. To this end, the first and second terminals 100 and 150 are provided with an IP address for internet access, and a web browser for internet browsing is installed.

Here, the first and second terminals 100 and 150 may be implemented as a computer or a portable terminal that can access the web server 200 through the network 300. Here, the computer includes, for example, a laptop, desktop, laptop, etc., which is equipped with a web browser, and the portable terminal is, for example, a wireless communication device that ensures portability and mobility. , Personal Communication System (PCS), Global System for Mobile communications (GSM), Personal Digital Cellular (PDC), Personal Handyphone System (PHS), Personal Digital Assistant (PDA), International Mobile Telecommunication (IMT) -2000, Code CDMA Division type multiple access (WDM) -2000, W-Code Division Multiple Access (W-CDMA), Wireless Broadband Internet (WBRO) terminal, and the like can include all types of handheld based wireless communication devices.

The web server 200 according to an embodiment of the present invention receives request messages from the first and second terminals 100 and 150 and provides a web document for each request message. Through this, the first and second terminals 100 and 150 may access the web document through various networks 300. In addition, the web server 200 according to an embodiment of the present invention may recognize the accessor of each terminal (100, 150) based on the unique ID included in the request message, and update the access history for the recognized accessor. have.

In particular, when the same accessor transmits a request message for a web document to the web server 200 by using a plurality of terminals 100 and 150 different from each other, the web server 200 recognizes this as the same accessor and updates the access history. can do. This will be described in detail with reference to FIG. 2.

2 is a flowchart illustrating a method for recognizing a visitor according to an embodiment of the present invention, and FIG. 3 is a diagram illustrating a connection history table according to an embodiment of the present invention.

First, the first terminal transmits a first request message to the web server (S100).

The first terminal 100 may transmit a first request message to the web server 200 to access a specific web site. The first request message may include URL information of a web document for the corresponding web site. The first request message is transmitted to the web server 200 via the network 300.

Next, the web server receives the first request message, and generates a unique ID for the first terminal (S110).

The web server 200 receives the first request message and determines whether the first request message includes a unique ID. If the first request message does not include a unique ID, a unique ID for the first terminal 100 is generated.

The unique ID is generated by using the IP address of the first terminal 100 or by combining the type, version information, installation information of various applications or version information of the operating system installed in the first terminal 100. Identified identification information can be used. Or identification information stored in cookies, user data or flash data. Alternatively, the unique ID may be any serial number or combination of characters that the web server 200 assigns to the first terminal 100.

Next, a unique identification image for the first terminal is generated (S120).

The web server 200 generates a unique identification image for the first terminal 100 by using the generated unique ID. The unique identification image may be an image for visually representing the unique ID. In addition, uniquely identifying images include QR Code, Bar Code, Data Matrix, PDF 417, Maxi Code, Color Code, Gray Code and 3D Barcode. It may be any one of, but is not limited thereto. The generated unique identification image includes or encodes URL information and a unique ID of a web site provided by the web server 200.

Next, the web server provides a web document in which the unique identification image is inserted into the first terminal (S130).

The web server 200 inserts the generated unique identification image into the predetermined area of the web document. Thereafter, the web document in which the unique identification image is inserted may be transmitted to the first terminal 100 through the network 300. Web documents can include any type of web page. The transmitted web document may be displayed on the first terminal 100, and in particular, a unique identification image may be included in a specific area of the web document.

Next, the unique identification image is transferred from the first terminal to the second terminal (S140).

The unique identification image may be delivered by being captured by the second terminal 150. For example, the second terminal 150 may capture a unique identification image (eg, a QR code) displayed on the first terminal 100 using the camera device provided in the second terminal 150. have. In addition, the second terminal 150 may extract a unique ID by decoding the unique identification image. In this case, the second terminal 150 may retain the unique ID as well as the unique ID in the form of data.

In addition, the unique identification image may be network transmitted (eg, email, MMS, photo transmission, etc.) by the first terminal 100. For example, the first terminal 100 may extract the unique identification image from the web document and transmit the extracted unique identification image to the second terminal 150 through the network 300.

In this embodiment, the transmission of the unique identification image is illustrated as a capture by the second terminal 150 or a network transmission by the first terminal 100, but is not limited thereto and may be performed through any medium or method. have.

Next, the second terminal transmits a second request message to the web server (S150).

The second terminal 150 having the unique identification image transmits a second request message for the web document via the network 300. The second request message may include URL information and a unique ID of the web document.

Next, the web server receives the second request message, and extracts a unique ID (S160).

The web server 200 receives the second request message and determines whether the second request message includes a unique ID. If the second request message includes the unique ID, the web server 200 parses and extracts the unique ID included in the second request message. In addition, if the second request message includes a unique identification image, the web server 200 extracts a unique identification image included in the second request message, and then decodes and extracts a unique ID encoded in the unique identification image. Can be.

Next, the user of the second terminal is recognized and the connection history of the second terminal is updated (S170).

The web server 200 recognizes an accessor of the second terminal 150 using the extracted unique ID. Since the unique ID extracted from the second request message is transmitted from the first terminal 100, the web server 200 may determine that the accessor of the second terminal 150 is the same as the accessor of the first terminal 100. have.

In addition, the web server 200 may update and record the access history of the second terminal 150 based on the recognized user of the first terminal 150. When the access history is pre-stored in the database, the web server 200 may search the access history having a unique ID matching the unique ID of the accessor of the second terminal 150 in the database. If the web server 200 determines that the accessor of the second terminal 150 is the same as the accessor of the first terminal 100, the access history of the second terminal 150 is based on the access history of the first terminal 100. Can be updated on a basic basis.

As illustrated in FIG. 3, the access history may include a unique ID, whether a connection is made through a unique identification image, an access web page URL, and an access time.

The unique ID is provided by the web server 200 and is identification information about an accessor that can be recognized by the web server 200. When the visitor accesses the web server 200, the web server 200 identifies the visitor's unique ID, and determines whether the visitor's access is through the unique identification image and stores the access. In addition, the web page URL, the connection time, and the like, which are accessed by the visitor, can be recorded in the connection history.

For example, when the accessor of the second terminal 150 transmits the second request message to the web server 200, the accessor's unique ID, whether the access is made through the unique identification image, and the access web page URL are determined by the access request. Can be inserted into predefined fields. The web server 200 may parse and extract the accessor's unique ID, whether the access is made through the unique identification image and the access web page URL from the second request message, and record the extracted access web page URL in the access history table.

If the unique IDs are the same, it is determined that the same user is connected. To this end, the web server 200 may search for a unique ID matching the unique ID of the accessor of the second terminal from the access history table. For example, if a visitor having a unique ID of `a1234` accesses a web page of` a1.com / b1` through the first terminal 100, the access history is stored as shown in FIG. Thereafter, if the accessor having the same unique ID accesses the web page 'a1.com/b2' through the second terminal 150, the web server 200 does not generate a connection history separately and based on the unique ID. You can update the connection history. The updated connection history can be recorded and stored in the database.

Referring back to FIG. 2, the web server then provides a web document to the second terminal (S180).

The web server 200 may transmit the web document to the second terminal 150 in response to the second request message. For example, the web document may correspond to the last access web page URL of the visitor of the first terminal 100.

For example, if a visitor having a unique ID `a1234` accesses the web site` a1.com` through the first terminal 100 and finally accesses the webpage `a1.com / b1`, The access history may be stored as shown in FIG. 3. Thereafter, if the accessor having the unique ID `a1234` requests access to the` a1.com` website through the second terminal 150 having the unique identification image, the web server 200 may finally access the webpage URL. A web document corresponding to `a1.com / b1` can be sent. For reference, the final access web page URL may be extracted from the access web page URL of the access history.

The visitor recognition method according to an embodiment of the present invention has the advantage that even if the same visitor accesses a web site using a plurality of different terminals, the history management can be performed as if using a single terminal. In addition, the visitor may also receive the same web service optimized for the user through history management through different terminals.

4 is a block diagram illustrating a web server according to an embodiment of the present invention.

Web server 200 according to an embodiment of the present invention is a message receiving unit 210, unique ID generation unit 220, unique identification image generation unit 230, unique ID extraction unit 240, access history update unit ( 250, a web document providing unit 260, and a database 270.

The message receiving unit 210 receives the first request message and the second request message for the web document from the first terminal 100 and the second terminal 150, respectively. The first request message may include URL information of a web document for the corresponding web site, and the second request message may include URL information and a unique ID of the web document.

The unique ID generator 220 generates a unique ID for the first terminal 100. The unique ID may be generated by using the address information of the first terminal 100. In this case, the web server 200 maps the generated unique ID and address information of the first terminal 100 corresponding thereto to a mapping table. Can be stored in The unique ID generator 220 determines the uniqueness of the first terminal 100 when the determination unit 222 determines whether the first request message includes the unique ID and the first request message does not include the unique ID. Generation unit 224 for generating an ID.

The unique identification image generator 230 generates a unique identification image for the first terminal 100 using the unique ID. The unique identification image can be any of QR code, bar code, Data Matrix, PDF 417, Maxi Code, Color Code, Gray Code and 3D barcode. It may be one, but is not limited thereto.

The web document providing unit 260 provides the first terminal 100 with a web document in which a unique identification image is inserted as a response to the first request message. The web document may include any type of web page and the transmitted web document may be displayed on the first terminal, in particular the unique identification image may be included in a specific area of the web document.

The unique ID extracting unit 240 parses and extracts a unique ID included in the second request message. For reference, the second request message may include a unique ID, whether to access through a unique identification image, and an access web page URL.

The access history updater 250 may recognize the accessor of the second terminal 150 using the unique ID, and the database 270 stores the access history. In addition, the access history update unit 250 may update and record the access history of the second terminal 150 based on the recognized unique ID. The access history updater 250 may search the access history having a unique ID that matches the unique ID of the accessor of the second terminal 150 among the access history stored in the database 270.

The access history updater 250 may update the access history of the accessor of the second terminal 150 based on the access history of the first terminal.

The access history may include the accessor's unique ID, whether the access is made through the unique identification image, the access web page URL, and the access time.

In addition, the web document providing unit 260 may provide the second terminal 150 with a web document corresponding to the last access web page URL of the accessor of the first terminal as a response to the second request message.

Since each sub configuration of the web server 200 and the web server 200 of FIG. 4 is the same as or similar to that described with reference to FIGS. 1 to 3, a description thereof will be omitted.

For reference, the components illustrated in FIG. 4 according to an embodiment of the present invention mean software components or hardware components such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and perform predetermined roles. .

However, 'components' are not meant to be limited to software or hardware, and each component may be configured to be in an addressable storage medium or may be configured to reproduce one or more processors.

Thus, as an example, a component may include components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, procedures, and subs. Routines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables.

Components and the functionality provided within those components may be combined into a smaller number of components or further separated into additional components.

One embodiment of the present invention can also be implemented in the form of a recording medium containing instructions executable by a computer, such as a program module executed by the computer. Computer readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. In addition, computer readable media may include both computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Communication media typically includes computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, or other transmission mechanism, and includes any information delivery media.

The foregoing description of the present invention is intended for illustration, and it will be understood by those skilled in the art that the present invention may be easily modified in other specific forms without changing the technical spirit or essential features of the present invention. will be. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive. For example, each component described as a single type may be implemented in a distributed manner, and similarly, components described as distributed may be implemented in a combined form.

The scope of the present invention is shown by the following claims rather than the above description, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included in the scope of the present invention. do.

100: first terminal 150: second terminal
200: web server 210: message receiving unit
220: unique ID generation unit 230: unique identification image generation unit
240: unique ID extraction unit 250: access history update unit
260: Web document provider 270: Database
300: Network

Claims (17)

In the visitor recognition method using a personalized unique identification image,
Receiving a first request message for a web document from a first terminal,
Generating a unique ID for the first terminal;
Generating a unique identification image for the first terminal by using the unique ID;
Providing a web document including the unique identification image to the first terminal in response to the first request message;
Receiving a second request message for a web document from a second terminal having the unique identification image,
Parsing and extracting a unique ID included in the second request message; and
Recognizing the accessor of the second terminal by using the unique ID, updating and recording the access history for the accessor of the second terminal
Visitor recognition method comprising a.
The method of claim 1,
The unique identification image,
Accessor recognition: QR Code, Bar Code, Data Matrix, PDF 417, Maxi Code, Color Code, Gray Code and 3D Barcode Way.
The method of claim 1,
Generating the unique ID,
Determining whether the first request message includes a unique ID; and
Generating a unique ID for the first terminal if the first request message does not include a unique ID
Visitor recognition method comprising a.
The method of claim 1,
The first request message includes URL information of a web document,
And the second request message includes URL information of the web document and a unique ID.
The method of claim 1,
And providing the web terminal into which the unique identification image is inserted to the first terminal, inserting the unique identification image into a predetermined area of the web document.
The method of claim 1,
The connection history,
And a unique ID of the visitor, access web page URL information of the visitor, and access time of the web page.
The method according to claim 6,
The step of updating and recording the access history for the accessor of the second terminal,
And retrieving a unique ID matching the unique ID of the accessor of the second terminal.
The method according to claim 6,
And providing the second terminal with a web document corresponding to the last access web page URL information of the visitor of the first terminal as a response to the second request message.
The method of claim 1,
And the second terminal is a mobile terminal capable of recognizing the unique identification image.
A web server that provides a personalized unique identification image,
A message receiver for receiving a first request message and a second request message for a web document from the first terminal and the second terminal, respectively;
Unique ID generation unit for generating a unique ID for the first terminal,
Unique identification image generation unit for generating a unique identification image for the first terminal by using the unique ID,
A web document providing unit which provides the first terminal with a web document in which the unique identification image is inserted as a response to the first request message;
Unique ID extracting unit for parsing and extracting a unique ID included in the second request message;
A connection history update unit for recognizing a visitor of the second terminal by using the unique ID and updating and recording a connection history of the visitor of the second terminal;
Web server comprising a.
The method of claim 10,
The unique identification image,
Web server: QR Code, Bar Code, Data Matrix, PDF 417, Maxi Code, Color Code, Gray Code, or 3D Barcode .
The method of claim 10,
The unique ID generation unit,
A determination unit determining whether the first request message includes a unique ID;
Generation unit for generating a unique ID for the first terminal, if the first request message does not include a unique ID
Web server comprising a.
The method of claim 10,
The first request message includes URL information of a web document,
The second request message includes a URL information and a unique ID of a web document.
The method of claim 10,
The connection history,
And a unique ID of the visitor, access web page URL information of the visitor, and an access time of the web page.
The method of claim 14,
Further comprising a database storing the access history,
The access history update unit is a web server for searching the access history having a unique ID matching the unique ID of the accessor of the second terminal of the access history stored in the database.
The method of claim 14,
The web document providing unit provides a web document corresponding to the last access web page URL information of the accessor of the first terminal to the second terminal in response to a second request message.
The method of claim 10,
And the second terminal is a mobile terminal capable of recognizing the unique identification image.

Images