Method and apparatus for authenticating vehicles

Abstract

An apparatus (130) for authenticating a first vehicle (120) for a predetermined function is described. The apparatus (130) is configured to determine an attribute codeword (113) dependent on vehicle attributes (122) of the first vehicle (120) and compare the attribute codeword (113) with a corresponding plurality of different reference codewords (201) for a plurality of different vehicles (120). The apparatus (130) is further configured to determine whether the first vehicle (120) is authenticated for the function based on the comparison.

Description

Technical Field

[0001] The present invention relates to a method and a corresponding device used to safely evaluate a vehicle registration number, for example, for at least either granting permission to a vehicle for a specific function or service or allowing it to be freely used.

Background Art

[0002] A vehicle can be uniquely identified by its registration number. It has been proposed to authenticate a vehicle for one or more functions and / or services using the vehicle's registration number. The problem here is that when it comes to storing and / or transmitting the registration number, especially when the vehicle user has not explicitly consented to its storage and / or transmission, it may pose a problem from the perspective of data protection laws.

Summary of the Invention

Problems to be Solved by the Invention

[0003] This document addresses the technical problem of enabling particularly secure authentication and / or usage permission of a vehicle for predetermined functions and / or services based on vehicle attributes, especially based on the vehicle registration number.

Means for Solving the Problems

[0004] This problem is solved by each independent claim. Advantageous embodiments are described especially in the dependent claims. It should be pointed out that the additional feature parts of the patent claims dependent on the independent patent claim can form an independent invention independent of the combination of all the feature parts of the independent patent claim, even without the feature part of the independent patent claim or just in combination with a part of the feature part of the independent patent claim, and it can be the subject of an independent patent claim, a divisional application, or a later application. This also applies to the technical teachings described in the specification, and an invention can be formed independent of the feature part of the independent patent claim.

[0005] In one embodiment, a device for certifying a first (automobile) vehicle for a predetermined function is described. Examples of functions include the vehicle's storage of an energy source (e.g., fuel or electricity) for driving the first vehicle, entry into a restricted area, and / or parking the first vehicle in a parking lot or parking building.

[0006] This device is configured to determine (in particular receive) an attribute codeword that depends on at least one vehicle attribute of a first vehicle. The vehicle attribute may include, in particular, the registration number of the first vehicle. The attribute codeword may be determined using a cryptographic hash function, such as SHA-2. Furthermore, the attribute codeword may be encrypted using at least one predetermined string, in particular, at least one predetermined salt (SALT). Thus, the attribute codeword can represent the vehicle attribute in an encrypted form.

[0007] Furthermore, this device is configured to compare attribute codewords with corresponding reference codewords for multiple different vehicles. These multiple different vehicles can be vehicles that have been certified and / or authorized to use the above functions.

[0008] The device may be configured to receive and store multiple reference codewords from one or more different service providers (prior to verification of attribute codewords) in a reference data bank for the purpose of settling charges for the provided functions. In this case, individual reference codewords associated with certificates may be received. A certificate for a single reference codeword relating to a given vehicle and a given (payment) service provider can indicate that verification has been completed that the service provider has the right to receive payment from the vehicle owner for the provided functions.

[0009] In other words, the device may be configured to receive certificates regarding a reference codeword from a specific service provider and regarding a specific vehicle. Next, based on these certificates, it can determine whether the service provider is authorized to settle the charges for the services provided to the specific vehicle. If the device determines that the service provider is not authorized to settle the charges for the services provided to the specific vehicle, it may be configured to reject the reference codeword. This further enhances security.

[0010] Various reference codewords may be derived based on the vehicle attributes of each vehicle. Each reference codeword may be derived using a cryptographic hash function such as SHA2. Furthermore, each reference codeword may be encrypted using at least one predetermined string, and in particular, at least one predetermined salt. Thus, each reference codeword can represent at least one vehicle attribute of a vehicle in its encrypted form.

