KR101469658B1 - Mehtod for providing service based on identity - Google Patents

Abstract

The method for providing an account based service according to an embodiment of the present invention is characterized in that when an NFC apparatus of the NFC mobile communication terminal transmits a first URL and a tag ID transmitted from an NFC tag to the application during execution of an application installed in the NFC mobile communication terminal, The operation server receiving the tag ID and the first connection request signal outputted from the application, the operation server storing the account ID corresponding to the tag ID, stored in the first database in response to the first connection request signal, When the management server transmits the second connection request signal to the management server in response to the second connection request signal and transmits the account information corresponding to the account ID to the operation server, The operating server generates an authentication request signal, and sends the authentication request signal to the application It may comprise the step of transmitting.

Description

METHOD FOR PROVIDING SERVICE BASED ON IDENTITY [0002]

An embodiment according to the concept of the present invention relates to a service providing method, and more particularly, to a method of providing an account based service using an NFC (near field communication) tag.

The service provider may issue an identity to the service, the device associated with the service, or the service customer using the service, while providing the service to the service customer.

The service customer must remember the account associated with the service, e.g., an account issued to confirm the use of the service and pay the service fee.

In addition, the provider or the manager who manages the service must also remember the issued account in order to confirm the use of the service by the service customer, manage the service, and the like.

1. Published Patent Publication No. 2011-0033119 (published on March 30, 2011) 2. Registration Patent Publication No. 10-0998327 (registered on November 29, 2010)

The technical problem to be solved by the present invention is to provide an account-based service to a customer who receives a service using an NFC tag or an administrator who manages the service.

The method for providing an account based service according to an exemplary embodiment of the present invention is a method for providing an account based service through a first ULC (uniform resource locator) transmitted from an NFC tag of an NFC apparatus of an NFC mobile communication terminal while an application installed in an NFC And an operation server receiving a first connection request signal output from the application when the operation server transmits the tag ID to the application, and the operation server, in response to the first connection request signal, Transmitting an account ID and a second connection request signal stored in a database and corresponding to the tag ID to a management server; and storing the account ID in the second database in response to the second connection request signal, When the corresponding account information is transmitted to the operation server, the operation server generates an authentication request signal It may include sending the authentication request signal to the application.

The method comprises the steps of: when a user of the NFC mobile communication terminal inputs authentication information according to the authentication request signal, the operating server compares the authentication information output from the application with the account information, Generating the account management information using the information and the tag information stored in the first database, and transmitting the account management information to the application.

The method includes storing the account usage information output from the application in the first database when the user of the NFC mobile communication terminal inputs the account usage information based on the account management information .

When the user of the NFC mobile communication terminal inputs the account use information based on the account management information, the operation server receives the account use information output from the application, To the management server.

The account information may include service information related to the service associated with the account, service customer information using the service, and manager information for providing or managing the inter-service.

The tag information may include a number of tackings of the NFC tag, a connection record of the operation server, and a recent tagging date of the NFC tag.

The account management information may include the tag information and the account information.

The account usage information may include current usage information for the service associated with the account, the service failure information, the service management information, the service use confirmation information, and the update information of the service customer.

The method of providing an account based service according to an exemplary embodiment of the present invention may be stored in a computer-readable recording medium.

The method of providing an account based service according to an embodiment of the present invention is effective in providing an account based service efficiently using an NFC tag even if a service customer or a service manager does not know an account.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS In order to more fully understand the drawings recited in the detailed description of the present invention, a detailed description of each drawing is provided.
1 shows a block diagram and a data flow of an account management system according to an embodiment of the present invention.

It is to be understood that the specific structural or functional descriptions of embodiments of the present invention disclosed herein are only for the purpose of illustrating embodiments of the inventive concept, But may be embodied in many different forms and is not limited to the embodiments set forth herein.

Embodiments in accordance with the concepts of the present invention are capable of various modifications and may take various forms, so that the embodiments are illustrated in the drawings and described in detail herein. It should be understood, however, that it is not intended to limit the embodiments according to the concepts of the present invention to the particular forms disclosed, but includes all modifications, equivalents, or alternatives falling within the spirit and scope of the invention.

The terms first, second, or the like may be used to describe various elements, but the elements should not be limited by the terms. The terms are intended to distinguish one element from another, for example, without departing from the scope of the invention in accordance with the concepts of the present invention, the first element may be termed the second element, The second component may also be referred to as a first component.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between. Other expressions that describe the relationship between components, such as "between" and "between" or "neighboring to" and "directly adjacent 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. The singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, the terms "comprises ", or" having ", or the like, specify that there is a stated feature, number, step, operation, , Steps, operations, components, parts, or combinations thereof, as a matter of principle.

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 to which this invention belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the meaning of the context in the relevant art and, unless explicitly defined herein, are to be interpreted as ideal or overly formal Do not.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the preferred embodiments of the present invention with reference to the accompanying drawings.

