EP3360099A1

EP3360099A1 - Management, authentication and activation of a data carrier

Info

Publication number: EP3360099A1
Application number: EP16754401.4A
Authority: EP
Inventors: Klaus Finkenzeller; Stephan RASCH; Dirk Riesenbeck; Hans-Jürgen ROTH
Original assignee: Giesecke and Devrient Mobile Security GmbH
Current assignee: Giesecke and Devrient Mobile Security GmbH
Priority date: 2015-08-24
Filing date: 2016-08-22
Publication date: 2018-08-15
Also published as: DE102015011083A1; US20180240102A1; US11449858B2; WO2017032453A1

Abstract

The invention relates to a method in a system (100) comprising at least one portable data carrier (40), an authentication server (10), and at least one reader device (24) of at least one service provider (20), wherein said reader device can be coupled to the authentication server (10). The data carrier (40) is configured to communicate contactlessly with the reader device (24) and comprises a security marking (42) which can be contactlessly read out by the reader device (24) and by means of which the data carrier (40) can be authenticated by the authentication server (10). The method comprises the step of equipping (S1) the data carrier (40) with a data carrier management marking (49) that codes a data carrier management information and can be read out contactlessly by a portable terminal (30) of a user of the system (100). Additional steps are: contactlessly reading out (S2) the data carrier management marking (49) using a portable terminal (30); transmitting (S3) the data carrier management information coded in the data carrier management marking (49) to the authentication server (10); and managing (S4) the data carrier (40) in the system (100) using said data carrier management information.

Description

MANAGEMENT, AUTHENTICATION AND ACTIVATION OF A DATA CARRIER

The present invention relates to a method for managing a data carrier in a transaction system, to an authentication server of such a system, and to the transaction system.

It is known to equip portable data carriers, such as smart cards or labels, with contactlessly readable identifiers, preferably in the form of transponders, in order to enable a transaction to be carried out between the data carrier and a correspondingly configured reading device. One possible form of such a transaction is the regulation of an access authorization, e.g. to a building, a traffic route, or other resources. Alternative transactions are, for example, pure payment transactions for acquiring goods or

Services. For this purpose, the data carrier can be coupled with a background system via which the payment transaction is then actually processed. A disadvantage of the method described is that, as a rule, every application of a service provider, for example an application which allows access to a parking garage of a first operator, requires a specific portable data carrier which is only used in conjunction with the specific application of this service provider. is reversible. Would a user like a similar application of a second

Service provider, for example, access to a parking garage of another operator, so it is usually required for the first portable media different second portable media. Object of the present invention is therefore to provide a way in which a single portable media in different applications, preferably against different service providers, can be used.

This object is achieved by a method, an authentication server and a system having the features of the independent claims. Advantageous embodiments and further developments are specified in the dependent claims.

The present idea is based on the basic idea of providing the portable data carrier with a further contactlessly readable identification which can be easily read and processed by means of a portable terminal of a user of the system. Information coded by means of the identification drawing can then be transmitted by the terminal to an authentication server of the transaction system. The authentication server is arranged to manage the volume in the system based on the received information. According to a first aspect, the invention relates to a method in a system which comprises at least one portable data carrier, for example a chip card or a label, an authentication server and at least one reader of at least one service provider which can be coupled to the authentication server via a communication network, for example the Internet , The data carrier is set up to communicate with the reader in a contactless manner in order to carry out a transaction with an application of a service provider, possibly only after activation in the system. The data medium comprises a part of the reading device contactlessly readable security tag, on the basis of which the data carrier can be authenticated by the authentication server.

The method according to a preferred embodiment comprises the following steps:

The volume is equipped with a volume management tag which encodes volume management information. In the authentication server, the volume management information is uniquely coupled with security information encoded by the security label of the data carrier in a manner to be described in more detail below. The volume management identifier of the data carrier is contactlessly readable by means of a portable terminal of a user of the system, for example by means of a conventional mobile radio terminal or a smartphone.

The volume management tag is read out without contact by means of a portable terminal of a user of the system, and the volume management information coded in the volume management tag is transmitted to the authentication server by means of the portable terminal.

The authentication server then manages the volume in the system using the volume management information.

