WO2015105263A1

WO2015105263A1 - Method for accessing webpage and method for accessing web server

Info

Publication number: WO2015105263A1
Application number: PCT/KR2014/009255
Authority: WO
Inventors: 이경전; 전정호
Original assignee: 주식회사 벤플
Priority date: 2014-01-08
Filing date: 2014-10-01
Publication date: 2015-07-16

Abstract

Disclosed is a method for accessing a webpage using an NFC tag. A method for accessing a webpage using an NFC tag, according to one embodiment of the present invention, comprises the steps of: an application installed on a mobile terminal receiving a tag ID from the NFC tag; the application program transmitting the tag ID to a first ID search engine; the application program receiving, from the first ID search engine, a uniform resource locator (URL) of a management system corresponding to the tag ID; the application program accessing the management system by using the URL of the management system, and requesting from the management system a URL of a webpage; the application program receiving the URL of the webpage from the management system; and the application system accessing the webpage using the URL of the webpage.

Description

How to access web pages and how to access web servers

The present invention relates to a web server connection method, and more particularly, to a method for connecting to a web server using an NFC tag or a beacon.

Near field communication (NFC) refers to a contactless communication technology that uses a frequency band of 13.56 MHz as one of electronic tag (or wireless tag) technologies.

With the development of smart phones, smart phones with NFC functions are widely used. In particular, when a smartphone having an NFC function approaches a NFC tag in which a uniform resource locator (URL) related to a specific website is stored, the NFC tag directly provides the URL to the smartphone.

In order to change a particular URL already written in the NFC tag, the user is inconvenient to install and run a special application including the NFC write function on the smartphone. In addition, when the URL of the web site corresponding to the first URL stored in the NFC tag is changed to the second URL, the NFC tag itself should be replaced with another NFC tag storing the second URL.

A beacon is a Bluetooth low energy (BLE) device that allows a customer carrying a smartphone to access a mobile application program installed on the smartphone when entering a store. For example, the beacon may be implemented as a small Bluetooth transceiver in the form of a USB memory. When the beacon is inserted into a USB port or a power outlet of a personal computer (PC) in a store, the installation of the beacon is terminated.

For example, BLE-based beacons can integrate location-based marketing platforms and payment services because the transmission distance is wider from 10 meters to 50 meters compared to NFC.

Since the beacon also provides a URL for accessing a specific web site directly to the smartphone, when the web site is changed to another web site, the beacon should be replaced.

The technical problem to be solved by the present invention is to provide a web server access method that can be connected to the changed web site without changing the NFC tag itself or the beacon itself even if the web site associated with the NFC tag or beacon.

According to an aspect of the invention, the step of the application program installed in the mobile terminal receives a tag ID from the NFC tag; The application program transmitting the tag ID to a first ID search engine; The application program receiving a uniform resource locator (URL) of a management system corresponding to the tag ID from the first ID search engine; The application program accessing the management system using the URL of the management system and requesting a URL of a web page from the management system; The application program receiving a URL of the web page from the management system; And accessing the web page by the application program using the URL of the web page.

The requesting the URL of the web page may transmit the tag ID to the management system together with the request.

The transmitting of the tag ID to the first ID search engine may include: transmitting, by the application program, the tag ID to a second ID search engine, the second ID search engine corresponding to the tag ID from the second ID search engine. This can be done when a URL is not received.

According to an aspect of the invention, the application program installed in the mobile terminal receiving a uniform resource locator (URL) of the management system from the NFC tag; The application program accessing the management system using the URL of the management system and requesting a URL of a web page from the management system; The application program receiving a URL of the web page from the management system; And accessing the web page by the application program using the URL of the web page.

When the application program receives a tag ID and a URL of the management system together from the NFC tag. The requesting the URL of the web page may transmit the tag ID to the management system together with the request.

According to an aspect of the invention, the step of receiving an beacon ID from the beacon, the application program installed in the mobile terminal; The application program transmitting the beacon ID to a first ID search engine; The application program receiving a uniform resource locator (URL) of a management system corresponding to the beacon ID from the first ID search engine; The application program accessing the management system using the URL of the management system and requesting a URL of a web page from the management system; The application program receiving a URL of the web page from the management system; And accessing the web page by the application program using the URL of the web page.

The requesting the URL of the web page may transmit the beacon ID to the management system together with the request.

The transmitting of the beacon ID to the first ID search engine may include: transmitting the beacon ID from the second ID search engine to the beacon ID after the application program transmits the beacon ID to a second ID search engine. This can be done when a URL is not received.

According to an aspect of the invention, the application program installed in the mobile terminal receiving a uniform resource locator (URL) of the management system from the beacon; The application program accessing the management system using the URL of the management system and requesting a URL of a web page from the management system; The application program receiving a URL of the web page from the management system; And accessing the web page by the application program using the URL of the web page.

When the application program receives a beacon ID and a URL of the management system together from the beacon. The requesting the URL of the web page may transmit the beacon ID to the management system together with the request.

According to an aspect of the present invention, a computer-readable recording medium having recorded thereon a computer program capable of executing the web page access method will be provided.

