EP3014540A1 - Procédé de transaction électronique et système informatique - Google Patents

Procédé de transaction électronique et système informatique

Info

Publication number
EP3014540A1
EP3014540A1 EP14726573.0A EP14726573A EP3014540A1 EP 3014540 A1 EP3014540 A1 EP 3014540A1 EP 14726573 A EP14726573 A EP 14726573A EP 3014540 A1 EP3014540 A1 EP 3014540A1
Authority
EP
European Patent Office
Prior art keywords
computer system
user
token
transaction
request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP14726573.0A
Other languages
German (de)
English (en)
Inventor
Frank Dietrich
Manfred Paeschke
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bundesdruckerei GmbH
Original Assignee
Bundesdruckerei GmbH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bundesdruckerei GmbH filed Critical Bundesdruckerei GmbH
Publication of EP3014540A1 publication Critical patent/EP3014540A1/fr
Pending legal-status Critical Current

Links

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/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
    • 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/3274—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
    • 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/4014—Identity check for transactions
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/20—Individual registration on entry or exit involving the use of a pass
    • G07C9/22—Individual registration on entry or exit involving the use of a pass in combination with an identity check of the pass holder
    • G07C9/25—Individual registration on entry or exit involving the use of a pass in combination with an identity check of the pass holder using biometric data, e.g. fingerprints, iris scans or voice recognition
    • G07C9/257—Individual registration on entry or exit involving the use of a pass in combination with an identity check of the pass holder using biometric data, e.g. fingerprints, iris scans or voice recognition electronically

