WO2018169285A2

WO2018169285A2 - Card management system and method using security device

Info

Publication number: WO2018169285A2
Application number: PCT/KR2018/002946
Authority: WO
Inventors: 김승훈
Original assignee: 김승훈
Priority date: 2017-03-13
Filing date: 2018-03-13
Publication date: 2018-09-20
Also published as: WO2018169285A3

Abstract

Disclosed is a card management system and method using a security device. According to an aspect of the present embodiment, an objective of the present invention is to provide a card management system and method for providing a target advertisement to a specific user who intends to charge a transportation card, so as to enable an operator of the card management system to create revenue.

Description

Card Management System and Method Using Security Device

The present invention relates to a card management system and method using a security device, and more particularly, to a card management system and method for managing payment, recharging, etc. of a traffic card using an online server.

The contents described in this section merely provide background information on the present embodiment and do not constitute a prior art.

With the development of public transportation and its associated discount services, transportation cards are an essential means of payment in our daily lives.

The first generation transportation card is a form in which a predetermined amount of money is charged to a card or various types of physical media similar to the card. Each transportation card has a card ID, and the card is charged, settled and settled based on the card ID. Charging and payment of the transportation card are made through the exchange of information between the transportation card and the payment terminal.

The exchange of information is done using signed data including the card and the terminal's unique key. Accordingly, in using the card, the unique key should never be exposed, and if the unique key is exposed, a specific amount may be charged to the card without the third party paying the money corresponding to the amount to be charged. Serious problems may arise that could manipulate the amount in the card. When a physical card is issued, the unique key of the card is embedded in the card along with the card ID.

Physical first generation transportation cards had to be uncomfortable to carry, and because the card is a bearer card, there was a problem that loses money if the card is lost.

The second generation traffic card is a type of so-called app card that is issued a virtual traffic card in the terminal, such as a smartphone, is charged and used. There is a huge advantage in that there is no physical card.

App cards are also operated using a unique key, the unique key is stored in the USIM in the smartphone. Since the unique key is stored in the USIM, it can be used without activating the screen of the smartphone.

However, the conventional app card also loses the USIM when the smartphone is lost, has a weak security problem, and has a structure in which the information is misused in the middle. Therefore, the conventional app card is operated in a form of minimizing the damage even if exposed by measures such as the daily usage limit is limited.

Conventional traffic cards have some major problems.

First, if both physical and app cards are lost, the charged balance is difficult to recover. In the case of AppCard, even if the USIM is changed, not lost, the card must be newly issued (a procedure for storing a unique key in the USIM).

Second, there is a disadvantage in that it is vulnerable to security because it is a form of physically carrying a unique key.

Third, in the case of an app card, it may be available depending on the type of USIM and the type of smartphone, and may not be available. In the case of complex interests, the use of the card may be very limited. Can be.

Therefore, while the security is increased, there is a demand for a card management system that is easy to use.

In addition, as the number of users using the app card increases, the demand for a method of generating revenue by the operator of the card management system in addition to paying the cost of the user using the app card is increasing.

One embodiment of the present invention is to provide a card management system and method that can be reused in the conventional use of a traffic card without re-purchasing the traffic card, even if the traffic card is lost or the smartphone is changed. have.

One embodiment of the present invention is to provide a card management system and method that can be used without restrictions of USIM, smartphones, affiliates, high security of unique keys.

An embodiment of the present invention provides a card management system and method for allowing a user to select and use a card suitable for a situation even when a plurality of cards of the same type are generated, and to allow a payment or a charging to be performed using the selected card. The purpose is to provide.

Another object of the present invention is to provide a card management system and method for providing a target advertisement to a specific user who wants to charge by using a transportation card, so as to generate revenue to the operator of the card management system. have.

According to an aspect of the present invention, an app including a security management module for storing the card management module and security data to manage the charging of the app card to enable the payment or charging using the terminal, and provides a specific terminal only advertisements In the card charging and target advertising system, receiving a charge request signal including the identifier of the app card, the identifier of the terminal and the amount to be charged from the terminal to transmit to the security database, and whether or not to charge from the security database Receives and transmits to the terminal, the card management module for determining whether to provide the target advertising information to the terminal according to whether the identifier of the terminal belongs to a predetermined group and the app card identification using the identifier of the app card To charge the balance information in the app card. It provides an app card charging and target advertising system, characterized in that it comprises a security database for charging the amount to be charged, and whether the charge to the card management module.

According to an aspect of the present invention, the card management module, when the identifier of the terminal belongs to the predetermined group, the card management module to display the target advertisement information only when the amount to be charged exceeds the reference value. It characterized in that the transmission to.

According to an aspect of the present invention, when the identifier of the terminal belongs to the preset group, the card management module is to charge the balance information in the app card when the amount to be charged exceeds the reference value It is characterized by reflecting both the amount and the predetermined additional amount.

According to an aspect of the invention, the card management module is characterized in that for requesting the cost for the predetermined additional amount to the target advertisement information providing server or card company server.

According to an aspect of the present invention, when the identifier of the terminal belongs to a preset group, the card management module determines to provide the terminal with target advertisement information to be provided to the preset group to the terminal. .

In addition, according to another aspect of the present invention, a security database that stores the card management module and security data to manage the charging of the app card to enable the payment or charging using the terminal and provides a specific database only advertisements App method charging and a target advertising system that includes charging the app card, the method for providing the target advertisement, the charging request including the identifier of the app card, the identifier of the terminal and the amount to be charged from the terminal A first transmission process of receiving a signal and transmitting the signal to the security database, a reflection process of identifying the app card by using an identifier of the app card, and reflecting the amount to be charged in the balance information in the app card; It is determined whether an identifier belongs to a preset group, and the preset A determination process of determining whether to transmit target advertisement information to be provided to the card management module; and whether the mobile terminal is charged with the app card or the app card from the security database, and receiving the target advertisement information from the terminal. It provides an app card charging and target advertising method comprising a second transmission process for transmitting to.

According to an aspect of the present invention, in the determining process, when the identifier of the terminal belongs to a predetermined group, it is determined to transmit target advertisement information to be provided to the predetermined group to the card management module.

According to an aspect of the present invention, in the determination process, when the identifier of the terminal belongs to the preset group, the target advertisement information is transferred to the card management module only when the amount to be charged exceeds a reference value. Determine to transmit.

According to an aspect of the present invention, when the identifier of the terminal belongs to the preset group, when the amount to be charged exceeds the reference value, the balance information in the app card to be charged It is characterized by reflecting both the amount and the predetermined additional amount.

According to an aspect of the invention, the reflecting process is characterized in that for requesting the cost for the predetermined additional amount to the target advertisement information providing server or card company server.

As described above, according to an aspect of the present invention, even if the smart phone is changed, there is an advantage that the traffic card used by the user can be used again without a traffic card repurchase.

According to one aspect of the present invention, it can be used without restrictions of the USIM, smart phone, affiliate, and because the security of the unique key is improved, there is an advantage that can have a high security.

According to an aspect of the present invention, even if a plurality of cards of the same type are generated, the user can select and use a card suitable for a situation, and there is an advantage that payment or charging can be performed using the selected card.

In addition, according to an aspect of the present invention, by providing a target advertisement to a specific user to charge using Kyotong card, there is an advantage that can be generated to the operator of the card management system.

1 is a diagram illustrating a card management system according to an embodiment of the present invention.

2 is a diagram illustrating a configuration of a terminal according to an embodiment of the present invention.

3 is a diagram showing the configuration of a card management server according to an embodiment of the present invention.

4 is a diagram illustrating a configuration of a data security device according to an embodiment of the present invention.

5 is a timing chart illustrating a process of issuing a card to a terminal in a card management system according to an embodiment of the present invention.

6 is a timing chart illustrating a process of reissuing a card to a terminal in a card management system according to an embodiment of the present invention.

7 is a timing chart illustrating a process of inquiring a state of a card in the card management system according to an exemplary embodiment of the present invention.

8 is a timing chart illustrating a process of completing charging by a terminal in a card management system according to an embodiment of the present invention.

9 is a timing chart illustrating a process of completing charging by a terminal in a card management system according to another embodiment of the present invention.