[0011] Here, multiple reference codewords and attribute codewords may each be derived based on a single vehicle attribute (of an individual vehicle) and / or on a single cryptographic hash function. In other words, the same cryptographic hash function may be used for different codewords. Furthermore, the same vehicle attribute (e.g., the registration number of each vehicle) may be used for different codewords.

[0012] In this way, by comparing attribute codewords with various reference codewords, it becomes possible to compare the vehicle attributes of a first vehicle with the corresponding vehicle attributes of multiple different vehicles in an encrypted manner.

[0013] The device is further configured to determine, based on this comparison, whether the first vehicle is authorized (authorized) for its function. In particular, the device may be configured to determine that the first vehicle is authorized (authorized) for its function if one of several reference codewords is identified as corresponding to an attribute codeword. Alternatively or additionally, the device may be configured to determine that the first vehicle is not authorized (authorized) for its function if none of the several reference codewords are identified as corresponding to an attribute codeword.

[0014] Therefore, this device enables authentication (authorization verification) or verification of the authority of a given vehicle for specific functions with high reliability and security, particularly in accordance with data protection regulations.

[0015] The device may be configured to send feedback to a (remote, geographically isolated) provider unit of the provider of a function, once it is determined that the first vehicle is authenticated for that function, in order to provide that function (for example, to enable refueling or charging or to allow entry). Alternatively or additionally, the device may be configured to cause a settlement unit to transfer the fee for the provided function from the user of the first vehicle to the provider of that function, once it is determined that the first vehicle is authenticated for that function. In this way, the function can be provided and settlement can be made in a secure and reliable manner (in particular, without viewing vehicle attributes in clear text).

[0016] Alternatively or additionally, the device may be configured to send feedback to a signal-emitting unit (e.g., a light-emitting element such as a lamp) when it is determined that the first vehicle has been authenticated for its function, and the signal-emitting unit is configured to inform the user of the first vehicle (e.g., by outputting an optical signal) that the first vehicle has been determined to be authenticated for its function. In this way, user comfort can be further enhanced.

[0017] These multiple reference codewords may contain multiple subgroups of reference codewords. Different subgroups may then be associated with different function providers and / or different payment units (e.g., different payment service providers). Reference codewords of different subgroups may each be encrypted with different strings. On the other hand, reference codewords of the same subgroup may be encrypted with the same string. Thus, different providers and / or different payment units may each be associated with different strings (in particular by different salts).

[0018] The device may be configured to determine that a first reference codeword among several reference codewords corresponds to a first attribute codeword. Furthermore, the device may be configured to determine the provider unit of the provider of the above function and / or the settlement unit for settling the charges for the provided above function, based on the string used to encrypt the first reference codeword. In this way, convenience and security can be further enhanced when providing the function and / or when settling the charges for the provided function.

[0019] In one embodiment, a system for authenticating a first vehicle for a predetermined function is described. This system has a sensor unit (e.g., equipped with a camera) which is configured to acquire (understand) the vehicle attributes (particularly the registration number) of the first vehicle. The sensor unit is further configured to determine an attribute codeword based on the vehicle attributes. Furthermore, this system has an authentication execution device described in this specification which is configured to authenticate the first vehicle based on the attribute codeword.

[0020] This system may have at least one payment unit of a payment service provider. This payment unit may be configured to settle fees for the services provided.

[0021] The sensor unit described above may be configured to receive a predetermined string, particularly a predetermined salt, from a payment service provider in order to authenticate the vehicle's attributes and determine the vehicle's attribute codeword.

[0022] In particular, the sensor unit can receive different strings from different payment service providers. Then, since each vehicle attribute can be encrypted using all existing strings, it becomes possible to determine multiple different attribute codewords for multiple different payment service providers. These can then be compared with a reference codeword by the authentication execution device. In this way, the vehicle can be authenticated for specific functions in a highly reliable and secure manner. Furthermore, in this way, the payment service provider responsible for the payment can be identified in an efficient and secure manner.

