KR102645154B1 - System and method for providing payment service using sharing payment means - Google Patents

Abstract

The present invention relates to a payment service system and method using a shared payment method, which includes a short-range communication unit that detects a wearable device in the short distance, a user authentication unit that authenticates the user, and at least one device detected through the short-range communication unit when the user is authenticated. A wearable device is provided that includes a control unit that transmits a first authentication token to a wearable device and activates a shared payment method with the detected wearable device when the second authentication token received from the detected wearable device is valid.

Description

Payment service system and method using shared payment methods {SYSTEM AND METHOD FOR PROVIDING PAYMENT SERVICE USING SHARING PAYMENT MEANS}

The present invention relates to a payment service system and method using a shared payment method. More specifically, the present invention relates to a payment service system and method using a shared payment method. More specifically, a wearable device detected through short-distance communication transmits its own authentication token to the detected wearable device and receives the authentication token from the detected wearable device. It relates to a payment service system and method using a shared payment method that activates shared payment methods when the authentication token is valid.

Wearable devices literally mean devices that can be worn on the human body, and depending on the part of the wearer, they include glasses, watches, bracelets, shoes, rings, belts, bands, necklaces, etc. There are many different types of headsets, clothing, etc. These wearable devices are currently in the rapid diffusion stage, and among them, wearable glasses, wearable watches, and wearable bands, which are very closely related to human life and are easy to wear, form the largest product group.

Meanwhile, wearable devices are also called smart devices. Although it is necessary to start operation by user input, once operation begins, various additional information can be automatically generated and provided to the user. For example, if a user wearing a wearable watch wants to measure his or her heart rate, the wearable watch measures the user's heart rate as soon as the user presses the heart rate measurement input button and generates various information based on the measured heart rate. It can be provided to the user. Meanwhile, many wearable devices that do not require startup by user input have recently appeared. For example, in the case of a wearable band, the user's heart rate can be continuously measured even without the user's input to start the operation, and future wearable devices are likely to develop in a direction that does not require the user's input to start the operation. Very high. This is because the convenience of operating the device increases as user input is not required.

The source of various additional information that these wearable devices provide to users is information measured from the user. Therefore, wearable devices must be equipped with sensors to measure various information from the user, and the more types of sensors installed, the more information can be measured from the user. Therefore, recent wearable devices tend to be equipped with heart rate sensors, GPS (Global Positioning System) sensors, and step count sensors, and research is continuing to install various sensors in the limited space inside the device.

A wearable device can measure information from a user through an installed sensor, then generate various additional information based on this and provide it to the user. For example, the user's current location can be measured to provide information about nearby stores or products related to the user's interests. Provision of such additional information may be provided through the functions of the wearable device itself, but since it is impossible to provide all necessary additional information to different users from one wearable device, recently, applications installed on wearable devices have been used. are being developed together. Here, the application can be viewed as a type of application program, and can play the role of generating and providing various additional information based on information measured through the functions of the wearable device itself. In the above example, provision of information about nearby stores or products related to the user's interests may all be performed by the application. In other words, whenever a new application is developed, the additional information that can be provided to users through wearable devices is bound to become more diverse, and the development of applications can be seen as a companion moving forward along with the development of the wearable device itself.

Recently, building a system that allows payment through wearable devices has emerged as a major interest in related industries. For example, by including an NFC (Near Frequency Communication) function in the wearable device itself and registering the user's credit card in the application, the user can make payments through the wearable device without having to take out their wallet to pay. In other words, it can replace a conventional wallet and perform a mobile wallet function. However, there are many security-related issues such as user personal information and card payment approval, so there are many technical challenges that need to be solved.

In addition, when making a payment using a common payment method (payment method), there is a problem that the common payment method can be used regardless of the consent of the joint holder, even though it is a public asset.

Prior Art 1: Korean Patent No. 1,062,011: Smart card with signature information input unit and user authentication method

The purpose of the present invention is to provide a payment service system and method using a shared payment method that allows payment through a shared payment method only when preset conditions are met when using a shared payment method.

Another object of the present invention is to provide a payment service system and method using a shared payment method that allows payment to be made safely even if the wearable device is lost when making a payment using a shared payment method.

Meanwhile, the technical problem to be achieved by the present invention is not limited to the technical problems mentioned above, and various technical problems may be included within the scope apparent to those skilled in the art from the contents described below.

According to one aspect of the present invention, a short-range communication unit that detects a short-range wearable device, a user authentication unit that authenticates the user, and when the user is authenticated, transmits a first authentication token to at least one wearable device detected through the short-range communication unit. In addition, if the second authentication token received from the detected wearable device is valid, a wearable device including a control unit that activates a shared payment method with the detected wearable device is provided.

The first authentication token or the second authentication token is a previously stored token or a newly created token and may include user identification information or an expiration date.

If the second authentication token is valid, the control unit performs pairing with the detected wearable device, confirms the shared payment method with the detected wearable device, and if the activation conditions of the shared payment method are satisfied, the sharing You can activate your payment method.

The control unit may perform payment using the activated shared payment method.

The wearable device may further include a storage unit that stores at least one of standard authentication information, information about a shared payment method shared with each wearable device, and activation conditions for activating the shared payment method.

According to another aspect of the present invention, in a method for a wearable device to provide a payment service using a shared payment method, (a) authenticating a user and obtaining or generating a first authentication token, (b) obtaining or Transmitting the generated first authentication token to at least one wearable device detected through short-distance communication, (c) receiving a second authentication token from the detected wearable device, and determining whether the second authentication token is valid. A payment service method using a shared payment method is provided, including the step of (d) activating a shared payment method shared with the detected wearable device when the second authentication token is valid.

Step (a) includes obtaining the user's biometric information, comparing the obtained biometric information with pre-stored biometric information to determine whether the two biometric information are identical, and, if the two biometric information are the same, pre-stored first authentication. It may include acquiring a token or generating a first authentication token.