10 is a timing chart illustrating a process of payment or charging to a terminal according to a request of a payment terminal or a charging terminal in a card management system according to an exemplary embodiment of the present invention.

11 is a flowchart illustrating a process of issuing a card to the terminal by the card management server according to an embodiment of the present invention.

12 is a flowchart illustrating a process of completing charging by a card management server according to a request of a terminal according to an embodiment of the present invention.

FIG. 13 is a flowchart illustrating a process in which a card management server performs a payment or charging to a terminal at the request of a payment terminal or a charging terminal according to an embodiment of the present invention.

14 is a timing chart illustrating a process of selecting a card to be used in the terminal according to an embodiment of the present invention.

15 is a timing chart illustrating a process of selecting a card to be used immediately before payment or charging in a terminal according to an embodiment of the present invention.

FIG. 16 is a flowchart illustrating a process of determining, by a card management server, a card to be used by receiving a card selection request from a terminal according to an embodiment of the present invention.

As the inventive concept allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention. In describing the drawings, similar reference numerals are used for similar elements.

Terms such as first, second, A, and B may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. The term and / or includes a combination of a plurality of related items or any item of a plurality of related items.

When a component is referred to as being "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may be present in between. Should be. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that there is no other component in between.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. It is to be understood that the term "comprises" or "having" in the present application does not exclude in advance the possibility of the presence or addition of features, numbers, steps, operations, components, parts or combinations thereof described in the specification. .

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art.

Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

1, the card management system 100 according to an embodiment of the present invention is a terminal 110, card management server 120, general database 130, security database 140 and card company server and data security Device 170. In addition, the card management system 100 may further include a payment terminal 150 and a charging terminal 160.

The terminal 110 is connected to the card management server 120 by using wireless communication such as LTE, TCP / IP, and the like, issuing a card from the card management server 120 by requesting the card management server 120 to issue a card. The device is used to make a payment using the issued card or to charge the balance in the issued card.

The card issued by the terminal 110 refers to a prepaid card that can distinguish users by using CI information or terminal ID, and can make a payment by charging a predetermined amount in advance. This is the case. The terminal 110 is a CI (Connecting Information, personal identification information) for identifying the user of the terminal 110, for example, CI information or terminal for identifying each user, such as the user's email address, the date of birth of the user (110) ID, for example, a terminal ID for identifying each terminal, such as a unique number of the terminal 110 or a telephone number of the terminal, is transmitted to the card management server 120 and requests for issuance of a card. Only information that does not need encryption among card information is stored in the terminal. The terminal may be implemented with various communication devices such as a PC and a notebook, as well as various smart devices such as a smartphone, a tablet PC, a smart watch, and the like. The card issued to the terminal may be implemented and stored as a card-specific application or program in the terminal, or may be implemented and stored as a module or service in a bank application or program. Hereinafter, the terminal is described as a smart phone, the issued card is implemented as one module in the bank application, but is not necessarily limited thereto.

When the terminal 110 receives a card from the card management server 120, only the card ID for identifying each issued card is received from the card management server 120 and stored. The card ID includes the ID and card number of the issuer who issued the card. The card ID may be used to identify which card issued by which issuer is the card having the corresponding card ID. Since the cards have different algorithms for encrypting information that requires encryption among card issuers, it is possible to confirm which encryption algorithm is used by including the issuer ID in the card ID.

The terminal 110 may receive and store a plurality of cards of the same type. As in the above example, when the issued card is assumed to be a traffic card, a traffic card different from each other is used for each area. A user of the terminal 110 may receive a plurality of regional traffic cards and store them in the terminal 110 so as to use compatible traffic cards for each region.

Before proceeding with charging or payment with the issued card, the terminal 110 may transmit a card selection signal to the card management server 120 to select a card to be used. The terminal 110 transmits a card selection signal to the card management server 120, so that the user of the terminal 110 may charge or pay in advance without having to determine a card to perform charging or payment troublesomely. Choose the card you wish to use for payment in advance. In particular, when there are a plurality of cards of the same type issued using the terminal 110, the user of the terminal 110 may select any one card to be used for charging or payment. For example, when a user of the terminal 110 stays in a specific region, other cards do not need to be used except for cards compatible in the region. Therefore, the terminal 110 may select a card so that a specific card can be continuously used for charging or payment in the future.

The terminal 110 requests a payment using the issued card or requests the card management server 120 to charge the remaining balance in the issued card. In order to make a payment using the card or to charge the balance in the card, not only the card ID but also the unique key of the card for security. However, since only the ID of the issued card is stored in the terminal 110, the terminal 110 requests payment or charges the remaining balance in the issued card to the card management server 120, and payment or charging is performed by the card management. This is done via the server 120.

The terminal 110 may request a payment or a charge and may transmit a card selection signal for selecting a card to be used. As described above, the terminal 110 may select a card to be used in advance by transmitting a card selection signal before proceeding with charging or payment. However, the terminal 110 may transmit a card selection signal for selecting a card to be used together with a payment or charging request signal when the charging or the charging process is to be performed immediately before or when the charging is performed. In particular, when the terminal 110 has received a plurality of cards of the same type, the terminal 110 requests a payment or charging of a card selection signal to select any one of the cards to be paid or charged. Can be sent with the signal. At this time, so that the card management server 120 can more easily determine the validity of the selected card, the terminal 110 may transmit its current location information together. The terminal 110 transmits its location information together with the card selection information to the card management server 120 so that the card management server 120 can determine whether the selected card is a compatible card in the region based on the location information. Can be.

According to this feature, even if the user of the terminal 110 loses the card or changes the smart phone, the user can re-use the conventional traffic card used by the user without repurchasing the traffic card. In addition, the conventional card management system has stored the unique key of the card necessary for security in the terminal, the USIM manufacturer, smart phone manufacturers and service partner's agreement is required for the storage, there was inconvenience. However, since the terminal 110 stores only the ID of the issued card, the terminal 110 according to an embodiment of the present invention has an advantage of providing a corresponding service (card management service) without the consent of the other manufacturer. A detailed description of the terminal 110 will be described with reference to FIG. 2.

When the card management server 120 receives the card issuing request from the terminal 110, the card management server 120 issues a card and transmits certain information of the issued card to the terminal 110. The issued card information includes the card ID, unique key, balance, whether the transportation card is for youth or general use, the issuing area, the area where the card is compatible, the card manufacturing information, and the card company's server information that manages payment or charging of the card. Various information is included. When the card management server 120 issues a card, the card management server 120 does not transmit all the information of the issued card to the terminal 110, but does not require encryption and information that does not require encryption for security among issued card information. The information is classified and stored in a separate medium (general database 130 or security database 140) and does not require encryption, for example, card ID, issuing region, region where the card is compatible, card manufacturing information, The card company server that manages payment or charging, and transmits various option information (use area, main use pattern, user age, etc.) to the terminal 110.

The card management server 120 may issue a plurality of cards of the same type and transmit certain information of each issued card to the terminal 110 at the request of the terminal 110. If necessary, the terminal 110 may request issuance of a plurality of cards of the same type (different), and the card management server 120 may issue each requested card. The card management server 120 classifies the information of each issued card and stores the information in a separate medium, and transmits only the information that does not require encryption of each card to the terminal 110.

When the card management server 120 receives the card selection signal from the terminal 110, the card management server 120 determines the validity of the corresponding card, determines whether to operate as the corresponding card, and transmits the card selection result to the terminal 110. The terminal 110 may transmit a card selection signal to select a card to be used for later payment or charging before transmitting the payment request or the charging request (before the payment or charging). When the card selection signal is received from the terminal 110, the card management server 120 determines the validity of the selected card. Since payment or charging is in progress, the card management server 120 mainly determines whether the corresponding card is validly issued in determining the validity of the selected card. For example, there may be a case where the card selected by the terminal 110 is a card that has not been issued yet. As such, when the card selection signal is received from the terminal 110, the card management server 120 determines the validity of the card including whether the selected card is validly issued. The card management server 120 determines whether to select a corresponding card according to whether the selected card is valid, and transmits the card selection result to the terminal 110. If the selected card is valid, the card management server 120 transmits to the terminal 110 that the corresponding card is selected because the corresponding card is valid and stores the ID of the selected card, and later, the charging or payment request signal from the terminal 110. When receiving the card to operate with the selected card. On the contrary, if the selected card is not valid due to not yet issued, the card management server 120 transmits an error message to the terminal 110 so as to know that the selected card is not valid. As such, the card management server 120 can continuously determine the validity of the card to be used (for charging or payment) and select the corresponding card according to the determination result, so that the terminal 110, in particular, a plurality of cards of the same type If you receive a card, you do not have to select a card to use each time.