[0023] The predetermined string of the payment service provider may be time-limited. Alternatively or additionally, the predetermined string may be valid only in a limited location as required. Alternatively or additionally, the predetermined string may be valid only for one or more specific functions as required. In this way, the security of the system can be further enhanced.

[0024] This system can have a large number of different authentication execution devices for their respective different reference codewords. The above sensor unit can be configured to determine (for example, while using a predetermined assignment rule (Zuweisungsregel)) to which of a large number of different authentication execution devices the attribute codeword should be sent for authentication based on the characteristics of the derived attribute codeword. In this way, the security and performance of the system can be further improved.

[0025] In a further aspect, a method for authenticating a first vehicle for a predetermined function is described. This method includes deriving an attribute codeword that depends on the vehicle attributes of the first vehicle. Further, this method includes comparing the above attribute codeword with a plurality of different corresponding reference codewords for a plurality of different vehicles. In addition, this method includes determining whether the first vehicle is authenticated for the above function based on the above comparison.

[0026] In a further aspect, a software (SW) program is described. This SW program can be executed on a processor and can be configured to implement the methods described herein.

[0027] In a further aspect, a recording medium is described. This recording medium can include a SW program that can be executed on a processor and is configured to implement the methods described herein thereby.

[0028] It should be noted that the methods, apparatuses, and systems described in this specification can be used alone or in combination with other methods, apparatuses, and systems described in this specification. Furthermore, any aspects of the methods, apparatuses, and systems described in this specification can be combined with each other in various ways. In particular, the characterizing portions of the claims can be combined with each other in various ways.

[0029] Hereinafter, the present invention will be described in detail based on examples.

Brief Description of the Drawings

[0030] [Figure 1] FIG. is a diagram showing an example of a system for evaluating vehicle attributes. [Figure 2] FIG. is a diagram showing an example of a database of codewords. [Figure 3] FIG. is a flowchart showing an example of a method for evaluating vehicle attributes.

Modes for Carrying Out the Invention

[0031] As described at the beginning, this specification deals with securely authenticating and / or granting permission for use of a (motor vehicle) vehicle (such as a passenger car, truck, bus, and / or motorcycle, etc.) with respect to a predetermined service and / or function, particularly with respect to data protection rules. In this regard, FIG. 1 shows an example of a system 100 having a provider unit 110 operated by a provider of a predetermined function and / or a predetermined service. Examples of functions and / or services are, for example, replenishment of an energy storage body of a vehicle 120, entry into a drive-in cinema, entry onto a specific road, etc.

[0032] The provider unit 110 can be configured to acquire sensor data, particularly image data, relating to vehicle attributes 122, especially the registration number of vehicle 120, using a sensor or sensor unit 112, particularly a camera. Furthermore, the provider unit 110 and / or sensor unit 112 can be configured to determine the attribute codeword 113 by encrypting the vehicle attributes 122. For this purpose, a cryptographic hash function (e.g., SHA-2) can be used. In this case, the vehicle attributes 122 can be encrypted with one or more salts to further enhance data security.

[0033] The attribute codeword 113 can be transmitted to an independent verification unit 130 (for example, a so-called broker). The verification unit 130 is also broadly referred to herein as a device. The verification unit 130 may be configured to compare the attribute codeword 113 with a reference codeword 201 from a reference data bank 200 (see Figure 2). The reference data bank 200 may contain multiple corresponding reference datasets 205 for multiple different vehicles 120.

[0034] A single reference dataset 205 for a particular vehicle 120 may contain a single reference codeword 201 for that particular vehicle 120, where the reference codeword 201 is here particularly encrypted, derived in the same way as the attribute codeword 113 for the particular vehicle 120, that is, based on the same vehicle attribute 112, based on the same cryptographic hash function, and / or based on one or more of the same salts.