Step (d) includes, if the second authentication token is valid, performing pairing with the detected wearable device, confirming a shared payment method with the detected wearable device, and activating conditions for the shared payment method. It may include determining whether satisfaction is satisfied and, if the activation condition is satisfied, activating the shared payment method.

According to another aspect of the present invention, in a method for a wearable device to provide a payment service using a shared payment method, (a) authenticating a user and obtaining or generating a first authentication token, (b) obtaining the first authentication token or transmitting the generated first authentication token to at least one wearable device detected through short-distance communication, (c) receiving a second authentication token from the detected wearable device, and using the first and second authentication tokens. A payment service method using a shared payment method including the step of transmitting to a user device paired with the user is provided.

The user device determines whether the first or second authentication token is valid, and if valid, confirms the shared payment method with the detected wearable device, and if the activation conditions of the shared payment method are satisfied, the shared payment method. The means can be activated.

Meanwhile, the 'payment service system and method using shared payment means' examined above may be implemented in the form of a program and then recorded on a recording medium readable by an electronic device or distributed through a program download management device (server, etc.). You can.

According to the present invention, payment is not made simply by holding a shared payment method, but payment can be made only when the activation conditions for using the shared payment method are met, thereby preventing private use of public payment methods.

Additionally, when paying using a shared payment method, the user is authenticated using authentication information, so payment services can be provided safely even when the wearable device is lost.

Meanwhile, the effects of the present invention are not limited to the effects mentioned above, and various effects may be included within the range apparent to those skilled in the art from the contents described below.

Figure 1 is a diagram showing a payment service system using a shared payment method according to an embodiment of the present invention.
Figure 2 is a block diagram schematically showing the configuration of a wearable device according to an embodiment of the present invention.
Figure 3 is a diagram showing a method for payment service using a shared payment method according to an embodiment of the present invention.
Figure 4 is a diagram showing a payment service system using a shared payment method according to another embodiment of the present invention.
Figure 5 is a block diagram schematically showing the configuration of a user device according to an embodiment of the present invention.
Figure 6 is a diagram showing a payment service method using a wearable device according to another embodiment of the present invention.

Hereinafter, the 'payment service system and method using a shared payment method' according to the present invention will be described in detail with reference to the attached drawings. The described embodiments are provided so that those skilled in the art can easily understand the technical idea of the present invention, and the present invention is not limited thereto. In addition, the matters expressed in the attached drawings may be different from the actual implementation form in the schematic drawings to easily explain the embodiments of the present invention.

Meanwhile, each component expressed below is only an example for implementing the present invention. Accordingly, other components may be used in other implementations of the present invention without departing from the spirit and scope of the present invention.

Additionally, each component may be implemented purely through hardware or software configurations, but may also be implemented through a combination of various hardware and software configurations that perform the same function. Additionally, two or more components may be implemented together by one hardware or software.

In addition, the expression 'including' certain components is an 'open' expression and simply refers to the existence of the corresponding components and should not be understood as excluding additional components.

Figure 1 is a diagram showing a payment service system using a shared payment method according to an embodiment of the present invention.

Referring to FIG. 1, a payment service system using a wearable device includes a first wearable device 100A and a second wearable device 100B connected through short-distance communication.

When the first wearable device 100A and the second wearable device 100B detect each other through short-distance communication, they each authenticate the user, and when the user is authenticated, they each transmit an authentication token to the detected wearable device. If the authentication token received from the device is valid, the shared payment method is activated. Here, the authentication token may be an authentication token issued and stored from an authentication server that issues authentication tokens, or an authentication token generated by a wearable device.

Hereinafter, a method for activating a shared payment method by the first wearable device 100A by storing information about the shared payment method will be described.

When the second wearable device 100B is detected through short-distance communication, the first wearable device 100A authenticates the user. At this time, the first wearable device 100A can authenticate the user using various authentication information such as the user's biometric information, ID/password, certificate, i-PIN, etc. Biometric information is information that can identify the user, for example, This may include fingerprints, iris, pulse rate, etc.

When the user is authenticated, the first wearable device 100A transmits the first authentication token to the detected second wearable device 100B. Here, when the first authentication token is a pre-stored authentication token, the first wearable device (100A) transmits the pre-stored authentication token to the second wearable device (100B). In addition, when the first authentication token is an authentication token generated by the first wearable device 100A, the first wearable device 100A combines user identification information, expiration date, etc., or uses a random number generation algorithm to generate the first authentication token. An authentication token can be generated, and the generated first authentication token can be transmitted to the second wearable device 100B. At this time, the generated first authentication token includes user identification information, validity period, etc., the user identification information may include first wearable device identification information, etc., and the validity period is the valid time for using the first authentication token. , for example, can be set to 10 to 30 minutes.

When the first wearable device 100A performs the above operation, the second wearable device 100B also performs the same operation as the first wearable device 100A. That is, when the second wearable device 100B detects the first wearable device 100A through short-distance communication, it authenticates the user. At this time, the second wearable device 100B can authenticate the user using various authentication information such as the user's biometric information, ID/password, certificate, i-PIN, etc. Biometric information is information that can identify the user, for example, This may include fingerprints, iris, pulse rate, etc.

When the user is authenticated, the second wearable device 100B transmits a second authentication token to the detected first wearable device 100A. Here, when the second authentication token is a pre-stored authentication token, the second wearable device (100B) transmits the pre-stored authentication token to the first wearable device (100A). In addition, when the second authentication token is an authentication token generated by the second wearable device (100B), the second wearable device (100B) combines user identification information, expiration date, etc., or uses a random number generation algorithm to generate the second authentication token. An authentication token can be generated, and the generated second authentication token can be transmitted to the first wearable device 100A. At this time, the generated second authentication token includes user identification information, validity period, etc., the user identification information may include second wearable device identification information, etc., and the validity period is the valid time for using the second authentication token. , for example, can be set to 10 to 30 minutes.

When the second authentication token is received from the detected second wearable device 100B, the first wearable device 100A determines whether the second authentication token is valid. That is, the first wearable device 100A analyzes the second authentication token, extracts user identification information, validity period, etc., and determines whether the extracted user identification information is registered information and is within the validity period. If the extracted user identification information is registered information and is within the validity period, it is determined that the second authentication token is valid.