The management of the volume in the system may include a step of activating the volume in the system. In this case, the volume in the system is not activated, ie can not be used to perform a transaction with a service provider's application, before the authentication server first receives the volume management information encoded in the volume management tag. In other words, a portable data carrier is registered in the system only after the volume management designation has been read out for the first time and the volume management information stored therein has been transmitted to the authentication server.

The management of the volume in the system may further comprise a step of associating a user with the volume. This step is optional, as applications are conceivable in which a user assignment to the volume can be omitted. Other applications, such as those associated with a payment transaction, necessarily require a specific assignment of a user to the volume, for example, to also be able to associate account information of that user with the volume.

In the associating step, user registration data such as a user name, a password, user bank data and the like may be transmitted to the authentication server. The user registration data is stored there together with the volume management information and assigned by the authentication server to the volume management information. Upon completion of this step, the volume is deemed to be associated with the user identified by the received user registration data.

The management of the volume in the system may further comprise a step of enabling an application of a service provider for the volume. It should be noted that the system is constructed in such a way that the authentication server can be connected to a large number of service providers, each of which offers at least one application of the type indicated above, for example access control, the sale of various goods or services, and the same. Each service provider comprises at least one reader via which the portable data carrier can come in communication with the service provider or with an application of the service provider. Now, if the disk is activated in the system and optionally assigned to a specific user, then different applications can be unlocked for the disk. Upon activation of the volume for a service provider application, the system is arranged to assist in performing a transaction between the service provider application and the volume. In other words, a user of the data carrier can generally only use an application of a service provider if this has been enabled for the specific data carrier.

The unlocking step can be carried out, for example, such that the authentication server displays to the user of the data carrier, for example via a suitable web interface, a list of potentially selectable applications of different service providers. The user of the data carrier can then select from this one or more applications, which are then enabled by the authentication server for the specific data carrier. For some of these applications, it may be necessary for the user of the data carrier to specify other user registration data, for example account information or the like, in order to allow complete and, in particular, automatic use of the application. Generally in the context of the present invention, the user of the data carrier can communicate with the authentication server via a suitable application ("app") which the user installs on his terminal, for example his smartphone, in a conventionally known manner The first user registration can then be supported by means of such an application Alternatively or additionally, the authentication server can provide a communication interface, for example the mentioned web interface, which about every conventional

Browser for the user of the data carrier is usable (after previous registration by means of the user registration data).

In all the management steps described above, the authenticating server recognizes the data carrier on the basis of the volume management information which has been transmitted to the authentication server by the user's portable terminal. This volume management information is stored in the authentication server, coupled with the security information of the portable volume, eg in a suitable database of the authentication server. Together with the volume management information and security information, corresponding user registration data can then also be stored and managed. This allows a user of the system in a very simple way to activate a disk in the system, register as a user of the disk and unlock the disk for different applications of different service providers. This allows a flexible and easy use of the data carrier in various application contexts. The step of unlocking an application of a service provider is usually performed by a user associated with the volume, as already explained.

Alternatively, it is also possible for individual applications of specific service providers to be activated by the respective service provider itself for a user of the data carrier. For this purpose, the service provider in turn can contactlessly read the volume management designation of the data carrier by means of a suitable reader and transmit the volume management information encoded in the volume management designation to the authentication server. This usually refers to applications that are only accessible to a specific group of users, such as access to a car park of a residential complex, which should only be accessible to residents of the residential complex. The service provider is e.g. the condominium operator who, after examining whether a potential user is also a resident of the condominium, can unlock it for access to the car park in the manner indicated.

In particular, an application of a service provider can be activated in such a way that a transaction between the data carrier and the application can subsequently be carried out automatically, that is to say without further user interaction or the need to enter further data or a transaction confirmation. This allows a particularly simple implementation of such transactions.

Alternatively or additionally, it is possible to unlock individual applications only in principle, while for performing the relevant Transaction, however, a user interaction, at least one transaction confirmation or the like is still provided.

A second preferred aspect of the present invention relates to a transaction method for performing a transaction between a portable data carrier having a security tag described above and a reader of a service provider of the type described above. This method is basically independent of that described above with reference to the first aspect of the invention disk management procedures. Thus, the transaction procedure will be described below without reference to a volume management tag on the volume and without reference to the volume management steps described above. Following the description of the transaction procedure, it will be shown how the volume management method and the transaction method can be advantageously combined.