[0035] Furthermore, the reference dataset 205 for the specific vehicle 120 mentioned above may include functional information 202. An example of functional information 202 is: - Information regarding one or more functions and / or services authorized to a specific vehicle 120, and / or - Information regarding payment methods for settling charges for services used, such as information about payment service providers. That is the case.

[0036] The verification unit 130 may be configured to compare an attribute codeword 113 provided by the provider unit 110 with one or more reference codewords 201 in the reference data bank 200. In particular, the verification unit 130 may be configured to verify whether the attribute codeword 113 matches a certain reference codeword 201 in the reference data bank 200. The verification unit 130 may then pass feedback 133 to the provider unit 110 in response to the verification. In particular, if it is determined that the attribute codeword 113 matches a certain reference codeword 201, the feedback 133 may grant permission to unlock that function and / or service. Furthermore, if necessary, it may return function information 202 from the reference dataset 201 with respect to the identified reference codeword 201. On the other hand, if it is determined that the attribute codeword 113 does not match any of the reference codewords 201 in the reference data bank 200, the feedback 133 may provide a rejection.

[0037] The verification unit 130 may also be configured to transmit settlement data 134 to the settlement unit 140. The settlement data 134 may, for example, indicate the amount that the vehicle 120 or the user of the vehicle 120 must pay for the functions and / or services provided through the provider. The settlement unit 140 may be operated, for example, by a bank or a payment service provider. Thus, settlement can be performed immediately by the verification unit 130. The settlement unit 140 may then transmit a confirmation document 141 to the provider unit 110 that settlement for the provided functions and / or services has been made. This communication can be performed without exchanging vehicle attributes 122 in plain text for communication.

[0038] Therefore, the system 100 enables the authentication and / or authorization of the vehicle 120 for a predetermined function and / or service without having to explicitly store and / or evaluate the vehicle attributes 122, particularly the registration number, for that purpose.

[0039] Thus, a method is described in which, for example, vehicle registration number 122 (and / or other vehicle attributes) is read and, if necessary, encrypted with one or more salts. One or more salts can here be stored directly in the memory (e.g., read-only memory (ROM)) of the scanning system 112 (e.g., camera). This can be done, for example, through the operator of the verification unit 130, and / or through the operator of the provider unit 110, and / or through the operator of the settlement unit 140.

[0040] Furthermore, the encrypted representation of the registration number + salt can be stored in the reference data bank 200 as reference codeword 201. This can be done for all users of system 100, and in particular for all vehicles 120 using system 100. The reference data bank 200 may also be stored in an independent broker system, i.e., in the verification unit 130, which can perform hash value comparisons, i.e., comparisons of codewords 113,201, thereby linking the function and / or service provider with the scanning system 112.

[0041] This method may comprise the following steps: Scanner 112 scans registration number 122, encrypts it with all of its stored salts, and sends its one or more hash values ​​113 to an independent broker 130. Broker 130 compares its one or more hash values ​​113 with all of its stored reference hash values ​​201. If a match is found, Broker 130 grants authorization and, if necessary, connects other systems for further communication. If no match is found, it can be determined that registration number 122 is not registered with any provider. Even in this case, registration number 122 was either not transmitted in plaintext or was not compared.

[0042] In one example, a designated vehicle 120 pulls up to, for example, a fuel dispenser. Its registration number 122 is scanned, and its hash value 113 is transmitted to a broker 130. After positive verification, the broker 130 reports that the hash value 113 is eligible for refueling. The fuel dispenser is then made available for use. Furthermore, the broker 130 can connect the gas station and a payment service provider 140 for automated settlement. This method can be used in the same way for entry eligibility and / or parking services.

[0043] In the preparation phase for operating the system 100 described above, different operators or service providers of different settlement units 140 (for example, different service providers for settlement of a particular function) may each prepare a string unique to each operator, in particular a salt, in at least one of the broker 130 or scanner 112. Furthermore, each operator or service provider may provide the broker 130 with the registration number 122 of each operator's customer, encrypted with the string unique to the operator, as a reference codeword 201.

