KR101604459B1 - Method, apparatus and system for generating transaction related otp - Google Patents

Abstract

The present invention relates to a method, apparatus and system for generating a transaction-based One Time Password (OTP), the method comprising: transmitting a transaction request to a payment server using a secure application (Trusted Application) Receiving transaction information in response to a transaction request, and generating a transaction interoperability using transaction information as an input value using a security application. In particular, when an AP (Application Processor) of a client terminal is logically divided into a general domain and a security domain, and when executing a security application, the security domain has rights to all hardware and software operations of the client terminal, And a security UI (Trusted User Interface) is displayed.

Description

[0001] METHOD, APPARATUS AND SYSTEM FOR GENERATING TRANSACTION RELATED OTP [0002]

The present invention relates to a method, apparatus and system for generating a transaction-related one-time password (OTP), and more particularly, to a method and system for generating an opportunistic information including transaction information using a secure operating system (OS) .

With the increasing use of digital devices such as computers and smart phones, electronic commerce using such digital devices has been widely used in various fields. In particular, mobile terminals such as smart phones have advantages that users always carry around, and various financial related applications are released to facilitate users' convenience.

OTP (typepi) input method is commercialized as a function of security and authentication by replacing various methods such as existing security card, USB security key, SMS OTP, CAPTCHA (virtual keyboard) and SMS in financial transactions using such a smartphone . However, there is a fear of inconvenience and loss of possessing a new terminal, and there is a risk of hacking in recent years.

Among these problems, in order to solve the inconvenience of having an autopilot terminal, Korean Patent Registration No. 10-0883154 discloses an autopilot generation / authentication system using a mobile phone having an autopilot program. However, the above-mentioned registered patent has a disadvantage in that it is easy to hack and weak in security because it is built in a wormhole chip and simply runs an opportunistic program.

In addition, in recent input / output stages of the OTT number, the OTT number is leaked or hacked, causing financial damage. For example, even if a correct account number and a transfer amount are displayed to a user at the time of transferring money, data may be modulated at the backend and transferred to another account number and a transfer amount. Therefore, there is a need to introduce a new method to prevent the risk of such hacking in a conventional method of generating an orthopyxis using a random number.

Korean Registered Patent No. 10-0883154 (registered on Feb. 4, 2009)

SUMMARY OF THE INVENTION It is an object of the present invention to provide a method, apparatus, and system for generating transaction-related opportunistic data to solve the above problems.

According to a first aspect of the present invention, there is provided a method of generating a transaction time ticket (OTP), the method comprising: transmitting a transaction request to a payment server using a security application (Trusted Application) Receiving the transaction information in response to the transaction information, and generating a transaction interoperability including the transaction information as an input value using the security application. In particular, when an AP (Application Processor) of a client terminal is logically divided into a general domain and a security domain, and when executing a security application, the security domain has rights to all hardware and software operations of the client terminal, And a security UI (Trusted User Interface) is displayed.

Optionally, the security application may be executed in a manner that is called or linked through a predefined function of a generic application running in the general domain. The security UI can be implemented such that the security area acquires all rights of the screen input / output at the time of execution and operation of data transmission, screen capture, and recording functions to the outside can not be performed. The secure area stores a static key distributed by the Trusted Server Manager (TSM) to the client terminal and the payment server. The client terminal and the payment server store a session key encrypted with the fixed key, And the payment server encrypts and generates a symmetric key for generating the transaction interoperability attribute with the session key, and transmits the generated secret key to the client terminal. When the client terminal receives the secret key using the session key And encrypting the encrypted symmetric key.

According to a second aspect of the present invention, there is provided an apparatus for generating transaction interoperability using a security application, comprising: an interface for transmitting a transaction request to a payment server through a security application and receiving transaction information in response to a transaction request; An autopilot generation processor for generating transaction-related opportunistic based on the received transaction information as an input value; And a display unit for displaying a transaction progress status according to a user's input using an interface and displaying the received transaction information, wherein the interface transmits the transaction interoperability generated in the opportunisticity generation processor to the payment server And displays the result of the verification on the display unit.

A third aspect of the present invention is a system using a transaction interlocking notifie, the system comprising: a server for transmitting a transaction request using a security application, receiving transaction information in response to a transaction request, A client terminal for generating an opportunistic; A payment server for receiving a transaction request and sending a transaction interlock request; A verification server for receiving the transaction interworking request and delivering it to the push server; And a push server for receiving the transaction interlocking request from the verification server and transmitting the transaction information corresponding to the transaction interlocking request to the client terminal.

According to the transaction-based opportunistic generation method and apparatus of the present invention, there is no need to possess a hardware opportunistic device. By using the portable terminal of the user, it is possible to promptly recognize and report even if it is lost. In addition, while the hardware off-chip unit requires replacement and replacement at the expense of the battery, the present invention is economical because it can reduce the battery replacement cost. The present invention is advantageous in that it is very practical and extensible in that it does not need to physically establish an integrated authentication center when replacing the existing dongle autopilot device and can be used jointly in various fields without additional cost.

According to the transaction-based opportunistic generation method and apparatus of the present invention, not only the safety and the security are improved because the opportunistic creation and the financial transaction are performed using the separate security operating system on the client terminal, Even if an off-chip number is leaked, it is possible to perform verification using the transaction information at the time of verification, and to prevent it from being used for other transactions or abused by others. In other words, in the past, when a user checks transfer details or purchase / payment details at a financial transaction or a commercial transaction, there is a problem that an account number or the like is changed by hacking at the time of actual transaction. However, It is possible to prevent the damage caused by the data value change in the middle by generating the transaction information confirmed by the smart phone as the transaction-related transaction. In particular, transaction-linked OTP is a key feature that allows customers to directly check transaction details and input their contents. Despite the advantage of being much safer than the current method, customers have to enter the same transaction again It was not commercialized. The TZ OTP system proposed in the present invention can be implemented in a form that the customer can check transaction details and automatically input in a safe manner without re-inputting, which is convenient and can be implemented commercially. It can be both safe and practical.