In a first step of the transaction procedure, the reading device of the service provider requests an authentication information comprising the security information of the data carrier from the data carrier.

The data carrier then provides the requested authentication information to the reader, which forwards the authentication information to the authentication server.

The authentication server authenticates the volume based on the one in the authentication information and transmits a result of authenticating the volume to the reader. In the case of successful authentication of the volume, a transaction can be made between an application of the service provider and the volume. The method accordingly comprises the steps:

Requesting authentication information from the volume comprising a security identity of the volume by a reader of the service provider;

Providing the authentication information by the data carrier to the reader;

Forwarding the authentication information by the reader to the authentication server;

Authenticating the volume based on the authentication information by the authentication server;

Determining, by the authentication server, an application identity associated with the volume in the service provider system based on the security identity; and

Transmitting the determined application identity associated with the volume to the reader of the service provider system.

In the following, individual steps of the transaction method are specified by way of example with reference to preferred embodiments and variants of the transaction method. The individual variants of the steps of the method, if not otherwise described, can be combined as desired. As a security identity, a (management system-wide clear) security information is described. As an application identity, a (public system-wide) public identity (or public ID) is described. As a rule, the security identifier is designed as a cryptographically secured security identifier, for example in the form of a transponder, which is set up to transmit security information (SID, "secret ID") to the reader in encrypted form only, preferably in an asymmetrical key architecture The encryption of the security information in the security tag takes place by means of a public key, the decryption by the authentication server by means of a corresponding secret key.

The reader may include such a cryptographically secured security tag, for example, in the context of establishing a communications link with the media, i. the transponder, recognized as cryptographically secure. The structure of the communication connection can be understood here as a first sub-step of a step of requesting the authentication information.

The reading device then sends a corresponding command to the data carrier in order to enable a cryptographically secure transmission of the authentication information by the data carrier (for example according to ISO / IEC 29167-19). As a rule, the authentication of the data carrier takes place by means of a challenge-response method.

For this purpose, the reader can first request the corresponding command from the authentication server and then forward a corresponding command received from the authentication server to the data carrier, ie the security identifier of the data carrier. The data carrier can generate as authentication information a response command according to the protocol used, for example in the form of a cryptogram, which encompasses the encrypted security information. The cryptogram may include further information that allows the authentication server to decrypt the security information.

This further information, which relates in particular to the selection of a key required for decrypting, can also be requested separately from the reading device in the data carrier and transmitted by the data carrier separately from the cryptogram to the reading device. The authentication information then includes the cryptogram and the further information. The data carrier then transmits the authentication information to the reader, which forwards the authentication information to the authentication server.

In the authentication server, the security information encrypted in the cryptogram is decrypted and the volume is authenticated by the authentication server. As mentioned, the authentication method can be carried out, for example, as a challenge-response method, in which the data carrier receives from the authentication server a "challenge", for example a random number, and "encrypts" it using the security information.

Optionally, the authentication server may associate the decrypted security information (SID) with a public identifier relating to the medium, a so-called PID ("public ID") Identification is static and clearly assigned to the safety information (SID).

There can be several different public identifiers for a data medium. As a rule, for each application of a service provider for which the data carrier is unlocked, exactly one public identification of the data carrier (on the part of the authentication server) is generated, which is then transmitted in the step of activating the data carrier for a selected application of a service provider of this application , Therefore, in addition to the volume management information and the security information, one or more public identifiers uniquely assigned to the security information can be stored in the database of the authentication server. The authentication server then transmits the result of the authentication to the reader. This result may simply be that the authentication server tells the reader whether or not the volume has been successfully authenticated. Optionally, the authentication server may transmit to the reader, in the case of a successful authentication of the volume, the corresponding public label of the volume corresponding to the application of the service provider currently envisaged to perform a transaction with the volume. Information about this application can be sent to the authentication server at any point in the method, for example at the beginning when requesting a command to be forwarded to the data carrier. It should be noted that at the time when the data carrier establishes a communication with a reading device of a service provider, the specific application of the service provider, with which the data carrier can subsequently carry out a transaction, is already clearly established. In the event that multiple applications of the service provider are "reachable" via a reader, the user can be given the opportunity to select one of these applications.

