Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
  • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
  • G06Q20/327—Short range or proximity payments by means of M-devices
  • G06Q20/3278—RFID or NFC payments by means of M-devices
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
  • G06F21/52—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
  • G06F21/53—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow by executing in a restricted environment, e.g. sandbox or secure virtual machine
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
  • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
  • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
  • G06Q20/3226—Use of secure elements separate from M-devices
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
  • G06F21/44—Program or device authentication
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
  • G06F21/71—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information
  • G06F21/74—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information operating in dual or compartmented mode, i.e. at least one secure mode
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/08—Payment architectures
  • G06Q20/20—Point-of-sale [POS] network systems
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
  • G06Q20/308—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using the Internet of Things
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
  • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
  • G06Q20/321—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wearable devices
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
  • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
  • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
  • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
  • G06Q20/326—Payment applications installed on the mobile devices
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/38—Payment protocols; Details thereof
  • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/38—Payment protocols; Details thereof
  • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
  • G06Q20/401—Transaction verification
  • G06Q20/4016—Transaction verification involving fraud or risk level assessment in transaction processing
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/12—Applying verification of the received information
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
  • H04L9/3234—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
  • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
  • H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
  • H04W12/10—Integrity
  • H04W12/106—Packet or message integrity
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
  • H04W12/10—Integrity
  • H04W12/108—Source integrity
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
  • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
  • G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
  • G06K19/00—Record carriers for use with machines and with at least a part designed to carry digital markings
  • G06K19/06—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
  • G06K19/067—Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components
  • G06K19/07—Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components with integrated circuit chips
  • G06K19/0723—Record carriers with conductive marks, printed circuits or semiconductor circuit elements, e.g. credit or identity cards also with resonating or responding marks without active components with integrated circuit chips the record carrier comprising an arrangement for non-contact communication, e.g. wireless communication circuits on transponder cards, non-contact smart cards or RFIDs
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/38—Payment protocols; Details thereof
  • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
  • G06Q20/409—Device specific authentication in transaction processing
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q2220/00—Business processing using cryptography
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
  • H04L2209/56—Financial cryptography, e.g. electronic payment or e-cash
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
  • H04L2209/80—Wireless
  • H04L2209/805—Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees

Definitions