Furthermore, the transaction-related authentication of the present invention can replace various methods such as a security card, a USB security key, an SMS OTP, a CAPTCHA (Virtual Keyboard), an SMS or a public certificate, and further authentication is unnecessary.

The present invention can provide a separate security area based on the hardware, and in particular, it is possible to completely block the forgery of data at the input / output end through the implementation of the security UI technology and to block the data transmission and screen capture action, It has the effect of complementing weakness of security technology and ensuring integrity at input / output stage.

Further, by using the E2E cipher system proposed in the present invention, it is possible to encrypt a chip value necessary for TZ OTP generation with a shared key, and to securely transmit a key from a server to a trust zone. By applying the E2E encryption method of the present invention to the trust zone technology of the present invention, it becomes possible to implement an encryption technique that maximizes security and safety.

FIG. 1 illustrates a system 100 using transactional transactions according to an embodiment of the present invention.
FIG. 2 illustrates an operating system of the client terminal 10 used for generating transaction-related opportunistic information according to an embodiment of the present invention.
Fig. 3 (a) shows a general operation in a client terminal according to an embodiment of the present invention, and Fig. 3 (b) shows an operation in a transaction- (C) shows an embodiment of a security UI according to an embodiment of the present invention.
FIG. 4 shows a method of generating transaction-related opportunistic according to an embodiment of the present invention.
FIG. 5 is a swimlane diagram showing a transaction method using a transaction-related attribute according to an embodiment of the present invention.
6 illustrates a key update protocol of a transaction-related attribute according to an embodiment of the present invention.
FIG. 7 illustrates a re-issuance protocol of a transaction-related entity according to an embodiment of the present invention.
8 illustrates an unlocking protocol on a client terminal or a payment server of a transaction-associated attribute according to an embodiment of the present invention.
9 is a screen shot showing an execution screen of the security UI according to an embodiment of the present invention.
10 is a diagram for explaining the E2E protocol according to an embodiment of the present invention.
In the various drawings, the same reference numerals and symbols denote the same elements.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference numerals even though they are shown in different drawings. In the following description of the embodiments of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the difference that the embodiments of the present invention are not conclusive. In this specification, when it is mentioned that a certain element includes an element, it means that it may further include other elements.

FIG. 1 illustrates a system 100 using transactional transactions according to an embodiment of the present invention. The system 100 includes a client terminal 10, a payment server 30, a verification server 40 and a push system 50. The components 10, 30, 40, Lt; RTI ID = 0.0 > 20 < / RTI > The payment server 30, the verification server 40 and the push system 50 may be embodied in a form in which some or all of the components 30, 40 and 50 are coupled to each other. have.

The client terminal 10 is a device capable of accessing the payment server 30 for online financing transactions, and is a computing device equipped with hardware and software capable of financial transactions and commerce. The client terminal 10 may be a variety of mobile computing devices such as computing devices such as personal digital assistants (PDAs), cellular phones, smart phones, as well as various digital computers such as laptops, desktops, workstations, And digital devices capable of communication such as IPTV using internet protocol. The description of the present invention is based on a smart phone having both performance and portability comparable to those of a computer, but is not limited thereto.

The biggest feature of the smartphone is that it can install, add or delete hundreds of various applications (applications, applications) as user wants, unlike the existing mobile phones which were released as finished products and used only the functions . In addition, smartphone users can directly access the Internet using wireless Internet, and can access Internet contents in various ways using various browsing programs. Furthermore, smartphones are now being applied to real life applications, such as mobile internet banking, mobile credit card, mobile social networking, and mobile shopping. For this purpose, banks, securities companies, credit card companies, social commerce companies, Shopping mall companies develop their own smartphone applications for their smartphone operating systems and distribute them to users for a fee or free of charge. As described above, according to the emergence of a mobile communication terminal having strong performance comparable to a computer and mobility due to a network function, the present invention is centered on a case where the user portable terminal 200 is a smart phone.