According to an aspect of the present invention, using a mobile application installed in a mobile terminal, receiving a first URL from a tag; Accessing a content management system corresponding to the first URL by using the mobile application; Receiving a second URL from the content management system using the mobile application; And accessing a first web server corresponding to the second URL by using the mobile application.

The web server access method using the mobile application, after the second URL is changed to a third URL by the content management system, using the mobile application to receive the first URL from the same tag as the tag; Accessing the content management system corresponding to the first URL by using the mobile application; Receiving the third URL from the content management system using the mobile application; And accessing a second web server corresponding to the third URL by using the mobile application.

The mobile application may be executed every time the first URL is received.

The method of accessing a web server using the mobile application may include receiving a beacon signal including a beacon ID from a beacon using the mobile application; Calculating a distance between the beacon and the mobile terminal based on the strength of the beacon signal using the mobile application; Transmitting the beacon ID and the calculated distance to the beacon ID directory server using the mobile application; Using the mobile application, receiving an intermediate URL from the beacon ID directory server; Accessing the content management system corresponding to the intermediate URL by using the mobile application; Using the mobile application, receiving a final destination URL from the content management system; And accessing a third web server corresponding to the final destination URL using the mobile application, wherein the intermediate URL may be selected based on the beacon ID and the calculated distance.

The mobile application may be executed in response to the beacon signal.

According to an aspect of the present invention, by using an application installed in a mobile terminal, receiving a beacon signal including a beacon ID from the beacon; Using the mobile application, calculating a distance between the beacon and the mobile terminal from the strength of the signal; Transmitting the beacon ID and the calculated distance to the beacon ID directory server using the mobile application; Using the mobile application, receiving an intermediate URL from the beacon ID directory server; Accessing a content management system corresponding to the intermediate URL by using the mobile application; Using the mobile application, receiving a final destination URL from the content management system; And accessing a first web server corresponding to the final destination URL by using the mobile application.

The intermediate URL may be selected based on the beacon ID and the calculated distance.

The method of accessing a web server using the mobile application may include receiving a first URL from a tag using the mobile application; Accessing the content management system corresponding to the first URL by using the mobile application; Receiving a second URL from the content management system using the mobile application; And accessing a second web server corresponding to the second URL by using the mobile application.

According to an aspect of the present invention, a computer-readable recording medium having recorded thereon a computer program capable of executing a web server connection method using the mobile application will be provided.

Embodiments of the present invention, even if the web site associated with the NFC tag or beacon has an effect that can be connected to the changed web site without changing the NFC tag itself or the beacon itself.

1 is a schematic block diagram of a system for accessing a web page using an NFC tag according to an embodiment of the present invention.

2 is a schematic block diagram of a system for accessing a web page using an NFC tag according to another embodiment of the present invention.

3 is a schematic block diagram of a system for accessing a web page using a beacon according to another embodiment of the present invention.

4 is a schematic block diagram of a system for accessing a web page using a beacon according to another embodiment of the present invention.

Figure 5 shows a schematic block diagram of a system according to another embodiment of the present invention.

6 is a schematic block diagram of a system according to another embodiment of the present invention.

7 illustrates a data flow for explaining a method of operating a system according to an exemplary embodiment.

8 is a data flow diagram illustrating a method of operating a system according to another embodiment of the present invention.

9 is a data flow diagram illustrating a method of operating a system according to another embodiment of the present invention.

In order to fully understand the present invention, the operational advantages of the present invention, and the objects achieved by the practice of the present invention, reference should be made to the accompanying drawings which illustrate preferred embodiments of the present invention and the contents described in the accompanying drawings.

Hereinafter, the present invention will be described in detail by explaining preferred embodiments of the present invention with reference to the accompanying drawings. Like reference numerals in the drawings denote like elements.

An application (application program or mobile application program) to be described herein is defined as an application capable of performing one or more of the various web page access methods described with reference to FIGS. 1 to 6.

1 is a schematic block diagram of a system for accessing a web page using an NFC tag according to an embodiment of the present invention. Referring to FIG. 1, the system includes an NFC tag 100, a mobile terminal 200, a first ID search engine 300, a management system 400, and a web server 500. ).

The mobile terminal 200 may be implemented as an internet of things (IoT) device or an internet of everything (IoE) device.

Each of the NFC tag 100 and the mobile terminal 200 may include a transmission / reception module for NFC.

The NFC tag 100 stores a tag ID. For example, the mobile terminal 200 may be implemented as a laptop computer, a smartphone, a tablet PC, a mobile internet device (MID), an internet tablet, a digital camera, or a wearable computer.

When the user scans, tags, or touches the NFC tag 100 using an application program installed in the mobile terminal 200, the NFC tag 100 may be an NFC tag ID (TID). ) Is transmitted to the mobile terminal 200 through the NFC (S110).

The application program App transmits the NFC tag ID (TID) to the first ID search engine 300 through a wired network, a wireless network, or Wi-Fi (S120). That is, the transmission and reception module implemented in the mobile terminal 200 transmits the NFC tag ID (TID) to the first ID search engine 300 under the control of the application program (S120).