Based on the result of the authentication, the reader can then decide whether the transaction should be performed between the application and the data carrier. A public identification of the data carrier transmitted to the reading device also enables the reading device to authenticate the data carrier unambiguously. The volume management method according to the first aspect of the invention and the transaction method according to the second aspect of the invention can advantageously be combined in such a way that the authentication server, in addition to authenticating the volume, can check whether the corresponding volume has already been activated in the system. Furthermore, the authentication server can check whether an appropriate user has already been assigned to the data carrier and whether the application which offers the service provider currently connected to the data carrier via the reading device has already been activated for the specific data carrier.

In the step of transmitting a result of the authentication, the authentication server can therefore inform the reader not only whether the volume has been successfully authenticated, but also whether the volume in the system has already been activated and whether the application in question for the volume has already been unlocked , On the other hand, if the authentication server detects, for example, that the application in question for the volume has not yet been unlocked, the authentication server can prompt the volume user to unlock the application.

A third aspect of the present invention relates to an authentication server for a transaction system. This system comprises at least one data carrier described above with reference to the first aspect of the invention, the authentication server itself and at least one reader of at least one service provider which can be coupled to the authentication server via a communication network. The authentication server is in particular configured to receive from the reader a security information encoded in the security identifier of the data carrier and to authenticate the data carrier on the basis of the security information. Furthermore, the authentication server is set up to receive a volume management information encoded in the volume management designation from a portable terminal that can be coupled to the authentication server via a communication network and to manage the volume in the system in the manner described above using the volume management information.

Preferably, the authentication server is set up, to which at least one data carrier, for example in a suitable database or the like, the security information, optionally a cryptographic key for decrypting an encrypted received security. unit information, together with the volume management information and possibly other management data relating to the data carrier, such as user registration data of a user assigned to the data carrier or information relating to applications of service providers released for the data carrier. In particular, the authentication server is set up to support a volume management method described above with reference to the first aspect of the invention, and preferably also a transaction method described above with reference to the second aspect of the invention.

A fourth aspect of the present invention relates to a corresponding transaction system, comprising at least one portable data carrier according to the first aspect of the invention, an authentication server according to the third aspect of the invention, and at least one of at least one service provider of the one described above, which can be coupled to the authentication server via a communication network Art.

The at least one data carrier of the system is preferably designed as a chip card or as a label (label, tag).

The at least one data carrier preferably comprises only the security tag. By means of a reader of the type with which the safety marking can be read out, there is thus no further identification, in particular no application identifier (public identification), which can be read out. Application tags (public tags) associated with the disk are only stored centrally in the authentication server, not the disk. The security tag of the portable data carrier can preferably be formed by means of an RFID transponder, for example as an NFC transponder or as a UHF transponder. According to a preferred variant, the transponder is set up to encrypt a security information stored in the transponder and to transmit it only encrypted to a reading device of a service provider.

The volume management identifier of the data carrier could also be provided in the form of a transponder, preferably by an NFC transponder. The data carrier administration identifier is preferably designed as an optically readable identification, preferably as a bar code, particularly preferably as a QR code. In particular, if the security marking and the data storage management information can be read out from the data carrier with different means in each case or are applied differently to the data carrier, the flexibility of the system is increased. For example, a disk management information which can be read out optically or read out via an NFC interface enables the disk management for a UHF-readable security tag (without the UHF reader having to be present at the user).

The present invention will be described by way of example with reference to the accompanying drawings. Show:

FIG. 1 shows components of a preferred embodiment of a system according to the invention; FIG. 2 shows steps of a preferred embodiment of a method for managing a data carrier in the system according to FIG. 1 and FIG. 3 shows a preferred embodiment of a transaction method in the system according to FIG.

A transaction system 100 shown by way of example and schematically in FIG. 1 comprises an authentication server 10, at least one portable data carrier 40, at least one reader 24 of a service provider 20, and at least one portable device 30 of a user of the system 100. As will become apparent hereinafter such system 100 typically includes a plurality of data carriers 40 and a plurality of readers 24 of different service providers 20.

