WO2014092266A1

WO2014092266A1 - Method for issuing nfc tags

Info

Publication number: WO2014092266A1
Application number: PCT/KR2013/004623
Authority: WO
Inventors: 이경전; 권선희
Original assignee: 주식회사 러브이즈터치
Priority date: 2012-12-11
Filing date: 2013-05-28
Publication date: 2014-06-19
Also published as: KR20140075236A; KR101454760B1

Abstract

According to the present invention, a method for issuing NFC tags uses an application which performs on a NFC mobile communication terminal and comprises the steps of: transmitting, by the application, a tag issuance request signal and user authentication information of the NFC mobile communication terminal to an administrator server; confirming the authentication information using user information in response to the tag issuance request signal by the administrator server, and when a URL corresponding to the NFC tag on the basis of the result of the confirmation is created, receiving, by the application, the URL transmitted from the administrator server; and writing, by the application, the URL in the NFC tag when the NFC mobile communication terminal approaches the NFC tag so that the administrator server can permit the NFC tag to issue the tag.

Description

How to issue an NFC tag

An embodiment according to the concept of the present invention relates to a near field communication (NFC) tag, and relates to an NFC tag issuing method using an application executed in an NFC mobile communication terminal.

Today, service customers are provided with each service provided by each service provider in each of the various spaces through NFC tags.

That is, when the service customer accesses an NFC device, such as an NFC reader, to the NFC tag, the NFC reader reads information stored in the NFC tag, for example, a uniform resource locator (URL), and corresponds to the URL. You can access a web site. Thus, the service customer can use the service provided by the website.

The URL corresponding to the web site is pre-made and manually input to the NFC writing device, and is written to the NFC tag through the NFC writing device.

In addition, the NFC tag is managed only by a server managing the web site corresponding to the URL.

The technical problem to be achieved by the present invention is to provide an NFC tag issuing method using an application running on the NFC mobile communication terminal.

NFC tag issuing method according to an embodiment of the present invention has the effect that it is easy to allow the tag issuance to the NFC tag by writing the URL generated from the operation server through the application installed on the NFC mobile communication terminal to the NFC tag.

In addition, each NFC tag allowed tag issuance has an effect that can be efficiently managed from one operating server.

The detailed description of each drawing is provided in order to more fully understand the drawings, which are incorporated in the detailed description of the invention.

1 is a block diagram of an NFC tag issuing system according to an embodiment of the present invention.

2 is a block diagram of an NFC tag issuing system according to another embodiment of the present invention.

NFC tag issuing method using an application executed in a near field communication (NFC) mobile communication terminal according to an embodiment of the present invention, the application in response to the tag issuance request for the NFC tag of the user of the NFC mobile communication terminal tag Generating an issuing request signal, transmitting the tag issuing request signal and authentication information of the user of the NFC mobile communication terminal to an operation server, and the operation server, in response to the tag issuing request signal, user information stored in a database; Confirming the authentication information by using and generating a uniform resource locator (URL) corresponding to the NFC tag based on a result of the verification, the application receiving the URL transmitted from the operation server, and the operation To allow the server to issue the tag to the NFC tag When the NFC mobile communication terminal approaches the NFC tag, the application may include writing the URL to the NFC tag.

The method includes the step of the application transmitting the UID to the primary server when a unique identification number (UID) is transmitted from the NFC tag to the NFC device of the NFC mobile terminal after the URL is written to the NFC tag. It may further include.

The method corresponds to the NFC tag in response to the user's request to create a content of the NFC mobile communication terminal, so that the operations server can provide the content to users interfacing the NFC tag. The method may further include generating the content and transmitting the content together with the UID to the operation server.

The method may be configured such that the application changes the content in response to a content change request of the user of the NFC mobile communication terminal so that the operation server may provide different contents to the users, and sends the changed content to the operation server. The method may further include transmitting.

NFC tag issuing method using an application and an operation server installed in the NFC (near field communication) mobile communication terminal according to an embodiment of the present invention, the user of the NFC mobile communication terminal while the application is running through the NFC tag When requesting a tag for issuing, the operation server receives the user's authentication information and a tag issuing request signal output from the application and uses the user information stored in a database in response to the tag issuing request signal. Verifying, generating a URL (uniform resource locator) corresponding to the NFC tag based on the verification result, and transmitting the URL to the NFC mobile communication terminal, and the operation server issues the tag to the NFC tag. To allow the NFC mobile communication terminal Approaching the NFC tag, the application writing the URL transmitted from the primary server to the NFC tag, and after the URL is written to the NFC tag, a UID (unique identification number) When the NFC tag is transmitted to the NFC device of the NFC mobile communication terminal, the application may include the step of transmitting the UID to the operating server.