Definitions

  • the invention relates to an electronic transaction method and a computer system.
  • the object of the invention is to provide an improved electronic transaction method and a corresponding computer system.
  • a “transaction” here means a financial transaction, such as the payment of a payment by making a transfer, direct debit or credit card debit, an ordering process for the ordering and delivery of a physical good or data, and other logistic, trade and / or or financial transactions and / or a database transaction, for example, for storing a value, such as a consumption value, a credit, or a payment amount.
  • Terminal is here understood to mean a device which has a display, ie a screen, for displaying a has optical pattern. The terminal can only capture information and output via the display, or it can have a user interface for inputting a selection of a user.
  • the terminal may be designed as a cash machine or vending machine.
  • the user may enter a request into the terminal, such as to withdraw cash, charge a cash card, or purchase a particular product, such as a drink.
  • the automaton displays an optically detectable pattern, such as a QR code, on its screen in response to this user request, the pattern containing information to initiate the transaction execution. This may be the desired cash amount or the purchase price of the product.
  • the terminal is designed as a telecommunication device, as a so-called smart meter, for the billing of, for example, electricity or gas consumption, taximeters or smartphones with a billing function.
  • a “pattern” is here understood to mean a static optical pattern which is output on the display of the terminal and into which information is coded, for example a barcode, in particular a one-dimensional, two-dimensional, high-capacity color barcode, MaxiCode, QR code or DataMatrix code, or a temporal order of several patterns, whereby the patterns and their chronological order encode information, as is the case, for example, with a flicker code
  • the "flicker code” is in itself for the so-called chipTAN-comfort or smart-code TAN-optic online banking procedures of the savings banks and hidingbanks known.
  • a “session” here means a temporary communication connection, that is to say a so-called communication session, which according to the OSI layer model can refer to the transport layer ("transport layer”) or the application layer (“application layer”) a session is an http session or an https session, whereby in the latter case the transport layer is protected by symmetric encryption.
  • transport layer transport layer
  • application layer application layer
  • ID token here is understood in particular to mean a portable electronic device which has at least one data memory for storing the at least one attribute and a communication interface for reading out the attribute of the at least one attribute in order to prevent the attribute stored in the memory area from being altered in an unauthorized manner or read out without the authorization required for this purpose, in particular the ID token may be a USB stick or a document, in particular a
  • a "document” means paper-based and / or plastic-based documents, in particular electronic sovereign documents, such as, for example, electronic identification documents, in particular passports, personal ID cards, visas and driver's licenses, vehicle registration documents, vehicle letters, company ID cards, health cards or other ID documents as well as chip cards, means of payment, in particular banknotes, bank cards and credit cards, waybills or other credentials, in which a data memory for storing the at least one attribute is integrated.
  • the ID token can be a hardware token or a soft token if it is cryptographically bound to a hardware token, that is to say to a so-called secure element, for example.
  • a J D provider computer system 1 is here understood to mean a computer system which is designed to read out at least one attribute from the ID token of a user.
  • the ID provider computer system is operated in a so-called trust center to provide the highest possible level of security.
  • a “service computer system” is understood here to mean a computer system which has a network interface for connection to the network, so that an internet browser or another application program can be used to access web pages stored or generated by the service computer system the service computer system is an Internet server for the provision of an e-commerce or e-government application, in particular an online shop or a government server.
  • a "user computer system” is understood here to mean a computer system to which the user has access, for example a personal computer (PC), a tablet PC or a mobile device, in particular a smartphone, with a conventional internet browser such as Microsoft Inter- net Explorer, Safari, Google Chrome, Firefox or any other application to access the service computer system.
  • the user computer system has an interface for connection to the network, wherein the network may be a private or public network, in particular the Internet.
  • the request of the service computer system is a SAML request and the response of the ID provider computer system to this is a SAML response (see Security Assurance Markup Language (SAML) V2. 0 Technical Overview, OASIS, Committee Draft 02, March 25, 2008).
  • SAML Security Assurance Markup Language
  • the ID provider computer system has a certificate in which the read rights for performing the read access are specified.
  • a “certificate” is understood here as a digital certificate, which is also referred to as a public-key certificate, which is a structured data that serves to identify a public key of an asymmetric cryptosystem of an identity, such as
  • the certificate may conform to the X.509 standard or another standard, and preferably, the certificate is a Card Verifiable Certificate (CVC)
  • CVC Card Verifiable Certificate
  • the attribute or attributes of the user stored in the protected storage area of the ID token entitle the ID provider computer system to perform the read access, which attributes may be personal attributes of the user, such as his name , Place of residence and age. These attributes can be used in their combination as user recognition be used to access the payment information of the registered user.
  • a pseudonym of the user which is stored at least temporarily by the ID token, can also be used as the user identifier.
  • Embodiments of the invention are particularly advantageous since a computer-implemented payment method that is suitable universally and also for e-commerce and e-government applications is created, which is at the same time flexible, easy to handle and secure. This is made possible, in particular, by the fact that the payment method is based on an ID token, whereby the prerequisite for the performance of a payment transaction is both the authentication of the user to the ID token and the authentication of the ID provider computer system to the ID token is.
  • the terminal is a device, for example for the payment of cash, for charging a cash card for the sale of a product, such as a ticket, a ticket or a food or beverage.
  • the terminal may be a cash dispenser.
  • the user enters a desired payout amount via a user interface of the cash machine.
  • This payout amount is then displayed on the screen as an optically readable pattern by the cash dispenser, and this pattern is detected by the user using an optical sensor, such as the camera of the user computer system, which may be a smartphone.
  • the pattern displayed on the screen may further include a logical address of the service computer system, such as a URL of the service computer system.
  • further information may be included in the pattern, such as account information of the operator of the ATM.
  • the user computer system decodes the pattern acquired from the screen of the terminal using the optical sensor and then generates a transaction request indicating the amount of payout and, if applicable, the other transaction data included in the pattern.
  • This transaction request is then transmitted from the user computer system to the service computer system via the network.
  • the service computer system then generates a request which contains an attribute specification, that is to say an indication of at least one attribute to be read out of the ID token, which is required for the execution of the transaction and / or which has to fulfill a predetermined checking criterion so that the Transaction can be performed.
  • the attribute may be a user's account account stored in the ID token or a user's pseudonym which serves as the access key to pseudonymized account information of registered users for the service computer system.
  • the attribute may be an age indication to verify that the user has the business skills required to complete the transaction.
  • the service computer system then sends the request to the 1D provider computer system.
  • the at least one attribute is then read from the ID token by the I D provider computer system via the Network with end-to-end encryption.
  • the I D provider computer system then generates a response that includes the at least one attribute read from the ID token.
  • the attributes and / or the response are signed by the 1D provider computer system and sent to the service computer system.
  • the service computer system then uses the attributes to perform the transaction, that is, for example, debiting the user's account with the payout amount, and / or verifying that a given criterion, eg, business ability, is met.
  • the service computer system After this debit of the account has occurred, the service computer system generates an acknowledgment signal, which is transmitted at the bank terminal.
  • the terminal that is to say the ATM here, is connected to the network so that the acknowledgment signal is transmitted from the service computer system via the network to the terminal.
  • Vorzugswei- the signing signal is signed by the service computer system to avoid tampering. Due to the receipt of a valid confirmation signal then takes place the issue of cash in the amount of the desired payout amount or alternatively the charging of a cash card of the user.
  • the terminal is designed as a vending machine.
  • a user interface of the vending machine allows the user to select a desired product.
  • the vending machine will then display on its display an optical pattern in which the purchase price of the selected by the user! product, as well as the account information of the account to which payment of this purchase price must be made.
  • the optical pattern includes the indication of a logical address, in particular a URL, of the service computer system.
  • the user captures this optical pattern with an optical sensor of his user computer system, for example using the camera of his smartphone.
  • the optical pattern is then decoded and a transaction request is generated that includes the payee's purchase price and account information. This transaction request is received from the user computer system
  • the service computer system then generates a request with the attribute specification of that required to deliver the product selected by the user
  • the service computer system receives a response from the 1D provider computer system that includes this age.
  • the service computer system carries out the transaction by, for example, transferring the purchase price from the user's account to the payee's account. Subsequently, the service Computer system from a confirmation signal from the vending machine, whereupon this then delivers the product previously selected by the user.
  • the terminal is designed as a consumption counter, in particular for detecting a consumption of electricity or gas.
  • an optical pattern is displayed on the display of the terminal, which includes the current meter reading and, for example, a counter number of the consumption meter and also the logical address of the service computer system.
  • the corresponding transaction request then contains this count as well as the counter number.
  • the attribute specification of the service computer system may specify, for example, personal information of the user and / or a pseudonym or an identifier of the user, such as the customer number. Due to receipt of the response from the ID provider computer system, the service computer system may determine which user has captured the optical pattern from the terminal.
  • the service computer system stores the count reported with the transaction request and the associated counter number in a database by means of a database Transaction. At a later time, a corresponding invoice can then be generated by the service computer system in order to settle the recorded consumption.
  • the service computer system generates an acknowledgment signal after the database transaction has been executed, sending this acknowledgment signal to the utility meter. The consumption meter can then be reset.
  • the terminal is a smartphone of a third party who wishes to sell the product to the user.
  • the smartphone has an app that starts the third party. In the app, the third party enters the purchase price and, for example, his bank account. This information as well the logical address of the service computer system are then output on the display of the smartphone as an optical pattern.
  • the corresponding transaction request then includes the purchase price and the account details of the third party.
  • the attribute specification in this case may, for example, relate to the personal information of the user by means of which the service computer system can access the previously registered account connection of the user.
  • the service computer system After receipt of the response, the service computer system then carries out the transaction, that is, the payment of the purchase price, using the account information of the third party and the user.
  • the service computer system then sends an acknowledgment signal to the third party's smartphone so that it is informed of the payment made and delivers the product to the user.
  • the terminal is designed as a taximeter.
  • the optical pattern includes a fare that bills a taxi driver for a taxi ride.
  • the taximeter Upon receipt of the confirmation signal from the service computer system confirming the execution of the corresponding payment, the taximeter outputs a corresponding receipt, that is, an acknowledgment.
  • the terminal has a network interface for communication over the network.
  • the acknowledgment signal may be transmitted from the Dtenst computer system over the network to the vending machine.
  • the acknowledgment signal is sent from the service computer system to the user computer system.
  • the user computer system may then display on a display of the user computer system an optical pattern in which this confirmation is encoded.
  • This optical pattern can then be detected by the terminal, which also has an optical sensor.
  • This embodiment has the advantage that the terminal does not need to be connected to the network, which has safety advantages.
  • the service computer system is connected to the terminal via a communication channel other than the network, such as an internal corporate network or a virtual private network via which the acknowledgment signal is transmitted from the service computer system to the terminal.
  • a first session is first established between the internet browser of the user computer system and the service computer system via the Internet, wherein the first session may be an http session or an https session.
  • the user can enter a transaction request in the Internet browser, for example, to initiate a payment process.
  • the user has previously ordered a product via the service computer system and would like to pay for this ordered product, for which purpose the user enters the corresponding transaction request in the internet browser, which is transmitted to the service computer system via the first session.
  • the service computer system then generates a request, ie a request for a request-response protocol.
  • the request can have a predefined or standardized structure.
  • the request may be text-based, have an XML, ASN.1 or binary structure or be configured as a SAML request.
  • the request for example the SAML request, contains an attribute specification which specifies the attributes to be read from the ID token for the execution of the transaction. These may be attributes that identify the user associated with the ID token and / or that provide payment information, such as an account or credit card information, and / or attributes that include the ID token itself such as the period of validity, the date of issue and / or the issuing organization or authority.
  • the request is transmitted from the service computer system via the user computer system to the ID provider computer system. Due to the receipt of the request by the user computer system, the further procedure for generating the response, including the authentication of the user and the ID provider computer system, is triggered.
  • the attribute specification may include the date of birth of the user if, for example, the age of majority of the user is to be verified by the service computer system as a prerequisite for the transaction to be performed.
  • the request also contains transaction data for specifying the transaction, that is, for example, a payment amount and account information, in particular the account connection of the service computer system on which the payment is to be made.
  • the request includes a Uniform Resource Locator (URL) of the ID provider computer system, which is to read the attributes from the ID token, and a URL of the service computer system for specifying a recipient for the response, which is based on the request from the ID provider computer system is to generate.
  • the service computer system generates an identifier for the request which uniquely identifies the request, e.g. a globally unique identifier (GUID). The request contains this identifier.
  • GUID globally unique identifier
  • the request is signed by the service computer system using a private key of a cryptographic key pair associated with the service computer system.
  • a web page is transmitted from the service computer system to the user computer system via the first session and displayed by the internet browser or the application program, in particular a so-called app. Together with the website, the request is transmitted, but it is not displayed.
  • the website has at least one input field for inputting additional information which is required for carrying out the transaction.
  • This additional information may be, for example, an account or credit card information of the user and / or authentication information to authenticate the user to the service computer system.
  • the authentication information may be a one-time password (OTP).
  • OTP one-time password
  • the additional information is encrypted using the public key of the service computer system by the user computer system, so that only the encrypted additional information is subsequently forwarded via a second session from the Internet browser or the application program to the ID provider computer system via the network.
  • This request also forwards the request via this second session.
  • the structure of the second session is carried out by calling the URL of the I D provider computer system, which is included in the request.
  • the second session is set up as a protected communication connection, namely with an encrypted transport layer, ie with Transport Layer Security (TLS), which is also referred to as Secure Sockets Layer (SSL), in particular as an https session.
  • TLS Transport Layer Security
  • SSL Secure Sockets Layer
  • the ID provider computer system generates an identifier for a still-to-be-established third session due to the receipt of the request over the second session, i. a so-called session ID.
  • the ID provider computer system stores the request and the additional information received along with the request for the second session with the session ID for the third session.
  • the ID provider computer system then sends a message about the second session, which includes a logical address of the ID provider computer system and, for example, the session ID of the third session. From this logical address, the Internet browser or the application program can later retrieve the response to the previously forwarded request.
  • the logical address may be a uniform resource locator (URL) through which the response is retrievable.
  • the third session is established on the application layer between a program of the user computer system and the I D provider computer system, via the secured transport layer of the second session.
  • the program may be a browser plug-in of the Internet browser or an application program other than the Internet browser.
  • the I D provider computer system transmits to the program the third session information needed to read the attribute (s) from the ID token.
  • This information includes at least one certificate of the ID provider computer system, which includes an indication of read rights of the ID provider computer system for reading one or more attributes.
  • the program of the user computer system checks whether the read rights specified in the certificate are sufficient to allow read access by the ID provider computer system to the attribute (s) to be read according to the attribute specification of the request. If the reading rights of the ID provider computer system are sufficient, the following further steps are performed: a) A local connection is established between the reader of the user computer system and the ID token. In the case of an ID token with a contact-type interface, for example a chip card interface, this can be done by inserting the ID token into the reader.
  • a contact-type interface for example a chip card interface
  • an ID token with a non-contact interface such as an RFID or an N FC interface
  • this can be done by placing the ID token on the reader.
  • Tokens with USB, BlueTooth or microSD cards as well as virtual SmartCards are also possible here.
  • the user authenticates himself to the ID token, for example by entering his Personal Identification Number (PIN) or by entering other information, such as the detection of a biometric metric feature of the user.
  • PIN Personal Identification Number
  • a session key is agreed.
  • the agreement of a session key can be made using a Diffie-Hellman protocol.
  • a fourth session is set up on the application layer, between a program of the ID token and the ID provider computer system, this fourth session running over the local connection and the third session, and an additional one on the application layer End-to-end encryption using the session key agreed in step b.
  • a mutual authentication of the ID token and the 1 D provider computer system takes place, for example by means of a challenge-response protocol.
  • the attribute or attributes according to the attribute specification, which the ID provider computer system has received with the request, are now read out of the ID token via the fourth session by the ID provider computer system. This requires the successful authentication of the user in step b and the successful mutual authentication of the ID token and the ID provider computer system in step d) and is encrypted over the fourth session, so that a maximum of security and trustworthiness in terms of given attributes is given.
  • the ID provider computer system then generates a response that includes the read out attributes and the identifier of the request and / or the additional information according to the request-response protocol to which the request is subject. In the case of a SAML request, therefore, a SAML response is generated accordingly.
  • the identifier of the request which is also contained in the response, the logical assignment of request and response, ie the so-called binding, is established here
  • the response is signed by the I D provider computer system and stored for retrieval by the logical address previously communicated to the user computer system via the message.
  • the user computer system then reads this response from the ID provider computer system using the logical address, such as the URL, and forwards the response to the service computer system through the first session.
  • this is assigned to the request and thus to the requested transaction, and then the transaction is executed by the service computer system, that is, for example, triggering a payment transaction and / or delivering an ordered product, if the content of the response permits.
  • the program of the user computer system is a browser plug-in of the Internet browser, wherein the Internet browser is a common browser program such as Microsoft Internet Explorer, Safari, Google Chrome or Firefox can.
  • the program of the user computer system may be an application program separate from the Internet browser.
  • the additional information entered by the user is payment information, such as, for example, an account connection of the user from which the payment amount specified in the request should be debited or withdrawn.
  • the so-called clearing that is the examination of the creditworthiness of the customer, as well as the initiation of the payment process can then be initiated by the I D provider computer system, which confirms the execution of the payment with the response to the service computer system. This has the advantage that the service computer system has no knowledge of the payment information of the user, that is, in particular his account connection must obtain.
  • the user may encrypt his payment information with the public key of the service computer system so that only the encrypted payment information of the user is transmitted to the ID provider computer system.
  • the I D provider computer system then forwards the encrypted payment information with the response to the service computer system, which decrypts the payment information and then performs the clearing and collects the payment amount from the user's account according to the payment information.
  • the computer system includes a terminal, such as an ATM or a vending machine.
  • a terminal such as an ATM or a vending machine.
  • the user may enter a request into the machine, such as for withdrawing cash or purchasing a particular product, such as a drink.
  • the vending machine displays an optically detectable pattern, such as a QR code, on its screen containing information to initiate the transaction, in response to this user request.
  • the terminal is used as a mobile telecommunication device, in particular as a so-called smart meter, for billing e.g. of electricity or gas consumption, taximeter or smartphone with a billing function.
  • the URL of the service computer system For example, on the smartphone of a seller, the URL of the service computer system, the payment amount and the payee in the form of a visually recorded pattern and recorded with the camera of the user computer system, which may also be configured as a smartphone, are detected. In this way, everyday payment transactions can be processed safely and conveniently.
  • FIG. 1 shows a block diagram of an embodiment of an ID token according to the invention
  • Fig. 2 shows an arrangement of an embodiment of an inventive
  • FIG. 1 shows an ID token 106, which may be, for example, an electronic identity card.
  • the protected memory area 120 of the ID token 106 is used to store a reference value needed for authentication of a user 102 against the! D token 106.
  • This reference value is, for example, an identifier, in particular a so-called personal identification number (PIN), or reference data for a biometric feature of the user 102, which can be used for the authentication of the user against the ID token 106.
  • PIN personal identification number
  • the protected area 122 is for storing a private key
  • the protected memory area 124 is for storing attributes, such as user 102, such as name, place of residence, date of birth, gender, and / or attributes including the ID token itself, such as the institution that created or issued the ID token, the validity period of the ID token, an identifier of the ID token, such as a passport number or a credit card number.
  • the electronic memory 118 may also have a memory area 126 for storing a certificate.
  • the certificate includes a public key associated with the private key stored in the protected storage area 122.
  • the certificate may have been created according to a public key infrastructure (PKI) standard, for example according to the X.509 standard.
  • PKI public key infrastructure
  • the certificate does not necessarily have to be stored in the electronic memory 118 of the ID token 106.
  • the certificate can also be stored in a public directory server.
  • the ID token 106 has a processor 128.
  • the processor 128 is for executing program instructions 130, 132, and 134.
  • the program instructions 130 are for user authentication, that is, for authenticating the user 102 to the ID token.
  • the user 102 inputs his PIN to his authentication in the ID token 106, for example via the user computer system 100.
  • Execution of the program instructions 130 then accesses the protected memory area 120 to store the entered PIN with the PIN to compare there stored reference value of the PIN. In the event that the entered PIN matches the reference value of the PIN, the user 102 is considered authenticated.
  • a biometric feature of the user 102 is captured.
  • the ID token 106 has a fingerprint sensor or a fingerprint sensor is connected to the user's computer system 100.
  • the biometric data acquired by the user 102 is compared to the biometric reference data stored in the protected memory area 120 by executing the program instructions 130 in this embodiment. If the biometric data acquired by the user 102 sufficiently matches the biometric reference data, the user 102 is considered authenticated.
  • the program instructions 134 are used to execute the steps of a cryptographic protocol concerning the ID token 106 for the purpose of authenticating an I D provider computer system 136 with respect to the ID token 106.
  • the cryptographic protocol can be a challenge-response protocol act based on a symmetric key or an asymmetric key pair.
  • the cryptographic protocol implements an Extended Access Control method as specified for machine-readable travel documents (MRTD) by the International Aviation Authority (ICAO).
  • MRTD machine-readable travel documents
  • ICAO International Aviation Authority
  • the 1D provider computer system 136 Upon successful completion of the cryptographic protocol, the 1D provider computer system 136 authenticates against the ID token, thereby verifying its readability to read the attributes stored in the protected storage area 124.
  • the authentication can also be mutually exclusive, ie the ID token 106 must then also authenticate itself to the ID provider computer system 136 according to the same or another cryptographic protocol.
  • the program instructions 132 are for end-to-end encryption of data transferred between the ID token 106 and an ID provider computer system 136 (see Fig. 2), or at least the data from the ID provider computer system 136 of protected memory area 124 read attributes.
  • a symmetric key may be used, which is agreed, for example, during the execution of the cryptographic protocol between the ID token 106 and the ID provider computer system 136.
  • the ID token 106 has an interface 108 for communicating with a corresponding interface 104 of a user computer system 00 (see FIG. 2).
  • the interface may be contactless or contact-based. In particular, it may be an RFID or an NFC communication interface.
  • the access to the protected memory area 124 for reading one or more of the attributes can only take place via the processor 128 of the ID token 06, since the protected memory area 124 as well as the other protected memory areas 120, 122 are not directly, for example via a bus system are connected to the interface 108, but only with the processor 128, that is, an access via the interface 08 directly to the protected memory area 124 is already excluded circuit technology. Only the processor 128 can that is read access to the protected memory area 124, then optionally output the read attributes via the interface 108.
  • FIG. 2 shows a user computer system 100 of the user 02.
  • the user computer system 100 may be a personal computer (PC) for a portable computer, such as a laptop, notebook or tablet computer, a mobile telecommunication device , especially a smartphone.
  • PC personal computer
  • portable computer such as a laptop, notebook or tablet computer
  • mobile telecommunication device especially a smartphone.
  • the user computer system has at least one processor 110 for executing an application program 1 12.
  • the application program 112 is configured to communicate via a network interface 114 of the user computer system 100 via a network 116.
  • the application program is an Internet browser or other specialized application program that can communicate over the network 116, in particular an HTML-capable application program.
  • the processor 1 10 is used to execute another program 1 3, which may be, for example, a plug-in for the application program 1 12, for example, a browser plug-in when the application program 12 is designed as an Internet browser , or a program separate from the application program.
  • another program 1 3 may be, for example, a plug-in for the application program 1 12, for example, a browser plug-in when the application program 12 is designed as an Internet browser , or a program separate from the application program.
  • the network can be a computer network, such as the Internet.
  • the network 16 may also include a mobile radio network.
  • the I D provider computer system 136 has a network interface 138 for communication over the network 116.
  • the ID provider computer system 136 further has a memory 140 with a protected memory area 141 in which a private key 142 of the I D provider And also the corresponding certificate 144.
  • This certificate can also be, for example, a certificate according to a PKI standard, such as X.509.
  • the ID provider computer system 136 further has at least one processor 145 for executing program instructions 146 and 148. By executing the program instructions 146, the steps of the cryptographic protocol concerning the ID provider computer system 136 are executed.
  • the cryptographic protocol is implemented by executing the program instructions 134 by the processor 128 of the ID token 106 and by executing the program instructions 146 by the processor 145 of the ID provider computer system 136.
  • the program instructions 148 are for implementing the end-to-end encryption on the I D provider computer system 136 side, for example, based on the symmetric key involved in executing the cryptographic protocol between the ID token 106 and the ID provider - Computer system 136 has been agreed.
  • any method known per se for agreeing the symmetric key for end-to-end encryption such as a Diffie-Hellman key exchange, may be used.
  • the ID provider computer system 136 is preferably located in a particularly protected environment, in particular in a so-called trust center, so that the ID provider computer system 36 in combination with the necessity of authentication of the user 102 against the ID token 06 forms the trust anchor for the authenticity of the attributes issued from the ID token 106.
  • a service computer system 150 may be configured to receive an order or order for a service or product, particularly an online service.
  • the user 102 may open an account online with a bank via the network 116, or may use other financial or banking services.
  • the service computer system 150 may also be configured as an on-line department store so that the user 102 may, for example, purchase a mobile phone or the like online.
  • the service computer system 150 may also be configured to provide digital content, such as for downloading music and / or video data.
  • the service computer system 150 has for this purpose a network interface 152 for connection to the network 1 16.
  • the service computer system 150 has at least one processor 154 for executing program instructions 156. By executing the program instructions 156, for example, dynamic HTML pages are generated, via which the user 102 can enter his order or his order, as well as transactions.
  • the service computer system 50 must review one or more attributes of the user 102 and / or its ID token 106 based on one or more predetermined criteria. Only if this check is passed will the order or order of the user 102 be accepted and / or executed. To carry out an electronic transaction, you can proceed as follows:
  • the user 102 starts the application program 1 12 of the user computer system, it being further assumed that this is an Internet browser without restriction of generality.
  • the user 102 enters a URL of the service computer system 150 in the Internet browser, so that then a first session 201 between the Internet browser 1 12 and the service computer system 150 is established via the network 1 16.
  • the user may then request via the first session 201 a service offered by the service computer system 50, such as ordering a product, requesting data for download, or requesting the execution of a financial transaction.
  • the Internet browser 1 2 sends a corresponding transaction request 158 to the service computer system 150, which signals this request.
  • the service computer system thus receives from the Internet browser via the first session a transaction request 158 of the user 02. Due to the receipt of the transaction request 158 via the first session 201, the service computer system 150 generates a request 166.
  • Request 166 includes (i) an attribute specification, the attribute to be read from the iD token for performing the transaction. These attributes may be personal information about the user 102 and / or data regarding the ID token 106 itself or a pseudonym of the user 102 available from the ID token 106.
  • the request further includes (ii) the transaction data specifying the transaction, such as a payment amount to be paid for the purchase of the ordered product or the performance of the ordered service to the service computer system 150 or a third party, and / or others Transaction data specifying the transaction to be performed.
  • the request furthermore contains (iii) an identifier 180 of the request, for example a GUID, which is required for the so-called binding of the request and a subsequently received response 74.
  • the service computer system 150 may include a GUI D generator.
  • the request also includes (iv) a URL of the I D provider computer system 136 and (v) a URL of the service computer system 150 itself.
  • the request is signed by the service computer system 150, namely by means of a private key of the service provider.
  • the request 166 may be a SAML request or another request of a request-response protocol.
  • the service computer system 150 sends a web page 160 to the user computer system 100 via the first session 201, the web page 160 having an input field 162 for inputting additional information by the user 102 for the transaction, and further Input element 164, which the user 102 can select by clicking, for example, when the web page 160 is rendered by the Internet browser 112 to allow the forwarding of the request 166.
  • the request 166 is also transmitted to the internet browser 112 via the first session 201. Due to the reception of the web page 160 and the request 166, the web page 160 is rendered by the internet browser 112 so that the user 102 can input the additional information into the input field 162.
  • the additional information is an account connection of the user 02, a credit card number of the user 102 or other supplementary transaction data and / or an authentication information for proving the authorization of the user 02 for carrying out the transaction, for which purpose the user 02, for example One-time password (OTP) in the input field 162 enters.
  • OTP One-time password
  • the additional information 168 entered by the user 102 is encrypted with the public key of the service computer system 150 by the user computer system 100 to obtain a corresponding ciphertext.
  • a second session 202 is established between the Internet browser 112 and the ID provider computer system 136 via the network 6, using the URL of the I D provider computer system 136, the user computer system 100 with the request 166 received.
  • the second session 202 is established with a secure transport layer, for example as an https session.
  • the request 166 and the additional information 168 or only the ciphertext of the additional information 168 obtained with the aid of the public key of the service computer system 150 are forwarded from the user computer system 100 to the ID provider computer system 136.
  • the ID provider computer system 136 Due to the receipt of the request 166 by the ID provider computer system 136, the latter generates a session ID for a still to be established third session 203 by executing its program instructions 170.
  • the request 166 and the additional information 168 are stored in the memory 140 of the iD provider computer.
  • Computer system 136 stored.
  • the ID provider computer system 136 then generates a message 172 that includes the Session ID for the construction of the third session 203 and a logical address.
  • the response 174 to be generated by the ID provider computer system 136 on the basis of the request 166 can be retrieved; in particular, the logical address can be embodied as a URL.
  • the message 172 is sent via the second session 202 from the ID provider computer system 136 to the Internet browser 112.
  • the third session 203 is established between the program 113 of the user computer system 100 and the ID provider computer system 136 via the secure transport layer of the second session 202.
  • program 113 is a browser plug-in of Internet browser 112.
  • program 113 may be another application program. It is also possible to implement the functionalities of the Internet browser 112 and those of the program 1 3 in a program.
  • At least the certificate 144 is then transmitted to the program 113 via the third session 203.
  • the program 113 then checks whether the read rights specified in the certificate 144 are sufficient to allow read access by the ID provider computer system 36 to the attribute (s) to be read according to the attribute specification included in the request 166. Only if these read rights are sufficient, the following steps are performed: a) A local connection 176 is established between the interfaces 104 and 108. For example, on the screen of the user computer system 100, a request for the user 102 to insert the ID token 106 into a reading device of the user computer system 100, which has the cut parts 104, or appears for placing the ID token 106 on a contactless interface 104.
  • the user 02 then authenticates himself to the ID token, for example by entering his PIN in the user computer system 100 or its reader.
  • the authentication of the user can take place with the aid of a cryptographic protocol, for example by means of a challenge-response protocol or based on a Diffie-Helman key exchange, wherein a session key is agreed as part of the authentication of the user.
  • a fourth session 204 is established between the ID token 106 and the I D provider computer system 136 via the local connection 176 and the third session 203.
  • the fourth session 204 is executed with a End-to-end encryption using the session key, which has been agreed in the authentication of the user in step b) protected.
  • the fourth session is then used to mutually authenticate the ID token 106 and the ID provider computer system 136 with the aid of the respective private key, that is to say the private key of the ID token 106 stored in the protected memory area 122 and the private one Key 142 of the ID provider computer system 136.
  • the certificates of the ID token 106 may be exchanged from the storage area 126 (see FIG. 1) as well as the certificate 144 of the ID provider computer system 136 over the fourth session.
  • the I D provider computer system 136 Given the successful authentication of the user to the ID token and the successful mutual authentication of the ID token 106 and the ID provider computer system 136, the I D provider computer system 136 then reads the attribute or attributes according to the attribute specification the ID Token 106, wherein the attributes are protected by the end-to-end encryption in the transmission of the ID token 106 to the I D provider computer system 136. For this purpose, the I D provider computer system sends a read command via the fourth session 204 to the ID token 106 via the fourth session.
  • the read command 182 contains the attribute specification, that is to say the selection of those attributes which originate from the protected memory area 124 of the ID Tokens 106 should be read.
  • the response 174 is then generated on the request 166 by the I D provider computer system 136.
  • the response 178 includes the attributes previously issued via the fourth session 240 from the ID token 106, the additional information 168 or, depending on the embodiment, not the additional information 168, but only the ciphertext of the additional information 168, and the identifier 180 indicating the service Computer system 150 has initially assigned to the request 166.
  • the response 174 is signed by the ID provider computer system 136 using the private key 142 and then stored in the memory 140 so that the request 166 is retrievable from the logical address.
  • the user computer system 100 such as, for example, its Internet browser 112, then reads the response 174 from the memory 140, for example via the second session 202, with the aid of the logical address.
  • the response 174 is then forwarded from the user computer system 100, for example from the Internet browser 12, via the first session 201 to the service computer system 150.
  • the user 102 is requested by the Internet browser 112 to enter a confirmation before the response 174 is forwarded to the service computer system.
  • the content of the response 174 is displayed in whole or in part by the Internet browser, in particular the information read from the ID token. tribute and / or additional information 168 to allow the user 102 to verify the accuracy of this data before continuing to the service computer system 150 to complete the transaction.
  • the service computer system 150 allocates the received response 174 to the request 166 based on the matching identifiers 180 of the request 166 and the response 174.
  • the service computer system 150 then checks the signature of the response 166 and reads out the required attribute (s) from the response 174.
  • the attributes are then used to check whether the requested transaction can be performed by comparing the attribute (s) to one or more predetermined criteria. These criteria may be, for example, the age or credit of user 102.
  • the attribute may also be a pseudonym of the user 102, by means of which the service computer system 150 then reads out an attribute of the user 102 stored in a database of the service computer system 150, such as a delivery address.
  • the test criterion here is whether a user is registered with the pseudonym included in the response 174 on the part of the service computer system 150.
  • the transaction is performed based on the transaction data and the additional information 168.
  • the program 113 is a browser plug-in which is registered in a registry of an operating system of the user computer system with a plug-in identifier, wherein the operating system is, for example, a Windows operating system, Android or iOS can be.
  • the message 172 from the ID provider computer system to the Internet browser 112 includes this plug-in identifier 184, so that the plug-in 113 is started due to the receipt of the message.
  • the program 113 is a separate application program from the Internet browser 112, such as a so-called citizen app or ID card app.
  • This application program 113 is started by the Internet browser 112 by calling a local URL, the local URL including a fixed port number according to the TCP protocol.
  • This local URL is transmitted together with the web page 160 from the service computer system 150 to the user computer system 100 via the first session 201 in order to start the application program 113 using the local URL by the internet browser 112. ken.
  • the service computer system 150 decrypts the ciphertext using the private key of the service computer system 150 to then perform the requested transaction using the additional information 168. This may be, for example, the execution of a financial transaction, such as the execution of a transfer in the amount of the payment amount, which is specified in the additional information 168.
  • the implementation of the payment by the I D provider computer system 136 is triggered. This can be done so that the l D provider computer system 136 receives the requisite transaction data about the request 166 and the additional information 168 and then performs or causes the payment.
  • the response 174 then includes an acknowledgment from the I D provider computer system 36 that the payment has been made.
  • submission of the additional information 168 to the service computer system 150 can then be omitted, which is advantageous for protecting the confidentiality of this additional information 168, since this additional information 168 then only needs to be disclosed to the trusted ID provider computer system 136.
  • the actual transaction eg the delivery of the ordered product, becomes then upon receipt of the payment confirmation included in the response 174, prompted by the service computer system 150.
  • the additional information 168 includes an OTP.
  • the service computer system 150 checks whether the OTP is valid as an additional prerequisite for the transaction to be performed.
  • the OTP is encrypted by the user's computer system 100 with the public key of the service computer system 150 and then decrypted by the service computer system 150 upon receipt of the additional information with the encrypted OTP, to then check its validity.
  • the computer system includes a terminal 186, which may be, for example, a vending machine, in particular a cash machine or vending machine.
  • a terminal 186 which may be, for example, a vending machine, in particular a cash machine or vending machine.
  • the user 102 may enter into the terminal 186 a sum of money to withdraw cash from his account.
  • An optically detectable pattern is then displayed on a display 188 of the machine, such as a QR code that includes a URL of the service computer system 150 and the amount of money desired by the user 102.
  • This optical pattern is detected by the display 88 by means of a camera 190 of the user computer system 100.
  • the user computer system 100 then generates the transaction request 158 indicating this amount of money.
  • the first session 201 is constructed here using the URL of the service computer system 150 captured from the optical pattern and the transaction request 158 with the desired amount of money is transmitted to the service computer system 150 via this first session 201.
  • the service computer system 150 then generates a corresponding request 166 to retrieve the attributes and additional information 168 required for the payment of the desired amount of money.
  • the ID provider computer system 136 or the service computer system 150 then causes the debit of an account of the user 102, which has indicated this, for example, in the additional information 168. Due to the receipt of the response 174 and the cause of the Payment then receives the terminal 186 a signal to issue the desired amount of money, for example in the form of cash or to charge a cash card of the user 102. This can be done so that the terminal 186 is directly connected to the Diensf computer system 150 or via the network 116.
  • the terminal 186 may also be a vending machine, whereupon no cash but a desired product, such as a soda can or cigarette pack, is dispensed from the vending machine after the payment is signaled by the service computer system 150 has been.
  • a desired product such as a soda can or cigarette pack
  • terminal 186 may be a mobile telecommunications device, particularly a smartphone. If the user 102 wants to buy something from the owner of the terminal 186, the holder of the terminal 186 enters the corresponding purchase price in the terminal 186, so that then on the display 188 in the form of the optically detectable pattern turn this purchase price as a payment amount and the URL of the service computer system 150 is output. Upon completion of the transaction, the terminal 186 receives from the service computer system 150 a signal indicating that the payment has been made and the owner of the terminal 186 then delivers the product to the user 102. This can also be implemented in the POS system of, for example, a supermarket.
  • Another application is a taximeter that detects taxi charges or another utility meter, such as a utility meter for household electricity or gas consumption, especially a so-called smart meter.