The authentication server 10 is set up to be coupled via a suitable communication network, for example the Internet, to the reader 24 or the service provider 20 to which the reader 24 is connected and to the terminal 30. The authentication server 10 comprises a suitable storage device 12, for example a database, for storing and managing various data described below in detail relating to the data carrier 40 and its management in the system 100. The function and operation of the authentication server 10 will be described below with reference to the methods of FIGS. 2 and 3.

The data carrier 40 includes a security tag 42. This is formed in the example shown as a transponder. Depending on the application, an NFC transponder, a UHF transponder or the like can be used for come. The transponder 42 comprises a transponder chip 46 and an antenna 44. A security information (SID) 48 and a public key KE for encrypting the security information 48 are stored in the transponder chip. The transponder chip 46 is set up to encrypt the security information 48 by means of the key KE and to transmit it only encrypted to a reader 24.

The data carrier 40 furthermore comprises a data carrier management identifier 49. The data carrier administration identifier 49 is set up to be read without contact by means of the portable terminal 30. In principle, the data carrier management designation 49 can also be designed as a transponder, for example as an NFC transponder. Preferably, however, the data carrier management identifier 49 is embodied, as shown in FIG. 1, as an optically readable identification, particularly preferably as a QR code. Reading out and evaluating such a label can be done in a simple manner by means of a conventional smartphone camera and a corresponding evaluation application.

The data carrier 40 is registered in the authentication server 10 of the system 100. For this purpose, the authentication server 10 stores the security information 48 of the data carrier 40 together with the volume management information coded in the volume management identifier 49. In this way, when the authentication server 10 receives one of these two pieces of information, ie the security information 48 or the volume management information, it can uniquely identify the volume 40 and make an association between the two pieces of information. As already mentioned, the portable terminal 30, as shown in Figure 1, be designed as a smartphone. The terminal 30 is set up to read out the volume management identifier 49 of the data carrier 40, in the illustrated example optically, by means of a camera 34 and a corresponding evaluation application 32. In the case that the volume management identifier 49 is designed as an NFC transponder, an NFC can be used as the terminal 30 enabled smartphone or the like. The terminal 30 may not be able to read the security label 42 of the data carrier 40.

The data carrier 40, i. specifically, the security tag 42 of the data carrier 40 may be connected via the reader 24 to an application 22 of the service provider 20 for performing a transaction, as described below with reference to FIG.

To enable the volume 40 in the system, assign it to a user, and unlock it for the application 22, a volume management method may be used, as described below with reference to FIG.

In a first step S1, the data carrier 40 is provided with a volume management designation 49, for example the QR code described above. In this case, the data medium management identifier 49 is placed on the data carrier 40 or inserted into the data carrier 40 in such a way that it can be read out contactlessly by the user's terminal 30.

The volume management tag 49 encodes volume management information, such as a string uniquely assigned to the volume. As already mentioned, the data carriers are administrative information of the data carrier 40 in the authentication server 10 is clearly coupled to the security information 48 of the data carrier 40.

In step S2, the volume management tag 49 is read out contactlessly by means of a portable terminal 30 of a user of the system 100. In the example shown, the user will read the QR code 49 by means of the smartphone 30 and the camera 34 and forward the data storage management information stored therein to the authentication server 10 in step S3. In the volume management identifier 49, in addition to the volume management information, for example, an Internet address of the authentication server s 10 may be stored in order to automate the step S3 of the transmission means.

In step S4, the authentication server 10 now manages the volume 40 in the system 100 using the volume management information received in step S3.

The management of the data carrier 40 in the system 100 can relate to various aspects, which are indicated in the sub-steps S4.1, S4.2 and S4.3 in FIG.

In step S4.1, the data carrier 40 is activated in the system 100. Basically, a data carrier 40 is arranged to be used in the system 100 in the manner described with reference to FIG. As a rule, however, this requires a one-time activation of the data carrier 40. Such activation may be effected by the authentication server 10 receiving once from the terminal 30 the volume management information encoded in the volume management designation 49. From this point on, the authentication server 10, as a data Carrier management step, the volume 40 as activated in the system 10 register. It is possible that the authentication server 10 also reverses such activation of the data carrier 40, for example, if there is an abuse of the data carrier 40 or at least suspected.