When the payment request or the charging request is received from the terminal 110, the card management server 120 transmits the payment request or the charging request to the security database 140 so that payment or charging is performed. At this time, the card management server 120 to determine the terminal 110 in the charging process, to determine whether the terminal 110 belongs to a predetermined group. If the terminal 110 belongs to a preset group, the card management server 120 may transmit the target advertisement information provided to the terminal 110 to the terminal 110. In this case, the card management server 120 may transmit the target advertisement information only when the terminal 110 attempts to charge an amount greater than or equal to the reference value. In this case, the terminal 110 sends an additional amount preset to the amount that the terminal intends to charge. In addition, it can be charged. The card management server 120 may request a target advertisement information providing server or a card company server for the preset additional amount. Accordingly, the operator of the card management server 120 may derive additional revenue through the provision of the target advertisement information. A detailed description of the card management server 120 will be described with reference to FIG. 3.

Further, the card management server 120 includes a module for encrypting or decrypting the signature value, and decrypts the electronic signature received from the payment terminal 150 or the charging terminal 160. At this time, the content of the information that can be decrypted by the card management server 120 is not able to decrypt all the electronically signed content, it can only decrypt information that does not require encryption, and decrypts the information that does not require encryption, Etc. can be judged.

The card management server 120 may receive a card selection signal from the terminal 110 together with a payment request or a charging request. The terminal 110 may transmit a card selection signal for selecting a card to be used for payment or charging together with a payment request or a charging request. When the card selection signal is received together, the card management server 120 determines whether to operate as the selected card by determining whether the selected card is valid before processing according to the payment or charging request. The card management server 120 determines whether the card selected by the terminal 110 is valid. The card management server 120 not only checks whether the card selected by the terminal 110 has been validly issued, but also finally the charging terminal 150 or the charging terminal 160 in which the corresponding card transmits a payment or charging request or charging or payment. The validity of the card is determined by determining whether the card is compatible with the card company server and the data security device 170 to be processed. The card management server 120 checks whether there is an ID of the selected card among the data stored in the general database 130, and information of the selected card (issuing area, region where the card is compatible, and card company server information managing payment or charging of the card). And the compatibility of the payment terminal 150, the charging terminal 160 or the card company server and the data security device 170 to determine the validity of the selected card. The card management server 120 directly compares the information of the selected card with the type of the payment terminal 150, the charging terminal 160 or the card company server and the data security device 170 in determining the validity, in particular, compatibility. In some embodiments, information on the selected card may be transmitted to the card company server and the data security device 170 to receive the determination result of the card company server and the data security device 170. Furthermore, when the terminal 110 receives the location information of the terminal together with the card selection signal, the card management server 120 uses the location information of the terminal and the information of the selected card, the payment terminal 150 and the charging terminal 160. ) Or more accurately determine whether the card company server and the data security device 170 is compatible. The card management server 120 determines whether to operate by selecting a corresponding card according to whether the selected card is valid, and transmits the card selection result to the terminal 110. If the selected card is valid, the card management server 120 transmits to the terminal 110 that the corresponding card is selected and the card is selected, and proceeds to the corresponding process (charge or payment) requested by the terminal 110. On the contrary, if the selected card is not valid due to not yet issued, the card management server 120 transmits an error message to the terminal 110 so as to know that the selected card is not valid.

The card management server 120 may receive a card selection signal before receiving a payment or charging request (regardless), or may receive a card selection signal together with a payment request or a charging request. When the card is selected by determining the validity of the selected card, the card management server 120 performs a request of the terminal 110 based on the selected card unless the card selection signal is received again. Accordingly, even though the user of the terminal 110 has been issued a plurality of cards of the same type, the user of the terminal 110 does not have any inconvenience in selecting each time in the process of payment or charging.

The general database 130 receives and stores information from the card management server 120 that does not require encryption among card information issued by the card management server 120. As the general database 130 stores information that does not require encryption, when the terminal 110 tries to charge or pay using the issued card, the general database 130 determines the validity of the card. The general database 130 stores information that does not require encryption of the issued card, so that the card management server 120 can determine the validity of the selected card.

The general database 130 stores the information of the selected card including the card ID from the card management server 120 in correspondence with the ID of the terminal 110 selecting the corresponding card. Accordingly, when the terminal 110 requests payment or charging without selecting a separate card, payment or charging may be performed using a previously selected card.

The general database 130 may receive and store a black list (BL) or a positive list (PL) for the card in advance from the card company server and the data security device 170. The general database 130 may determine the validity of the card to be used by the terminal, and first determine whether the card corresponds to the black list or the positive list, and block the transaction.

In addition, the general database 130 receives the charging or payment facts from the card company server and the data security device 170 or the security database 140 and stores the transaction details. The transaction history is a term used to refer to the details of charging or payment using a card, and includes transaction time, transaction location, transaction amount, and balance information after transaction. The card company server and data security device 170 notifies the fact to the general database 130 after charging or paying a certain amount on a specific card or after reflecting the amount or amount of payment in the balance information stored in the security database 140. And, the general database 130 receives this fact and stores it as a transaction.

The security database 140 stores and modifies information that requires encryption among card information issued by the card management server 120. The general database 130 or the security database 140 may be implemented in the form of a card or a module, and may be implemented in the form of a USB in the card management server 120, or a card by wired communication or wireless communication such as LTE, TCP / IP, or the like. It may be connected to the management server 120. Since the security database 140 needs to store information that needs to be encrypted, except for the supervisor, a worker cannot see the information that needs to be encrypted and can not be manipulated. For example, the security database 140 may be implemented as a hardware security module (HSM). The security database 140 decrypts the information requiring encryption received from the card management server 120 to grasp the information, and may modify the stored information according to the grasped information. Information that requires encryption includes unique keys, card passwords, balance information, and the like. In particular, the security database 140 stores the stored balance information in the balance information of the transaction history most recently reflected among the stored transactions in the general database, the balance information of the card company server and the corresponding card stored in the data security device 170, and at predetermined intervals. Or by comparing each request, the balance information in the card can be verified. In addition, the security database 140 determines the authenticity of the electronically signed authentication key, and electronically signs and transmits information to be transmitted to the card management server 120. A detailed description of the security database 140 will be described with reference to FIG. 4.

The payment terminal 150 is a terminal for requesting a predetermined amount of payment to the card management server 120 via the terminal 110. The payment terminal 150 checks whether the card to be used by the terminal 110 is a normal card without forgery by receiving the electronically signed authentication result from the terminal 110. If it is determined that the terminal is using a normal card, the payment terminal 150 transmits the electronic signature payment start signal to the terminal 110, so that payment for the payment amount is made.

At this time, the payment terminal 150 is given by the issuer ID of the card that can be paid by itself, the ID of the payment terminal 150 owned by the card management server 120 and the card company server and the data security device 170. The unique key for payment is stored, and the digital signature is verified using the stored information, thereby verifying the validity of the payment terminal 150 itself. The payment terminal 150 transmits the electronic signature to the terminal 110 after the electronic signature using the ID and the unique key for payment, thereby proving its validity.

The charging terminal 160 is a terminal for requesting a certain amount of charge to the card management server 120 via the terminal 110. Like the payment terminal 150, the charging terminal 160 receives the electronically signed authentication result from the terminal 110 to check whether the card to be used by the terminal 110 is a normal card that is not forged. If it is determined that the terminal is using a normal card, the charging terminal 150 transmits the electronic signature charging start signal to the terminal 110, so that the amount of money is charged.