For reference, an application is a kind of software operating on an operating system (OS), and is a program designed to directly perform a specific function with respect to a user or another application program. A security application used in a client terminal such as a smart phone according to an embodiment of the present invention may be a mobile application that is designed to be applied to a mobile device. The mobile application may depend on a browser-based application and a terminal operating system A native application manufactured in accordance with the present invention, a hybrid application combining them, or the like. Application data, system data, and the like are recorded and stored in a predetermined programming language (for example, C language or Java (JAVA)) on a computer-readable recording medium. The application data is data having various program functions (for example, screen switching by recognizing a user's touch through a display screen) implemented so as to enable interaction with a user, and is also referred to as full mode data. System data refers to data including application management information, start-up information, and the like, and attribute and operation information for reproducing application data. And information for implementing other additional functions can be stored in the recording medium.

The client terminal 10 according to the present invention includes hardware and software capable of operating various applications on a terminal. In particular, the present invention provides a security OS (hereinafter referred to as " An operating system).

The client terminal 10 of the present invention performs a financial transaction using a security OS independently operated, unlike a general OS used for executing a general application of the client terminal 10 during a financial transaction. The environment in which the secure OS and the security application operate in the client terminal 10 is referred to as a security zone (for example, a trust zone). The present invention relates to a trust zone-based financial transaction. The operation of the trust zone based will be described in more detail with reference to FIGS. 2 and 3. FIG.

The client terminal 10 can be used in general financial transactions such as banking, and commerce using merchant sites or online shopping malls. The client terminal 10 accesses the payment server 30 via the network 20 and proceeds with the transaction process according to the guidance. At this time, the network 20 may be implemented as digital data communication (e.g., a communication network) of any form or medium. Examples of the communication network include a local area network (LAN), a wide area network (WAN) It can be used in various mobile networks including various forms of wireless communication such as 3G, WiFi, and LTE.

The payment server 30 may be a server operated by a bank or a financial institution for financial transactions, or an online payment server for commerce. After receiving the transaction or payment request from the client terminal 10, the payment server 30 performs authentication and verification procedures, and then transmits the transaction result to the client terminal to notify whether the transaction is terminated. At this time, the verification can be performed in cooperation with the verification server 40 at the time of authentication or verification. The verification server may be driven by the same entity as the payment server 30, and may be driven by a separate verification authority.

The push system 50 serves to send a push message to the client terminal 10 in response to a push request from the payment server or the verification server. In one embodiment of the present invention, the push information may be transmitted on the transaction information for transaction interoperability creation on the client terminal 10.

The present invention can be applied to a client terminal 10 via a payment server, a verification server, and a push system at the time of a financial transaction and a commercial transaction using a smart phone using these components 10, 20, 30, 40, The client terminal 10 transmits the transaction information including the amount of money and the account number, and the client terminal 10 generates the opportunistic copy using the received transaction information. In the following, the opportunistic information generated by using the transaction information is referred to as a " transaction-linked opportunistic. &Quot; The transaction-linked attribute can be used for other transactions because it can be verified by using the transaction information at the time of verification even when the object number is leaked at the input / output stage of the object number, and has the advantage of improving the security. The transaction interlocking suggestion proposed in the present invention includes the transaction information of the bank identification code, the account number, and the transfer amount in the financial transaction, and the transaction information in the commercial transaction includes the purchase product name, the purchase amount, and the purchase place. The input values (transaction information) for generating transaction-related opportunistic information can be input as numeric or character data. In the present exemplary embodiment, the transaction information to be set so that the transaction can not be changed at the time of transaction is selectively selected as the input value. However, the present invention is not limited thereto, and further transaction information may be additionally input to generate transaction interoperability.

In addition, since transactional authentication is generated in the security application using a security OS independently operating on the client terminal, safety and security are ensured, and security cards, USB security keys, SMS OTPs, CAPTCHAs (virtual keyboards) It is possible to substitute various security measures such as SMS or public certificate, and it is unnecessary to perform additional authentication, so that the convenience of the user can be achieved. In addition, in the past, there has been a problem that the user checks transfer details or purchase / payment details at the time of a financial transaction or a commercial transaction, but there is a problem that the account number or the like is changed by hacking at the actual transaction. However, It is possible to prevent the damage caused by the data value change in the middle by generating the transaction information confirmed by the smart phone as the transaction-related transaction.

In particular, transaction-linked OTP is a key feature that allows customers to directly check transaction details and input their contents. Despite the advantage of being much safer than the current method, customers have to enter the same transaction again It was not commercialized. The TZ OTP system proposed in the present invention can be implemented in a form that the customer can check transaction details and automatically input in a safe manner without re-inputting, which is convenient and can be implemented commercially. It can be both safe and practical.

The present invention can provide a separate security area based on the hardware, and in particular, it is possible to completely block the forgery of data at the input / output end through the implementation of the security UI technology and to block the data transmission and screen capture action, The transaction-based opportunistic method of the present invention can be applied to a time synchronization method, a time synchronization method, an event combination method, - It is applicable to the challenge-response method.

A concrete method of generating such a transaction-related attribute will be described in detail with reference to FIGS. 2 to 5. FIG.

FIG. 2 illustrates an operating system of the client terminal 10 used for generating transaction-related opportunistic information according to an embodiment of the present invention. The client terminal 10 of the present invention includes a normal environment 110 for driving the general OS 114 and the general application 112 and a trust zone 130 operating independently of the normal environment 110 do. The Trust OS 134 and the Trusted App 132 operate independently of the normal OS 114 and the general application 112 in the Trust Zone 130 which is a security environment, May share some or all of the user interface 120, as shown. The client terminal 10 also includes an ARM processor 150 based on a trust zone technology capable of selectively operating the trust zone 130 and the general environment 110.

The trust zone 130 includes a secure OS 134 supporting a secure environment and a secure application 132 operated by a secure OS. The trust zone 130 is a hardware-based security execution environment (TEE) that logically separates a mobile CPU (AP) of a client terminal such as a smart device into a general area and a security area and then implements access to the security area, Technology. The security area is logically separated from the general environment 110 and can be communicated only through a predefined interface by implementing it so that it can not access each other except for the predefined interface 120 and the shared memory, Access is blocked. In addition, the trust zone 130 restricts installation and use of applications only by a service provider authorized by the Trusted Service Manager (TSM), and operates in a completely separated manner in a separate area, . In this way, secure storage is possible even when storing the E2E key, private key, etc. through the implementation of the completely separated security zone. The E2E encryption method will be described in more detail with reference to FIG.

In one embodiment, data stored using the secure application 132 in the trust zone 130 may be stored in the general environment 110 as an encrypted form, but it is not decryptable in a normal environment, It is implemented so that decoding is not possible in the application. As another embodiment, even if an application of the same kind as that of the security application 132 is used, it can not be decrypted by another device.

As such, the trust zone 130 is logically completely separated and driven independently, so that it is possible to safely store and process financial-related information and financial-related information using the client terminal 10.

In particular, the trust zone-based security application 132 implements a secure UI (Trust UI) to implement security authentication and secure login, thereby realizing generation of secure transaction-related authentication in the security domain, The necessary information can be safely handled. Furthermore, by implementing a new technology that combines a security UI with the E2E encryption method described later in the security domain, it becomes possible to implement a non-hackable transaction-oriented authentication. The security UI will be described in more detail with reference to Figure 3. In one embodiment, the security application 132 of the present invention can perform login or authentication processing that requires security in general commerce as well as financial transactions. Further, the security application 132 of the present invention can generate a transaction-related attribute using transaction information, and the transaction-related attribute can be a security card, a general OTP token, a USB security key, an SMS OTP, a CAPTCHA It is possible to replace the various security measures such as the public key, the public key certificate, and the public key certificate, thereby enabling simple and safe transactions, and can be utilized as an authentication means in the Internet of things (IOT). Since the transaction-related authentication proposed in the present invention is generated substantially without a physical medium, there is an advantage that a user can be easily issued online without visiting a bank or the like (for example, an online bank And can be implemented so as to be issued.

3 (a) shows a general operation in the client terminal 10 according to an embodiment of the present invention, and FIG. 3 (b) shows an operation in the trust zone 130 according to another embodiment of the present invention (C) shows an implementation example of the security UI.

2, the general environment 110 and the trust zone 130 are logically separated, and when the general application 112 is executed, the general OS 114 supports the operation, and the display unit 170 displays, (UI) 116 (FIG. 3 (a)).

On the other hand, at the time of execution of the security application 132, the security OS 134 supports the operation thereof and displays a security UI 136 ('TUI') through the display unit 170 (Fig. 3 (b)). As shown in FIG. 3 (c), since the security UI 136 is displayed with higher priority than the general UI, the security UI 136 can not be accessed in the normal environment 110, It is possible to secure the safety of financial transaction or commerce executed through the trust zone 130. [

Particularly, when the security UI 136 is activated, all input / output information can not be captured outside. When the security screen is activated, the security zone uses the CPU exclusively. Therefore, all operations and operations of the general area are suspended, and the application of the trust zone based on the separate OS (ie, security OS) It blocks access itself. At this time, it is possible to prevent hardware data transmission such as capturing and recording by implementing not to execute even hardware operation keys such as home button and back button except input keypad. In order to return to the normal environment, It can be implemented only through the SW Back button. For example, if a smartphone with a trust zone is connected to a PC and the PC screen is displayed through a projector, if the smartphone is running TZ OTP, the screen changes on the smartphone from the moment when the security UI screen is executed, The output port is blocked and nothing is displayed on the PC and projector screen.

When the security UI is executed, all rights of the screen input / output can be acquired by the security area, and data input / output can be blocked. Capture or recording of the output screen is also impossible. For example, there is no way to block the screen capture by a hardware capture method (for example, a method of capturing a screen by pressing the home key and the power key at the same time) even if a security screen is implemented through an existing software security method. However, when the security UI 136 implemented in the present invention is operated, it is prevented from capturing or recording by a screen capture action, thereby completing the weakness of the existing security method. In addition, all coordinate values input on the screen can not be deodorized from the outside, and data forgery can be prevented. When the security UI according to the present invention is driven, additional security devices such as a virtual keyboard are unnecessary. Therefore, it is possible to prevent forgery and falsification without a separate security solution, and also to provide a keyboard and coordinate value security.

The security UI 136 is used in the OTP PIN number input screen and the OTP generation result screen, and it is possible to safely protect the OTP generation value after the PIN number authentication from the risk of hacking through the security UI screen.

FIG. 4 shows a method of generating transaction-related opportunistic according to an embodiment of the present invention. The client terminal 10 of the present invention can perform financial transactions and commercial transactions using the transaction interlocking notifying function in cooperation with the payment server 30, the verification server 40, and the push system 50.

The client terminal 10 of the present invention conducts a transaction utilizing the transaction interoperability (OTP) using the security application 132. Here, when a user executes a general application and selects a menu requiring security such as OTP registration and confirmation through a general UI screen executed in a normal area, the security application is called (or linked) Run the application. The security application runs with the security UI implementation at the time of execution of the menu requiring security, and can switch back to the normal application mode through the predefined key.

In an exemplary embodiment, the client terminal 10 receives input information necessary for a transaction such as a payment amount (or a transfer amount) and a transfer account in accordance with an input of a user in a financial transaction or a commercial transaction, (Step 410). For example, when executing a bank transfer application by executing a bank application on a smart phone, when the user executes the bank application, the bank application is executed on the trust zone 130, and the information is transferred from the user using the security UI 136 And transmit it to the payment server 30.

At this time, an authentication process is performed between the client terminal 10 and the payment server 30 for initialization. The client terminal generates a signature value with the client public key and transmits the signature value to the payment server 30. The payment server 30 receives the signature value and generates a signature value using the server public key and transmits the signature value to the client terminal 10 to perform authentication. The client terminal 10 and the payment server 30 may include a user random or a server random value when transmitting / receiving data for authentication, in order to prevent reuse. Next, the client terminal 10 generates a session key, encrypts the session key with the server public key, and transmits the encrypted session key to the payment server 30. The payment server 30 encrypts the session key using the session key after generating the serial and seed values, ) To share the serial and seed values and complete the initialization process.

After the connection for the transaction between the client terminal 10 and the payment server 30 is made, the financial transaction or the commerce process is performed on the client terminal 10 through the security application 132, (Step 410). ≪ / RTI >

The payment server 30 receives a payment request for a transaction from the client terminal and then sends a transaction interlock request to the verification server 40 and the verification server 40 transmits the transaction interlock request to the client terminal 10 through the push system 50 And to transmit the transaction information (operation 420). The client terminal 10 receives the transaction information including the transfer amount, the account number, the transfer bank (bank identification code), etc. from the push system 50, and confirms the transaction information received on the client terminal 10 (Step 430). The detailed description of the present invention focuses on the configuration for transmitting the transaction information through the push system 50. In another embodiment, the payment server 30 or the verification server 40 does not pass the push system 50 And to transmit the transaction information to the client terminal 10.

When the client terminal 10 receives the transaction information, it generates an OTP based on the received transaction information as an input value (operation 440). The present invention is characterized in that, unlike the conventional OTIFI, 'transaction interoperability' is generated and used by using transaction information. It is not a random number formed randomly but a transaction that contains transaction information as an input value. It is a one-time password that can not be estimated with the generated office number but can confirm the transaction information at the time of verification. For example, the existing authentication number uses the six-digit number, but the transaction-related attribute can be implemented as eight-digit number.

In one embodiment, the transaction information may include a bank identification code, an account number, and a transfer amount, and the security application 132 of the client terminal 10 may apply the transaction information to the input value, You can create a tissue. As described above, the transaction-related attribute proposed in the present invention includes the transaction information of the bank identification code, the account number, and the transfer amount in financial transaction, and the transaction information in the commercial transaction includes the purchase product name, do. The input values (transaction information) for generating transaction-related opportunistic information can be input as numeric or character data. In the present exemplary embodiment, the transaction information to be set so that the transaction can not be changed at the time of transaction is selectively selected as the input value. However, the present invention is not limited thereto, and further transaction information may be additionally input to generate transaction interoperability.

The transaction information is automatically applied as an input value after receiving through the push system 50 to generate an overtape. Therefore, it is possible to reduce the inconvenience of the user having to input transaction information separately, It is possible to generate it by using the above-mentioned method.

Such transaction-related authentication is virtually impossible to take out or tamper with the outside from the OTIF I / O unit by using the security UI technology. Even if it is hacked or leaked at the input / output stage of OTIFI and used by others, , If the transaction information included in the atopy is different from the transaction information transmitted through the push system 50 at the time of verification, the transaction is impossible. Therefore, when the security UI technology of the present invention is used, it is impossible to access from the outside and data can be taken out to the outside through the hardware-based security, and even if the otipi is leaked to another person in a physical way, It can prevent various financial accidents. In this way, the transaction-oriented approach improves security and stability of financial transactions and has infinite scalability in various fields.

Next, the client terminal 10 transmits the created transaction interoperability attribute to the payment server 30 (operation 450). In one embodiment, the payment server 30 may receive the transaction interoperability and verify itself, and then pass the verification result to the client terminal 10, or as another embodiment, And delivery of the verification results.

When the verification is completed, the client terminal 10 receives a payment completion message (or transaction / verification completion message) as a verification result (operation 460). That is, after receiving the verification result, the security application 132 may proceed with another transaction or complete the transaction. If the payment completion message is not received or an authentication failure message is received, the payment server 30 may request the payment again (step 410) and regenerate the transaction interoperability.

According to the transaction-based opportunistic generation method of the present invention, there is no need to possess a hardware opportunistic device. By using a client terminal carried by the user, there is an advantage that the user can quickly recognize and report it when lost. In addition, in the case of a hardware off-chip device, the battery is exhausted and replaced at an additional cost, whereas the transaction-based off-chip generating system according to the present invention has a cost saving effect in this respect.

In addition, not only the safety and security are ensured because the opportunistic creation and the financial transaction are performed using a separate security operating system on the client terminal, and even if the offi number is leaked at the input / output stage of the automatic ticket number, It can be verified and prevented from being abused by others. Furthermore, the transaction-related authentication of the present invention can replace a security card or a public certificate, and it is unnecessary to perform additional authentication, so that the convenience of the user can be improved, and the system can be expanded in various transaction fields including financial transactions.

FIG. 5 is a swimlane diagram showing a transaction method using a transaction-related attribute according to an embodiment of the present invention. As described with reference to FIG. 4, the client terminal 10 can proceed with the financial transaction and the commerce transaction process using the security application 132.

The client terminal 10 receives input information necessary for a transaction such as a payment amount (or a transfer amount) and a transfer account according to an input of a user in a financial transaction or commerce. For example, if the user makes a transfer transaction, the user receives transfer information from the user and transmits a transfer request to the payment server 30 (operation 510). As another example, when the payment is made at the online site, the client terminal 10 transmits a payment request to the payment server 30 (step 510).

The payment server 30 receives the payment request 510 from the client terminal 10 and transmits a transaction interlock request to the verification server 40 in operation 520. That is, it requests the verification server 40 to proceed with the transaction using the transaction interoperability. After receiving the transaction interlock request from the payment server 30, the verification server 40 sends a push request to the push system 50 (step 530). After receiving the push request from the verification server 40, the push system transmits the transaction information to the client terminal 10 in the form of a push message (operation 540). The transaction information is transmitted from the payment server 30 or the verification server 40 to the client terminal 10 without passing through the push system . ≪ / RTI >

The client terminal 10 can confirm the received transaction information through the security application 132 (550). For example, if the user confirms the transaction information and approves creation of the atype, the security application can be automatically implemented to generate the transaction interoperability (step 560). The client terminal 10 can generate a transaction interoperability using a part or all of the transaction information received from the push system 50 at the time of transaction interoperability. The transaction information may include a bank identification code, an account number, and a transfer amount in a financial transaction. The transaction information includes a purchase product name, a purchase amount and a purchase place at the time of a transaction, and generates an authentication number through a hash algorithm when generating transaction- can do.

The client terminal 10 transmits the generated api to the payment server 30 in step 570 and the payment server 30 verifies the transaction-related authentication to the verification server 40 (Step 580). The verification server 40 transmits the verification result of the received transaction interoperability attribute to the payment server 30 and is transmitted to the client terminal 10 (steps 590 and 595).

The verification result may be delivered in the form of a payment completion message (or a transaction / verification completion message), or may be implemented such that payment is automatically completed upon completion of verification. If the payment completion message is not received or an authentication non-authentication message is received, the payment server 30 may request the payment again to regenerate the transaction interoperability.

According to such a transaction-related opportunistic generation method, not only safety and security are ensured but also verification using transaction information at the time of verification can be performed even if an off-chip number is leaked at the input / output stage of the automatic ticket number, Can be prevented. Further, the transaction-related authentication of the present invention has an advantage that it can replace various security measures such as a security card, a general OTP token, a USB security key, an SMS OTP, a CAPTCHA (virtual keyboard), an SMS or a public certificate.

Hereinafter, additional functions will be described in the transaction using the transaction interoperability in FIGS. 6 to 8. FIG.

FIG. 6 shows a key update protocol of the transaction-related attribute. When the client terminal is newly replaced, the existing client terminal 10 generates an update utility value (610), inputs the update utility value and the serial value on the new client terminal (620) The OTP SEED may be updated on the database of the payment server 30. The payment server 30 verifies the api value and processes the same to register the same serial and new api value in the new client terminal (630 to 670). With this function, it is possible to utilize the autopilot generation function even when the client terminal is replaced, and it is easy to register and manage on the payment server.

FIG. 7 shows a re-issuance protocol of transaction-related attributes. If it is impossible to update the api from the existing client terminal, the api can be reissued to the new client terminal. For example, when the user requests re-issuance to the payment server 30 using the Internet as the user terminal 17, the payment server 30 transmits the serial and the authentication value to the user after performing the user authentication (710 to 740 ). The user inputs the received serial and the authentication value to the new client terminal 15 and transmits the received serial and authentication value to the payment server 30 so that the payment server 30 updates the authentication and oticity of the serial and new authentication key values (760 to 790).

Although the data communication between the payment server 30 and the client terminal 10 has been described in the above example in the case of updating or reissuing the authentication key in the new client terminal, the payment server 30 includes a registration server, a verification server, , And a management server, or may be implemented as a single server.

Fig. 8 shows the unlocking protocol on the client terminal or the payment server of the transaction-related attribute. The transaction-based offi-generating system according to the present invention has a function of switching the client terminal 10 to the lock mode when the PIN verification has failed more than a predetermined number of times (Fig. 8 (a)). In this case, the user also accesses the management server 30 with the other terminal 17 to request the client unlock, receives the unlocked value after authentication, inputs the unlocked value to the locked client terminal 10, It can be easily released. In many cases, the transaction itself can not be used in the case of failing to input the password. In many cases, it is possible to cancel the lock state by resetting the password through the counter service by visiting the relevant institution such as the direct bank, The unlock function of the user can be used to facilitate the user's convenience.

As another example, if the verification is failed at the server end, the payment of the payment server 30 may be set to the lock mode (Fig. 8 (b)). At this time, an unlock value is generated on the client terminal 10. When the client terminal 10 generates an unlock value and accesses the payment server 30 to request unlocking of the server (unlocking of the server), the server verifies the unlock value through the verification server 40 and releases the lock mode of the server can do.

In this way, when the verification on the user pin or the server fails, the client lock mode or the server lock mode is automatically set so that the transaction can be used more flexibly than the case where the transactions can not be uniformly performed. It can be easily unlocked through the authentication, so that it is possible to eliminate the inconvenience of having to visit the institution directly. In addition, the agency can also reduce these tasks that are not directly related to financial transactions, which has the advantage of streamlining operations and increasing efficiency.

9 is a screen shot showing an execution screen of the security UI according to an embodiment of the present invention. FIG. 9 is a view for explaining an example of the security UI described in FIGS. 2 and 3, and shows a screen shot when the client terminal 10 actually is implemented.

9A shows a general application and a general UI screen driven in a normal region, FIG. 9B shows a security application running in a security zone (trust zone) FIG.

The user of the client terminal 10 executes the general application installed in the general environment. Here, the general application is an application that interlocks with the security application of the present invention. Since the user can not directly access and execute the security application, the general application provides a general application that can call the security application when generating the OTP .

FIG. 9A shows a general UI screen 910 executed by a user in a general area (Normal World) by executing a general application. The general UI screen is capable of general terminal operation (e.g., capture). When a menu requiring security such as OTP registration and confirmation is selected on the general application shown, a security application is called (or linked) in a general application to execute the security application.

The security application supports the operation of the security OS (Trust OS) and displays the security UI (TUI) through the display unit. As described above, since the security UI is displayed at a higher level than the general UI with the highest priority, it can not be accessed in a normal environment, and the screen touch coordinate is implemented so that it can not be known in a normal environment. Therefore, Safety can be achieved.

In this embodiment, the security UI is used in the OTP PIN number input screen 920 and the OTP generation result screen 930, and it is possible to securely protect the OTP generation value after the PIN number authentication from the risk of hacking through the security UI screen .

When the security UI 136 is activated, when the security screen is activated, all operations in the general area are suspended, and since an app in the trust zone based on a separate OS (i.e., a security OS) is executed, . At this time, it is possible to prevent hardware data transmission such as capturing and recording by implementing not to execute even hardware operation keys such as home button and back button except input keypad. In order to return to the normal environment, It can be implemented only through the SW Back button.

When the security UI is executed, all rights of the screen input / output can be acquired by the security area, and data input / output can be blocked. Capture or recording of the output screen is also impossible. For example, there is no way to block the screen capture by a hardware capture method (for example, a method of capturing a screen by pressing the home key and the power key at the same time) even if a security screen is implemented through an existing software security method. However, when the security UIs 920 and 930 implemented in the present invention are operated, capture and recording are prevented from being performed even with a screen capture action. In addition, all coordinate values input on the screen can not be deodorized from the outside, and data forgery can be prevented. When the security UIs 920 and 930 of the present invention are driven, an additional security device such as a conventional virtual keyboard is unnecessary. Therefore, it is possible to prevent forgery and falsification without a separate security solution, .

10 is a diagram for explaining the E2E protocol according to an embodiment of the present invention. The TZ OTP proposed in the present invention employs E2E encryption (End-to-End Encryption). In order to use the OTP, the secret values necessary for OTP generation must be mutually shared. In the system of the present invention, the OTP key is generated in the server and transmitted to the TZ OTP (TA) The OTP key is encrypted using a specific key value to be transmitted. TSM provides the ability to distribute keys to clients and servers (TSM Personalization).

The Trusted Service Manager (TSM) as a server in the trust zone or as a separate server may also be referred to as another name, such as Trusted Application Manager (TAM), and may be referred to as a TZ OTP client 2100 and a TZ OTP And shares a static key with the server 2400 (1010).

Here, the TSM 2200 of the present invention has a key personalization method. The TSM 2200 derives an OTP key value by using the TSM function (which distributes the key) Used for encryption. When registering the TZ OTP to TSM, the administrator creates a Personalization Master Key and registers it with TSM, installs the service provider by TSM, and installs TZ OTP. Next, a personalization key derived from the registered Personalization Master Key is generated. After the TZ OTP installation is completed, a personalization object installation process is performed. In this process, a personalization key is installed.

After the TSM 2200 distributes the fixed key, the TZ OTP client 2100 transmits the company code in the initialization step, the TZ OTP server 2400 confirms the enterprise code, And generates a random value (steps 1020 and 1030) and transmits it to the TZ OTP client 2100.

The TZ OTP client 2100 generates a client random value (step 1040), generates a session key to be used for E2E encryption, authenticates and verifies the session key generated in the TZ OTP client 2100 A client Cryptogram is generated (steps 1050 and 1060). In this case, the concrete values of the session key and the client cryptogram are as follows. The session key encrypts the client random value, the server random value, and the hash value of the enterprise code with a fixed key. The Cryptogram encrypts the client random value, the server random value, Code, and session key.

Session Key = Encrypt Static Key (Client Random + Server Random + HASH (Company Code))

Cryptogram = HASH (Client Random + Server Random + Company Code + Session Key)

The TZ OTP client 2100 transmits the generated client random value and the client Cryptogram to the TZ OTP server 2400 for authentication and verification, and the TZ OTP server 2400 receiving the generated client random value and the client Cryptogram generates a session key to be used for E2E encryption (Step 1070). After verifying the client cryptogram (step 1080), a server Cryptogram is generated for authentication and verification of the session key generated by the server (step 1090).

The TZ OTP server 2400 transmits the generated Server Cryptogram value to the TZ OTP client 2100, and the TZ OTP client 2100 receives the Server Cryptogram value and verifies the Server Cryptogram in step 1110.

Next, the TZ OTP server 2400 generates a symmetric key required for OTP generation, transmits the encrypted transmission using the shared session key (step 1020), and transmits the symmetric key encrypted by the TZ OTP client By decrypting using the shared session key, the TZ OTP client and the server share a symmetric key (step 1130).

As described above, by using the E2E cipher system proposed in the present invention, it is possible to encrypt the chip value necessary for generating the TZ OTP with the shared key, and to transmit the key from the server to the trust zone securely. The E2E encryption scheme of the present invention can be applied to the trust zone technology of the present invention, thereby realizing an encryption technique with maximized security and safety.

Furthermore, the OTP (TZ OTP) technology based on the trust zone technology proposed by the present invention can be applied to the electronic money transaction means and the disposable passwords specified in Article 34 (Compliance with Electronic Financial Transactions) It is an epoch-making technology that meets the requirement "to separate and use the medium that serves as the transaction authentication means" and to integrate the OTIFI technology with the mobile device. Technologies combining existing OTPs with mobile terminals do not satisfy the above media separation regulations, and thus there is a problem in actual implementation (for example, a software application uses an OTIPI app installed in a general area) However, the present invention is not limited to the above-described embodiments, and the present invention is not limited thereto. There is no need to add or replace additional hardware to the mobile phone, thereby improving the convenience of the user while improving the spread and stability.

Further, in the E2E encryption method of the present invention, there is an effect of preventing forgery and falsification by storing a key necessary for generating an attribute in a trust zone where hacking is impossible. While existing software opitations have been difficult to cope with duplication and tampering threats of such malicious codes, the present invention can fully compensate for the weaknesses of the existing technology.

While the present invention has been described in detail in the foregoing for the purpose of illustration, it is to be understood that the components, their connections and relationships, and their functions are merely exemplary. In the present invention, each component may be implemented as a physically separated form or as an integrated form of one or more components as needed.

The present invention is not necessarily limited to these embodiments, as all the constituent elements constituting the embodiment of the present invention are described as being combined or operated in one operation. That is, within the scope of the present invention, all of the components may be selectively coupled to one or more of them.

Furthermore, the terms "comprises", "comprising", or "having" described above mean that a component can be implanted unless otherwise specifically stated, But should be construed as including other elements. All terms, including technical and scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs, unless otherwise defined. Commonly used terms, such as predefined terms, should be interpreted to be consistent with the contextual meanings of the related art, and are not to be construed as ideal or overly formal, unless expressly defined to the contrary.

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

10: Client terminal
20: Network
30: Payment server
40: verification server
50: Push system

Claims (26)

1. A transaction-based One Time Password (OTP)
Transmitting a transaction request to a payment server using a security application (Trusted Application) running on the client terminal;
Receiving transaction information in response to the transaction request; And
And generating a transaction interoperability using the security application as the input value of the transaction information,
An application processor (AP) of the client terminal is logically divided into a general area and a security area,
When the security application is executed, a security UI (Trusted User Interface) is displayed in the security area and displayed above the general UI,
The security UI acquires all privileges of the screen input / output at the time of execution, the security area acquires the data, the data transmission, the screen capture and the recording function can not be manipulated outside, and the security operating system monopolizes the CPU, And the operation is suspended and allowed to return to the normal environment only through the SW Back button provided in the security UI,
Wherein the secure area previously stores a static key allocated by the Trusted Server Manager (TSM) to the client terminal and the payment server,
The client terminal and the payment server generate a session key encrypted with the fixed key,
When the payment server encrypts and generates a symmetric key for generating the transaction interoperability attribute with the session key, and transmits the generated secret key to the client terminal, the client terminal receives the symmetric key encrypted using the session key, And decrypting the transaction key. The method according to claim 1,
Wherein the security application is operated by a security operating system (Trust OS) running independently of a general operating system running on the client terminal. The method according to claim 1,
Wherein the transaction information includes a bank identification code, an account number, and a transfer amount. The method according to claim 1,
Wherein the transaction information includes a purchase product name, a purchase amount, and a purchase location. The method according to claim 1,
Wherein the step of receiving the transaction information in response to the transaction request is received in the form of a push message through a push system linked with the payment server. The method according to claim 1,
Transmitting the transaction interoperability attribute to the payment server; And
Further comprising the step of receiving a result of the verification of the transmitted interoperability attribute. The method according to claim 1,
Wherein the transaction interworking attribute is generated in the second client terminal using a key update protocol or a re-issuance protocol. The method according to claim 1,
Wherein the security application is executed in a manner that is called or linked through a predefined function of a general application running in a general area. delete The method according to claim 1,
The session key is generated by encrypting a client random value generated at the client terminal, a value obtained by hashing a server random value and a company code generated at the payment server with the fixed key ,
The client terminal and the payment server perform a cryptogram verification step before the symmetric key transmission, and the cipher text is generated by hashing the client random value, the server random value, the enterprise code, and the session key Wherein the transaction is a transaction-related transaction. A transaction-related opportunistic-generation apparatus using a security application,
An interface for transmitting a transaction request to the payment server through the security application and receiving transaction information in response to the transaction request;
An opportunistic generation processor for generating a transaction interoperability based on the received transaction information as an input value; And
And a display unit for displaying a transaction progress status according to a user's input using the interface and displaying the received transaction information,
The interface receives the verification result after transmitting the transaction interoperability attribute generated by the attribute generation processor to the payment server and displays the verification result on the display unit,
An AP (Application Processor) of the transaction interoperability object generation apparatus is logically divided into a general area and a security area,
When the security application is executed, a security UI (Trusted User Interface) is displayed in which the security zone (Trust Zone) has authority over all operations of the transaction interoperability object generation apparatus,
The security UI acquires all privileges of the screen input / output at the time of execution, the security area acquires the data, the data transmission, the screen capture and the recording function can not be manipulated outside, and the security operating system monopolizes the CPU, And the operation is suspended and allowed to return to the normal environment only through the SW Back button provided in the security UI,
Wherein the secure area previously stores a static key allocated by the TSM (Trusted Server Manager) and the payment server,
Wherein the transaction interoperability authorizing device and the payment server generate a session key encrypted with the fixed key,
When the payment server encrypts and generates a secret key for generating the transaction-related offi cipher with the session key, and transmits the generated secret key to the transaction-associated api-based product generation device, And decrypting the symmetric key encrypted using the session key. The method of claim 11,
Wherein the security application is operated by a security operating system (Trust OS) that is independently operated from a general operating system running on the transaction interoperability object generating apparatus. The method of claim 11,
Wherein the transaction information includes a bank identification code, an account number, and a transfer amount. The method of claim 11,
Wherein the transaction information includes a purchase product name, a purchase amount, and a purchase location. The method of claim 11,
Wherein the transaction information is received in the form of a push message through a push system interlocked with the payment server. The method of claim 11,
Wherein the security application is executed in a manner of calling or linking through a predefined function of a general application running in a general area. delete The method of claim 11,
The session key may include a client random value generated in the transaction interoperability apparatus, a server random value generated in the payment server, and a hashed value of a company code, Encrypted,
Wherein the transaction interoperability offiotype generation device and the payment server perform a cryptogram verification step before the transmission of the symmetric key, and the cipher text is a hash value obtained by hashing the client random value, the server random value, the enterprise code, Value of the transaction-related attribute. As a system using transaction-oriented opportunistic,
A client terminal for transmitting a transaction request using a security application, receiving transaction information in response to the transaction request, and generating a transaction interoperability including the transaction information as an input value;
A payment server receiving the transaction request and transmitting a transaction interlock request;
A verification server for receiving the transaction interworking request and delivering the request to the push server; And
And a push server for receiving the transaction interlock request from the verification server and transmitting the transaction information corresponding to the transaction interlock request to the client terminal,
An application processor (AP) of the client terminal is logically divided into a general area and a security area,
When the security application is executed, a security UI (Trusted User Interface) is displayed in which the security zone (Trust Zone) has authority over all operations of the client terminal and is displayed above the general UI,
The security UI acquires all privileges of the screen input / output at the time of execution, the security area acquires the data, the data transmission, the screen capture and the recording function can not be manipulated outside, and the security operating system monopolizes the CPU, And the operation is suspended and allowed to return to the normal environment only through the SW Back button provided in the security UI,
Wherein the secure area previously stores a static key allocated by the Trusted Server Manager (TSM) to the client terminal and the payment server,
The client terminal and the payment server generate a session key encrypted with the fixed key,
When the payment server encrypts and generates a symmetric key for generating the transaction interoperability attribute with the session key, and transmits the generated secret key to the client terminal, the client terminal receives the symmetric key encrypted using the session key, And decrypting the key. The method of claim 19,
The client terminal transmits the generated transaction interoperability to the payment server,
Wherein the payment server delivers the verification result of the transaction interworking entity to the client terminal through the verification server. The method of claim 19,
Wherein the security application is operated by a security operating system (OS) running independently of a general operating system running on the client terminal. The method of claim 19,
Wherein the transaction information includes a bank identification code, an account number, and a transfer amount. The method of claim 19,
Wherein the transaction information includes a purchase product name, a purchase amount, and a purchase place. The method of claim 19,
Wherein the security application is executed in a way that is called or linked through a predefined function of a general application running in a general area. delete The method of claim 19,
The session key is generated by encrypting a client random value generated at the client terminal, a value obtained by hashing a server random value and a company code generated at the payment server with the fixed key ,
The client terminal and the payment server perform a cryptogram verification step before the symmetric key transmission, and the cipher text is generated by hashing the client random value, the server random value, the enterprise code, and the session key And a transaction-related-attribute-creation-system.

Images