1 shows a block diagram and a data flow of an account management system according to an embodiment of the present invention.

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

The NFC mobile communication terminal 110 includes a mobile communication terminal including the NFC device 112 such as a laptop computer, a mobile phone, a smart phone, or a tablet PC .

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

The application 114 may be downloaded and installed from the operating server 130.

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

The NFC mobile terminal 110 and the NFC tag 120 can communicate with each other through interfacing, e.g., scan or contactless tagging.

The user of the NFC mobile communication terminal 110 executes the application 114 installed in the NFC mobile communication terminal 110 in order to receive the account based service from the operation server 130 When the user of the NFC mobile communication terminal 110 approaches the NFC device 112 of the NFC mobile communication device 110 such as the NFC reader 120 through the NFC tag 120, A uniform resource locator (URL1) and a tag ID (TID) of the operation server 130 providing the information stored in the tag 120, for example, an account based service (S110). This is called scanning or tagging.

Depending on the embodiment, the tag ID (TID) may be a unique number issued from the operating server 130 to the NFC tag 120. The tag ID (TID) may also be used to connect to the operational server 130.

The "account" used herein refers to a service provided or managed by the operation server 130 and / or the management server 140, a device associated with the service, or an identification number assigned to a service customer using the service .

According to an embodiment, the service may be to provide or manage city gas, electricity, water, or the like. For example, the device associated with the service may be a meter capable of verifying the usage of the city gas, the electricity, or the water supply.