If the second authentication token is valid, the first wearable device 100A performs pairing with the second wearable device 100B and confirms the shared payment method shared with the second wearable device 100B. Then, the first wearable device 100A The wearable device 100A determines whether the activation conditions of the shared payment method are satisfied, and if the activation conditions are satisfied, activates the shared payment method. Then, the user can make a payment through the activated shared payment method. Here, , Shared payment methods may include cards (credit cards, check cards, etc.) or bankbooks in common names, membership cards, coupons, payment cards, etc. that members wish to share, and the activation conditions are expiration date, and when multiple members are members. It may include the number of attendees, number of paired wearable devices, etc.

In this way, the first wearable device 100A can enable payment by activating a shared payment method when a plurality of pre-registered wearable devices are within a predetermined distance. In addition, payment can be made using a shared payment method if the activation condition that multiple registered wearable devices must be present within a certain distance at the time of payment is satisfied. In addition, it is determined that the activation conditions are satisfied only when the detected wearable devices are within a certain distance for a specific time (eg, 10 to 30 minutes), and the shared payment method can be activated.

Here, the case where two wearable devices are used is explained, but it can also be applied when multiple wearable devices are used.

For example, a lover can register a couple account created at a bank as a shared payment method, eat at a restaurant while wearing a smart coupling ring, and then make payment using the shared payment method. After the couple broke up, the boyfriend tries to pay with the couple's bank account when purchasing drinks at a convenience store, but the payment cannot be made because the payment is not activated.

In addition, by registering the membership fee account book created to store the membership fee as a shared payment method in a participating group with multiple members, and attending a regular meeting while wearing a wearable device, the company meal fee can be paid through the shared payment method. After the meeting, the secretary catches a taxi to go home and tries to pay the taxi fare using his membership fee account, but the payment cannot be made because the payment is not activated.

In this way, payments are not made just by owning a shared payment method, but payments can be made only when the co-owner of the shared payment method satisfies certain conditions, thereby preventing private use of public funds.

This wearable device 100 refers to a device that a user can wear on the body, and depending on the part of the wearer, it includes glasses, watches, bracelets, shoes, rings, belts, bands, necklaces, and headsets. There are many different types of products such as (headset) and clothing.

The wearable device 100 may store applications (or applets) that can perform payment service processing using a shared payment method, and payment can be performed using a shared payment method through these applications.

For a detailed description of the wearable device 100, refer to FIG. 2.

Figure 2 is a block diagram schematically showing the configuration of a wearable device according to an embodiment of the present invention.

Referring to FIG. 2 , the wearable device 100 includes a short-range communication unit 110, a user authentication unit 120, a control unit 130, and a storage unit 150.