Another volume management step, indicated with reference to step S4.2, involves associating a user with the volume 40. Applications are conceivable in which such user assignment to the volume that does not a priori is not required. As a rule, however, an assignment of a user to the data carrier 40 will take place once. In this case, the user registers with the authentication server 10 as the user of the data carrier 40. If such a registration is completed, no other user can register more than users of the data carrier 40, that is to say the data carrier 40 is uniquely assigned to the user who is the first user registered. In principle, it can be provided that a once registered user is changed and a new user is entered. It may also be provided that per volume a limited number of users, i. more than one user, can be registered, preferably with the same password, to avoid abuse.

Also for assigning a user to the data carrier 40, in the manner described above, the data carrier management identifier 49 is read out by means of the terminal 30 and the data carrier management information coded therein is transmitted to the authentication server 10. Subsequently, if the authentication server 10 has identified the data carrier 40 on the basis of the volume management information, user registration data of the user can be sent to the authentication server 10. transmitted by means of the terminal 30. Such user registration data may in particular include a username and password of the user. In this way, the user can subsequently log on to the authentication server 10 for further administration of the data carrier 40 and for entering further data relating to the use of the data carrier 40 in the system, for example for entering or changing account information in order to enable an automatic execution of the data Payment transaction by means of the data carrier 40 or the like. A further management step relates to the activation of an application of a service provider 20 for the data carrier 40, as indicated in step S4.3. Before a user can use an application 22 of a service provider 20, for example the application 22 shown in FIG. 1, by means of the data carrier 40, ie can carry out a transaction with application 22 by means of the data carrier 40, the relevant application 22 for the data carrier 40 must be unlocked , In order to enable such a disconnection, the user of the data carrier 40, again by reading the volume management identifier 49 by means of the terminal 30 and by transmitting the volume management information encoded in the volume management identifier 49 to the authentication server 10, can virtually log the volume 40 on to the authentication server 10. The authentication server 10 then offers the option of enabling individual applications 22, which are displayed to the user of the data carrier 10, for example in the form of a list. The user of the data carrier 40 can select individual applications from this list, which are then enabled by the authentication server 10 for use for the data carrier 40. In principle, applications can also be provided which are of one in the system activated disk 40 can be used without prior activation.

It is understood that after a single reading of the volume management designation 49 and transmission of the data carrier management information encoded therein, more or less within a "session", a plurality of steps S4.1, S4.2 or S4.3 can be performed without prior to If, however, the data communication between the terminal 30 and the authentication server 10 has been completed once, the renewed or first-time performance of, for example, the step S4.3 requires previously the steps S2 again and S3.

With reference to FIG. 3, a transaction method, ie a method for carrying out a transaction between the data carrier 40 and an application 22 of the service provider 20, will be described below by way of example. Such a method is fundamentally independent of a data carrier management method according to FIG. 2. In step T 1, a reader 24 of a service provider 20, when it detects a portable data carrier 40 in the response area of the reader 24, requests the data carrier 40 to provide authentication information. The reader 24 can be set up to detect whether the data carrier 40 is a secure data carrier in such a way that the security identifier 42 of the data carrier 40 can provide security information 48 of the data carrier 40, by means of which the authentication server 10 can authenticate the data carrier 40 , only in encrypted form. In this case, the reader 24 may request from the authentication server 10, for example, a corresponding command, which An authentication method using encrypted security information 48 is enabled. In the context of the present invention, for example, a protocol in accordance with ISO / IEC 29167-19 can be used, in which a special challenge-response method for data carrier authentication is used. The security information 48 is defined in this case as an eight-byte long identifier.