The first ID search engine 300 receives the NFC tag ID (TID), searches for the URL (MS_URL) of the management system 400 corresponding to the received NFC tag ID (TID) (S130), and the managed management. The URL (MS_URL) of the system 400 is transmitted to the mobile terminal 200 (S140).

Here, the URL is a protocol for indicating where the resource is located on the network. The URL may represent not only a web site address but also a resource on a computer network. Therefore, in order to access the web site address, it is necessary to know the protocol corresponding to the URL and to connect with the same protocol.

According to an embodiment, the application program (App) is connected to the management system 400 using the URL (MS_URL) of the management system 400 transmitted from the first ID search engine 300, the web to the management system 400 An address (eg, URL; WP_URL) of a page (web page WP) may be requested (S150). According to another embodiment, the application program (App) may transmit the NFC tag ID (TID) to the management system 400 with the request (S150).

The transmission and reception module implemented in the mobile terminal 200 may transmit or receive data with the management system 400 under the control of an application program (App).

According to an embodiment, the management system 400 may search for the URL WP_URL of the web page WP in response to the request (S160). According to another embodiment, when the request and the NFC tag ID (TID) are transmitted together by an application program (App), the management system 400 in response to the request and the NFC tag ID (TID) in response to a web page ( The URL (WP_URL) of the WP) may be searched for (S160).

The management system 400 transmits the URL WP_URL of the found web page WP to the application program App of the mobile terminal 200 (S170).

The application program App may access the web server 500 or the web site managing the web page WP by using the URL WP_URL of the found web page WP (S180).

Referring to FIG. 2, the system includes an NFC tag 100-1, a mobile terminal 200, a management system 400, and a web server 500.

Each of the NFC tag 100-1 and the mobile terminal 200 may include a transmission / reception module for NFC. The NFC tag 100-1 stores the URL of the management system 400.

When the user scans, tags, or touches the NFC tag 100-1 using an application program installed in the mobile terminal 200, the NFC tag 100-1 may be managed according to embodiments. URL (MS_URL) of the) may be transmitted to the mobile terminal 200 through NFC or the URL (MS_URL) and NFC tag ID (TID) of the management system 400 may be transmitted to the mobile terminal 200 through NFC (S210). ).

According to an embodiment, the application program (App) is connected to the management system 400 using the URL (MS_URL) of the management system 400 transmitted from the NFC tag 100-1, the web to the management system 400 The transmission of the URL WP_URL of the page WP may be requested (S220). According to another embodiment, the application program (App) may transmit the NFC tag ID (TID) to the management system 400 with the request (S220).