The short-range communication unit 110 detects a nearby wearable device. This short-range communication unit 110 detects wearable devices through short-range wireless communication, for example, Wi-Fi, Bluetooth communication, zigbee communication, NFC communication, infrared communication (IrDA), UHF (Ultra High Frequency), and VHF ( It can be performed in various standards such as RF (Radio Frequency) such as Very High Frequency and Ultra-Wideband (UWB).

The user authentication unit 120 authenticates the user wearing the wearable device 100. At this time, the user authentication unit 120 can authenticate the user using various authentication information such as biometric information, ID/password, certificate, and i-PIN, and biometric information is information that can identify the user, such as fingerprint, iris, etc. , pulse rate, etc.

That is, when the second wearable device is detected through the short-range communication unit 110, the user authentication unit 120 requests input of authentication information for user authentication, and the user inputs the authentication information. The user authentication unit 120 compares the input authentication information with previously stored standard authentication information, and determines that the user is an authenticated user if the two authentication information are the same. For example, when authenticating a user using biometric information, the user authentication unit 120 requests input of biometric information for user authentication, and the user inputs biometric information such as a fingerprint or iris. Then, the user authentication unit 120 determines whether the input biometric information is the same as the previously stored reference biometric information and authenticates the user.

The control unit 130 provides a shared payment method including a shared payment method, user identification information to share the shared payment method (e.g., wearable device identification information, etc.), and activation conditions (e.g., expiration date, number of members, etc.) of the shared payment method. The means information is input and stored in the storage unit 140.

Additionally, the control unit 130 receives authentication information for user authentication and registers it as standard authentication information.

When a user is authenticated through the user authentication unit 120, the control unit 130 acquires or generates a first authentication token from the storage unit 140, and sends the acquired or generated first authentication token to the short-range communication unit 110. It is transmitted to the second wearable device detected through, and if the second authentication token received from the second wearable device is valid, the shared payment method with the second wearable device is activated.

That is, when the user is authenticated as a result of the authentication of the user authentication unit 120, the control unit 130 obtains the first authentication token from the storage unit 140 or generates the first authentication token and detects the first authentication token. transmitted to the second wearable device. Here, when the first authentication token is an authentication token stored in the storage unit 140, the control unit 130 acquires the first authentication token stored in the storage unit 140 and transmits it to the second wearable device. Additionally, if the first authentication token is an authentication token generated by a wearable device, the control unit 130 may generate the first authentication token by combining user identification information, expiration date, etc., or using a random number generation algorithm, etc. The generated first authentication token can be transmitted to the second wearable device. The first authentication token includes user identification information, an expiration date, etc., and the user identification information may include first wearable device identification information, etc., and the expiration date is a valid time for using the first authentication token, for example, 10 It can be set to ~30 minutes, etc. The control unit 130 can generate an authentication token using various methods for generating a conventional authentication code or authentication token.

When the second authentication token is received from the detected second wearable device, the control unit 130 analyzes the second authentication token to extract user identification information, expiration date, etc., and stores the extracted user identification information in the storage unit 140. Determine whether it is saved and whether the current time is within the validity period. The control unit 140 determines that the second authentication token is valid if the extracted user identification information is registered information and is within the validity period.

If the second authentication token is valid, the control unit 130 performs pairing with the second wearable device and searches the storage unit 140 to determine the shared payment method shared with the second wearable device and the activation conditions for the shared payment method. Extract. At this time, when there are multiple shared payment methods, the control unit 130 outputs a plurality of shared payment methods, and the user can select at least one of the output shared payment methods. Additionally, when the priorities of a plurality of shared payment methods are set, the control unit 130 can extract the shared payment method with the highest priority.

Then, the control unit 130 determines whether the activation conditions of the shared payment method are satisfied, and if the activation conditions are satisfied, activates the shared payment method. Users can make payments through activated shared payment methods.

For example, the control unit 130 may determine that the activation condition is satisfied only when the detected wearable devices are within a certain distance for a specific time (eg, 10 to 30 minutes) and activate the shared payment method.

This control unit 130 may include at least one computing device, where the computing device includes a general-purpose central processing unit (CPU), a programmable device element (CPLD, FPGA) implemented suitably for a specific purpose, and a custom semiconductor operation. It can be a device (ASIC) or a microcontroller chip.

The storage unit 140 is a component that stores data related to the operation of the wearable device 100. Here, the storage unit 140 may use a known storage medium, for example, one or more of known storage media such as ROM, PROM, EPROM, EEPROM, RAM, etc.

In particular, the storage unit 140 stores standard authentication information for the user authentication unit 120 to authenticate a user. Standard authentication information is information that can authenticate (identify) a user and may include, for example, biometric information, ID/password, certificate, i-PIN, etc.

In addition, the storage unit 140 includes a shared payment method, user identification information to share the shared payment method (e.g., wearable device identification information, etc.), and activation conditions for the shared payment method (e.g., expiration date, number of members, etc.). The shared payment method information is stored. Here, shared payment methods may include cards (credit cards, check cards, etc.) or bankbooks in common names, membership cards, coupons, payment cards, etc. that members wish to share, and the activation conditions include expiration date, majority of members, etc. In the case of a meeting, the number of attendees can be included.

In addition, the storage unit 140 may store an application (or applet) that can perform a payment service using a shared payment method, and the stored information may be selected by the control unit 120 as needed. .

The control unit 130 can store an application (or applet) that can perform payment service processing using a shared payment method in the storage unit 140, and can run this application to make a payment using a shared payment method. .

The wearable device 100 according to the present invention may further include a display unit (not shown) for displaying various information related to the operation of the wearable device 100. In particular, the display unit can display various information such as biometric information measured by the sensor unit 120 and a shared payment method. This display unit can be implemented through various display devices including LCD, LED, etc.

Additionally, the wearable device 100 according to the present invention may further include an input unit (not shown) for receiving information from the user. In particular, the input unit includes a shared payment method, user identification information to share the shared payment method (e.g., wearable device identification information, etc.), and activation conditions for the shared payment method (e.g., expiration date, number of members, etc.). It can be used to input information such as information and authentication information. Meanwhile, the input unit may be implemented as an input device such as a keypad or a touch panel, or as a device for inputting or measuring biometric information. In addition to these devices, the input unit may be implemented as a variety of input devices. Additionally, the input unit may be implemented in the form of a touch screen integrated with the display unit.

Additionally, the wearable device 100 according to the present invention may further include a power supply unit (not shown) that supplies power.

Figure 3 is a diagram showing a method for payment service using a shared payment method according to an embodiment of the present invention.

Referring to FIG. 3, when the first wearable device detects the wearable device through short-distance communication (S302), it authenticates the user (S304). That is, when the wearable device is detected through short-distance communication, the first wearable device obtains the user's authentication information and authenticates the user using the obtained authentication information. At this time, the first wearable device requests input of authentication information such as biometric information, ID/password, certificate, and i-PIN according to a preset authentication method. Then, the user inputs authentication information according to a preset authentication method, and the first wearable device compares the input authentication information with pre-stored standard authentication information and, if the two authentication information are the same, determines the user to be an authenticated user. For example, when authenticating a user using biometric information, the first wearable device requests input of biometric information for user authentication, and the user inputs biometric information such as a fingerprint or iris. Then, the first wearable device determines whether the input biometric information is the same as the previously stored reference biometric information and authenticates the user.

If the user is an authenticated user as a result of the authentication in S304, the first wearable device acquires or generates a first authentication token (S306) and transmits the acquired or first authentication token to the detected wearable device (S308). Here, the first authentication token may be an authentication token issued and stored from an authentication server that issues authentication tokens, or an authentication token generated by a wearable device. The first wearable device may generate the first authentication token by combining user identification information, expiration date, etc., or using a random number generation algorithm. The first authentication token may include user identification information, validity time, etc., and the user identification information may include first wearable device identification information.

When S308 is performed, when a second authentication token is received from the detected second wearable device (S310), the first wearable device determines whether the second authentication token is valid (S312). That is, the first wearable device analyzes the second authentication token to extract user identification information, validity period, etc., and determines whether the extracted user identification information is registered information and is within the validity period. If the extracted user identification information is registered information and is within the validity period, it is determined that the second authentication token is valid.

As a result of the determination in S312, if the second authentication token is valid, the first wearable device performs pairing with the second wearable device (S314) and confirms the shared payment method shared with the second wearable device (S316). At this time, when there are a plurality of shared payment methods, the first wearable device outputs a plurality of shared payment methods, and the user can select at least one of the output shared payment methods. Additionally, when the priorities of a plurality of shared payment methods are set, the first wearable device can extract the shared payment method with the highest priority.

Then, the first wearable device determines whether the activation conditions for the shared payment method are satisfied (S318). That is, the first wearable device determines whether activation conditions, such as whether a preset number of wearable devices are paired within the validity period, are satisfied.

As a result of the determination in S318, if the activation conditions are satisfied, the first wearable device activates the corresponding shared payment method (S320). Users can make payments through activated shared payment methods. For example, the first wearable device may determine that the activation condition is satisfied only when the detected wearable devices are within a certain distance for a specific time (eg, 10 to 30 minutes) and activate the shared payment method.

Figure 4 is a diagram showing a payment service system using a shared payment method according to another embodiment of the present invention.

Referring to FIG. 4, the payment service system using a wearable device includes a first wearable device 100A worn by a first user, a user device 200 storing information about a shared payment method, and a second wearable device worn by a second user. It includes a wearable device 100B, and they are connected through short-distance communication.

When the first wearable device 100A and the second wearable device 100B detect each other through short-distance communication, they each authenticate the user, and when authenticated, each transmits an authentication token to the detected wearable device or user device. Here, the authentication token may be an authentication token issued and stored from an authentication server that issues authentication tokens, or an authentication token generated by a wearable device. The authentication token includes user identification information, validity time, etc., and the user identification information may include wearable device identification information, etc.

The wearable device 100 is capable of multi-pairing (e.g., pairing between wearable devices and pairing with a user device), and when pairing between wearable devices, pairing status is transmitted to the user device 200 and shared on the user device 200. You can activate your payment method.

The user device 200 is a device paired with the first wearable device 100A, receives an authentication token from the first wearable device 100A, and activates the shared payment method if the authentication token is valid.

Hereinafter, a method of activating a shared payment method using a user device will be described.

That is, when the first wearable device 100A detects the second wearable device 100B through short-distance communication, it authenticates the user. At this time, the first wearable device 100A can authenticate the user using various authentication information such as the user's biometric information, ID/password, certificate, i-PIN, etc. Biometric information is information that can identify the user, for example, This may include fingerprints, iris, pulse rate, etc.

In the case of an authenticated user, the first wearable device (100A) generates a first authentication token or acquires a previously stored first authentication token, and exchanges the generated or acquired first authentication token with the detected second wearable device (100B). Transmitted to user device 200. At this time, the first wearable device 100A may generate the first authentication token by combining user identification information, expiration date, etc., or using a random number generation algorithm. The first authentication token includes user identification information, an expiration date, etc., and the user identification information may include first wearable device identification information, etc., and the expiration date is a valid time for using the first authentication token, for example, 10 It can be set to ~30 minutes, etc.

When the first wearable device 100A performs the above operation, the second wearable device 100B also performs the same operation as the first wearable device 100A. That is, when the second wearable device 100B detects the first wearable device 100A through short-distance communication, it authenticates the user. At this time, the second wearable device 100B can authenticate the user using various authentication information such as the user's biometric information, ID/password, certificate, i-PIN, etc. Biometric information is information that can identify the user, for example, This may include fingerprints, iris, pulse rate, etc.

In the case of an authenticated user, the second wearable device (100B) generates a second authentication token or acquires a previously stored second authentication token, and sends the generated or acquired second authentication token to the detected first wearable device (100A). send. At this time, the second wearable device 100B may generate a second authentication token by combining user identification information, expiration date, etc., or by using a random number generation algorithm. The second authentication token includes user identification information, an expiration date, etc., and the user identification information may include second wearable device identification information, etc., and the expiration date is a valid time for using the second authentication token, for example, 10 It can be set to ~30 minutes, etc.

When a second authentication token is received from the detected second wearable device 100B, the first wearable device 100A transmits the second authentication token to the user device 200. That is, the first wearable device 100A transmits the first authentication token and the second authentication token to the user device 200 paired with the first wearable device 100A.

The wearable device 100 that performs this operation has the same configuration as the wearable device 100 shown in FIG. 2, but only the operation of the control unit 130 is different, so only the operation of the control unit 130 will be described.

The control unit 130 receives authentication information for user authentication and registers it as standard authentication information.

When the user is authenticated, the control unit 130 acquires a pre-stored first authentication token or generates a new first authentication token, and transmits the first authentication token to the second wearable device detected through the short-range communication unit 110. , When the second authentication token is received from the second wearable device, the first authentication token and the second authentication token are transmitted to the user device 200 paired with the user device.

This wearable device 100 refers to a device that a user can wear on the body, and depending on the part of the wearer, it includes glasses, watches, bracelets, shoes, rings, belts, bands, necklaces, and headsets. There are many different types of products such as (headset) and clothing.

When the first and second authentication tokens are received from the first wearable device 100A, the user device 200 determines whether the first or second authentication token is valid. That is, the user device 200 analyzes the authentication token, extracts user identification information, validity period, etc., and determines whether the extracted user identification information is registered information and is within the validity period. If the extracted user identification information is registered information and is within the validity period, the authentication token is determined to be valid.

If the first or second authentication token is valid, the user device 200 confirms the shared payment method shared with the second wearable device 100B.

Then, the user device 200 determines whether the activation conditions for the shared payment method are satisfied and, if the activation conditions are satisfied, activates the shared payment method. Users can make payments through activated shared payment methods. Here, shared payment methods may include cards (credit cards, check cards, etc.) or bankbooks in common names, membership cards, coupons, payment cards, etc. that members wish to share, and the activation conditions include expiration date, majority of members, etc. In the case of a meeting, the number of attendees can be included.

For example, the user device 200 may determine that the activation condition is satisfied only when the detected wearable devices are within a certain distance for a specific time (eg, 10 to 30 minutes) and activate the shared payment method.

The user device 200 is a PDA (Personal Digital Assistant) that can be applied to various wired and wireless environments, a smartphone, a cellular phone, a PCS (Personal Communication Service) phone, a GSM (Global System for Mobile) phone, and a W-CDMA (Wideband CDMA) phone. Includes phones, CDMA-2000 phones, MBS (Mobile Broadband System) phones, etc. Here, the user device 200 may represent a portable small device, but if it includes a camcorder or a laptop computer, it may be referred to as a mobile communication terminal, and therefore, embodiments of the present invention will not be particularly limited thereto.

For a detailed description of this user device 200, refer to FIG. 5.

In this way, payments are not made just by owning a shared payment method, but payments can be made only when the co-owner of the shared payment method satisfies certain conditions, thereby preventing private use of public funds.

Figure 5 is a block diagram schematically showing the configuration of a user device according to an embodiment of the present invention.

Referring to FIG. 5, the user device 200 includes a data communication unit 210, an input unit 220, a display unit 230, a storage unit 240, and a short-range communication unit 250 for transmitting and receiving data with various electronic devices. , includes a control unit 260.

The data communication unit 210 is configured to transmit and receive data with various electronic devices. Specifically, the data communication unit 210 is configured to connect through a wired communication network or a wireless communication network, and based on this connection, an application that provides a payment service using a shared payment method can be downloaded.

This data communication unit 210 may include various wired communication modules or wireless communication modules, and may transmit or receive data through various wireless or wired communication standards. For example, the data communication unit 210 may be implemented in a form that includes various standard communication modules such as ITU, IEEE, ISO, IEC, etc., and may be implemented in a form that includes various communication modules in addition to these standard communication modules. there is.

The input unit 220 is configured to receive information from the user. In particular, this input unit 220 includes a shared payment method, user identification information to share the shared payment method (e.g., wearable device identification information, etc.), and activation conditions for the shared payment method (e.g., expiration date, number of members, etc.). It can be used to input shared payment method information and authentication information.

Meanwhile, the input unit 220 may be implemented as an input device such as a keypad or a touch panel, and may be implemented as a variety of input devices in addition to these input devices. Additionally, the input unit 220 may be implemented in the form of a touch screen integrated with the display unit 230.

The display unit 230 is configured to display various information related to the operation of the user device 200, and may be implemented through various display devices including LCD, LED, etc.

The storage unit 240 is a component that stores data related to the operation of the user device 200. For example, the storage unit 240 may store various data including data for implementing a UI, data transmitted through the data communication unit 210, and data input through the input unit 220. This storage unit 240 may be implemented in a form that includes various types of memory elements.

In addition, the storage unit 240 includes a shared payment method, user identification information to share the shared payment method (e.g., wearable device identification information, etc.), and activation conditions for the shared payment method (e.g., expiration date, number of members, etc.). The shared payment method information is stored. Here, shared payment methods may include cards (credit cards, check cards, etc.) or bankbooks in common names, membership cards, coupons, payment cards, etc. that members wish to share, and the activation conditions include expiration date, majority of members, etc. In the case of a meeting, the number of attendees can be included.

The short-range communication unit 250 may include a short-range wireless communication module such as Wi-Fi, and communicates with the first wearable device paired with it.

When the first and second authentication tokens are received from the first wearable device, the control unit 260 determines whether the first or second authentication token is valid.

That is, the control unit 260 analyzes the authentication token to extract user identification information, validity period, etc., and determines whether the extracted user identification information is registered information and is within the validity period. If the extracted user identification information is registered information and is within the validity period, the control unit 260 determines that the authentication token is valid.

If the first or second authentication token is valid, the control unit 260 searches the storage unit 240 to extract the shared payment method shared with the second wearable device and the activation conditions for the shared payment method. At this time, when there are multiple shared payment methods, the control unit 260 outputs a plurality of shared payment methods, and the user can select at least one of the output shared payment methods. Additionally, when the priorities of a plurality of shared payment methods are set, the control unit 260 can extract the shared payment method with the highest priority.

Then, the control unit 260 determines whether the activation conditions of the shared payment method are satisfied, and if the activation conditions are satisfied, activates the shared payment method. Users can make payments through activated shared payment methods. For example, the control unit 260 may determine that the activation condition is satisfied only when the detected wearable devices are within a certain distance for a specific time (eg, 10 to 30 minutes) and activate the shared payment method.

This control unit 260 may include at least one computing device, where the processing device includes a general-purpose central processing unit (CPU), a programmable device element (CPLD, FPGA) implemented suitably for a specific purpose, and a custom semiconductor operation. It can be a device (ASIC) or a microcontroller chip.

Figure 6 is a diagram showing a payment service method using a wearable device according to another embodiment of the present invention.

Referring to FIG. 6, when the first wearable device detects the wearable device through short-distance communication (S602), it authenticates the user (S604). That is, when the wearable device is detected through short-distance communication, the first wearable device obtains the user's authentication information and authenticates the user using the obtained authentication information. At this time, the first wearable device requests input of authentication information such as biometric information, ID/password, certificate, and i-PIN according to a preset authentication method. Then, the user inputs authentication information according to a preset authentication method, and the first wearable device compares the input authentication information with pre-stored standard authentication information and, if the two authentication information are the same, determines the user to be an authenticated user. For example, when authenticating a user using biometric information, the first wearable device requests input of biometric information for user authentication, and the user inputs biometric information such as a fingerprint or iris. Then, the first wearable device determines whether the input biometric information is the same as the previously stored reference biometric information and authenticates the user.

If the user is authenticated as a result of the authentication in S604, the first wearable device acquires or generates a first authentication token from the storage unit (S606) and transmits the acquired or generated first authentication token to the detected second wearable device (S608) ). The first wearable device may generate the first authentication token by combining user identification information, expiration date, etc., or using a random number generation algorithm. The first authentication token may include user identification information, validity time, etc., and the user identification information may include first wearable device identification information.