The method may further include generating, by the operations server, the content corresponding to the NFC tag to provide content to users who interface the NFC tag, and storing the content in the database.

The method may further include the operation server storing the UID and the URL output from the application in the database.

The method is characterized in that when the application generates a content change request signal in response to a content change request of the user of the NFC mobile communication terminal, such that the operation server can provide different contents to the users, The method may further include changing the content in response to the content change request signal output from the application, and storing the changed content in the database.

NFC tag issuing method according to an embodiment of the present invention may be written in a computer program and stored in a computer-readable recording medium.

Specific structural or functional descriptions of the embodiments according to the inventive concept disclosed herein are provided for the purpose of describing the embodiments according to the inventive concept only. It may be embodied in various forms and is not limited to the embodiments described herein.

Embodiments according to the inventive concept may be variously modified and have various forms, so embodiments are illustrated in the drawings and described in detail herein. However, this is not intended to limit the embodiments in accordance with the concept of the present invention to specific embodiments, it includes all changes, equivalents, or substitutes included in the spirit and scope of the present invention.

Terms such as first or second may be used to describe various components, but the components should not be limited by the terms. The terms are only for the purpose of distinguishing one component from another, for example, without departing from the scope of the rights according to the inventive concept, the first component may be named a second component, and similarly The second component may also be referred to as the first component.

When a component is referred to as being "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may be present in between. Should be. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that there is no other component in between. Other expressions describing the relationship between components, such as "between" and "immediately between," or "neighboring to," and "directly neighboring to" should be interpreted as well.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. As used herein, the terms "comprise" or "having" are intended to indicate that there is a feature, number, step, action, component, part, or combination thereof that is described, and that one or more other features or numbers are present. It should be understood that it does not exclude in advance the possibility of the presence or addition of steps, actions, components, parts or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art, and are not construed in ideal or excessively formal meanings unless expressly defined herein. Do not.

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

Referring to FIG. 1, a near field communication (NFC) tag issuing system 10A may include an NFC mobile communication terminal 110, an NFC tag 120, and an operation server 130.

NFC mobile communication terminal 110 may include a mobile communication terminal including NFC device 112, such as a laptop computer, a mobile phone, a smart phone, or a tablet PC. Can be.

NFC mobile communication terminal 110 may be installed with an application 114 that can execute the method according to an embodiment of the present invention shown in FIG.

According to an embodiment, the application 114 may be downloaded and installed from the operation server 130.

According to another embodiment, the application 114 may be downloaded and installed from a web store or an android market.

When the user of the NFC mobile communication terminal 110 requests to issue a tag for the NFC tag 120 while the application 114 installed in the NFC mobile communication terminal 110 is running, the application 114 corresponds to the tag issuance. The tag issuance request signal REQ may be generated.

That is, the application 114 generates a tag issuing request signal REQ in response to a tag issuing request for the NFC tag 120 of the user of the NFC mobile communication terminal 110 and operates a tag issuing request signal REQ. It may transmit to the server 130.

Therefore, the user of the NFC mobile communication terminal 110 can easily request the issuance of the tag for the NFC tag 120 to the operation server 130 through the application 114.

For example, the user of the NFC mobile communication terminal 110 may be an operator who manages the NFC tag 120 or an administrator employed by the operator.

In addition, the user of the NFC mobile communication terminal 110 may be a manager hired by the operator of the operation server 130 or the operator of the operation server 130 to manage the NFC tag 120.

The application 114 may transmit the authentication information ATI and the tag issuance request signal REQ of the user of the NFC mobile communication terminal 110 to the operation server 130 (S110).

For example, the authentication information ATI may be an identification and password that can execute the application 114. In addition, the authentication information (ATI) may be an ID and password for connecting to the operation server 130. The ID and password capable of running the application 114 may be the same as the ID and password capable of connecting to the production server 130. According to an embodiment, the authentication information ATI may further include a phone number of the NFC mobile communication terminal 110.

The operation server 130 may request the user information (UAI) from the database 135 in response to the tag issuance request signal (REQ).

Although the database 135 is illustrated outside of the operation server 130 in FIG. 1, the database 135 may be implemented inside the operation server 130 according to an embodiment.

The database 135 may transmit user information (UAI) to the operation server 130 in response to a request of the operation server 130 (S113).

For example, the user information UAI may include a list for each preset or registered authentication information.

The primary server 130 may check the authentication information ATI using the user information UAI transmitted from the database 135.

The operation server 130 confirms the authentication information (ATI) using the user information (UAI) transmitted from the database 135, and based on the verification result, the operation server 130 generates a uniform resource locator (URL) corresponding to the NFC tag 120. The generated URL may be transmitted to the NFC mobile communication terminal 110 (S120).