According to an embodiment, the management system 400 may search for the URL WP_URL of the web page WP in response to the request (S230). According to another embodiment, when the request and the NFC tag ID (TID) are transmitted together by an application program (App), the management system 400 in response to the request and the NFC tag ID (TID) in response to a web page ( The URL (WP_URL) of the WP may be searched for (S230).

The management system 400 may transmit the URL WP_URL of the found web page WP to an application program (S240).

The application program App may access the web server 500 or the web site managing the web page WP using the URL WP_URL of the found web page WP (S250).

3 is a schematic block diagram of a system for accessing a web page using a beacon according to another embodiment of the present invention. Referring to FIG. 3, a system may include at least one beacon 110 and / or 110-1, a mobile terminal 200, a first ID search engine 300, a management system 400, and a web server 500. Include.

In the present specification, a beacon (beacon) is a hardware that provides information to the Internet of Things (IoT) device or the Internet of Things (IoE) device by the method of broadcasting (broadcasting) using a variety of communication technologies including Bluetooth or the same function as the hardware Collectively, the software to perform.

In addition, the beacon may refer to a device for data communication using Bluetooth low energy (BLE). For example, the beacon may transmit data to the mobile terminal even if the mobile terminal passes through the place where the beacon is installed without tagging the mobile terminal (eg, a smartphone) close to the NFC module like NFC.

For example, the beacon refers to a hardware or hardware module for communication using a local area network (WPAN), or an infrared data association (IrDA). For example, the WPAN includes Bluetooth, Zigbee, or Ultra Wide Band (UWB).

The mobile terminal 200 refers to a wireless communication terminal capable of communicating with at least one beacon 100 and / or 110-1. As described above, the mobile terminal 200 may be implemented as an IoT device, an IoE device, a smartphone, a tablet PC, a mobile internet device, an internet tablet, a digital camera, or a wearable computer.

Each of the at least one beacon 110 and / or 110-1 and the mobile terminal 200 may include a transmission / reception module for communication. Each beacon 110 or 110-1 stores each beacon ID BID1 or BID2.

An application program installed in the mobile terminal 200 may search for a beacon signal output from at least one beacon 110 and / or 110-1 (S310). The step S310 may not be performed by setting the application program or by setting the user of the mobile terminal 200.

Each beacon 110 or 110-1 transmits each beacon ID BID1 or BID2 to the mobile terminal 200 (S320 or S321).

The application program App may transmit at least one of the beacon IDs BID1 and BID2 to the first ID search engine 300 through a wired network or a wireless network (S330). That is, the application program App may query the first ID search engine 300 whether each beacon ID BID1 or BID2 exists.

The first ID search engine 300 receives each beacon ID BID1 or BID2, searches for the URL (MS_URL) of the management system 400 corresponding to each received beacon ID BID1 or BID2 (S340). In operation S350, the searched URL (MS_URL) of the management system 400 may be transmitted to the mobile terminal 200.

The application program App accesses the management system 400 using the URL (MS_URL) of the management system 400 transmitted from the first ID search engine 300, and the web page WP to the management system 400. The transmission of the URL (WP_URL) may be requested (S360). According to another embodiment, the application program (App) may transmit the beacon ID (BID1 or BID2) to the management system 400 with the request (S360).

According to an embodiment, the management system 400 searches for the URL WP_URL of the web page WP in response to the request (S370). According to another embodiment, when the request and the beacon ID (BID1 or BID2) are transmitted together by an application program (App), the management system 400 uses the request and the beacon ID (BID1 or BID2). The URL (WP_URL) of the (WP) may be searched for (S370).

The management system 400 transmits the URL (WP_URL) of the found web page (WP) to the application program (S380).

The application program App may access the web server 500 or the web site managing the web page WP by using the URL WP_URL of the found web page WP (S390).

4 is a schematic block diagram of a system for accessing a web page using a beacon according to another embodiment of the present invention. Referring to FIG. 4, the system includes at least one beacon 110A and / or 110-1A, a mobile terminal 200, a management system 400, and a web server 500.

The application program installed in the mobile terminal 200 may search for a beacon signal output from at least one beacon 110A and / or 110-1A (S410). The step S410 may not be executed by setting the application program or by setting the user of the mobile terminal 200.

According to embodiments, each beacon 110A or 110-1A transmits the URL (MS_URL) of the management system 400 to the mobile terminal 200 or each beacon ID (BID1A) together with the URL (MS_URL) of the management system 400. Alternatively, the BID2A may be transmitted to the mobile terminal 200 (S420 or S421).

The application program App accesses the management system 400 using the URL (MS_URL) of the management system 400 transmitted from each beacon 110A or 110-1A, and the web page WP to the management system 400. Request the transmission of the URL (WP_URL) of (S430). According to another embodiment, the application program App may transmit a beacon ID (BID1A or BID2A) corresponding to the request to the management system 400 (S430).

According to an embodiment, the management system 400 searches for the URL WP_URL of the web page WP in response to the request (S440). According to another embodiment, when the beacon ID (BID1A or BID2A) corresponding to the request is transmitted together by the application program (App), the management system 400 is configured to send the beacon ID (BID1A or BID2A) corresponding to the request. In operation S440, the URL WP_URL of the web page WP may be searched for.

For example, the management system 400 may access a database that stores URLs of web pages managed by beacon IDs.

The management system 400 transmits the URL (WP_URL) of the found web page (WP) to the application program (S450). The application program App may access the web server 500 or the web site managing the web page WP by using the URL WP_URL of the found web page WP (S460).

Figure 5 shows a schematic block diagram of a system according to another embodiment of the present invention. Referring to FIG. 5, the system includes a mobile terminal 200, a first ID search engine 300A, a second ID search engine 300-1A, and a third ID search engine 300-2A.

1, 3, and 5, the operation method when the first

ID search engine

300 or 300A (collectively '300A') fails to search the URL (MS_URL) of the management system 400 is described. It is explained below.

The application program installed in the mobile terminal 200 transmits an NFC tag ID (TID) or each beacon ID (BID1 or BID2, collectively 'BID') to the first ID search engine 300A (S120, S330, or S510). The first ID search engine 300A searches for the URL (MS_URL) of the management system 400 corresponding to the NFC tag ID (TID) or each beacon ID (BID) (S130, S340, or S520).

As a result of the search, when the first ID search engine 300A fails to search the URL (MS_URL) of the management system 400 corresponding to the NFC tag ID (TID) or the beacon ID (BID), the first ID search engine ( 300A) transmits the NFC tag ID (TID) or the beacon ID (BID) to the second ID search engine 300-1A (S530).

The second ID search engine 300-1A searches for the URL (MS_URL) of the management system 400 corresponding to the NFC tag ID (TID) or the beacon ID (BID) transmitted from the first ID search engine 300A ( S540).

As a result of the search, when the second ID search engine 300-1A fails to search the URL (MS_URL) of the management system 400 corresponding to the NFC tag ID (TID) or the beacon ID (BID), the second ID search The engine 300-1A transmits a result of the search, that is, a failure value (eg, a flag) indicating a failure, to the first ID search engine 300A (S550).

In response to the failure value, the first ID search engine 300A transmits an NFC tag ID (TID) or a beacon ID (BID) to the third ID search engine 300-2A (S560).

The third ID search engine 300-2A searches for a URL (MS_URL) of the management system 400 corresponding to the NFC tag ID (TID) or the beacon ID (BID) transmitted from the first ID search engine 300A. (S570).

As a result of the search, when the third ID search engine 300-2A searches the URL (MS_URL) of the management system 400 corresponding to the NFC tag ID (TID) or the beacon ID (BID) (that is, the search is successful). The third ID search engine 300-2A transmits a search result, that is, a success value (eg, URL (MS_URL) of the management system 400), to the first ID search engine 300A (S580). .

The first ID search engine 300A may transmit a URL (MS_URL) of the management system 400 to an application program (App) installed in the mobile terminal 200 (S590).

As described with reference to FIG. 1 or 3, the application program (App) obtains the URL (WP_URL) of the found web page (WP) and moves to a web server (500) or a website that manages the web page (WP). Can be.

For example, when the second ID search engine 300-1A searches the URL (MS_URL) of the management system 400 corresponding to the NFC tag ID (TID) or the beacon ID (BID) (that is, the search is successful). The second ID search engine 300-1A may transmit a result of the search, that is, a success value (eg, URL (MS_URL) of the management system 400) to the first ID search engine 300A.

In FIG. 5, three ID search engines 300A, 300-1A, and 300-2A are shown for convenience of description, but the system shown in FIG. 5 may use two ID search engines or four. The above ID search engines may be used.

6 is a schematic block diagram of a system according to another embodiment of the present invention. Referring to FIG. 6, the system includes a mobile terminal 200, a first ID search engine 300-1B, a second ID search engine 300-2B, and a third ID search engine 300B.

1, 3, and 6, an application program installed in the mobile terminal 200 removes an NFC tag ID (TID) or each beacon ID (BID1 or BID2, collectively 'BID'). 1 ID is transmitted to the search engine (300-1B) (S610). The first ID search engine 300-1B searches for a URL (MS_URL) of the management system 400 corresponding to the NFC tag ID (TID) or the beacon ID (BID) (S620).

As a result of the search, when the first ID search engine 300-1B does not search the URL (MS_URL) of the management system 400 corresponding to the NFC tag ID (TID) or the beacon ID (BID) (that is, the search is In case of failure), the first ID search engine 300-1B transmits a result of the search, that is, a failure value (eg, a flag) indicating the failure to the application program (S630).

In response to the failure value (eg, a flag) transmitted from the first ID search engine 300-1B, the application program App determines an NFC tag ID (TID) or a beacon ID (BID). 2B) (S640). The second ID search engine 300-2B searches for a URL (MS_URL) of the management system 400 corresponding to the NFC tag ID (TID) or the beacon ID (BID) (S650).