Abstract

L4invention concerne un procédé de transaction électronique à l'aide d'un jeton d'identification (106) qui est associé à un utilisateur (102). Le jeton d'identification comprend une mémoire électronique (118) avec un secteur de mémoire protégée (124) dans lequel sont enregistrés un ou plusieurs attributs. Un accès au secteur protégé de la mémoire est possible uniquement par l'intermédiaire d'un processeur (128) du jeton d'identification et le jeton d'identification comporte une interface de communication (108) servant à la communication avec un appareil de lecture d'un système informatique (100) d'un utilisateur.
EP14726573.0A 2013-06-28 2014-05-22 Procédé de transaction électronique et système informatique Pending EP3014540A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102013212646.8A DE102013212646B4 (de) 2013-06-28 2013-06-28 Elektronisches Transaktionsverfahren und Computersystem
PCT/EP2014/060540 WO2014206659A1 (fr) 2013-06-28 2014-05-22 Procédé de transaction électronique et système informatique

Publications (1)

Publication Number Publication Date
EP3014540A1 true EP3014540A1 (fr) 2016-05-04

Family

ID=50828891

Family Applications (1)

Application Number Title Priority Date Filing Date
EP14726573.0A Pending EP3014540A1 (fr) 2013-06-28 2014-05-22 Procédé de transaction électronique et système informatique

