[go: up one dir, main page]

WO2015105263A1 - Procédé d'accès à une page web et procédé d'accès à un serveur web - Google Patents

Procédé d'accès à une page web et procédé d'accès à un serveur web Download PDF

Info

Publication number
WO2015105263A1
WO2015105263A1 PCT/KR2014/009255 KR2014009255W WO2015105263A1 WO 2015105263 A1 WO2015105263 A1 WO 2015105263A1 KR 2014009255 W KR2014009255 W KR 2014009255W WO 2015105263 A1 WO2015105263 A1 WO 2015105263A1
Authority
WO
WIPO (PCT)
Prior art keywords
url
management system
beacon
web page
application program
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2014/009255
Other languages
English (en)
Korean (ko)
Inventor
이경전
전정호
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BENPLE Inc
Original Assignee
BENPLE Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020140002485A external-priority patent/KR101555360B1/ko
Priority claimed from KR1020140026363A external-priority patent/KR101596690B1/ko
Application filed by BENPLE Inc filed Critical BENPLE Inc
Priority to US14/655,116 priority Critical patent/US9706041B2/en
Publication of WO2015105263A1 publication Critical patent/WO2015105263A1/fr
Anticipated expiration legal-status Critical
Priority to US15/617,372 priority patent/US10122842B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9554—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL] by using bar codes