After performing S608, when the first wearable device receives the second authentication token from the detected second wearable device (S610), it transmits the first and second authentication tokens to the user device paired with the first wearable device (S612).

The user device determines whether the first or second authentication token is valid (S614). That is, the user device analyzes the first and second authentication tokens to extract user identification information and validity period, respectively, and determines whether the extracted user identification information is registered information and is within the validity period. If the extracted user identification information is registered information and is within the validity period, it is determined that the first and second authentication tokens are valid.

As a result of the determination in S614, if the first or second authentication token is valid, the user device confirms the shared payment method shared with the second available device (S616).

Then, the user device determines whether the activation conditions of the confirmed shared payment method are satisfied (S618). That is, the user device determines whether activation conditions, such as whether a preset number of wearable devices are paired within the validity period, are satisfied.

As a result of the determination in S618, if the activation conditions are satisfied, the user device activates the shared payment method (S620). Users can make payments through activated payment methods.

If the activation condition is not satisfied as a result of the determination in S620, the user device notifies that the activation condition is not satisfied (S622).

If the first or second authentication token is not valid as a result of the determination in S614, the user device notifies that the authentication token is invalid (S624).

This payment service method using a shared payment method can be written as a program, and the codes and code segments that make up the program can be easily inferred by a programmer in the field. Additionally, a program related to a payment service method using a shared payment method is stored in an information storage medium (readable media) that can be read by an electronic device, and can be read and executed by the electronic device.