Country Status (3)

Country Link
EP (1) EP3014540A1 (fr)
DE (1) DE102013212646B4 (fr)
WO (1) WO2014206659A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102016117134A1 (de) 2016-09-13 2018-03-15 Martin Schwemmer Verfahren zum bargeldlosen Bezahlen an einem Bezahlterminal und Bezahlterminal
CN106875162B (zh) * 2016-12-30 2020-12-04 朗新科技集团股份有限公司 数据抓取方法、数据抓取装置、软收银对接接口及终端
CN111192036B (zh) * 2019-08-01 2023-06-20 腾讯科技（深圳）有限公司 账号资源更新方法、装置、计算机设备以及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050080681A1 (en) * 2003-10-08 2005-04-14 Shinichi Ohnishi System for providing information of automatic transaction apparatus
DE102008000067A1 (de) * 2008-01-16 2009-07-23 Bundesdruckerei Gmbh Verfahren zum Lesen von Attributen aus einem ID-Token
WO2012088512A2 (fr) * 2010-12-23 2012-06-28 Paydiant, Inc. Procédés et systèmes de traitement atm par téléphone mobile

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1282055A4 (fr) * 2000-03-09 2009-08-12 Kitagawa Yoshiko Appareil de traitement de l'information equipe d'un lecteur de donnees optiques, serveurs et procede de commerce electronique
DE102011082101B4 (de) 2011-09-02 2018-02-22 Bundesdruckerei Gmbh Verfahren zur Erzeugung eines Soft-Tokens, Computerprogrammprodukt und Dienst-Computersystem
DE102011089580B3 (de) * 2011-12-22 2013-04-25 AGETO Innovation GmbH Verfahren zum Lesen von Attributen aus einem ID-Token

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050080681A1 (en) * 2003-10-08 2005-04-14 Shinichi Ohnishi System for providing information of automatic transaction apparatus
DE102008000067A1 (de) * 2008-01-16 2009-07-23 Bundesdruckerei Gmbh Verfahren zum Lesen von Attributen aus einem ID-Token
WO2012088512A2 (fr) * 2010-12-23 2012-06-28 Paydiant, Inc. Procédés et systèmes de traitement atm par téléphone mobile

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of WO2014206659A1 *