In addition, the charging terminal 160 is received from the card issuer ID, the card company server and the data security device 170 of the charging terminal 160 owned by the card management server 120, the issuer ID of the card that can be charged By using the unique key for charging the electronic signature and then delivered to the terminal 110, it is possible to prove their validity.

The card company server and data security device 170 finally approves the charging or payment of the card, and reflects this. When there is a request for charging or payment of the balance in the card from the terminal 110, the card company server and the data security device 170 finally approves the request so that the balance in the card is charged or paid in the balance. The card company server and the data security device 170 receive the signed charge amount information or the payment amount information from the security database 140, approve it, reflect it to the balance in the card, and notify the security database 140 to notify the security database 140. 140) to reflect the stored balance information. Alternatively, after the security database 140 reflects the balance information stored in the security database 140 according to the charging or payment request of the terminal, the card company server and the data security device 170 receive the corresponding transaction details from the card management server. Approves that the recharge or payment amount will be finally reflected in the card.

The card management system 100 may also include a plastic card (not shown) of the terminal 110. The plastic card communicates wirelessly with the terminal 110 and requests the synchronization to the terminal 110 or is a device that is synchronized with the terminal 110. The plastic card is provided with a memory and a communication unit therein, and may store a balance in the memory, its own ID and a unique key for charging, and the terminal 110 through wireless communication (mainly NFC) using the communication unit. Information can be sent and received. When the charging terminal 160 is implemented as a plastic card, the charging terminal 160 may transfer the balance stored therein to the terminal 110 as a charging amount for synchronization, and provides the charging amount information on its ID and charge. The electronic signature may be delivered to the terminal 110 using an authentication key including a unique key. Alternatively, when the terminal 110 charges the balance in the card using the charging terminal 160 or online, the plastic card may request synchronization with the plastic card, and the plastic card receives the balance information from the terminal 110 and stores the balance information. Synchronize with the balance information of.

In FIG. 1, although the general database 130 and the security database 140 are shown as separate devices, the present invention is not limited thereto, and the general database 130 and the security database 140 may be implemented as one device with the operating area separated.

2, the terminal 110 according to an embodiment of the present invention includes a communication module 210, a registration card management module 220, a memory unit 230, and an application 240.

The communication module 210 transmits a card issuing request to the card management server 120 and receives information that does not require encryption from the card management server 120. The communication module 210 transmits a card issuing request to the card management server 120 and transmits a CI, a terminal ID, and various option information (use area, main use pattern, user age, etc.), and the card management server 120. From the card, information such as card ID that does not require encryption is received. The communication module 210 may transmit a request for issuing a plurality of cards of the same type in requesting a card issuance.

The communication module 210 may transmit a card state request signal for confirming the state of the card to the card management server 120 and receives card state information from the card management server 120.

When the terminal 110 intends to proceed charging without using a separate terminal, the communication module 210 transmits a charge request signal to the card management server 120 together with a card ID for determining the validity of the card. When the charging is completed, the charging completion information is received through the card management server 120 indicating that the amount of money electronically signed by the security database 140 has been charged. Accordingly, the user of the terminal 110 may confirm that the amount desired by the terminal 110 is charged into the card.

When the terminal 110 intends to proceed with payment or charging by using the payment terminal 150 or the charging terminal 160, the communication module 210 may provide an electronic signature from the payment terminal 150 or the charging terminal 160. Receives the start signal or the charge start signal and delivers to the card management server (120). Before receiving the payment start signal or the charging start signal, the communication module 210 determines the type of the card that the payment terminal 150 or the charging terminal 160 wants to use for the terminal 110. The card ID request signal may be received from the payment terminal 150 or the charging terminal 160 to transmit the card ID.

The communication module 210 transmits a card selection signal to the card management server 120 that selects a card to be used before proceeding with payment or charging (regardless) or simultaneously with the payment or charging. The communication module 210 may transmit the location information of the terminal 110 itself to the card management server 120 together with the card selection signal. Thereafter, the communication module 210 receives the card selection result from the card management server 120. The card selection result includes a message indicating that the card is selected and an error message indicating that the card is not valid.

In the charging or payment process, in particular, in order to proceed with the payment, the payment terminal 150 or the charging terminal 160 may transmit a card balance inquiry request signal to check how much is left in the card. The communication module 210 receives the card balance inquiry request signal and transmits it to the card management server 120, and receives the card balance information from the card management western unit 120 and transmits it to the payment terminal 150 or the charging terminal 160. do.

The communication module 210 receives the electronic signature of the terminal from the payment terminal 150 or the charging terminal 160 and transmits the card ID to the card management server 120 together with the received electronic signature. The communication module 210 receives the validity of the card and the validation result of the payment terminal 150 or the charging terminal 160 from the card management server 120 and transmits the result to the payment terminal 150 or the charging terminal 160. Accordingly, the terminal 110 and the payment terminal 150 or the charging terminal 160 determines whether the card to be used by the terminal 110 is valid and whether the payment terminal 150 or the charging terminal 160 is valid. You can check before the transaction.

Thereafter, the communication module 210 receives an electronic signature payment start signal or a charging start signal from the payment terminal 150 or the charging terminal 160 and transmits the signal to the card management server 120. The communication module 210 receives electronically signed payment completion information or charging completion information from the card management server 120 and transmits it to the payment terminal 150 or the charging terminal 160. In this case, the communication module 210 may receive the target advertisement information from the card management server 120 in receiving the charging completion information.

The card management module 220 controls the communication module 210 to make an appropriate request to the card management server 120 according to an input of whether the card issuance, payment or charging. Card management module 220 may be implemented in the application 240 or may be implemented separately from the application 240, whether the application 240 issuing one or more cards received from the user of the terminal 110, whether payment or not Depending on whether the charging, the card management server 120, payment terminal 150 or charging terminal 160 to control the communication module 210 to make an appropriate request. The card management module 220 receives the card selection information received and controls the communication module 210 to transmit a card selection signal to the card management server 120.

In addition, when the card management module 220 receives the card status request from the terminal 110, the card management module 220 inquires the card status information stored in the memory 230 and provides the terminal 110 to the terminal 110.

The memory unit 230 stores information that does not require encryption received from the card management server 120. The memory unit 230 stores card IDs and other optional information as information that does not require encryption. Since the terminal 110 receives and stores only information that does not require encryption, the terminal 110 can simply store the information without consultation with other manufacturers, and does not store information that requires encryption, and thus has an advantageous effect in terms of security.

In addition, the memory unit 230 receives and stores state information of a card from an issuer that issues each card for each card ID stored in the memory unit 230. The status information of the card includes whether the card can be used, and what the usage limit of the card is. The memory unit 230 receives and stores the state information of the card from the issuer server which issued the card, and provides the state information of the requested card when the card management module 220 inquires.

The application 240 provides a user interface (UI) so that the user of the terminal 110 can receive an input of whether a card is issued, whether to pay or charge. The application 240 may be implemented as one module or service in a bank application or program. Alternatively, the application 240 may be implemented as a separate application or program. Further, when the communication module 210 receives the target advertisement information, the application 240 causes the target advertisement to be played by executing the target advertisement information.

The application 240 may provide a UI to receive a selection of a card to be used for charging or payment from the user of the terminal 110, and may receive or confirm location information of the terminal 110. The application 240 transmits the received or confirmed information to the card management module 220.

Referring to Figure 3, the card management server 120 according to an embodiment of the present invention is a communication module 310, control module 320, memory unit 330, signature value encryption / decryption module 340 and security It includes a data separation module 350.

The communication module 310 receives the card issuing request together with the CI or the terminal ID from the terminal 110, and encrypts the information that does not need encryption with the terminal 110 and the general database 130, with the security database 140. Sends the necessary information. The communication module 310 may receive a request for issuing a plurality of cards of the same type from the terminal 110.

The communication module 310 receives a card status request signal from the terminal 110 and transmits a card status information signal.

When the communication module 310 receives the card ID from the terminal 110, in order to check whether the corresponding card is valid, the communication module 310 transmits a validation request of the card to the general database 130, and the verification result from the general database 130. Receives and transmits to the terminal 110 or the terminal 110 and the payment terminal 150 / charging terminal 160, the communication module 310 with the card ID from the terminal 110 with the payment terminal 150 or charging The electronic signature of the terminal 160 may be received together, and the digital signature verification request signal of the payment or charging terminal may be transmitted to the security database 140 so that the security database 140 may verify the validity of the corresponding terminal. The communication module 310 receives the verification result from the security database 140 and transmits it to the terminal 110 or the terminal 110 and the payment terminal 150 / charging terminal 160,