As such, a person skilled in the art to which the present invention pertains will be able to recognize that the present invention can be implemented in other specific embodiments without changing its technical idea or essential features. Therefore, the embodiments described above are merely illustrative and should be understood as not limiting in scope. In addition, the flow charts shown in the drawings are merely exemplary sequential sequences to achieve the most desirable results in carrying out the present invention, and of course, other additional steps may be provided or some steps may be deleted. .

The technical features described in this specification and implementations that implement them are implemented as digital electronic circuits, computer software, firmware, or hardware including the structures described in this specification and their structural equivalents, or a combination of one or more of these. It can be implemented as: Additionally, an implementation that implements the technical features described in this specification may be a computer program product, that is, as a module of computer program instructions encoded on a tangible program storage medium for controlling the operation of or execution by a processing system. It may be implemented.

A computer-readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter that affects a machine-readable radio wave signal, or a combination of one or more of these.

Meanwhile, in this specification, “device” or “system” includes all instruments, devices, and machines for processing data, including, for example, processors, computers, or multiple processors or computers. A processing system includes any code that, in addition to the hardware, forms an execution environment for computer programs on demand, for example, the code that makes up the processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of these. can do.

A computer program, known as a program, software, software application, script, or code, may be written in any form of a programming language, including a compiled or interpreted language, or an a priori or procedural language, and may be a standalone program or module, component, or subprogram. It may be implemented in any form, including routines or other units suitable for use in a computer environment.