[0044] The scanner 112 can then determine the corresponding number of attribute passwords 113 by encrypting the acquired registration number 122 with each individual character of a number of strings. The number of attribute passwords 113 can then be transmitted to the broker 130, which can determine, by comparing them with the reference codeword 201, whether the acquired registration number 122 is registered with an operations manager or service provider, and to which operations manager or service provider the acquired registration number 122 is registered.

[0045] Thus, a payment service provider (e.g., a gas station payer) can transmit its salt to individual scanners 112 (cameras) via broker 130, and the scanner uses it to encrypt registration number 122 and transmit it to broker 130. Each payment service provider has at least one unique salt. At the same time, payment service providers store their customer data in the form of a hash value (customer registration number + salt), i.e., a reference codeword 201, at the broker. Without performing the comparison itself, scanner 112 transmits N hash values ​​113 (for payment service providers of company N) to broker 130, which then compares these with the reference codeword 201. Once matching is performed, the payment service provider is identified based on the payment service provider's salt. Then, data on the operation manager of the function (e.g., a gas station) or data on the amount to be paid can be handed over to the payment service provider. Payment can be made based on known online payment methods.

[0046] To further enhance security, salts (and consequently the hash values ​​derived using them) may be time-limited. Therefore, after a predetermined period has elapsed, the payment service provider may provide the broker 130 with one or more new salts and the reference codeword 201 encrypted with those new salts. The expired salts and / or reference codeword 201 can then be deleted.

[0047] Alternatively or additionally, the salt and / or reference codeword 201 may have spatial validity (and each may be valid only for a specific region). In this way, the performance of scanner 112 and / or broker 130 can be improved.

[0048] Alternatively or additionally, individual salts may have semantic restrictions relating to individual functions or groups of functions. For example, a certain salt may be valid only for the refueling function or only for the parking function, as needed. This reduces the number of hash values ​​113 that the scanner 112 must calculate. Thus, the efficiency of the system 100 can be increased.

[0049] To distribute the load and / or to further enhance security, the hash values ​​201(multiple) of the (payment) provider or service provider x can be distributed to y>1 broker 130, in particular, so that each of these brokers 130 stores only a portion of the known hash values ​​201. The distribution algorithm here can be based on the obtained hash values ​​201, which are known to the service provider and / or scanner 112. In particular, a standard method can be used to distribute the hash values ​​201. For example, all even hash values ​​201 can be stored in broker A, and all odd hash values ​​201 can be stored in broker B. If necessary, for performance reasons, for example to ensure a fast response time, further mirroring can be performed. For example, brokers A and B (even hash values ​​201) and brokers C and D (odd hash values ​​201) can each have the same dataset 205. In this case, all even hash values ​​201 can be sent from scanner 112 to brokers A and B of the service provider. All odd hash values ​​of 201 can be sent to brokers C and D, and as a result, even if one broker becomes overloaded, a fast response can still be expected through the other broker. This is also true for other distributed algorithms.

[0050] System 100 can display an interface for notifying successful and / or unsuccessful matches. For example, System 100 may be configured to recognize that a vehicle 120 is authorized to park in a particular parking lot (for example, with the consent of the vehicle owner and the parking lot owner). Broker 130 recognizes the match and notifies the service provider. If the service provider agrees, the information can be sent to a further display device, such as a lamp in the parking lot that lights up green when the match is successful (and remains off otherwise). This allows System 100 to provide an immediate answer as to whether it has correctly identified the vehicle.

[0051] If necessary, the functions of the broker 130 can be integrated into the scanner 112. In that case, the scanner 112 must have sufficient computing power. Moreover, data protection security will be affected, at least partially.