The communication module 310 receives the electronically signed payment or charging request signal together with the card ID from the terminal 110 and transmits it to the security database 140. The communication module 310 receives the electronically signed payment or charging completion information from the security database 140 and transmits it to the terminal 110 or the terminal 110 and the payment terminal 150 / charging terminal 160. The communication module 310 may transmit the transaction history for each card ID checked in the general database 130 to the card company server and the data security device 170 according to preset conditions. The communication module 310 may receive a card balance inquiry request signal from the terminal 110 and transmit a card balance inquiry request to the security database 140 before receiving a payment or charging request signal. The communication module 310 may receive the card balance information from the security database 140 and transmit it to the terminal 110.

The communication module 310 receives a card selection signal from the terminal 110 to select a card to be used before proceeding with payment or charging (regardless) or simultaneously with payment or charging. The communication module 310 may also receive location information of the terminal 110 itself from the terminal 110 together with the card selection signal. Thereafter, the communication module 310 transmits the card selection result to the terminal 110.

When receiving the card issuing request from the terminal 110, the control module 320 checks the terminal ID or CI and various option information received with the card issuing request. The control module 320 transmits the terminal ID or CI to the general database 130 to check whether it is stored in the general database 130. The control module 320 according to whether the terminal ID or CI received from the terminal 110 in the general database 130 is stored, whether the issuance request of the card requested by the terminal 110 is the initial issuing request or reissued. You can check if it is a request.

When the issuing request of the card requested by the terminal 110 is the initial issuing request, the control module 320 assigns the card ID stored in the memory unit 330 according to the terminal ID or CI. The control module 320 transmits the terminal ID, the CI, and the card ID to the signature value encryption / decryption module 340, so that the signature value encryption / decryption module 340 generates or matches the unique key according to the card ID. Create a. The card is issued as the security key is generated. Here, the security key is information including the ID and unique key of the issued card, and is essential information for digitally signing information or data in order to prevent forgery and forgery. In this case, the control module 320 does not control to transmit the security key of the issued card to the terminal 110, but as described above, only the information that does not require encryption for the issued card is transmitted to the communication module 310. To control. To this end, the control module 320 controls the security data separation module 350 to separate the information necessary for encryption and the information that is not required among the information of the issued card. When the security data separation module 350 separates each piece of information, the control module 320 sends the information requiring encryption to the security database 140 and the information that does not require encryption to the general database 130 and the terminal 110. The communication module 310 is controlled to transmit.

When the issuing request of the card requested by the terminal 110 is a re-issuing request, the control module 320 receives information that does not require encryption stored corresponding to the corresponding terminal ID or CI in the general database 130. Control the communication module 310 to transmit to.

When the card selection signal is received from the terminal 110 before the payment start signal (payment request) or the charge start signal (charge request) is received, the control module 320 determines whether the corresponding card is valid. Since payment or charging is in progress, the card management server 120 mainly determines whether the corresponding card is validly issued in determining the validity of the selected card. For example, there may be a case where the card selected by the terminal 110 is a card that has not been issued yet. As such, when receiving the card selection signal from the terminal 110, the control module 320 may determine whether the ID of the selected card exists in the general database 130 to determine whether the card is validly issued. As such, the control module 320 determines the validity of the card, including whether the card has been issued effectively. The control module 320 determines whether to select a corresponding card according to whether the selected card is valid, and controls the communication module 310 to transmit the card selection result to the terminal 110. If the selected card is valid, the control module 320 transmits to the terminal 110 that the corresponding card is selected and the corresponding card is selected, and stores the ID of the selected card in the general database 130, and later, the terminal 110. When a charge or payment request signal is received from the card, the selected card operates as a stored card. On the contrary, if the selected card is not valid for reasons such as not yet issued, the control module 320 transmits an error message to the terminal 110 so that the selected card is not valid.

When the control module 320 receives a card ID, an electronic signature or a payment start signal or a charging start signal from the terminal 110, the control module 320 controls the transmission to the general database 130 or the security database 140, respectively. On the contrary, when the control module 320 receives the authentication result, electronically signed payment completion information or charging completion information from the general database 130 or the security database 140, the control module 320 and the payment with the terminal 110 or the terminal 110. Control to transmit to the terminal 150 / charging terminal 160.

When the card selection signal is received from the terminal 110 together with the payment initiation signal or the charging initiation signal, the control module 320 determines whether the selected card is valid before performing processing according to the payment or charging request. Decide whether to act as a card. The control module 320 determines whether the card selected by the terminal 110 is valid. The control module 320 not only whether the card selected by the terminal 110 is validly issued, but also the payment terminal 150 or the charging terminal 160 to which the corresponding card transmits a payment or charging request or finally charge or payment. It is determined whether the card is valid by determining whether the card is compatible with the card company server and the data security device 170 to be processed. When receiving the location information of the terminal together with the card selection signal from the terminal 110, the control module 320 uses the location information of the terminal and the information of the selected card payment terminal 150, charging terminal 160 or card company The compatibility with the server and the data security device 170 can be more accurately determined. The control module 320 determines whether to operate by selecting a corresponding card according to whether the selected card is valid, and transmits the card selection result to the terminal 110. If the selected card is valid, the control module 320 transmits to the terminal 110 that the corresponding card is selected and the corresponding card is selected, and proceeds the process (charge or payment) requested by the terminal 110 to the corresponding card. On the contrary, if the selected card is not valid for reasons such as not yet issued, the control module 320 transmits an error message to the terminal 110 so that the selected card is not valid.

When receiving the charging start signal from the terminal 110, the control module 320 determines whether to provide the target advertisement information by determining whether the terminal ID or CI belongs to a predetermined group. By determining whether the terminal ID or the CI belongs to a preset group, the control module 320 may provide the target advertisement information to the terminal 110 only when the terminal ID or the CI belongs to a preset group. When the terminal ID or the CI belongs to a preset group, the control module 320 may provide the target advertisement information to the terminal 110 only when the charging amount requested by the terminal 110 in the charging start signal is greater than or equal to the predetermined amount. Can be. For the terminal 110 provided with the target advertisement information, the control module 320 requests the security database 140 to further charge a predetermined additional amount to the charging amount requested by the terminal 110. Here, the preset additional amount may be a certain amount or may be a certain amount proportional to the charge amount requested by the terminal. Accordingly, by providing the target advertisement information to the terminal, the control module 320 may obtain a predetermined cost from the target advertisement information server or the card company server, and by watching the target advertisement information from the user's point of view of the terminal 110, There is an advantage that can be charged additionally.

The memory unit 330 stores a card ID of a card to be newly issued. The memory unit 330 may receive and store a card ID every time it is issued from a card company server (not shown), or may receive and store a predetermined number of card IDs at once. When the memory unit 330 receives a terminal ID or CI from the control module 320, the memory unit 330 provides one of the stored card IDs to the control module 320. The memory unit 330 provides the control module 320 with a different card ID for each terminal ID or CI.

In addition, the memory unit 330 stores target advertisement information to be provided to the terminal 110. The memory unit 330 may receive and store target advertisement information from a target advertisement information providing server or a card company server. Accordingly, each time the control module 320 requests the target advertisement information, the memory unit 330 provides the stored target advertisement information.

The signature value encryption / decryption module 340 receives the card ID from the control module 320 and generates a security key. The signature value encryption / decryption module 340 generates a unique key or stores the generated unique key, and generates a security key when receiving the card ID from the control module 320. Here, the unique key is a unique key for verifying the device's authority to a specific request and is essential information for digital signature. Therefore, for the security of the unique key, the signature value encryption / decryption module 340 may encrypt the generated unique key. The signature value encryption / decryption module 340 assigns the generated unique key or the stored unique key to each received card ID, and generates a security key using the card ID and the unique key. The signature value encryption / decryption module 340 uses the security key generated by generating the unique key information assigned to the specific card ID, and then transmits the electronic signature to the control module 320. Here, the signature value encryption / decryption module 340 may be implemented as a security application module (SAM), but is not limited thereto. The signature value encryption / decryption module 340 may be replaced with any module that generates and encrypts a unique key and a security key. have.