On the other hand, a computer program does not necessarily correspond to a file in the file system, either within a single file provided to the requested program, or in multiple interacting files (e.g., storing one or more modules, subprograms, or portions of code). It may be stored within a file), or within a portion of a file that holds other programs or data (e.g., one or more scripts stored within a markup language document).

The computer program may be implemented to run on multiple computers or one or more computers located at one site or distributed across multiple sites and interconnected by a wired/wireless communication network.

Meanwhile, computer-readable media suitable for storing computer program instructions and data include, for example, semiconductor memory devices such as EPROM, EEPROM, and flash memory devices, magnetic disks such as internal hard disks and external disks, and magneto-optical disks. and all forms of non-volatile memory, media, and memory devices, including CD and DVD disks. The processor and memory may be supplemented by, or integrated into, special-purpose logic circuitry.

Implementations that implement the technical features described herein may include a backend component, for example, a data server, or a middleware component, for example, an application server, or, for example, a user may use an implementation of the subject matter described herein. It may be implemented in a front-end component, such as a web browser or a client computer with a graphical user interface capable of interacting with the computer, or in a computing system that includes any combination of one or more of such back-end, middleware, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication, for example, a telecommunications network.

Hereinafter, in addition to the contents described above, more specific embodiments that can implement the components included in the system described in this specification and the payment service method using a shared payment method will be described in detail.

The payment service method using the system and shared payment method described in this specification is a means of executing computer software, program code, or instructions on a client device or a server related to a web-based storage system or one or more processors included in the server. It can be used partially or fully. Here, the processor may be part of a computing platform such as a server, client, network infrastructure, mobile computing platform, fixed computing platform, etc., and may specifically be a type of computer or processing device capable of executing program instructions, code, etc. In addition, the processor may further include a memory that stores service methods, instructions, codes, and programs for regulating the user's body temperature. If the processor does not include memory, a payment service method using a shared payment method, instructions, and You can also access storage devices such as CD-ROM, DVD, memory, hard disk, flash drive, RAM, ROM, cache, etc. where codes and programs are stored.

Additionally, the payment service method using the system and shared payment method described in this specification may be used partially or entirely through a server, client, gateway, hub, router, or device running computer software on network hardware. Here, the software can be executed on various types of servers such as file servers, print servers, domain servers, Internet servers, intranet servers, host servers, distributed servers, etc. The above-mentioned servers include memory, processors, computer-readable storage media, It may further include an interface for accessing storage media, communication devices, ports, clients, and other servers through wired/wireless networks.

Additionally, payment service methods, commands, and codes using shared payment methods can also be executed by the server, and other devices required to execute payment service methods using shared payment methods may be implemented as part of the hierarchy associated with the server. You can.

In addition, the server can provide an interface to other devices, including without limitation clients, other servers, printers, database servers, print servers, file servers, communication servers, distributed servers, etc., and connections through the interface can be made through wired/wireless networks. It is possible to facilitate remote execution of programs.

In addition, any of the devices connected to the server through the interface may further include at least one storage device capable of storing a payment service method using a shared payment method, commands, codes, etc., and the central processor of the server may store a payment service method using a shared payment method, commands, codes, etc. Commands, codes, etc. to be executed can be provided to the device and stored in the storage device.

Meanwhile, the system described in this specification and the payment service method using a shared payment method can be used partially or entirely through a network infrastructure. Here, the network infrastructure may include devices such as computing devices, servers, routers, hubs, firewalls, clients, personal computers, communication devices, routing devices, etc., as well as separate modules capable of executing each function, as mentioned above. In addition to one device and module, it may further include storage media such as story flash memory, buffer, stack, RAM, ROM, etc. In addition, payment service methods, commands, codes, etc. using shared payment methods can also be executed and stored by any one of the devices, modules, and storage media included in the network infrastructure, and can be used to execute the membership management service method of an offline store. Other devices required for this can also be implemented as part of the network infrastructure.

Additionally, the payment service method using the system and shared payment method described in this specification may be implemented with hardware or a combination of hardware and software suitable for a specific application. Here, hardware includes both general-purpose computer devices such as personal computers and mobile communication terminals and enterprise-specific computer devices, and computer devices include memory, microprocessors, microcontrollers, digital signal processors, application integrated circuits, programmable gate arrays, and programmable array organizations. It may be implemented as a device including, or a combination thereof.