In step T2, the data carrier 40 provides a corresponding authentication information to the reader 24. In particular, this authentication information comprises the security information 48, as mentioned above, preferably in encrypted form. For this purpose, the security identifier 42 comprises an encryption key KE for encrypting the security information 48. The key KE can be, for example, a public key of an asymmetrical key pair, wherein the authentication server 10 comprises a secret key KD associated with the key pair (see FIG encrypted security information 48 to decrypt again. The data carrier 40 may generate the authentication information, for example, as a cryptogram in accordance with the standard described above. In particular, the authentication information also includes further information which allows the authentication server 10 to determine the secret key KD ZU required for decrypting the encrypted security information. This additional information can be part of the cryptogram. Alternatively, the reader 24 may request such additional information separately from the data carrier 40 and add it to the authentication information. An example of such further information is a specific group identity, which is a group defines which of the data carrier 40 is assigned. For each of these groups there then exists a uniform public key KE and a corresponding secret key KD. In step T3, the reader 24 forwards the authentication information received from the data carrier 40 to the authentication server 10.

The latter authenticates the data carrier 40 in step T4 on the basis of the security information 48 contained in the authentication information. For this purpose, the authentication server 10 decrypts, by means of the secret key KD, the encrypted security information 48 contained in the authentication information. Using a challenge-response method indicated above In this way, a clear authentication of the data carrier 40 can take place in a manner known per se.

Optionally, the authentication server 10 now, after successful authentication of the data carrier 40, the security information 48 of the data carrier 40 uniquely assign a public identification (PID) of the data carrier 40. It can be provided that the authentication server 10 for each application 22 of a service provider 20, which has been unlocked for the disk 40 generates a separate public identification of the disk 40, the security information 48 of the data carrier 40 assigned, and the respective application transmitted by the service provider. The application can then uniquely authenticate the data carrier 40 via the corresponding public identification.

The format of such a public identification is basically freely selectable per application 22 and can be adapted to the requirements of the application 22. On the basis of such public labeling can an application 22, if required, "recognizes" a user of the volume 40 during a transaction, such as a toll application with a plurality of toll booths. "The true identity of the user of the volume 40 typically associated with the service provider 20 In this case, the transfer of the public identification instead of the security identifier 48 from the authentication server 10 to the reader 24 furthermore offers the advantage that the reader 24 then does not have both plain text (security identifier) and cryptogram (encrypted security identifier ), and possibly draw conclusions about the encryption.

In step S5, the authentication server 10 transmits a result of the authentication to the reader 24, that is, in particular, the fact whether the data carrier 40 has been successfully authenticated and, if so, additionally a public identifier of the data carrier 40, that of the application 22 of a service provider 20 is associated with which the volume 40 now intends to carry out a transaction. As indicated above, the authentication server 10 is aware of the specific application 22.

In step T6, the reader 24 checks the results obtained, that is to say it checks whether the data carrier 40 has been uniquely authenticated by the authentication server 10 and, if appropriate, whether the received public label of the data carrier 40 is associated with the public identification known for the application matches. If there are inconsistencies in the public labeling or authentication has generally failed, the procedure is aborted as indicated with reference to step T8. In the case of an overall successful authentication, a transaction between the data carrier 40 and the application 22 of the service provider 20 is performed in step T7.

In general, it can be stated that the authentication server 10 thus provides a number of advantageous functionalities. On the one hand, it can check the authenticity of the data carrier 40 for different applications 22 of different service providers 20, while the data carrier 40 can remain anonymous to the service providers. The authentication server 10 may also determine if the volume 40 for a specific application 22 has already been unlocked. Furthermore, since the user registration data corresponding to the data carrier 40 can be managed by the authentication server 10, the authentication server 10 can operate as a clearing instance and, for example, support billing of different applications for different service providers.

Providing the volume management tag 49 on the volume 40 allows a user of the volume 40 to easily manage the volume 40 in the system 100. To do so, no new technology is required, a conventional smartphone that the user uses in everyday life anyway completely sufficient to carry out the essential data carrier management steps, namely the activation of the data carrier 40 in system 100, the assignment of a user to the data carrier 40 and the activation of individual applications 22. In this way, it becomes possible for the first time to provide one and the same portable data carrier 40, which can interact contactlessly with different applications 22 of different service providers 20. It is understood that a user can use various portable data carriers 40, for example once in the form of a chip card, once in the form of a label. Of course, the authentication server 10 can also manage different data carriers 40 for one user.

Claims

Patent claims

A method in a system (100), which comprises at least one portable data carrier (40), an authentication server (10) and at least one reader (24), which can be coupled to the authentication server (10), of at least one service provider (20). 40) is arranged to contactlessly communicate with the reader (24), and a by the reader (24) contactlessly readable security tag (42), based on which the data carrier (40) by the authentication server (10) is authentifizier bar, comprising the Steps:

Providing (Sl) the data carrier (40) with a volume management identifier (49) which encodes a volume management information and which is contactlessly readable by means of a portable terminal (30) of a user of the system (100);