When the electronic signature of the payment terminal 150 or the charging terminal 160 is received from the terminal 110, the signature value encryption / decryption module 340 decodes the electronic signature. However, the signature value encryption / decryption module 340 may not decrypt all the contents of the electronic signature of the payment terminal 150 or the charging terminal 160, but may issue the issuer ID and the payment terminal 150 or the charging terminal ( Only information that does not require encryption, which is the ID of 160, can be decrypted. Therefore, the signature value encryption / decryption module 340 decrypts and confirms only information that does not require encryption, and decrypts the information that requires encryption in the security database.

The security data separation module 350 separates the information received from the control module 320 according to whether encryption is required. The security data separation module 350 receives various IDs, CIs, various option information, balance information in issued cards, unique keys, etc. received from the control module 320. The security data separation module 350 separates the received information and the unique key information into information that requires encryption and information that does not require encryption. Information that requires encryption includes a unique key, balance information, and the like, and information that does not require encryption includes CI, various option information, various IDs such as a card ID, and a terminal ID. The secure data separation module 350 performs encryption only on the information that requires encryption, and indexes the encrypted information and the unencrypted information by using the same specific flag. Using indexing, both information can be identified as one data. For example, the secure data separation module 350 may identify both pieces of information as one piece of data by indexing using a value having a predetermined serial number, and index both pieces of information by indexing them using CI or card ID. Can be identified by its data. The security data separation module 350 transmits the separated amount information to the control module 320 and electronically signs the information requiring encryption. The secure data separation module 350 may also be implemented as a SAM like the signature value encryption / decryption module 340, but is not limited thereto. In addition, the security data separation module 350 is shown in the configuration implemented in the card management server 120, but is not necessarily limited thereto, and is connected to the card management server 120 by wired or wireless communication or in the form of a card or module. The card management server 120 may be implemented in the form of a USB or the like.

4 is a diagram illustrating a configuration of a security database according to an embodiment of the present invention.

4, the security database 140 according to an embodiment of the present invention is a communication module 410, control module 420, signature value verification module 430, signature value encryption and decryption module 440 and The memory unit 450 is included.

The communication module 410 receives information that requires encryption from the card management server 120.

The communication module 410 receives a card balance inquiry request from the card management server 120 and transmits card balance information to the card management server 120.

The communication module 410 receives the digital signature verification request signal from the card management server 120 and transmits the verification result to the card management server 120.

The communication module 410 receives an electronically signed payment request signal or a charging request signal from the card management server 120, and transmits the electronically signed payment completion information or charging completion information to the card management server 120.

When receiving the information that requires encryption from the card management server 120, the control module 420 controls the signature value encryption / decryption module 440 to decrypt the information, and, if decrypted, stores the corresponding information in the memory unit ( 450) My store.

When the card balance inquiry request is received from the card management server 120, the control module 420 checks the balance information corresponding to the corresponding card ID stored in the memory 450. The control module 420 controls the communication module 410 to transmit the confirmed card balance information to the card management server 120.

When the digital signature verification request signal is received from the card management server 120, the control module 420 controls the signature value verification module 430 and the signature value encryption / decryption module 440 to verify whether the digital signature is valid. do. The control module 420 controls the signature value encryption / decryption module 440 to digitally sign the verification result, and the terminal 110 or the terminal 110 and the payment terminal 150 / charging terminal The communication module 410 is controlled to transmit to the 160.

When receiving the card ID and the electronically signed payment or charging request signal from the card management server 120, the control module 420 controls the memory unit 450 to request or charge the payment in the balance stored in the memory unit 450 Ensure that the requested amount is reflected. The control module 420 controls the signature value encryption / decryption module 440 to decode the electronically signed payment or charge request signal to determine the payment or charge request amount, and the payment terminal 150 or the charging terminal 160 The memory unit 450 is controlled so that the requested payment or charge amount is reflected in the balance information of the corresponding card (card corresponding to the card ID) stored in the memory unit 450. When the reflection is completed, the control module 420 controls the signature value encryption / decryption module 440 and the communication module 410 to electronically sign payment completion information or charge completion information to the card management server 120.

In addition, the control module 420 verifies whether the balance information stored in the memory unit 450 is correct. When the control module 420 receives a verification request for the balance, or at predetermined intervals, the balance information of the transaction data most recently reflected among the balances stored in the memory 450 and the transactions stored in the general database, the card company server, and the data. By comparing the balance information of the card stored in the security device 170, the accuracy of the balance information stored in the memory unit 450 is verified.

The signature value verification module 430 verifies the digital signature of the payment terminal 150 or the charging terminal 160 decrypted by the signature value encryption / decryption module 440. A unique key identical to a unique key for payment or charging of the payment terminal 150 or the charging terminal 160 included in the electronic signature of the decrypted payment terminal 150 or the charging terminal 160 is stored in the memory unit 450. The validity of the digital signature.

The signature value encryption / decryption module 440 decodes the electronic signature of the payment terminal 150 or the charging terminal 160 received from the card management server 120. According to the control of the control module 420, it is decrypted so that the electronic signature of the payment terminal 150 or the charging terminal 160 can be verified. The signature value encryption / decryption module 440 decrypts all information requiring encryption that the card management server 120 cannot decrypt by using a unique key for payment or charging stored in the memory unit 450. In addition, the signature value encryption / decryption module 440 also decodes a payment or charging start signal electronically signed by the payment terminal 150 or the charging terminal 160. Accordingly, the control module 420 checks how much the payment terminal 150 or the charging terminal 160 requests the payment or charging, and reflects it in the remaining balance information stored in the memory 450. . In addition, the signature value encryption / decryption module 440 digitally signs payment completion information or charge completion information.

The memory unit 450 stores the decrypted information from the signature value encryption / decryption module 440. The information decrypted from the signature value encryption / decryption module 440 is information that requires encryption for the card issued by the card management server 120 and includes balance and unique key information. The memory unit 450 stores the decrypted information so that the signature value verification module 430 can verify the electronic signature of the payment terminal 150 or the charging terminal 160. In addition, the memory unit 450 also stores the unique key for the payment given to the payment terminal 150 or the unique key for the charge given to the charging terminal 160, thereby performing the authentication key in the payment request or the charge request. Make sure that your digital signature is valid.

The terminal 110 transmits a card issuing request signal together with the terminal ID or CI to the card management server 120 (S510).

The card management server 120 transmits the terminal ID or CI to the general database 130 (S520). The card management server 120 transmits the terminal ID or CI to the general database 130 to check whether there is a card issued for the terminal ID or CI.

The general database 130 transmits whether the terminal ID or CI is stored (S530). The general database 130 checks whether the received terminal ID or CI is stored and transmits the confirmation result to the card management server 120.

The card management server 120 issues a card and generates a security key of the card to be issued (S540). When the terminal ID or CI is not stored in the general database 130, the card management server 120 checks the received terminal ID or CI and gives the card ID, and generates or matches a unique key according to the card ID. Generate a security key. The card is issued as the security key is generated.

The card management server 120 separates the issued card information into information that requires encryption and information that does not require encryption (S550). Here, the information that requires encryption includes a unique key, balance information, and the like, and information that does not require encryption includes CI, various option information, a terminal ID, a card ID, and the like.

The card management server 120 stores unnecessary information in the general database 130 (S560).

The card management server 120 stores the information requiring encryption in the security database 140 (S570).

The card management server 120 transmits information requiring no encryption to the terminal 110 (S580). The card management server 120 transmits only the information that does not need encryption among the separated information to the terminal 110.

The terminal 110 stores information that does not require encryption (S590). Since there is a case where the terminal 110 needs to quickly exchange information with the payment terminal 150 or the charging terminal 160 by using information that does not need encryption, information that does not require encryption is stored in the terminal 110.

The terminal 110 transmits a card issuing request signal together with the terminal ID or CI to the card management server 120 (S610).

The card management server 120 transmits the terminal ID or CI to the general database 130 (S620).

The general database 130 checks whether the received terminal ID or CI is stored (S630).

The general database 130 grasps information that does not need encryption, stored together with the terminal ID or CI (S640). For a card that has already been issued, the CI of the user who requested the issuance of the card or the ID of the terminal is stored in the general database 130 together with information that does not require card encryption. Therefore, the general database 130 grasps information that does not require encryption stored with the received terminal ID or CI.

The general database 130 transmits information that does not need encryption, stored together with the terminal ID or CI, to the terminal 110 through the card management server 120 (S650). Since the general database 130 transmits unnecessary encryption information to the terminal 110, the terminal 110 may be reissued a card.

The terminal 110 transmits a card status information request signal to the card management server 120 (S710). The terminal 110 transmits a card status request signal to the card management server 120 together with the card ID to request status information.

The card management server 120 inquires the card state information (S720). The card management server 120 inquires the card state information stored in the card management server 120 and provides it to the terminal 110.

The card management server 120 transmits the card state information to the terminal 110 (S730).

The terminal 110 transmits a charge request signal together with the card ID to the card management server 120 (S810).

The card management server 120 transmits a validity authentication request signal of the card to the general database 130 (S815). When receiving the card ID, the card management server 120 requests the validity authentication to the general database 130 to determine whether the card is a valid card.

The general database 130 authenticates the validity of the card (S820). The general database 130 authenticates validity based on whether the card ID received from the card management server 120 in the general database 130 is stored.

The general database 130 transmits the authentication result of the card to the card management server 120 (S825).

If the card is valid, the card management server 120 transmits the card ID and the charge request signal received from the terminal 110 to the security database 140 (S830).

The security database 140 reflects the charged amount in the balance information (S835). The security database 140 grasps the balance information stored in correspondence with the card ID and the charge amount information included in the charge request signal, and reflects the charge amount in the balance information.

The security database 140 notifies the general database 130 of the charge amount of money (S840).

General database 130 stores the transaction history for the card ID (S845). When receiving the amount of charge from the security database 140, the general database 130 stores the transaction history for the card ID. General database 130 stores the transaction date and time, place, amount, balance, etc. for the corresponding card ID.

The security database 140 transmits the electronically signed charging completion information to the terminal 110 via the card management server 120 (S850).

The card management server 120 transmits the transaction history for each card ID according to a predetermined condition to the card company server and the data security device 170 (S855). In the card management server 120 transmits the transaction history to the card company server and the data security device 170 so that the charge amount is reflected, the card company server and the data security device 170 for the transaction history whenever there is a charge request from a specific terminal. Can be sent, but not necessarily. For example, if a predetermined condition is stored in a transaction number more than a specific number of times or is set in a predetermined cycle, the card management server 120 may transmit the transaction history for each card ID when the set condition is satisfied. The card management server 120 transmits to the card company server and the data security device 170 when the transaction details of the various cards satisfy the preset conditions, so that the charge amount is finally reflected for each card.

The terminal 110 transmits a charge request signal together with the card ID to the card management server 120 (S910).

The card management server 120 transmits a validity authentication request signal of the card to the general database 130 (S915).

The general database 130 authenticates the validity of the card (S920).

The general database 130 transmits the authentication result of the card to the card management server 120 (S925).

If the card is valid, the card management server 120 transmits the card ID and the charge request signal received from the terminal 110 to the security database 140 (S930).

The security database 140 transmits the signed card ID and the charge amount information to the card company server and the data security device 170 (S935). The security database 140 digitally signs the charge request signal received from the card management server 120, and transmits the electronically signed card ID and the charge amount information included in the charge request signal to the card company server and the data security device 170. send.

The card company server and data security device 170 charges the amount requested to the card (S940). The card company server and the data security device 170 decode the electronically signed card ID and the amount of charge information received from the security database 140 to determine how much the amount of charge is required for which card. The card company server and the data security device 170 charge the required amount of charge in the remaining balance of the card.

The card company server and the data security device 170 notify the general database 130 and the security database 140 of the amount of money charged (S945).

The security database 140 reflects the charged amount in the balance information (S950). When the security database 140 receives the fact that the requested amount is charged from the card company server and the data security device 170, the security database 140 reflects the charge amount requested to be charged in the remaining balance information corresponding to the corresponding card ID.

The general database 130 stores the transaction history for the card ID (S955).

The security database 140 transmits the electronically signed charging completion information to the terminal 110 via the card management server 120 (S960).

The payment terminal 150 or the charging terminal 160 requests the card ID to the terminal 110 (S1000). Since the card has a unique encryption algorithm for each issuer, the payment terminal 150 or the charging terminal 160 requests the card ID to the terminal to check whether the card to be used by the terminal is a card of a type compatible with the card. This is because the card ID includes the issuer ID in addition to the card information.

The terminal 110 transmits the card ID to the payment terminal 150 or the charging terminal 160 (S1005).

The payment terminal 150 or the charging terminal 160 requests the card management server 120 to check the card balance via the terminal 110 (S1010). Payment terminal 150 or charging terminal 160 to the terminal 110, the terminal 110 requests the card balance inquiry with the card ID to the card management server 120. In particular, in order to determine whether the balance in the card is less than the payment amount at the time of payment, the payment terminal 150 requests the terminal 110 to check the card balance.

The card management server 120 inquires the balance of the card to the security database 140 (S1015). The card management server 120 inquires the balance of the card to the security database 140, the security database 140 checks the balance information stored corresponding to the card ID and transmits to the card management server 120.

The card management server 120 transmits the card balance information to the payment terminal 150 or the charging terminal 160 (S1020).

The electronic signature of the payment terminal 150 or the charging terminal 160 is transmitted to the terminal 110 (S1025). The payment terminal 150 or the charging terminal 160 verifies the validity of the payment terminal 150 or the charging terminal 160, and checks the verification result of the terminal 110 on the electronic signature of the terminal 110. To send.

The terminal 110 transmits the card ID to the card management server 120 together with the received electronic signature (S1030). The terminal 110 also transmits the card ID to the card management server 120 together with the received electronic signature in order to verify the validity of the card to be used and confirm the other components.

The card management server 120 transmits a card validation request signal to the general database 130 (S1035).

The card management server 120 transmits the digital signature verification request signal of the payment terminal 150 or the charging terminal 160 to the security database 140 (S1040).

The general database 130 verifies the validity of the card (S1045). The general database 130 verifies the validity of the card as to whether the card ID is stored.

The security database 140 verifies the validity of the payment terminal 150 or the charging terminal 160 (S1050). The security database 140 decrypts the received digital signature and verifies the validity of the payment terminal 150 or the charging terminal 160 based on whether the security key of the payment terminal 150 or the charging terminal 160 is stored. .

The general database 130 and the security database 140 transmit the verification result. The general database 130 receives the validation result of the card, and the security database 140 receives the validation result of the payment terminal 150 or the charging terminal 160 via the card management server 120 and the terminal 110. 150 or transmits to the charging terminal 160.

The payment terminal 150 or the charging terminal 160 transmits the electronically signed payment request signal or the charging request signal to the terminal 110 (S1060). If the payment terminal 150 or the charging terminal 160 has a sufficient balance in the card and the card is valid, the payment terminal 150 or the charging terminal 160 electronically signs and transmits a payment request signal or a charging request signal to the terminal 110. The payment terminal 150 or the charging terminal 160 electronically signs the payment request signal or the charge request signal, thereby preventing the required charge amount or payment amount from being changed.

The terminal 110 transmits a payment request signal or a charging request signal to the card management server 120 together with the card ID (S1065).

The card management server 120 transmits a payment request signal or a charging request signal together with the card ID to the security database 140 (S1070).

The security database 140 reflects the payment or charging amount in the balance information (S1075). The security database 140 decodes the electronically signed payment request signal or charge request signal to determine how much the payment amount or the charge amount is. Thereafter, the security database 140 reflects the payment amount or the charge amount grasped in the remaining balance information corresponding to the card ID.

The security database 140 notifies the general database 130 of the payment or charging of the amount (S1080).

The general database 130 stores the transaction history for the card ID (S1085). The general database 130 stores the payment or recharge of the amount for a specific card in the transaction history and stores the transaction history for each card ID.

The security database 140 transmits the electronically signed payment completion information or charging completion information to the payment terminal 150 or the charging terminal 160 (S1090).

The card management server 120 transmits the transaction history for each card ID according to a predetermined condition to the card company server and the data security device 170 (S1095).

11 is a flowchart illustrating a process of issuing a card to the terminal by the card management server according to an embodiment of the present invention. Since it has been described in detail with reference to Figures 1 to 10, the detailed description will be omitted.

The card management server 120 receives the card issuing request signal from the terminal 110 together with the terminal ID or the CI (S1110).

The card management server 120 determines whether the terminal ID or CI received in the general database 130 is stored (S1120).

If the terminal ID or CI received in the general database 130 is not stored, the card management server 120 issues a card and generates a security key of the issued card (S1130).

The card management server 120 separates the issued card information into information that requires encryption and information that does not require encryption (S1140).

The card management server 120 stores the separated information in the general database 130 and the security database 140 (S1150).

When the terminal ID or CI received in the general database 130 is stored, the card management server 120 grasps information that does not need encryption, stored together with the terminal ID or CI in the general database 130 (S1160). .

The card management server 120 transmits information that does not require encryption to the terminal (S1170).

The card management server 120 receives the card ID and the balance charge request signal from the terminal 110 (S1210).

The card management server 120 transmits a card validity authentication request signal to the general database 130 (S1220).

The card management server 120 receives the card validity authentication result from the general database 130 (S1230).

The card management server 120 transmits the card ID and the charging request signal to the security database 140 (S1240).

The card management server 120 receives the fact that the charge amount is reflected in the balance information from the security database 140 and transmits it to the terminal (S1250).

The card management server 120 transmits the transaction history for each card ID to the card company server and the data security device according to preset conditions (S1260).

The card management server 120 receives a card balance inquiry request for a specific card ID from the payment terminal 150 or the charging terminal 160 and inquires the balance of the specific card ID in the security database (S1310).

The card management server 120 transmits the balance of the specific card ID to the payment terminal 150 or the charging terminal 160 (S1320).

The card management server 120 receives the electronic signature of the payment terminal 150 or the charging terminal 160 and the card ID of the terminal from the terminal 110 (S1330).

The card management server 120 transmits the digital signature of the payment terminal 150 or the charging terminal 160 and the card validation request signal to the security database 140 to receive the verification result from the security database 140 (S1340). ).