Definitions

  • 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.
  • NFC Near field communication
  • the user 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.
  • 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.
  • the beacon may be implemented as a small Bluetooth transceiver in the form of a USB memory.
  • PC personal computer
  • 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.
  • 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.
  • 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.
  • URL uniform resource locator
  • 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.
  • 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.
  • URL uniform resource locator
  • the application program 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.
  • 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.
  • URL uniform resource locator
  • 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.
  • 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.
  • URL uniform resource locator
  • the application program 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.
  • a computer-readable recording medium having recorded thereon a computer program capable of executing the web page access method will be provided.
  • 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.
  • 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.
  • a computer-readable recording medium having recorded thereon a computer program capable of executing a web server connection method using the mobile application.
  • 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.
  • FIG. 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.
  • FIG. 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.
  • FIG. 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.
  • FIG. 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.
  • FIG. 6 is a schematic block diagram of a system according to another embodiment of the present invention.
  • FIG. 7 illustrates a data flow for explaining a method of operating a system according to an exemplary embodiment.
  • FIG. 8 is a data flow diagram illustrating a method of operating a system according to another embodiment of the present invention.
  • FIG. 9 is a data flow diagram illustrating a method of operating a system according to another embodiment of the present invention.
  • 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.
  • FIG. 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.
  • 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.
  • IoT internet of things
  • IoE internet of everything
  • 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.
  • 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.
  • MID mobile internet device
  • the NFC tag 100 may be an NFC tag ID (TID). ) Is transmitted to the mobile terminal 200 through the NFC (S110).
  • TID NFC tag ID
  • 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).
  • 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.
  • 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
  • WP_URL e.g., URL; WP_URL
  • 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).
  • App application program
  • the management system 400 may search for the URL WP_URL of the web page WP in response to the request (S160).
  • 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).
  • FIG. 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.
  • 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.
  • 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). ).
  • 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).
  • the application program (App) may transmit the NFC tag ID (TID) to the management system 400 with the request (S220).
  • the management system 400 may search for the URL WP_URL of the web page WP in response to the request (S230).
  • 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).
  • 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.
  • a 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.
  • the beacon may refer to a device for data communication using Bluetooth low energy (BLE).
  • BLE Bluetooth low energy
  • 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.
  • the beacon refers to a hardware or hardware module for communication using a local area network (WPAN), or an infrared data association (IrDA).
  • 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.
  • 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).
  • the application program (App) may transmit the beacon ID (BID1 or BID2) to the management system 400 with the request (S360).
  • the management system 400 searches for the URL WP_URL of the web page WP in response to the request (S370).
  • 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).
  • 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.
  • 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.
  • 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).
  • the application program App may transmit a beacon ID (BID1A or BID2A) corresponding to the request to the management system 400 (S430).
  • the management system 400 searches for the URL WP_URL of the web page WP in response to the request (S440).
  • the management system 400 is configured to send the beacon ID (BID1A or BID2A) corresponding to the request.
  • the URL WP_URL of the web page WP may be searched for.
  • 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.
  • 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.
  • 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).
  • the first ID search engine 300A 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).
  • the second ID search engine 300-1A 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).
  • a failure value eg, a flag
  • 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).
  • TID NFC tag ID
  • BID beacon ID
  • 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).
  • 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).
  • MS_URL a URL of the management system 400
  • App application program installed in the mobile terminal 200
  • 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.
  • 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.
  • 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.
  • FIG. 6 is a schematic block diagram of a system according to another embodiment of the present invention.
  • 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.
  • 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).
  • 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).
  • a failure value eg, a flag
  • 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).
  • 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).
  • a failure value eg, a flag
  • 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).
  • 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).
  • 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.
  • 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.
  • a success value eg, the URL (MS_URL) of the management system 400
  • 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.
  • 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.
  • 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.
  • WP_URL a URL
  • 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.
  • FIG. 7 illustrates a data flow for explaining a method of operating a system according to an exemplary embodiment.
  • 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.
  • 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.
  • CMS_URL a 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.
  • MID mobile internet device
  • 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.
  • 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.
  • 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). ).
  • CMS_URL the URL
  • S720 wireless Internet network
  • 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.
  • 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 second web server eg, a URL (CMS_URL) stored in the NFC module 100 and a mobile application installed in the mobile terminal 200.
  • CMS_URL a URL
  • a method of connecting to 520 is described.
  • the URL (CMS_URL) stored in the NFC module 100 is transmitted to the mobile terminal 200 through 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). ).
  • CMS_URL the URL
  • S720 wireless Internet network
  • 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.
  • 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.
  • FIG. 8 is a data flow diagram illustrating a method of operating a system according to another embodiment of the present invention.
  • 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).
  • BLE Bluetooth Low Energy
  • 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.
  • the beacon 110 refers to a hardware or hardware module for communication using a local area network (WPAN), or an Infrared Data Association (IrDA).
  • WPAN local area network
  • IrDA Infrared Data Association
  • the WPAN includes Bluetooth, Zigbee, or Ultra Wide Band (UWB).
  • UWB Ultra Wide Band
  • 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).
  • 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).
  • BID beacon ID
  • S815 calculate a distance DISi using the strength of the received beacon signal.
  • 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). .
  • RSSI received signal strength indication
  • 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).
  • BID beacon ID
  • DISi distance
  • each intermediate URL DURLi may be a URL corresponding to the content management system 600.
  • 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
  • the second intermediate URL (DURL2) may be a content management system 600.
  • 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.
  • 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.
  • 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).
  • 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).
  • the mobile terminal 210 may access a web site corresponding to the second web server 620 by using an application (S882).
  • the content management system 600 determines the third final destination URL (FURL3) corresponding to the third intermediate URL (DURL3).
  • the mobile terminal 210 may access a web site corresponding to the third web server 630 by using an application (S883).
  • 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.
  • CMS_URL a URL
  • beacon signal output from the beacon 110 May be implemented.
  • 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.
  • FIG. 9 is a flowchart illustrating a data flow for explaining a method of operating a system, according to another exemplary embodiment.
  • 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.
  • the mobile terminals 200 and 210 may mean the same mobile terminal.
  • 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.
  • APP mobile application
  • 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.
  • APP mobile application
  • 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.
  • 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.
  • CMS_URL a 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
  • APP a mobile application
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé pour accéder à une page Web en utilisant une étiquette NFC. Un procédé pour accéder à une page Web en utilisant une étiquette NFC, selon un mode de réalisation de la présente invention, comprend les étapes consistant en ce que : une application installée sur un terminal mobile reçoit un ID d'étiquette de l'étiquette NFC ; le programme d'application transmet l'ID d'étiquette à un premier moteur de recherche d'ID ; le programme d'application reçoit, du premier moteur de recherche d'ID, une adresse Web (URL) d'un système de gestion correspondant à l'ID d'étiquette ; le programme d'application accède au système de gestion en utilisant l'URL du système de gestion, et demande au système de gestion une URL d'une page Web; le programme d'application reçoit l'URL de la page Web du système de gestion ; et le système d'application accède à la page Web en utilisant l'URL de la page Web.
PCT/KR2014/009255 2014-01-08 2014-10-01 Procédé d'accès à une page web et procédé d'accès à un serveur web Ceased WO2015105263A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US14/655,116 US9706041B2 (en) 2014-01-08 2014-10-01 Web page access method and web server access method
US15/617,372 US10122842B2 (en) 2014-01-08 2017-06-08 Web page access method and web server access method

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
KR1020140002485A KR101555360B1 (ko) 2014-01-08 2014-01-08 모바일 애플리케이션을 이용한 웹 서버 접속 방법
KR10-2014-0002485 2014-01-08
KR20140008617 2014-01-23
KR10-2014-0008617 2014-01-23
KR10-2014-0026363 2014-03-06
KR1020140026363A KR101596690B1 (ko) 2014-01-23 2014-03-06 Nfc 태그 또는 비컨을 이용한 웹 페이지 접속 방법

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US14/655,116 A-371-Of-International US9706041B2 (en) 2014-01-08 2014-10-01 Web page access method and web server access method
US15/617,372 Division US10122842B2 (en) 2014-01-08 2017-06-08 Web page access method and web server access method