In this case, the URL may be a URL for accessing a web site provided by an administrator who manages the NFC tag 120, for example, a user of the NFC mobile communication terminal 110 or an operation server 130.

The application 114 may receive the URL transmitted from the operation server 130 (S120) and transmit the received URL to the NFC device 112 (S130).

That is, in response to the tag issuance request signal REQ, the operation server 130 confirms the authentication information ATI using the user information UAI stored in the database 135 and responds to the NFC tag based on the verification result. If the generated URL, the application 114 may receive the URL transmitted from the operation server 130 (S120).

The NFC device 112, such as the NFC reader and the NFC tag 120, of the NFC mobile communication terminal 110 may communicate with each other via interfacing, for example, scanning or contactless tagging. Can be.

When the NFC mobile communication terminal 110 approaches the NFC tag 120, the application 110 transmits from the operations server 130 so that the operations server 130 can permit tag issuance to the NFC tag 120. The written URL may be written to the NFC tag 120 (S140).

Therefore, the operation server 130 may easily permit the tag issuance to the NFC tag 120 by writing the URL to the NFC tag 120 through the application 114 installed in the NFC mobile communication terminal 110.

In addition, NFC tags allowed to issue tags and web sites corresponding to the allowed NFC tags may be efficiently managed from one operation server 130.

After the URL transmitted from the operation server 130 is written on the NFC tag 120, the NFC device 112 may read information stored in the NFC tag 120, for example, a unique identification number (UID) (S150). This is called scanning or tagging.

The NFC device 112 may receive the UID transmitted from the NFC tag 120 (S150) and transmit the received UID to the application 114 (S160).

The application 114 may transmit the UID transmitted from the NFC device 112 to the operation server 130 (S170).

That is, when the UID is transmitted from the NFC tag 120 to the NFC device 112 of the NFC mobile communication terminal 110 after the URL is written to the NFC tag 120 (S150), the application 114 operates the UID. The server 130 may transmit the data to the server 130 (S170).

The operation server 130 may store the URL and the UID output from the application 114 in the database 135 (S175). For example, the operation server 130 may store a list of matching URLs and UIDs in the database 135.

According to an embodiment, after the tag issuance for the NFC tag 120 is made, the operation server 130 receives the UID every time the NFC tag 120 is interfaced to record or accumulate the number of UID receptions in the list. Can be.

For example, the UID may be information for confirming whether the NFC tag 120 is actually scanned or tagged by the NFC device 112.

That is, by issuing a tag for the NFC tag 120 from one operation server 130, the operation server 130 needs or actions of those who interface the NFC tag 120 from the number of UID received Can be analyzed.

Accordingly, the user of the NFC mobile communication terminal 110 requests the number of touches on the NFC tag 120, for example, the number of times of receiving the UID, to the operation server 130 through the application 114, and as a result of the inquiry request The number of times of UID reception or analysis of the operation server 130 may be confirmed.

Therefore, the operation server 130 may check the NFC tag 120 which is popular among people from the number of times of receiving the UID, and may provide various services to those who will newly interface the NFC tag 120 according to the confirmation result. . For example, the various services may include a stamp service and a coupon service.

In order for the operations server 130 to provide content (CNTS) to users who interface the NFC tag 120, the application 114 responds to the user's request for content creation of the NFC mobile communication terminal 110. The content CNTS corresponding to 120 may be generated, and the content CNTS generated together with the UID may be transmitted to the operation server 130 (S180).

As used herein, the term "transmit together" means both transmitting simultaneously or sequentially at regular time intervals.

The content CNTS may be a still image, a video, a sound source, or an advertisement image.

For example, when the content CNTS is advertising content, an administrator who manages the NFC tag 120, for example, a user or an operation server 130 of the NFC mobile communication terminal 110 may interface the advertising content with the NFC tag 120. It can increase the advertising effect by providing to the users.

That is, a user of the NFC mobile communication terminal 110 provides the contents CNTS corresponding to the NFC tag 120 to the operation server 130 through the application 114, thereby interfacing the NFC tag 120 in the future. They can access the web site corresponding to the URL and use the content (CNTS).

The operation server 130 may receive the content CNTS generated from the application 114 and store the received content CNTS in the database 135 along with the URL and the UID output from the application 114 (S182). ).

According to an embodiment, the application 114 responds to the content change request of the user of the NFC mobile communication terminal 110 so that the operation server 130 can provide different content to users who interface the NFC tag 120. The generated content CNTS may be changed and the changed content C_CNTS may be transmitted to the operation server 130 (S200).

The operation server 130 may change the generated content CNTS into the changed content C_CNTS and store it in the database 130 (S210).