The computer software, instructions, codes, etc. described above may be stored or accessed by a readable device, where the readable device is a computer component, such as RAM or ROM, that contains digital data used for computing during a certain time interval. Semiconductor storage, permanent storage such as optical disks, mass storage such as hard disks, tapes, drums, etc., optical storage such as CDs or DVDs, flash memory, floppy disks, magnetic tapes, paper tapes, independent RAM disks, large capacity removable from the computer. It may include storage and memory such as dynamic memory, static memory, variable storage, and network-attached storage such as cloud. Meanwhile, the commands and codes here include data-oriented languages such as SQL, dBase, etc., system languages such as C, Objective C, C++, assembly, etc., architectural languages such as Java, NET, etc., and application languages such as PHP, Ruby, Perl, Python, etc. It includes all the same languages, but is not limited thereto, and may include all languages widely known to those skilled in the art in the technical field to which the present invention pertains.

Additionally, “computer-readable media” as used herein includes all media that contribute to providing instructions to a processor for program execution. Specifically, it includes, but is not limited to, non-volatile media such as data storage devices, optical disks, magnetic disks, etc., volatile media such as dynamic memory, and transmission media such as coaxial cables, copper wires, optical fibers, etc. that transmit data.

Meanwhile, configurations that implement the technical features of the present invention included in the block diagram and flow chart shown in the drawings attached to this specification represent logical boundaries between the configurations.

However, according to an embodiment of the software or hardware, the depicted configurations and their functions are executed in the form of stand-alone software modules, monolithic software structures, codes, services, and combinations thereof, and can execute stored program code, instructions, etc. Since the functions can be implemented by being stored in a medium executable on a computer equipped with a processor, all of these embodiments should also be regarded as falling within the scope of the present invention.

Accordingly, although the attached drawings and their descriptions illustrate the technical features of the present invention, they should not be simply inferred unless a specific arrangement of software for implementing these technical features is clearly stated. In other words, various embodiments described above may exist, and since such embodiments may be partially modified while retaining the same technical features as the present invention, these should also be regarded as falling within the scope of the present invention.

In addition, in the case of a flow chart, operations are depicted in the drawing in a specific order, but this is shown to obtain the most desirable results, and such operations must be executed in the specific order or sequential order shown, or all illustrated operations must be executed. It should not be understood as something that must be done. In certain cases, multitasking and parallel processing may be advantageous. Additionally, the separation of various system components in the embodiments described above should not be construed as requiring such separation in all embodiments, and the program components and systems described are generally integrated together into a single software product or integrated into multiple software products. It should be understood that it can be packaged.

As such, this specification is not intended to limit the invention to the specific terms presented. Accordingly, although the present invention has been described in detail with reference to the embodiments described above, those skilled in the art can make modifications, changes, and modifications to the embodiments without departing from the scope of the present invention. Transformations can be made.

The scope of the present invention is indicated by the claims described later rather than the detailed description above, and the meaning and scope of the claims and all changes or modified forms derived from the equivalent concept are interpreted to be included in the scope of rights of the present invention. It has to be.

The present invention does not allow payment just by holding a shared payment method, but allows payment only when the activation conditions for using the shared payment method are met, thereby preventing private use of public payment methods.

Additionally, since the user is authenticated using biometric information, payment services can be provided safely even when the wearable device is lost.

100: Wearable device
110, 250: Short-distance communication unit
120: User authentication unit
130, 260: Control unit
150, 240: storage unit
200: user device
210: Data communication department
220: input unit
230: display unit

Claims (10)

A short-range communication unit that detects other wearable devices in the short distance;
a user authentication unit that authenticates users; and
When the user is authenticated, the first authentication token is transmitted to at least one other wearable device detected through the short-distance communication unit, and if the second authentication token received from the other detected wearable device is valid, the other detected wearable device Perform pairing with the device, confirm the shared payment method with the detected other wearable device, and check the number of paired other wearable devices to determine if the number of paired other wearable devices is preset in the activation conditions of the shared payment method. If the number matches and each of the paired other wearable devices is within a preset distance for a preset time according to the activation conditions, it is determined that the activation conditions are satisfied and the shared payment method is activated, and the activated shared payment method is A control unit that performs payment using;
A wearable device including a.
◈Claim 2 was abandoned upon payment of the setup registration fee.◈ According to paragraph 1,
The first authentication token or the second authentication token is a previously stored token or a newly created token, and is a wearable device characterized in that it includes user identification information or an expiration date.
delete delete ◈Claim 5 was abandoned upon payment of the setup registration fee.◈ According to paragraph 1,
A wearable device further comprising a storage unit storing at least one of standard authentication information, information about a shared payment method shared with each other wearable device, and activation conditions for activating the shared payment method.
In a method for a wearable device to provide a payment service using a shared payment method,
(a) authenticating a user and obtaining or generating a first authentication token;
(b) transmitting the acquired or generated first authentication token to at least one other wearable device detected through short-distance communication;
(c) receiving a second authentication token from the detected other wearable device and determining whether the second authentication token is valid;
(d) if the second authentication token is valid, performing pairing with the detected other wearable device;
(e) confirming a shared payment method with the detected other wearable device;
(f) Check the number of paired other wearable devices, and if the number of paired other wearable devices matches the number preset in the activation conditions of the shared payment method, each of the paired other wearable devices is preset according to the activation conditions. determining that the activation condition is satisfied if the activation condition is within a preset distance for a period of time;
(g) activating the shared payment method when the activation conditions are met; and
(h) performing payment using the activated shared payment method;
A payment service method using a shared payment method including.
◈Claim 7 was abandoned upon payment of the setup registration fee.◈ According to clause 6,
In step (a),
Obtaining biometric information of the user;
Comparing the obtained biometric information with previously stored biometric information to determine whether they are identical;
When the two biometric information are the same, a payment service method using a shared payment method comprising the step of acquiring a pre-stored first authentication token or generating a first authentication token.
delete delete delete

Images