The card management server 120 receives a payment or charging request signal from the terminal 110 together with the card ID and transmits the received signal to the security database 140 (S1350).

The card management server 120 receives the fact that the payment or the charged amount is reflected in the balance information from the security database and transmits it to the terminal (S1360).

The terminal 110 transmits a card selection signal to the card management server 120 (S1410).

When receiving the card selection signal, the card management server 120 determines whether the selected card is validly issued (S1420).

The card management server 120 determines whether to operate with the selected card according to the determination result (S1430).

The card management server 120 transmits the card selection result to the terminal 110 (S1440).

The terminal 110 transmits the card selection signal to the card management server 120 together with the payment or charging request signal (S1410). In addition, the terminal 110 may transmit current location information of the terminal 110 together.

The card management server 120 determines whether the selected card is valid (S1520).

If the selected card is valid, the card management server 120 performs an operation for payment or charging with the selected card (S1530). The card management server 120 transmits a message indicating that the card is selected to the terminal 110 and proceeds with the operation.

If the selected card is not valid, the card management server 120 transmits an error message indicating that the selected card is not valid to the terminal 110 (S1530).

The card management server 120 receives a card selection signal from the terminal 110 (S1610). The card management server 120 may receive a card selection signal before (not related to) a charging or payment request, or may receive it along with a charging or payment request.

