Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; 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/42—Confirmation, e.g. check or permission by the legal debtor of payment
  • G06Q20/425—Confirmation, e.g. check or permission by the legal debtor of payment using two different networks, one for transaction and one for security confirmation
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; 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/4014—Identity check for transactions
  • G06Q20/40145—Biometric identity checks
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; 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/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; 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/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
  • G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
  • G06Q20/3674—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes involving authentication
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; 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
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; 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/382—Payment protocols; Details thereof insuring higher security of transaction
  • G06Q20/3823—Payment protocols; Details thereof insuring higher security of transaction combining multiple encryption tools for a transaction
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; 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/382—Payment protocols; Details thereof insuring higher security of transaction
  • G06Q20/3825—Use of electronic signatures
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; 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/385—Payment protocols; Details thereof using an alias or single-use codes
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; 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
• • 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/321—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 a third party or a trusted authority
  • H04L9/3213—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 a third party or a trusted authority using tickets or tokens, e.g. Kerberos
• • 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/3215—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 a plurality of channels
• • 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/3247—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 digital signatures
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
  • H04L2463/082—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying multi-factor authentication

Definitions

• the present system and method pertain to electronic transactions and more particularly to a secure method of authorization an electronic transaction through a multi-factor verification process.
• the current method to perform electronic transactions normally utilize hardware tokens, such as chip or magnetic stripe cards to identify the account of a party involved in the transaction. It may also be used for security purposes as "something-you-have" for their first factor authentication method.
• Online purchase secured by 3-D secure implementation (Verified by Visa, MasterCard SecureCode, American Express SafeKey, etc) include password or one-time codes which are entered into the application being displayed on a browser running on the same device. Online wire transfers or banking can use a one-time password provided to an external device, however that password must then be directly entered into the application being displayed on the same browser running on the same device.
• the present system contemplates a secure method of authorizing a transaction by having a unique identifier routed through the transaction processing system triggering autonomous independent channel (out-of-band) multi-factor multi-user identity verification ( s ) .
• the transaction data or its direct derivative will be injected into the out-of-band communication channel with the unique identifier.
• the transaction authorization may consist of one or more sub- authorizations (multi-user) in order for the full transaction authorization to be completed. Each sub-authorization requires the designated user to successfully complete a multi-factor authentication; where the user may or may not be a transaction originator.
• the multi-factor authentication may be provided through specialized combinations of including, but not limited to: codes, biometrics, and/or digital signatures.
• an account owner i.e. the rightful owner of the credentials associated with a physical token
• the corresponding identity verification response may be either: a logical sum of individual responses OR a response from an individual selected from the collective based on the policy of a verification process owner.
• the policy of the verification process owner may be determined based on the transaction data details.
• the out-of-band channel may be defined as either a completely separate device using a completely separate communications channel or it can be the same physical device using the same communications channel but by a completely independent application and associated backend service.
• This invention allows the system performing the transaction to not have to participate in the additional transaction authorization mechanism that has been triggered, thus greatly simplifying deployment of the multi-factor authentication solution.
• the invention allows for the same type of multi-factor multi-user verification ( s ) to be performed in both card present (when the person performing the transaction is physically at the transaction location) and card not present (when the person is performing a transaction on-line) transactions.
• a method for authorizing a transaction based on a parallel autonomous multi-factor authentication utilizes a transaction processing system.
• the transaction processing system operates initially by obtaining a physical token to originate a transaction by a transactor and then transmitting a plurality of credentials contained within the physical token to a transaction platform.
• the transaction platform communicates the credentials to a transaction process owner to verify the account owner to determine whether to authorize the transaction.
• a verification process owner is automatically activated by the credentials associated with the physical token.
• the transaction processing system conducts a parallel authentication of an account owner by the transaction process owner and the verification process owner.
• the transaction platform Upon receiving responses from the transaction process owner and the verification process owner as to the verification and authorization of the transaction, the transaction platform will combine their responses. Finally, the combined response, if containing authorizations from the verification process owner and the transaction process owner, will authorize the transaction by a transactor.
• the parallel autonomous multi-factor authentication includes transmitting an identity verification request to the account owner by the verification process owner.
• the account owner in response to the identity verification request provides a plurality of identity verification data by the account owner to help verify the account owner by the verification process owner.
• FIG. 1 illustrates a block diagram of an exemplary distributed computer system and networked environment for implementation of instant system and method.
• FIG. 2 illustrates a block diagram of the communication between the components in the system.
• FIG. 3 illustrates a flow diagram of the data analysis performed by the system.
• FIG. 4 illustrates a block diagram of one embodiment where a transaction platform delivers transaction details data to a verification process owner.
• FIG. 5 illustrates a block diagram of one embodiment wherein the verification process owner combines the transaction details and identity verification data of an account owner.
• FIG. 6 illustrates one embodiment of an exemplary computing system, wherein the systems and methods disclosed herein may be implemented using one or more computer systems.
• FIG. 1 illustrates a block diagram of one embodiment of a transaction processing system 10 for verifying an electronic transaction.
• a transactor 2 originates a transaction utilizing a physical token 4 obtained from an account owner 6 of the physical token 4.
• the physical token 4 is a device or card that contains credentials used in the processing of the transaction, wherein the credentials from the physical token 4 are linked to the account holder 6.
• the credentials of the physical token 4 are received by the transactor 2, the credentials are sent to a transaction platform 30.
• the transaction platform 30 is the platform that the transaction is being conducted through (i.e.
• a credit card processing company wherein the transaction platform 30 is in data communication with a transaction process owner 8 who manages the transaction requests and responds based on its pre-defined business rules.
• a verification process owner 12 is automatically activated by the credentials associated with the physical token 4 utilized by the transactor 2.
• the verification process owner 12 is in data communication with the account owner 6 and to autonomously verify the identity of the account owner 6 to confirm that the account owner 6 and the transaction 2 authorize the transaction being processed. Once the transaction platform 30 has received information from the transaction process owner 8 and the verification process owner 12 the transaction platform 30 transmits a message back to the transactor 2 to either approve or deny the transaction.
• FIG. 2 illustrates a flow diagram of an embodiment of the data analysis performed by the transaction processing system 10.
• the transactor 2 obtains a physical token 4 that is utilized at a point of origin 50; the point of origin 50 is in electronic and data communication with the transaction platform 30.
• the point of origin 50 initiates the transaction in the transaction platform 30 with transaction data and the credentials associated with the physical token 4.
• the transaction platform 30 communicates the transaction details and the credentials provided by the physical token 4 to the verification process owner 10.
• the verification process owner 12 is automatically activated by the credentials associated with the physical token 4 sends an identity verification request to the account owner 6.
• the verification process owner initiates an autonomous identify verification request to the account owner 6 to verify that the account owner 6 is authorized the transaction initiated at step 100 by the transactor 2.
• the identity verification request is transmitted as a unique code to the account owner 6 associated with the credentials provided by the physical token 4.
• the identity verification request is sent to the account owner's 6 mobile device, however in other embodiments the request is sent to the account holder' s personal computer or an online accessible account associated with the account holder 6.
• the account owner 6 responds to the identity verification request transmitted by the verification process owner 12 by providing a plurality of personal codes, biometrics and/or digital signatures which are combined with the unique code that were transmitted to the account owner 6.
• the combined response by the account owner 6 to the verification process owner 12 verifies the identity of the account owner 6 and authorizes the transaction initiated by the transactor 2.
• the account holder 6 may also respond with a message that either authorizes or denies the transaction.
• the verification process owner 12 provides the transaction platform 30 with a response based on the response, or lack thereof, from the account holder 6.
• the transaction platform 30 communicates the transaction details and the provided credentials from the physical token 4 to the transaction process owner 8.
• the transaction process owner 8 processes the information received from the transaction platform 30 based on pre-determined business rules.
• the transaction process owner 8 responds to the transaction platform 30.
• the transaction process owner 8 response will either approve or deny the transaction based on pre-determined business rules.
• the transaction platform combines the responses from the verification process owner 12 and the transaction process owner 8 and sends the appropriate response to the point of origin 50.
• the appropriate response will only be an approval if the response from both the verification process owner 12 and the transaction process owner 8 is that the transaction is authorized. If the transaction is denied by either the verification process owner 12 or the transaction process owner 8 the response for the transaction platform 30 will be a denial.
• the point of origin 50 notifies the transactor 2 of whether the transaction is approved or denied.
• FIG. 3 illustrates a flow diagram of one embodiment for the authorization of a transaction by the transaction processing system 30.
• the credentials from a physical token 4 are obtained by a transactor 2 at a point of origin 50.
• the point of origin 50 initiates a transaction by transmitting the credentials from the physical token 4 and the transaction details to the transaction platform 30.
• the transaction platform 30 sends the credentials from the physical token 4 and the transaction details to the verification process owner 12.
• the verification process owner 12 identifies the account owner 6 associated with the credentials from the physical object 4 and asks the account owner 6 whether they approve of the transaction.
• the account owner 6 responds to the verification process owner 12 with an identification confirmation and either an approval or a denial of the transaction.
• the verification process owner 8 sends a verification signal to the transaction platform 30 with the approval, denial, or failed identification from the account owner 6.
• the transaction platform 30 sends the credentials from the physical token 4 and the transaction details to the transaction process owner 8.
• the transaction process owner 8 processes the transaction details based on pre-determined business rules to determine whether the transaction is approved or denied.
• the transaction process owner 8 sends a verification response to the transaction platform 30 either approving or denying the transaction based on pre-determined business rules.
• the transaction platform combines the verification responses from the transaction process owner 8 and the verification process owner 8. If both verification responses approve the transaction the combination will result in a transaction approval. If the combination of the verifications fails to collect approvals from both the transaction process owner 8 and the verification process owner 8, the combination will result in a denial.
• the transaction platform 30 sends the result of the combination to the point of origin 50.
• FIG. 4 illustrates an alternate embodiment of the communication between the account owner 6 and the verification process owner 12 to authorize an initiated transaction.
• the transaction Platform 30 delivers a set of transaction details data 300 or a subset thereof to the verification process owner 12. Following the delivery of the transaction details data 300, the verification process owner 12 subsequently transmits an identity verification request message 302, wherein the identity verification request message 302 also includes the transaction details data 300 or its subset, such that account owner 6 is able to inspect the transaction details data 300 before making a positive or negative authorization decision.
• the account owner 6 may respond to verification process owner 12 by providing a plurality of identity verification data 304 which includes, but is not limited to: a personal code, a biometric identifier or a derivative thereof.
• identity verification data 304 includes, but is not limited to: a personal code, a biometric identifier or a derivative thereof.
• the identify verification data is 304 is combined with the Transaction Details Data 300 subset, and the indicator of positive of negative Authorization decision by the account owner 6.
• This produces a combined response message 306 which contains the account owner 6 identity verification data 304 together with transaction details 304 and a digital signature 308 or signatures of the full message or certain parts of the message.
• This embodiment only makes the identity verification valid in the context of the specific transaction initiated and the transaction authorization is only valid if the identity of the account owner whose physical token was utilized to initiate the transaction is verified.
• This methodology effectively combines the data used for Authentication, the response providing Authorization and confirmation that Authorization is linked to a specific event (transaction) in one response message 306. The message itself when stored provides an Audit trail of the Authentication and Authorization.
• FIG. 5 illustrates an alternate embodiment wherein the identity verification data 304 or derivative thereof of the account owner 6 is only present within the digital signature 308 of the response message 306.
• the verification process owner 12 must combine a set of previously known transaction details 310 and previously known identity verification data of the account owner 6 or a part thereof to verify the digital signature 308 of the response message 306 without the need to obtain (receive) the body of the message from the account owner 6, as the verification process owner 12 may recreate the body of the response message 306 based on the verification process owner's 12 previous knowledge. This allows the account owner 6 and the verification process owner 12 to complete a combined Authentication/Authorization process using a derivative of the identity verification data 304.
• the advantages of this embodiment include that the identity verification data 304 remains secure even if the communication channel is compromised. Also, the amount of data messages and the size of the messages transmitted back to the verification process owner 12 is minimized making this embodiment suitable for real ⁇ time implementation even over data links with slow speed and high latency .
• FIG. 6 illustrates an exemplary embodiment of a computer system 500, wherein the systems and methods disclosed herein may be implemented using one or more computer systems.
• the computer system 500 can include one or more processors 502 which can control the operation of the computer system 500.
• the processor (s) 502 can include any type of microprocessor or central processing unit (CPU) , including programmable general-purpose or special-purpose microprocessors and/or any one of a variety of proprietary or commercially available single or multi-processor systems.
• the computer system 500 can also include one or more memories 504, which can provide temporary storage for code to be executed by the processor (s) 502 or for data acquired from one or more users, storage devices, and/or databases.
• the memory 504 can include read-only memory (ROM) , flash memory, one or more varieties of random access memory (RAM) (e.g., static RAM (SRAM), dynamic RAM (DRAM) , or synchronous DRAM (SDRAM) ) , and/or a combination of memory technologies.
• RAM random access memory
• the various elements of the computer system 500 can be coupled to a bus system.
• the bus system can be any one or more separate physical busses, communication lines/interfaces, and/or multi-drop or point-to-point connections, connected by appropriate bridges, adapters, and/or controllers.
• the computer system 500 can also include one or more network interface (s) 506, one or more input/output (10) interface (s) 508, and one or more storage device (s) 510.
• the network interface (s) 506 can enable the computer system 500 to communicate with remote devices (e.g., other computer systems) over a network, and can be, for example, remote desktop connection interfaces, Ethernet adapters, and/or other local area network (LAN) adapters.
• the 10 interface (s) 508 can include one or more interface components to connect the computer system 500 with other electronic equipment.
• the 10 interface (s) 508 can include high speed data ports, such as USB ports, 1394 ports, etc.
• the computer system 500 can be accessible to a human user, and thus the 10 interface (s) 508 can include displays, speakers, keyboards, pointing devices, and/or various other video, audio, or alphanumeric interfaces.
• the storage device (s) 510 can include any conventional medium for storing data in a non- volatile and/or non-transient manner.
• the storage device (s) 510 can thus hold data and/or instructions in a persistent state (i.e., the value is retained despite interruption of power to the computer system 500) .
• the storage device (s) 510 can include one or more hard disk drives, flash drives, USB drives, optical drives, various media cards, and/or any combination thereof and can be directly connected to the computer system 500 or remotely connected thereto, such as over a network.
• the elements illustrated in FIG . 6 can be some or all of the elements of a single physical machine. In addition, not all of the illustrated elements need to be located on or in the same physical or logical machine. Rather, the illustrated elements can be distributed in nature, e.g., using a server farm or cloud-based technology.
• Exemplary computer systems include conventional desktop computers, workstations, minicomputers, laptop computers, tablet computers, PDAs, mobile phones, and the like. Although an exemplary computer system is depicted and described herein, it will be appreciated that this is for sake of generality and convenience. In other embodiments, the computer system may differ in architecture and operation from that shown and described here.

Landscapes

• Engineering & Computer Science (AREA)
• Business, Economics & Management (AREA)
• Accounting & Taxation (AREA)
• Computer Security & Cryptography (AREA)
• Theoretical Computer Science (AREA)
• General Business, Economics & Management (AREA)
• General Physics & Mathematics (AREA)
• Physics & Mathematics (AREA)
• Strategic Management (AREA)
• Finance (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Microelectronics & Electronic Packaging (AREA)
• Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)
• Computer And Data Communications (AREA)

Priority Applications (10)

Applications Claiming Priority (2)

Publications (1)

Family

ID=57983625

Family Applications (1)

Country Status (11)

Families Citing this family (8)

Citations (2)

Family Cites Families (15)

• 2016
  • 2016-08-10 US US15/751,584 patent/US11328299B2/en active Active
  • 2016-08-10 WO PCT/US2016/046332 patent/WO2017027580A1/en not_active Ceased
  • 2016-08-10 KR KR1020187006776A patent/KR102658597B1/ko active Active
  • 2016-08-10 MX MX2018001763A patent/MX2018001763A/es unknown
  • 2016-08-10 CN CN201680057390.3A patent/CN108352987A/zh active Pending
  • 2016-08-10 EP EP16835828.1A patent/EP3335371A4/en active Pending
  • 2016-08-10 JP JP2018527839A patent/JP2018533144A/ja active Pending
  • 2016-08-10 CA CA2995379A patent/CA2995379C/en active Active
  • 2016-08-10 BR BR112018002841A patent/BR112018002841A8/pt not_active Application Discontinuation
  • 2016-08-10 AU AU2016304860A patent/AU2016304860A1/en not_active Abandoned
• 2018
  • 2018-03-09 CO CONC2018/0002528A patent/CO2018002528A2/es unknown

Patent Citations (2)

Also Published As

Similar Documents

Legal Events