[0052] System 100 may be configured to provide or guarantee, through a certification system, evidence that the service provider has reached a contractual agreement with the owner of vehicle 120. For example, an authorized ID manager can verify that Mr. Mustermann (represented, for example, by the username m.mustermann within System 100) is the current legal owner of vehicle 120 with registration number 122X-YZ1234. The service provider can then, based on this verification, inquire with a state or independent agency (e.g., the Registration Bureau) to obtain an electronic certificate proving the consistency between registration number X-YZ1234 and the identity of vehicle owner Mr. Mustermann. Thus, the certificate indicates that the service provider has a valid contractual relationship with the owner of registration number X-YZ1234. Based on this, another independent third-party agency can then calculate a hash value (i.e., reference codeword 201) using the service provider's salt and the registration number of vehicle 120. At this point, a certificate regarding the overall legality of the data comparison can be bound together. Broker 130 is provided with the hash value 201 and a certificate. Broker 130 can then, if necessary, accept the query only if the certificate is valid. In this way, data security can be further enhanced.

[0053] Figure 3 shows a flowchart of an exemplary method 300 (which may be implemented by a computer) for authenticating a first vehicle 120 for a predetermined function (e.g., a refueling process or a charging process). This method 300 includes determining an attribute codeword 113 that depends on the vehicle attributes 122 of the first vehicle 120. This attribute codeword 113 may contain or be a hash value determined based on the vehicle attributes 122 by a cryptographic hash function. This attribute codeword 113 can be determined by at least one of the following: by a sensor unit 112 or by a provider unit 110 of the provider of the above function, and can be transmitted to, for example, a verification unit or a broker 130.

[0054] This method 300 further includes comparing the attribute codeword 113 with a number of different reference codewords 201 corresponding to a number of different vehicles 120. The reference codewords 201 may be determined in advance and stored in a memory unit (of the verification unit 130).

[0055] This method 300 further includes determining, based on comparison, whether the first vehicle 120 is certified for the above-mentioned functions 303. In this way, vehicle certification can be made reliable and secure, particularly with respect to data protection.

[0056] The present invention is not limited to the embodiments shown. In particular, it should be noted that the description and drawings are intended to illustrate the principles of the proposed methods, apparatus, and systems for illustrative purposes only.

Claims

1. A device (130) for certifying a first vehicle (120) for a predetermined function, An encrypted attribute codeword (113) is determined, which depends on the vehicle attribute (122) of the first vehicle (120). The attribute codeword (113) is compared with a plurality of different reference codewords (201) corresponding to a plurality of different vehicles (120), which are encrypted in the same way as the attribute codeword (113), and it is verified whether the attribute codeword (113) matches any of the reference codewords (201). Based on the above comparison, it is determined whether the first vehicle (120) is certified for the above function. For the purpose of settling charges for the provided functions, the system receives the aforementioned multiple reference codewords (201) from one or more different service providers and stores them in the reference data bank (200). Regarding the reference codeword from a specific service provider and regarding a specific vehicle (120), a certificate was received. Based on the aforementioned certificate, verify whether the service provider is authorized to settle the charges for the functions provided to the specific vehicle (120), If it is determined that the service provider is not authorized to settle the charges for the functions provided to the specific vehicle (120), the service provider will reject the reference codeword. The configured device (130).

2. The apparatus (130) according to claim 1, Once it is determined that the first vehicle (120) is certified for the function, To provide the aforementioned function, feedback (133) is sent to the provider unit (110) of the provider of the aforementioned function, and / or A feedback (133) is sent to the signal transmitting unit, which is configured to inform the user of the first vehicle (120) that it has been determined that the first vehicle (120) is authenticated for the function, and / or, The payment unit (140) is configured to have the user of the first vehicle (120) transfer the fee for the provided function to the provider of the function. The device (130) is considered to be part of the configuration.

3. The apparatus (130) according to claim 1 or 2, The aforementioned plurality of reference codewords (201) and attribute codewords are, respectively, Based on a single vehicle attribute (122), and / or, Based on a single cryptographic hash function, The device that was identified.