As a result of the search, when the second ID search engine 300-2B does not search the URL (MS_URL) of the management system 400 corresponding to the NFC tag ID (TID) or the beacon ID (BID) (that is, the search is In case of failure), the second ID search engine 300-2B transmits a result of the search, that is, a failure value (eg, a flag) indicating failure to the application program App (S660).

In response to the failure value (eg, a flag) transmitted from the second ID search engine 300-2B, the application program may convert the NFC tag ID (TID) or the beacon ID (BID) into the third ID search engine 300 or the like. 300B) (S670). The third

ID search engine

300 or 300B searches for the URL (MS_URL) of the management system 400 corresponding to the NFC tag ID (TID) or the beacon ID (BID) (S680).

As a result of the search, when the third

ID search engine

300 or 300B searches the URL (MS_URL) of the management system 400 corresponding to the NFC tag ID (TID) or the beacon ID (BID) (that is, the search is successful). The third

ID search engine

300 or 300B transmits the result of the search, that is, the success value (eg, the URL (MS_URL) of the management system 400), to the application program (S690) (S690).

As illustrated in FIG. 1 or 3, the application program manages the web page WP as described with reference to FIG. 1 or 3 using the URL (MS_URL) of the discovered management system 400. A web server 500 or a website can be accessed.

For example, when the second ID search engine 300-2B searches the URLMS_URL of the management system 400 corresponding to the NFC tag ID (TID) or the beacon ID (BID) (that is, the search is successful), 2 The ID search engine 300-2B may transmit a result of the search, that is, a success value (eg, the URL (MS_URL) of the management system 400) to the application program App.

In FIG. 6, three ID search engines are shown for convenience of description, but the system illustrated in FIG. 6 may use two ID search engines or four or more ID search engines.

An application program (App) capable of performing the method according to an embodiment of the present invention may be downloaded and executed from an app store to an IoT device.

As described above, the management system 400 has an effect of managing a plurality of web pages (or web sites) using one tag ID or one beacon ID.

For example, the management system 400 assigns a URL (WP_URL) of a web page provided to the mobile terminal 200 for an advertisement to a first web page (or a first web site), and then, for the first web page. If the advertisement period has expired, the management system 400 may reassign the URL (WP_URL) of the web page provided to the mobile terminal 200 for another advertisement to the second web page (or second website). In this case, the mobile terminal 220 may access the second web page instead of the first web page.

Accordingly, the management system 400 may have the same effect as changing the URL of the web page that the mobile terminal 200 can access without changing the NFC tag or the beacon itself.

Referring to FIG. 7, the system includes an NFC module 100, a mobile terminal 200, a content management system 600, and a plurality of

web servers

510 and 520.