Also Published As

Publication number Publication date
DE102013212646B4 (de) 2018-11-22
DE102013212646A1 (de) 2014-12-31
WO2014206659A1 (fr) 2014-12-31

Similar Documents

Publication Publication Date Title
EP2949094B1 (fr) Procédé d'authentification d'un usager vis-à-vis d'un distributeur automatique
DE102011082101B4 (de) Verfahren zur Erzeugung eines Soft-Tokens, Computerprogrammprodukt und Dienst-Computersystem
DE102012219618B4 (de) Verfahren zur Erzeugung eines Soft-Tokens, Computerprogrammprodukt und Dienst-Computersystem
EP2454705B1 (fr) Procédé pour lire les attributs d'un jeton d' identification et générateur de mot clefs a usage unique
WO2015154536A1 (fr) Procédé et système de paiement à multiples mécanismes de composition de sécurité fondés sur un code visible
EP2817758B1 (fr) Procédé de paiement informatisé
DE102011116489A1 (de) Mobiles Endgerät, Transaktionsterminal und Verfahren zur Durchführung einer Transaktion an einem Transaktionsterminal mittels eines mobilen Endgeräts
DE102013212627B4 (de) Elektronisches Transaktionsverfahren und Computersystem
DE102013212646B4 (de) Elektronisches Transaktionsverfahren und Computersystem
WO2013093026A1 (fr) Procédé pour effectuer des paiements authentifiés
DE102011079317A1 (de) Mobiles system für finanztransaktionen
EP2879073B1 (fr) Procédé de transaction électronique et système informatique
DE102013022436B3 (de) Elektronisches Transaktionsverfahren und Computersystem
DE102013022434B3 (de) Elektronisches Transaktionsverfahren und Computersystem
DE102013022433B3 (de) Elektronisches Transaktionsverfahren und Computersystem
EP2916252B1 (fr) Procédé de transaction électronique et système informatique
DE102013022438B3 (de) Elektronisches Transaktionsverfahren und Computersystem
DE102013022445B3 (de) Elektronisches Transaktionsverfahren und Computersystem
EP2819079B1 (fr) Procédé de transaction électronique et système informatique
DE102013022447B3 (de) Elektronisches Transaktionsverfahren und Computersystem
DE102013022435B3 (de) Elektronisches Transaktionsverfahren und Computersystem
DE102013022448B3 (de) Elektronisches Transaktionsverfahren und Computersystem
WO2003070493A2 (fr) Systeme informatique et procede pour la transmission electronique de paiements

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20160128

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20170802

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230526