• the subject matter in general relates to digital payments. More particularly, but not exclusively, the subject matter relates to a COTS/loT device based secure financial payment acceptance method and a device thereof.
• the method comprises requesting a Trusted Application Manager (TAM) to verify the COTS/loT device identity and executing the application on a COTS/loT device.
• TAM installs a Trusted Application (TA) in a Trusted Execution Environment (TEE) of the COTS/loT Device.
• TEE Trusted Execution Environment
• the COTS/loT device includes a distributed ledger, and wherein the distributed ledger comprises information corresponding to at least one of COTS/loT device ownership, manufacture, and usage information.
• the information corresponding to the COTS/loT device in the distributed ledger is modified through the TEE.
• the application is executed in the operating system of the COTS/loT device.
• the TAM is a remote system which verifies the identity of the COTS/loT device and installs the TA in the TEE of the COTS/loT device.
• the resonance response is performed multiple times, and a distance of the tag from the COTS/loT device is calculated for each of the multiple resonance responses.
• the secure financial transaction is initiated in an event a decrease in distance is identified in subsequent resonance responses using the COTS/loT device.
• the resonance response to calculate the distance is implemented using one or more of light proximity, sound proximity or accelerator in order to determine the relative distance, for the payment processing to begin.
• the relative distance is configurable and is used for the purpose of fraud detection by ensuring the payment is initiated from a trusted/genuine payment card. The distance may be adjusted to accommodate changes to the guidelines pertaining to payment schemes at present and in future.
• a COTS/loT device for processing a secure financial transaction.
• the COTS/loT device is configured to request using the operating system part of the processor, a Trusted Application Manager (TAM) to verify device identity and install a Trusted Application (TA) in a Trusted Execution Environment (TEE) of the COTS/loT Device, Wherein the TEE is isolated from the operating system of the COTS/loT device and runs in parallel on a TEE part of the processor. Further, execute an application on a COTS/loT device.
• TAM Trusted Application Manager
• TEE Trusted Execution Environment
• the COTS/loT device further comprises a distributed ledger, and wherein the distributed ledger comprises information corresponding to at least one of COTS/loT device ownership, manufacture, and usage information.
• FIG. 1 is an exemplary simple architecture of a Trusted Execution Environment (TEE) system 100 used for secure financial transactions, in accordance with an embodiment of the invention
• FIG. 2 is an exemplary flow diagram 200 for deploying a Trusted
• TA in the TEE environment of the COTS/loT device, in accordance with an embodiment of the invention
• FIG. 3 illustrates an exemplary block diagram of a system 300 for secure financial transactions using a COTS/loT device with added security by incorporating a distributed ledger among the COTS/loT devices, in accordance with an embodiment of the invention
• Fig. 4A and 4B illustrates an exemplary resonance response and a tag discovery, distance or resonance response time calculation, respectively, in accordance with an embodiment of the invention.
• FIG. 5 is a flowchart of an exemplary method 500 for processing a secure financial transaction using a COTS/ loT device, in accordance with an embodiment of the invention.
• the terms“a” or“an” are used, as is common in patent documents, to include one or more than one.
• the term “or” is used to refer to a non-exclusive“or,” such that“A or B” includes“A but not B,”“B but not A,” and“A and B,” unless otherwise indicated.
• inventions disclose techniques for secure financial transaction acceptance using a Commercial of-the-shelf (COTS) device or Internet of Things (loT) device.
• COTS Commercial of-the-shelf
• LoT Internet of Things
• embodiments provide a COTS/loT device for processing a secure financial transaction.
• the COTS/loT device is configured to execute, using an operating system part of a processor, an application on a COTS/loT device. Further, request using the OS part of the processor, a Trusted Application Manager (TAM) to verify and install a Trusted Application (TA) in a Trusted Execution Environment (TEE) of the COTS/IOT
• TAM Trusted Application Manager
• the TEE of the COTS/loT device is isolated from the OS environment of the COTS/loT device and both run in parallel. Further, a resonance response is initiated when a tag is within a predetermined distance from the COTS/loT device and the tag information is received from the tag. Further a secure financial transaction is processed using the COTS/loT device based on the received tag information by accessing the TEE part of the processor.
• the COTS/loT device further comprises a distributed ledger, which comprises information corresponding to at least one of COTS/loT device ownership, manufacture, and usage information.
• FIG. 1 is an exemplary simple architecture of a Trusted Execution Environment (TEE) system 100 used for secure financial transactions, in accordance with an embodiment of the invention.
• TEE Trusted Execution Environment
• OS Operating System
• TEE Trusted Execution Environment
• OS Operating System
• TEE Trusted Execution Environment
• the sensitive elements of the critical applications may be executed in TEE in isolation from OS application environment. This facilitates extra level of security as the associated code and data may be protected from more vulnerable OS side of the COTS/loT device.
• TEE Trusted Application
• the execution of a Trusted Application (TA) in TEE may affect execution of applications in OS, however, execution in the OS cannot interfere with the execution in TEE.
• the application running on OS may request to execute code or verify tokens/keys through the TEE client API. Further, the TEE may execute respective TA or verify keys/tokens and provide the result to the TEE client API.
• the COTS/loT devices may include smart phones, laptops, computers, tablets, and smart watches, among other COTS/loT devices known in the art.
• FIG. 2 is an exemplary flow diagram 200 for deploying a Trusted Application (TA) in the TEE environment of the COTS/loT device, in accordance with an embodiment of the invention.
• the Trusted Application Manager is a remote server configured to establish communication with the TEE of the COTS/loT device.
• TAM may also authorize the installation of the Trusted Application in the TEE of the COTS/loT device.
• TAM may further be configured to push data or other confidential keys for a TA into the TEE.
• the application store may a platform on which a developer/company may host their applications for download.
• the users of the COTS/loT devices may download an application from the application store.
• the typical examples of application store may include Google Play and App Store by Apple, among others.
• the flow ‘a’ indicates a developer/company involved in developing an application which is hosted in the app store. It shall be understood that, for the sake of simplicity the TAM and developer/company have been grouped into one, however it is always possible that the developer/company may be different from TAM. Also, it shall be noted that the application is signed as a Trusted Application by TAM or Manufactures before moving to TAM.
• the flow‘b’ indicates creating a security domain after the application is downloaded and running for the first time in the COTS/loT device.
• the security domain is a place where keys can be stored, where the trusted application when at rest may be encrypted to keep safe.
• the application requests the TAM to approve the installation of the TA in the TEE.
• the TAM at flow‘d’ may perform several checks such as verifying the identity of the COTS/loT device, verifying whether it’s a trust worthy end point, and keep a track of the number of trusted applications deployed, among others, and upon positive verification issue a token/key to authorise the installation of TA in the TEE of the COTS/loT device.
• the TA is installed in the TEE of the COTS/loT device and is safely stored in TEE. Additionally, the TAM may also share some personalisation data to the application.
• the identifier T indicates the positively verified and installed TA loaded into the TEE of the COTS/loT device.
• FIG. 3 illustrates an exemplary block diagram of a system 300 for secure financial transactions using a COTS/loT device with added security by incorporating a distributed ledger among the COTS/loT devices, in accordance with an embodiment of the invention.
• the system 300 includes an COTS/loT device 1.
• the COTS/loT device 1 includes an application for processing a secure payment by accessing a trusted application (TA) installed in the TEE.
• the TEE is isolated from the operating system of the COTS/loT device and runs in parallel on a TEE part of the processor.
• a tag as illustrated in the figure is bought close to the COTS/loT device a resonance response is initiated.
• the tag may include, but not limited to, for example a credit card, debit card, smart watch, and a smart ring, among other devices capable of storing information pertaining to payment credentials.
• the resonance response may be initiated only the tag is within a predetermined distance from the COTS/ loT device.
• the TAG may share the information corresponding to the tag with the COTS/loT device for processing a payment.
• Fig. 4A and 4B illustrates an exemplary resonance response and a tag discovery, distance or resonance response time calculation, respectively, in accordance with an embodiment of the invention.
• the TAG is within the range of the actual signal strength‘m’ it may be discoverable by the COTS/loT device.
• the information for the tag may not be accepted until the tag is within the distance of ‘n’ form the COTS/loT device.
• the distance of the tag is continuously monitored upon its discovery.
• the tag information may be received by the COTS/loT device.
• the financial transaction may be initiated thereafter.
• different techniques may be adapted to implement a resonance response for example, but not limited to, using one or more of light proximity, sound proximity and relative distance, among other techniques known in the art.
• the plurality of COTS/loT devices may share a distributed ledger among themselves.
• This may be implemented using state-of-the-art distributed ledger technologies such as, but not limited to, Blockchain and Hash graph, among other technologies.
• the distributed ledger may include information corresponding to the unique identification number of the COTS/loT device, ownership of the COTS/loT device, usage information of the COTS/loT device, and manufacture information of the COTS/loT device, among other information.
• the information corresponding to accessing the distributed ledger such as the private key and other cryptos may also be stored in the TEE, through an update via TAM to the TA. This enables tracking the ownership details of the device. Further crowd leasing may also be facilitated i.e. allowing ownership of the devices via “crowd leasing” approach and genuinely identifying individual of the lease. The duration of ownership may also be recorded, and this enables distribution of return of the leasing if desired.
• the usage/consumption information may include, but not limited to, estimated lifespan of the device, automation of maintenance, and charging by usage, among others.
• FIG. 5 is a flowchart of an exemplary method 500 for processing a secure financial transaction using a COTS/ loT device, in accordance with an embodiment of the invention.
• the method 500 may be implemented in a COTS/loT device.
• the COT/loT device is embedded with a unique key during the manufacturing stage.
• a developer application may be signed by a TAM so that the TA can be installed in the TEE of COTS/loT.
• a request to install a trusted application in the TEE of the COTs/loT device may be send to the TAM.
• the application may be executed on the COTS/loT device at step 504.
• a resonance response may be initiated when a tag is discovered to be within a predetermined distance from the COTS/loT device.
• the information from the tag is used to process a secure financial transaction using the COTS/loT device by accessing the TEE.
• a distributed ledger such as blockchain or hash graph may be implemented to maintain a ledger in all the COTS/loT devices.
• the distributed ledger may comprise information corresponding to ownership, usage information, and manufacturer of the COT/loT device, among other details.