That is, when the operation server 130 records or accumulates the number of UID receptions in the list, the operation server 130 may also store the number of contents (CNTS) provided in the list, and the user of the NFC mobile communication terminal 110 may operate in the operation server ( 130 may be provided with the number of times of providing the content (CNTS).

Accordingly, the user of the NFC mobile communication terminal 110 may change the content CNTS by reflecting an analysis result of the needs or behaviors of those who interface the NFC tag 120 and provide the changed content C_CNTS.

Referring to FIG. 2, the NFC (near field communication) tag issuing system 10B may include an NFC mobile communication terminal 110, an NFC tag 120, and an operation server 130.

Steps S110 through S175 shown in FIG. 2 are substantially the same as those described above with reference to FIG. 1, and thus description thereof will be omitted.

The operation server 130 generates the content CNTS corresponding to the NFC tag 120 to provide the content CNTS to users who interface the NFC tag 120, and stores the generated content CNTS in a database ( 135) (S230).

According to an embodiment, the operation server 130 may generate the content CNTS based on the user information UAI stored in the database 135. For example, the user information (UAI) may further include a service provided by a user of the NFC mobile communication terminal 110, previously provided content, a service area of interest, and the like.

The application 114 may generate a content change request signal C_REQ in response to the content change request of the user of the NFC mobile communication terminal 110 and transmit the content change request signal C_REQ to the operation server 130 ( S240).

The operation server 130 may change the content CNTS in response to the content change request signal C_REQ output from the application 114 and store the changed content C_CNTS in the database 135 (S250).

Although the present invention has been described with reference to one embodiment shown in the drawings, this is merely exemplary, and it will be understood by those skilled in the art that various modifications and equivalent other embodiments are possible. . Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

The present invention can be used in a terminal capable of reading an NFC tag, an operation server for managing the NFC tag, and a method for issuing the NFC tag.

Claims

In the NFC tag issuing method using an application running on a NFC (near field communication) mobile communication terminal,

The application generates a tag issuing request signal in response to a tag issuance request for the NFC tag of the user of the NFC mobile communication terminal, and operates the tag issuing request signal and the authentication information of the user of the NFC mobile communication terminal Transmitting to;

The application server checks the authentication information using user information stored in a database in response to the tag issuance request signal, and generates a URL (uniform resource locator) corresponding to the NFC tag based on a result of the verification. Receiving the URL sent from the operating server; And

The application writing the URL to the NFC tag when the NFC mobile communication terminal accesses the NFC tag so that the operations server allows the tag issuance to the NFC tag. How to issue an NFC tag.
The method of claim 1,

When the URL is written to the NFC tag and a UID (unique identification number) is transmitted from the NFC tag to the NFC device of the NFC mobile communication terminal, the application further comprising transmitting the UID to the operations server. NFC tag issuance method.
The method of claim 2,

The application may provide the content corresponding to the NFC tag in response to the content generation request of the user of the NFC mobile communication terminal, so that the operation server may provide the content to the users who interface the NFC tag. And generating and transmitting the content together with the UID to the operation server.
The method of claim 3,

The application changing the content in response to a content change request of the user of the NFC mobile communication terminal and transmitting the changed content to the operation server so that the operation server can provide different contents to the users. NFC tag issuing method comprising more.
In the NFC tag issuing method using an application and an operation server installed in a near field communication (NFC) mobile communication terminal

When the user of the NFC mobile communication terminal requests to issue a tag for the NFC tag through the application while the application is running, the operation server receives the user authentication information and a tag issuing request signal output from the application. In response to the tag issuing request signal, confirming the authentication information using user information stored in a database, and generating a uniform resource locator (URL) corresponding to the NFC tag based on a result of the verification; Transmitting to the NFC mobile communication terminal;

When the NFC mobile communication terminal approaches the NFC tag, the application server writes the URL transmitted from the production server to the NFC tag so that the production server may allow the tag issuance to the NFC tag. ); And

When the URL is written to the NFC tag and a UID (unique identification number) is transmitted from the NFC tag to the NFC device of the NFC mobile communication terminal, the application sending the UID to the operations server. How to issue an NFC tag.
The method of claim 5,

And generating, by the operation server, the content corresponding to the NFC tag to provide content to users who interface the NFC tag, and storing the content in the database.
The method of claim 5,

NFC server issuing method further comprises the step of storing the UID and the URL output from the application in the database.
The method of claim 6,

When the application generates a content change request signal in response to the user's content change request of the NFC mobile communication terminal so that the production server can provide different content to the users, the production server is sent from the application. And changing the content in response to the output content change request signal, and storing the changed content in the database.
A computer-readable recording medium having recorded thereon a computer program capable of performing the NFC tag issuing method according to claim 1.