The NFC module 100 may mean a module including an NFC function. For example, the NFC module 100 may be implemented with an NFC tag and store a URL (CMS_URL) corresponding to or for connecting to the content management system 600.

The mobile terminal 200 includes a transmission and reception module capable of performing the NFC function. The mobile terminal 200 may be implemented as a smart phone, a tablet PC, a mobile internet device (MID), an internet tablet, a digital camera, or a wearable computer.

The mobile terminal 200 is installed with a mobile application that can provide a web server connection service to be described herein. According to embodiments, the mobile application may be executed by the user before the step S710 is performed, or may be automatically executed as the S710 is performed.

When the user tags the NFC module 100 installed in a specific place using the mobile terminal 200, the URL (CMS_URL) stored in the NFC module 100 is transmitted to the mobile terminal 200 through the NFC (S710).

The mobile terminal 200 connects to the server corresponding to the URL (CMS_URL) transmitted from the NFC module 100, that is, the content management system 600, using a mobile application through a wireless communication network or a wireless Internet network (S720). ).

Thereafter, the content management system 600 reads the final destination URL (URL_A) stored in the database (S730) and transmits the final destination URL (URL_A) to the mobile terminal 200 through a wireless communication network or a wireless Internet network ( S740).

The mobile terminal 200 accesses the first web server 510 corresponding to the final destination URL URL_A by using the mobile application (S750). Accordingly, the user's mobile terminal 200 may access a web site provided by the first web server 510 using a mobile application.

After the final destination URL is changed from URL_A to URL_B by the content management system 600, a user uses a second web server (eg, a URL (CMS_URL) stored in the NFC module 100 and a mobile application installed in the mobile terminal 200. A method of connecting to 520 is described.

When the user tags the NFC module 100 using the mobile terminal 200, the URL (CMS_URL) stored in the NFC module 100 is transmitted to the mobile terminal 200 through NFC (S710).

The content management system 600 reads the changed final destination URL URL_B stored in the database (S730), and transmits the final destination URL URL_B to the mobile terminal 200 (S740).

The mobile terminal 200 accesses the second web server 520 corresponding to the final destination URL URL_B using the mobile application in operation S760. Accordingly, the user's mobile terminal 200 may access a web site provided by the second web server 520 using a mobile application.

That is, in the service or the system providing the service according to the embodiment of the present invention, the NFC for changing the URL for accessing the content management system 600 without changing the URL first written to the NFC module 100 is changed. Even if the module 100 itself is not changed, the mobile terminal 200 can access the web server corresponding to the final destination URL using the final destination URL provided from the content management system 600.

Referring to FIG. 8, the system includes a beacon 110, a mobile terminal 210, a beacon ID directory server 700, a content management system 600, and a plurality of

web servers

610, 620, and 630. Include.

The beacon 110 may refer to a device for data communication using BLE (Bluetooth Low Energy). For example, the beacon may transmit data to the mobile terminal just by passing the place where the beacon is installed, without having to tag the mobile terminal (eg, a smartphone) close to the NFC module like NFC.

For example, the beacon 110 refers to a hardware or hardware module for communication using a local area network (WPAN), or an Infrared Data Association (IrDA).

For example, the WPAN includes Bluetooth, Zigbee, or Ultra Wide Band (UWB).

The mobile application installed in the mobile terminal 210 receives a beacon signal including a beacon ID (BID) from the beacon 110 (S810), between the beacon 110 and the mobile terminal 210 based on the beacon signal The distance DISi may be calculated (S815).

For example, a mobile application installed in the mobile terminal 210 may receive a beacon signal output from the beacon 110 and include a beacon ID (BID), and calculate a distance DISi using the strength of the received beacon signal. (S815).

For example, the mobile application installed in the mobile terminal 210 may calculate the distance DISi between the beacon 110 and the mobile terminal 210 using the received signal strength indication (RSSI) (S815). .

According to embodiments, the distance DISi may be calculated numerically or numerically, and may also be calculated by indicating a relative distance such as stop, middle, nearness, and the like.

The mobile application installed in the mobile terminal 210 may transmit a directory request including a beacon ID (BID) and a distance (DISi) to the beacon ID directory server 700 (S820).

The beacon ID directory server 700 may selectively read the intermediate URL (DURLi, i = 1, 2, or 3) from the database by using the beacon ID BID and the distance DISi (S830).

For example, even if the same beacon ID (BID), different intermediate URLs (DURLi, i = 1, 2, or 3) according to the distance (DISi, i = 1, 2, or 3) are stored in the beacon ID directory server 700. Can be selected.

According to an embodiment, each intermediate URL DURLi may be a URL corresponding to the content management system 600. For example, the first intermediate URL (DURL1) may be a first URL for accessing a first directory (or first web page) of the content management system 600, and the second intermediate URL (DURL2) may be a content management system 600. May be a second URL for accessing a second directory (or second web page), and the third intermediate URL (DURL3) is for accessing the third directory (or third web page) of the content management system 600. It may be a third URL for.

That is, each intermediate URL DURLi may be a URL for accessing a file other than a directory or a page of the content management system 600. For example, each intermediate URL DURLi may be updated or changed by the beacon ID directory server 700.

Beacon ID directory server 700 transmits the selected intermediate URL (DURLi) to the mobile terminal 210 (S840),

The mobile terminal 210 transmits the intermediate URL (DURLi) transmitted from the beacon ID directory server 700 to the content management system 600 by using the mobile application (S850). The content management system 600 reads the final destination URL FURLi corresponding to each intermediate URL DURLi from the database (S860).

For example, when the first intermediate URL DURL1 is selected according to the beacon ID BID and the first distance DIS1, the content management system 600 may determine the first final destination URL corresponding to the first intermediate URL DURL1. FURL1 is transmitted to the mobile terminal 210 through a wireless communication network or a wireless internet network (S870). Therefore, the mobile terminal 210 may access a web site corresponding to the first web server 610 using a mobile application (S881).

When the second intermediate URL (DURL2) is selected according to the beacon ID (BID) and the second distance (DIS2), the content management system 600, the second final destination URL (FURL2) corresponding to the second intermediate URL (DURL2) To transmit to the mobile terminal 210 (S870). Accordingly, the mobile terminal 210 may access a web site corresponding to the second web server 620 by using an application (S882).

When the third intermediate URL (DURL3) is selected according to the beacon ID (BID) and the third distance (DIS3), the content management system 600 determines the third final destination URL (FURL3) corresponding to the third intermediate URL (DURL3). To transmit to the mobile terminal 210 (S870). Accordingly, the mobile terminal 210 may access a web site corresponding to the third web server 630 by using an application (S883).

The mapping relationship between each intermediate URL DURL1, DURL2, and DURL3 and each final destination URL FURL1, FURL2, and FURL3 may be updated or changed by the content management system 600.

The mobile application described herein may be executed by a user, or automatically executed in response to a URL (CMS_URL) output from the NFC module 100, or automatically in response to a beacon signal output from the beacon 110. May be implemented.

As described with reference to FIG. 8, as each intermediate URL (DURLi) stored in the beacon ID directory server 700 is changed or each final destination URL (FURLi) of the content management system 600 is changed, the mobile terminal 210 is changed. The mobile application installed at) may access the web server corresponding to the changed final destination URL.