Thus, the account may be granted to identify the service, the device associated with the service, or the service customer from the operations server 130 and / or the management server 140. [

The NFC apparatus 112 receives the first URL (URL1) and the tag ID (TID) transmitted from the NFC tag 120 in step S120 and transmits the received first URL (URL1) and the tag ID (TID) (S125).

The application 114 may generate the first connection request signal REQ1 using the first URL (URL1) to access a web site corresponding to the first URL (URL1), for example, the operational server 130 have.

The application 114 may transmit the tag ID (TID) and the first connection request signal REQ1 to the operational server 130 (S130).

That is, when the first URL (URL1) and the tag ID (TID) are received from the NFC apparatus 112, the application 114 generates the first connection request signal REQ1 and transmits the tag ID (TID) And may transmit the signal REQ1 to the operation server 130 (S130).

The operation server 130 may transmit the tag ID (TID) received from the application 114 to the first database 131 in response to the first connection request signal REQ1 (S131).

The first database 131 is shown on the outside of the operational server 130 in FIG. 1, but may also be implemented within the operational server 130 according to an embodiment.

The first database 131 searches for an account ID (AID) matching or corresponding to the tag ID (TID) received from the tag ID list and transmits the account ID (AID) (URL2) for connection to the operation server 130 (S133). For example, the tag ID list may be a list of account IDs matched to each of the tag IDs previously issued or registered.

According to the embodiment, the first database 131 may transmit the account ID (AID), the second URL (URL2), and the tag information T_I together to the operation server 130 (S133).

According to an embodiment, the tag information T_I may include NFC tag 120 tagging count, connection record to the operation server 130, and NFC tag 120 recent tagging date.

The operation server 130 may generate the second connection request signal REQ2 using the second URL (URL2) received from the first database 131. [

The operation server 130 may transmit the account ID (AID) and the second connection request signal REQ2 to the management server 150 (S140).

The management server 150 may transmit the account ID (AID) received from the operation server 130 to the second database 151 in response to the second access request signal REQ2 (S141).

The second database 151 may retrieve the account information A_I that matches or corresponds to the account ID AID received from the account ID list and may transmit the retrieved account information A_I to the management server 150 (143).

Although the second database 151 is shown outside the management server 150 in FIG. 1, it may be implemented in the management server 130 according to an embodiment.

According to the embodiment, the account information A_I may include service information including general information of the service, service customer information using the service, and manager (or provider) information for providing or managing the service.

For example, the service information may include information on the previous usage amount of the service, information on payment of the usage fee of the service, and the like.

The service customer information may include a name, a mobile phone number, an e-mail address, and a resident registration number of the service customer.

The manager information may include a name of the manager, a mobile phone number, an e-mail address, a resident registration number, and an employee number.

The management server 150 may transmit the account information A_I to the operation server 130 (S150).

When the account information A_I is received from the management server 150, the operation server 130 may generate an authentication request signal CREQ of the NFC mobile communication terminal 110.

The operational server 130 may transmit the authentication request signal CREQ to the application 114 (S160).

The application 114 may display a graphic user interface corresponding to the authentication request signal CREQ on the display of the NFC mobile communication terminal 110. [

The user of the NFC mobile communication terminal 110 can input the authentication information (CI) according to the authentication request signal (CREQ).

The user of the NFC mobile communication terminal 110 may be the service customer using the service or the manager (or business entity) managing the service.

When the user of the NFC mobile communication terminal 110 inputs the authentication information (CI) according to the authentication request signal (CREQ), the application 114 can transmit the input authentication information (CI) to the operation server 130 S165).

The operation server 130 compares the authentication information CI received from the application 114 with the account information A_I and outputs the account management information AMI (T_I) and the accounting information A_I Can be generated.

The operational server 130 may send the account management information (AMI) to the application 114 (S170).

For example, the account management information (AMI) may include tag information T_I and account information A_I.

The application 114 may display the account management information (AMI) received from the operation server 130 on the display of the NFC mobile communication terminal 110. [

The user of the NFC mobile communication terminal 110 can input the account usage information AUI based on the AMI displayed on the display of the NFC mobile communication terminal 110. [

The application 114 may transmit the account usage information (AUI) input by the user of the NFC mobile communication terminal 110 to the operation server 130 (S175).

For example, the account usage information (AUI) may include current usage information for the service, the service failure information, the service management information, the service use confirmation information, and the update information of the service customer.

The operating server 130 may store the account usage information (AUI) sent from the application 114 in the first database 131. [

According to an embodiment of the present invention, the operation server 130 may provide a settlement service for paying a service use fee for the use of the service based on the account use information (AUI) to a user of the NFC mobile communication terminal 110, .

According to another embodiment, the operating server 130 may use a system for paying service usage costs for service use based on account usage information (AUI), such as a payment server (not shown) For example, a service allowing the service customer to access the service.

According to another embodiment, the operational server 130 sends the account usage information (AUI) to the management server 150, and the management server 150 moves the payment service to the NFC based on the account usage information (AUI) To the user of the communication terminal 110, for example, the service customer.

While the present invention has been described with reference to exemplary embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the scope of the present invention . Accordingly, the true scope of the present invention should be determined by the technical idea of the appended claims.

10: Account Management System
110: NFC mobile communication terminal
112: NFC device
114: Application
120: NFC tag
130: Operational server
131: first database
150: management server
151: second database

Claims (9)

A first UL (uniform resource locator) and a tag ID (identification) for connecting an NFC apparatus of an NFC mobile communication terminal to an operation server transmitted from an NFC tag while an application installed in an NFC mobile communication terminal is executed, To the application, the operating server receiving the tag ID and the first connection request signal from the application;
The operation server reads the account ID corresponding to the tag ID and the second URL for accessing the management server from the first database in response to the first connection request signal, Transmitting to the server; And
The management server reads the account information corresponding to the account ID stored in the second database in response to the second connection request signal, and transmits the read account information to the operation server. The operation server generates an authentication request signal, And sending a signal to the application. The method according to claim 1,
A user of the NFC mobile communication terminal inputs authentication information according to the authentication request signal and the operation server compares the authentication information transmitted from the application with the account information and if the authentication information matches the account information Generating account management information using the account information and the tag information stored in the first database, and transmitting the account management information to the application. 3. The method of claim 2,
Further comprising the step of the user of the NFC mobile communication terminal inputting account use information based on the account management information and the operation server storing the account usage information transmitted from the application in the first database Based service delivery method. 3. The method of claim 2,
The user of the NFC mobile communication terminal inputs the account use information based on the account management information, the operation server receives the account usage information transmitted from the application, and transmits the account usage information to the management server The method further comprising the steps of: The method according to claim 1,
Wherein the account information includes service information regarding a service associated with the account, service customer information using the service, and manager information for providing or managing the service. 3. The method of claim 2,
Wherein the tag information includes a tagging count of the NFC tag, a connection record of the operation server, and a latest tagging date of the NFC tag. 3. The method of claim 2,
And the account management information includes the tag information and the account information. The method of claim 3,
Wherein the account usage information includes current usage information for a service associated with the account, service failure information, service management information, service usage confirmation information, and update information of the service customer. A computer-readable recording medium storing a computer program capable of performing the account-based service providing method according to claim 1.

Images