Publications (1)

Publication Number Publication Date
WO2015105263A1 true WO2015105263A1 (fr) 2015-07-16

Family

ID=53524066

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2014/009255 Ceased WO2015105263A1 (fr) 2014-01-08 2014-10-01 Procédé d'accès à une page web et procédé d'accès à un serveur web

Country Status (1)

Country Link
WO (1) WO2015105263A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101846778B1 (ko) * 2017-03-29 2018-04-06 전자부품연구원 Id 확인 서비스 방법 및 이를 적용한 m2m 시스템
WO2019231019A1 (fr) * 2018-05-31 2019-12-05 전자부품연구원 Procédé de service de résolution d'id, et système m2m l'utilisant
CN113037838A (zh) * 2021-03-08 2021-06-25 深圳奇迹智慧网络有限公司 操作响应方法、装置、计算机设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060079649A (ko) * 2005-01-03 2006-07-06 에스케이 텔레콤주식회사 존 기반 정보 서비스 방법 및 그 시스템
KR20090005461A (ko) * 2007-07-09 2009-01-14 에스케이 텔레콤주식회사 Ｒｆｉｄ 태그를 이용한 광고 제공 시스템 및 방법
US20110165859A1 (en) * 2010-01-04 2011-07-07 Alcatel-Lucent Usa Inc. Interactive id system using mobile devices
KR101281953B1 (ko) * 2012-03-05 2013-08-23 주식회사 러브이즈터치 Ｎｆｃ 태그 ｕｉｄ를 이용한 서비스 제공 방법과 상기 방법을 수행할 수 있는 운영 서버
KR20130101199A (ko) * 2012-03-05 2013-09-13 주식회사 러브이즈터치 Ｉｅｅｅ 802.11을 이용한 네트워킹 방법

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20060079649A (ko) * 2005-01-03 2006-07-06 에스케이 텔레콤주식회사 존 기반 정보 서비스 방법 및 그 시스템
KR20090005461A (ko) * 2007-07-09 2009-01-14 에스케이 텔레콤주식회사 Ｒｆｉｄ 태그를 이용한 광고 제공 시스템 및 방법
US20110165859A1 (en) * 2010-01-04 2011-07-07 Alcatel-Lucent Usa Inc. Interactive id system using mobile devices
KR101281953B1 (ko) * 2012-03-05 2013-08-23 주식회사 러브이즈터치 Ｎｆｃ 태그 ｕｉｄ를 이용한 서비스 제공 방법과 상기 방법을 수행할 수 있는 운영 서버
KR20130101199A (ko) * 2012-03-05 2013-09-13 주식회사 러브이즈터치 Ｉｅｅｅ 802.11을 이용한 네트워킹 방법

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101846778B1 (ko) * 2017-03-29 2018-04-06 전자부품연구원 Id 확인 서비스 방법 및 이를 적용한 m2m 시스템
WO2019231019A1 (fr) * 2018-05-31 2019-12-05 전자부품연구원 Procédé de service de résolution d'id, et système m2m l'utilisant
CN113037838A (zh) * 2021-03-08 2021-06-25 深圳奇迹智慧网络有限公司 操作响应方法、装置、计算机设备和存储介质