The mobile application according to an embodiment of the present invention may perform one or two of the method described with reference to FIG. 7 and the method described with reference to FIG. 8.

The mobile application may be downloaded and installed from the app store to the

mobile terminal

200 or 210 through a wireless communication network or a wireless internet network. The app store may include a recording medium, such as a database, capable of storing the mobile application.

9 is a flowchart illustrating a data flow for explaining a method of operating a system, according to another exemplary embodiment.

Referring to FIG. 9, the system 1000 represents an embodiment in which the system described with reference to FIG. 7 and the system described with reference to FIG. 8 are implemented as one system. In this case, the

mobile terminals

200 and 210 may mean the same mobile terminal.

For example, when the NFC module 100 and the beacon 110 are installed in a specific space at the same time, the mobile terminal 200 uses one content management system 600 and one mobile application (APP) to specify a specific final destination. You can connect to the web server corresponding to the URL.

That is, depending on how each URL (URL_A and URL_B) is set, the mobile terminal 200 uses any one of the plurality of

web servers

510, 520, 610, 620, and 630 using the mobile application APP. Can be accessed. Also, depending on how each URL (FURL1, FURL2, and FURL3) is set, the mobile terminal 200 uses a mobile application (APP) to generate a plurality of web servers (510, 520, 610, 620, and 630). Can be connected to either.

According to embodiments, the final destination URL (any one of URL_A and URL_B) of FIG. 7 and the final destination URL (any one of FURL1, FURL2, and FURL3) of FIG. 8 may be set as URLs of the same web server.

As described with reference to FIGS. 7 to 9, in the service or the system providing the service according to the embodiment of the present invention, (1) without changing the URL written first in the NFC module 100 and (2) Even if the NFC module 100 itself is not changed to change the URL for accessing the content management system 600, the mobile terminal 200 does not change the final destination URLs provided from the content management system 600 (eg, URL_A, URL_B, Any one of FURL1, FURL2, and FURL3) may be connected to any one of the plurality of

web servers

510, 520, 610, 620, and 630.

For example, when a URL (CMS_URL) transmitted from the NFC module 100 and a beacon signal transmitted from the beacon 110 are received simultaneously or in parallel with the mobile terminal 200, the user may use a mobile application (APP). You can decide which to do first.

Although the present embodiment has been described in detail with reference to the drawings, the scope of the present invention is not limited to the above-described drawings and descriptions.

As described above, the present invention is not limited to the described embodiments, and various modifications and changes can be made without departing from the spirit and scope of the present invention, which will be apparent to those skilled in the art. Therefore, such modifications or variations will have to be belong to the claims of the present invention.

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a web server connection method, and more particularly, to an industry related to web server connection using NFC tags or beacons.

Claims

Receiving, by the application program installed in the mobile terminal, the tag ID from the NFC tag;

The application program transmitting the tag ID to a first ID search engine;

The application program receiving a uniform resource locator (URL) of a management system corresponding to the tag ID from the first ID search engine;