4. The apparatus (130) according to any one of claims 1 to 3, A device in which the plurality of reference codewords (201) and the attribute codewords are encrypted using at least one predetermined string, and in particular using at least one predetermined salt.

5. The apparatus (130) according to any one of claims 1 to 4, When one of the plurality of reference codewords (201) is identified as corresponding to the attribute codeword (113), the first vehicle (120) is identified as being authenticated for the function, and / or If none of the aforementioned multiple reference codewords (201) are identified as corresponding to the attribute codeword (113), then the first vehicle (120) is identified as not being certified for the function. The configured device (130).

6. The apparatus (130) according to any one of claims 1 to 5, The aforementioned plurality of reference codewords (201) include a plurality of subgroups of reference codewords (201), Each of the aforementioned reference codewords (201) in different subgroups is encrypted with a single different string. The aforementioned reference codeword (201) in the same subgroup was encrypted with the same string, Based on the above comparison, it was determined that the first reference codeword (201) among the plurality of reference codewords (201) corresponds to the attribute codeword (113), Based on the string used for the encryption of the first reference codeword (201), the provider unit (110) of the provider of the function and / or the settlement unit (140) for settling the charges for the provided function are determined. The configured device (130).

7. A device (130) according to any one of claims 1 to 6, wherein the vehicle attribute (122) includes, in particular, the registration number of the first vehicle (120).

8. The apparatus (130) according to any one of claims 1 to 7, wherein the function is Housing for an energy holder for driving the first vehicle (120), Entering restricted areas, and / or Parking of the first vehicle (120) in a parking lot or parking building A device that includes this.

9. A system (100) for certifying a first vehicle (120) for a predetermined function, It has a sensor unit (112), and the sensor unit is The vehicle attributes (122) of the first vehicle (120) are obtained, Based on the aforementioned vehicle attributes (122), the attribute codeword (113) is determined. It is composed of, The device (130) for performing authentication according to any one of claims 1 to 8 is configured to authenticate the first vehicle (120) based on the attribute code word (113). System (100).

10. The system (100) according to claim 9, Having at least one payment unit (140) of a payment service provider, The sensor unit (112) is configured to receive a predetermined string, in particular a predetermined salt, from the payment service provider in order to authenticate the vehicle attributes (122) of the vehicle (120) and determine the attribute codeword (113) of the vehicle (120). System (100).

11. The system (100) according to claim 10, The aforementioned predetermined string has a time limit and / or, The aforementioned predetermined string is valid only in limited locations, and / or The aforementioned predetermined string is valid for only one or more specific functions. system.

12. A system (100) according to any one of claims 9 to 11, The system has multiple different authentication execution devices (130) for each of the corresponding multiple different reference codewords (201), The sensor unit (112) is configured to determine, based on the characteristics of the identified attribute codeword (113), which of the numerous different authentication execution devices (130) to which the attribute codeword (113) should be sent for authentication. System (100).

13. A method (300) for certifying a first vehicle (120) for a predetermined function, Implemented by computer, An encrypted attribute codeword (113) is determined (301) that depends on the vehicle attributes (122) of the first vehicle (120), The attribute codeword (113) is compared (302) with a plurality of different reference codewords (201) for a plurality of different vehicles (120), each encrypted in the same way as the attribute codeword (113), and it is verified whether the attribute codeword (113) matches any of the reference codewords (201). Based on the above comparison, it is determined (303) whether the first vehicle (120) is certified for the above function. For the purpose of settling charges for the provided functions, the system receives the aforementioned multiple reference codewords (201) from one or more different service providers and stores them in the reference data bank (200). Regarding the reference codeword from a specific service provider and regarding a specific vehicle (120), a certificate was received. Based on the aforementioned certificate, verify whether the service provider is authorized to settle the charges for the functions provided to the specific vehicle (120), If it is determined that the service provider is not authorized to settle the charges for the functions provided to the specific vehicle (120), the service provider shall reject the reference codeword. A method including (300).

Images