The card management server 120 determines whether the selected card is valid (S1620).

If the selected card is valid, the card management server 120 to operate as the selected card, or proceed with the operation for charging or payment (S1630).

If the selected card is not valid, the card management server 120 transmits an error message to the terminal 110 (S1640).

In FIGS. 11 to 13 and 17, each process is described as being sequentially executed, but this is merely illustrative of the technical idea of the exemplary embodiment of the present invention. In other words, a person of ordinary skill in the art to which an embodiment of the present invention belongs may change the order of the processes described in each drawing or execute one or more of the processes without departing from the essential characteristics of the embodiment of the present invention. 11 and 13 and 17 are not limited to the time series since the processes may be applied in various ways.

Meanwhile, the processes illustrated in FIGS. 11 to 13 and 17 may be implemented as computer readable codes on a computer readable recording medium. The computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer system is stored. That is, the computer-readable recording medium may be a magnetic storage medium (for example, ROM, floppy disk, hard disk, etc.), an optical reading medium (for example, CD-ROM, DVD, etc.) and a carrier wave (for example, the Internet Storage medium). The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

The above description is merely illustrative of the technical idea of the present embodiment, and those skilled in the art to which the present embodiment belongs may make various modifications and changes without departing from the essential characteristics of the present embodiment. Therefore, the present embodiments are not intended to limit the technical idea of the present embodiment but to describe the present invention, and the scope of the technical idea of the present embodiment is not limited by these embodiments. The scope of protection of the present embodiment should be interpreted by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present embodiment.

Claims

In the card management server for receiving a card issuance request from the terminal to issue a card to the terminal,

Receiving a card issuing request including a terminal ID or CI (Connecting Information, personal identification information) information of the terminal from the terminal, and the information that does not require encryption of the information of the issued card to the terminal and the general database, Communication unit for transmitting the information that needs encryption of the information of the issued card to the security database;

The card ID is assigned to the terminal ID or the CI information, the card is controlled to generate a security key using the assigned card ID, and the card is issued. The information of the issued card is divided into information that does not require encryption and information that requires encryption. Control unit to control each of the transmission to a different configuration;

A memory unit for storing a card ID of a card to be issued;

A signature value encryption / decryption module for generating a security key using the card ID and the unique key by matching a unique key generated or previously generated and stored to a card ID given by the controller; And

Separation module for separating the information of the card issued by the controller into information that does not require encryption and information that requires encryption

Card management server comprising a.
The method of claim 1,

The card issuing request is

Card management server comprising the option information for the card to issue.
The method of claim 2,

The information of the issued card is,

And some or all of the terminal ID, the card ID, the CI information, the option information, the balance information in the issued card, and the unique key.
The method of claim 3,

The information that does not require the encryption,

The terminal ID, the card ID, the CI information, and the option information;

The information that requires encryption includes card balance information and the unique key in the issued card.
The method of claim 1,

The control unit,

When the card issuance request is received from the terminal, the terminal ID or the card ID is transmitted to the general database in order to determine whether the terminal requests a card issuance for the first time or reissues a previously issued card. Card management server, characterized in that for controlling the communication unit to.
In the card management server receives a card issuance request from the terminal to issue a card to the terminal,

Receiving a card issuing request including a terminal ID or CI (connecting information) information of the terminal user from the terminal;

A card ID is assigned to the terminal ID or the CI information, and a card is issued by generating a security key using the card ID and the unique key by matching the unique key generated or stored in the assigned card ID. Issuing process;

Separating the information of the issued card into information that does not require encryption and information that requires encryption; And

A process of transmitting the information that does not need encryption to the terminal and the general database, and information that needs to be encrypted among the information on the issued card to a security database.

Card issuing method comprising a.
The method of claim 6,

The card issuing request is

Card issuing method comprising the option information for the card to be issued.
The method of claim 7, wherein

The information of the issued card is,

And the terminal ID, the card ID, the CI information, the option information, the balance information in the issued card, and some or all of the unique keys.
The method of claim 8,

The information that does not require the encryption,

The terminal ID, the card ID, the CI information, and the option information;

The card issuing method includes the balance information and the unique key in the issued card.
The method of claim 6,

The issuing process,

When the card issuance request is received from the terminal, the terminal ID or the card ID is transmitted to the general database in order to determine whether the terminal requests a card issuance for the first time or reissues a previously issued card. Card issuing method, characterized in that.