Similar Documents

Publication Publication Date Title
WO2016013767A1 (fr) Procédé pour assurer un service de communications entre terminaux mobiles en utilisant un dispositif sans fil en champ proche
WO2014200240A1 (fr) Procédé et appareil d'enregistrement de dispositif sans fil dans un système de communication sans fil
WO2014163341A1 (fr) Système de reconnaissance d'utilisateur à courte portée, et système et procédé permettant de fournir des informations l'utilisant
WO2014069844A1 (fr) Système et procédé de connexion de dispositifs par l'intermédiaire d'un réseau wi-fi
WO2014030889A1 (fr) Procédé et appareil de partage de contenu
WO2012033340A2 (fr) Procédé et système pour la communication bluetooth
WO2015108330A1 (fr) Dispositif électronique de commande d'un dispositif externe à l'aide d'un numéro et procédé associé
WO2012033271A1 (fr) Système d'affichage de pages web mises en cache, serveur, terminal et procédé correspondants, et support d'enregistrement lisible par ordinateur sur lequel est enregistré le procédé
WO2019156506A1 (fr) Système et procédé de fourniture de contenus conversationnels
WO2018190650A1 (fr) Dispositif électronique et procédé par lequel un dispositif électronique transmet et reçoit des informations d'authentification
WO2014030956A1 (fr) Appareil de téléchargement en amont de contenus, appareil terminal d'utilisateur de téléchargement en aval de contenus, serveur, système de partage de contenus et leur procédé de partage de contenus
WO2016021823A1 (fr) Procédé d'authentification d'utilisateur à l'aide d'un numéro de téléphone et d'un appareil nfc ou d'une balise
WO2018016877A1 (fr) Procédé et appareil pour une communication dans un système de communication sans fil
WO2011129635A2 (fr) Procédé et appareil pour la fourniture d'un service applicatif dans un système de communication mobile
WO2016018048A1 (fr) Procédé de transmission de contenu entre des terminaux par liaison de dispositif de commande de service
WO2016208992A1 (fr) Dispositif électronique et procédé de commande d'affichage d'image panoramique
EP3097743A1 (fr) Dispositif électronique de commande d'un dispositif externe à l'aide d'un numéro et procédé associé
WO2014042357A1 (fr) Système de commande de synchronisation d'écran, et procédé et appareil de synchronisation d'un écran à l'aide de ce système
WO2014077458A1 (fr) Procédé de distinction de type de réseau de communication et procédé de fourniture de contenu l'utilisant
WO2015046954A1 (fr) Appareil et procédé permettant d'accéder à un dispositif électronique ayant une fonction de point d'accès sans fil
WO2016006735A1 (fr) Dispositif électronique et procédé de recherche par un dispositif électronique d'un point d'accès dans un réseau local
WO2016122071A1 (fr) Terminal mobile et son procédé de commande
WO2015105263A1 (fr) Procédé d'accès à une page web et procédé d'accès à un serveur web
WO2013036035A2 (fr) Système de plateforme pour le marquage d'objets et procédé afférent
WO2018088703A1 (fr) Système de partage de parc de stationnement prenant en compte des niveaux de compétence de conduite, procédé associé et support d'enregistrement enregistré avec un programme d'ordinateur

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 14655116

Country of ref document: US

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14877903

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 20.10.2016)

122 Ep: pct application non-entry in european phase

Ref document number: 14877903

Country of ref document: EP

Kind code of ref document: A1