Landscapes

• Engineering & Computer Science (AREA)
• Business, Economics & Management (AREA)
• Computer Security & Cryptography (AREA)
• Theoretical Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Accounting & Taxation (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• General Business, Economics & Management (AREA)
• Strategic Management (AREA)
• Signal Processing (AREA)
• Computer Hardware Design (AREA)
• Computing Systems (AREA)
• General Engineering & Computer Science (AREA)
• Software Systems (AREA)
• Finance (AREA)
• Mathematical Physics (AREA)
• Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Priority Applications (6)

Applications Claiming Priority (2)

Publications (1)

Family

ID=68616131

Family Applications (1)

Country Status (9)

Cited By (2)

Families Citing this family (1)

Citations (5)

Family Cites Families (14)

• 2018
  • 2018-05-24 MY MYPI2018702015A patent/MY197067A/en unknown
• 2019
  • 2019-05-24 CN CN201980035082.4A patent/CN112166449A/zh active Pending
  • 2019-05-24 JP JP2020565801A patent/JP6926349B2/ja active Active
  • 2019-05-24 WO PCT/MY2019/050032 patent/WO2019226042A1/en active Application Filing
  • 2019-05-24 GB GB2020524.1A patent/GB2587746B/en active Active
  • 2019-05-24 US US17/058,061 patent/US20210209579A1/en active Pending
  • 2019-05-24 AU AU2019272261A patent/AU2019272261A1/en not_active Abandoned
  • 2019-05-24 TW TW108118038A patent/TW202004635A/zh unknown
  • 2019-05-24 SG SG11202011225YA patent/SG11202011225YA/en unknown

Patent Citations (5)

Also Published As

Similar Documents

Legal Events