The application program accessing the management system using the URL of the management system and requesting a URL of a web page from the management system;

The application program receiving a URL of the web page from the management system; And

The application program accessing the web page using the NFC tag comprising the step of accessing the web page using the URL of the web page.
The method of claim 1,

The requesting the URL of the web page is a web page access method using the NFC tag to transmit the tag ID to the management system with the request.
The method of claim 1, wherein the transmitting of the tag ID to the first ID search engine comprises:

Access to a web page using an NFC tag performed when the application program transmits the tag ID to a second ID search engine and fails to receive a URL of the management system corresponding to the tag ID from the second ID search engine. Way.
Receiving, by an application program installed in a mobile terminal, a uniform resource locator (URL) of a management system from an NFC tag;

The application program accessing the management system using the URL of the management system and requesting a URL of a web page from the management system;

The application program receiving a URL of the web page from the management system; And

The application program accessing the web page using the NFC tag comprising the step of accessing the web page using the URL of the web page.
The method of claim 4, wherein

When the application program receives a tag ID and a URL of the management system together from the NFC tag.

The requesting the URL of the web page is a web page access method using the NFC tag to transmit the tag ID to the management system with the request.
Receiving, by the application program installed in the mobile terminal, the beacon ID from the beacon;

The application program transmitting the beacon ID to a first ID search engine;

The application program receiving a uniform resource locator (URL) of a management system corresponding to the beacon ID from the first ID search engine;

The application program accessing the management system using the URL of the management system and requesting a URL of a web page from the management system;

The application program receiving a URL of the web page from the management system; And

And accessing the web page by the application program using the URL of the web page.
The method of claim 6,

The requesting the URL of the web page may include transmitting a beacon ID to the management system along with the request.
The method of claim 6, wherein transmitting the beacon ID to the first ID search engine comprises:

A method of accessing a web page using a beacon performed when the application program transmits the beacon ID to a second ID search engine and fails to receive a URL of the management system corresponding to the beacon ID from the second ID search engine. ..
Receiving, by an application program installed in a mobile terminal, a uniform resource locator (URL) of a management system from a beacon;

The application program accessing the management system using the URL of the management system and requesting a URL of a web page from the management system;

The application program receiving a URL of the web page from the management system; And

And accessing the web page by the application program using the URL of the web page.
The method of claim 9,

When the application program receives a beacon ID and a URL of the management system together from the beacon.

The requesting the URL of the web page may include transmitting a beacon ID to the management system along with the request.
A computer-readable recording medium having recorded thereon a computer program capable of executing the web page access method according to any one of claims 1 to 10.
Receiving a first URL from a tag using a mobile application installed in the mobile terminal;

Accessing a content management system corresponding to the first URL by using the mobile application;

Receiving a second URL from the content management system using the mobile application; And

Connecting to a first web server corresponding to the second URL by using the mobile application.
The method of claim 12,

After the second URL is changed to a third URL by the content management system, receiving the first URL from the same tag as the tag by using the mobile application;

Accessing the content management system corresponding to the first URL by using the mobile application;

Receiving the third URL from the content management system using the mobile application; And

Connecting to a second web server corresponding to the third URL by using the mobile application.
The method of claim 13,

The mobile application is a web server access method using a mobile application that is executed every time the first URL is received.
The method of claim 13,

Using the mobile application, receiving a beacon signal including a beacon ID from a beacon;

Calculating a distance between the beacon and the mobile terminal based on the strength of the beacon signal using the mobile application;

Transmitting the beacon ID and the calculated distance to the beacon ID directory server using the mobile application;

Using the mobile application, receiving an intermediate URL from the beacon ID directory server;

Accessing the content management system corresponding to the intermediate URL by using the mobile application;

Using the mobile application, receiving a final destination URL from the content management system; And

Using the mobile application, accessing a third web server corresponding to the final destination URL,

The intermediate URL is selected based on the beacon ID and the calculated distance Web server access method using a mobile application.
The method of claim 15,

The mobile application is a web server access method using a mobile application that is executed in response to the beacon signal.
Receiving a beacon signal including a beacon ID from the beacon, using an application installed in the mobile terminal;

Using the mobile application, calculating a distance between the beacon and the mobile terminal from the strength of the signal;

Transmitting the beacon ID and the calculated distance to the beacon ID directory server using the mobile application;

Using the mobile application, receiving an intermediate URL from the beacon ID directory server;

Accessing a content management system corresponding to the intermediate URL by using the mobile application;

Using the mobile application, receiving a final destination URL from the content management system; And

Connecting to a first web server corresponding to the final destination URL by using the mobile application.
The method of claim 17,

The intermediate URL is selected based on the beacon ID and the calculated distance Web server access method using a mobile application.
The method of claim 17,

Using the mobile application, receiving a first URL from a tag;

Accessing the content management system corresponding to the first URL by using the mobile application;

Receiving a second URL from the content management system using the mobile application; And

Connecting to a second web server corresponding to the second URL by using the mobile application.
A computer-readable recording medium having recorded thereon a computer program capable of executing the method according to claim 12 or 17.