Contactless (S2) reading the volume management tag (49) by means of a portable terminal (30) and transmitting (S3) the volume management information encoded in the volume management tag (49) to the authentication server (10);

Managing (S4) the volume (40) in the system (100) using the volume management information.

2. The method according to claim 1, characterized in that the management of the data carrier (40) in the system (100) comprises a step of activating (S4.1) the data carrier (40) in the system (100), wherein the data carrier ( 40) in the system (100) is preferably activated when the authentication server (10) first receives the volume management information encoded in the volume management designation.

The method of claim 1 or 2, characterized in that the management of the volume (40) in the system (100) comprises a step of associating a user with the volume (S4.2), wherein in the step of associating user registration data of a user transmitted to the authentication server (10) and associated with the volume management information.

4. The method according to any one of claims 1 to 3, marked thereby, that the management of the data carrier (40) in the system (100) a

Step of enabling an application (22) of a service provider (20) for the data carrier (S4.3), wherein the system (100) is preferably set up after the application (22) has been enabled to perform a transaction between the application (22 ) of the service provider (20) and the data carrier (40).

5. The method according to claim 4, characterized in that the step of enabling an application (22) of a service provider (20) from a the volume (40) associated user is performed.

6. The method according to claim 5, characterized in that the step of enabling an application (22) of a service provider (20) by the service provider (20) itself is performed, for which the service provider (20) in turn the volume management designation (49) by means of a suitable Read out the reader contactlessly and transmit the volume management information encoded in the volume management identifier (49) to the authentication server (10).

7. The method according to any one of claims 4 to 6, characterized in that the application (22) is unlocked such that a transaction between the data carrier (40) and the application (22) can be carried out automatically below.

8. The method according to any one of claims 1 to 7, characterized by the further steps:

Requesting (T 1) an authentication information comprising the security information (48) of the data carrier (40) from the data carrier (40) by the reading device (24) of the service provider (20);

Providing (T2) the authentication information by the data carrier (40) to the reader (24);

Forwarding (T3) the authentication information by the reader (24) to the authentication server (10);

- authenticating the data carrier (T4) based on the security information (48) contained in the authentication information by the authentication server (10);

Transmitting a result of authenticating the volume to the reader (T5); and

upon successful authentication of the volume (T6), performing a transaction (T7) between an application (22) of the service provider (20) and the volume (40).

9. Authentication server (10) for a system (100) which has at least one portable data carrier (40), the authentication server (10) and at least one reader (24), which can be coupled to the authentication server (10) via a communication network, of at least one service provider (20). wherein the data carrier (40) is set up to communicate in a contactless manner with the reading device (24) and to monitor a reading device (24) which is in contact with the reading device (24). tactlessly readable security tag (42) and a means of a portable terminal (30) contactless readable disk management mark (49),

wherein the authentication server (10) is set up,

receive security information (48) encoded by the reader (24) in the security tag (42) and to authenticate the medium (40) based on the security information (48), and

receive from a terminal (30) a volume management information encoded in the volume management designation drawing (49) and manage the volume (40) in the system (100) using the volume management information.

The authentication server (10) according to claim 9, characterized in that the authentication server (10) is arranged to store and manage at least one data carrier (40) the security information (48) together with the volume management information and a method to support one of claims 1 to 8.

11. System (100) comprising

at least one portable data carrier (40),

the authentication server (10) according to claim 9 or 10 as well as at least one reading device (24) of at least one service provider (20) which can be coupled to the authentication server (10) via a communication network,

wherein the data carrier (40) is arranged to contactlessly communicate with the reader (24) and a non-contact readable by the reader (24) safety marking (42) and by means of a portable terminal (30) contactless readable volume management tag (49).

12. System (100) according to claim 11, characterized in that the data carrier (40) is designed as a chip card or as a label.

13. System (100) according to claim 11 or 12, characterized in that the security marking (42) of the data carrier (40) is designed as an RFID transponder, preferably as an NFC transponder or as a UHF transponder.

14. System (100) according to claim 13, characterized in that the transponder (42) is set up to encrypt a security information (48) stored in the transponder (42) and to transmit it only encrypted to a reading device (24).

15. System (100) according to one of claims 11 to 14, characterized in that the data management identifier (49) is designed as an optically readable identification, preferably as a bar code, particularly preferably as a QR code.