DE102015224838B4 - Devices, information system, method and computer program for checking an authentication feature - Google Patents

Abstract

Device (10) for checking an authentication feature, comprising a communication module (12) designed to communicate with an authentication entity (200) via a communication connection; and a control module (14) designed to: control the communication module (12), determine an availability of the communication connection with the authentication entity (200), and remotely check the authentication feature by providing information about the authentication feature for the authentication entity (200) and obtaining information about a result of checking the authentication feature from the authentication entity (200) if the communication link with the authentication entity (200) is available, or locally checking the authentication feature based on information about a check of the authentication feature if the communication link with the authentication entity (200) is not available ,wherein the control module (14) is designed to determine the availability of the communication connection after the local checking, and to verify the local checking by remotely checking the authentication feature when the communication connection with the authentication entity (200) is available again, the remote checking of the authentication feature and the local checking of the authentication feature by the control module (14) are based on the information about the verification of the authentication feature, the control module (14) being further designed to update the information about the verification of the authentication feature based on the authentication feature, if the removed one Check is successful.

Description

The invention relates to devices, an information system, methods and a computer program for checking an authentication feature, more specifically, but not exclusively, based on local or remote testing of the authentication feature.

Functionalities of electronic devices are often protected by protective mechanisms: These can, for example, prevent unauthorized people from using certain functions or can enable fine-grained activation of functions. For example, with many mobile phones it is common practice for a user to have to unlock the device before use, for example by entering a code, a password or by comparing their fingerprint. Another example is rental cars. Especially for rental cars with a short rental period, such as shared cars (also known as car sharing), a variety of options are used for user authentication, from radio-activated transponder cards (also known as radio frequency identification cards, RFID) to computer programs for programmable mobile phones (also known as mobile phones). . Apps for smartphones).

In some cases, authentication features can be used across a variety of devices. The authentication features can be checked, for example, by a server in a network; an identification feature (e.g. a user name and a password) can be used, for example, to access multiple devices. The prerequisite for this is that the device that requires user authentication is connected to the corresponding server.

The printed matter US 7,234,157 B2 , WO 2011 / 124 257 A1 , US 2013 / 0 290 705 A1 , US 2012 / 0 313 796 A1 , US 2015 / 0 145 645 A1 and US 7,506,054 B1 generally deal with authentication.

In particular deals with US 7,234,157 B2 with a system for providing user access to secured resources based on user authentication to a remote authentication server. If authentication fails, it is checked whether there is a connection to the authentication server. If there is a connection, access is denied. If there is no connection, user privileges to access the secured resources are taken from a cache.

In US 7,506,054 B1 a client device attempts to authenticate itself to a local network device. This local network device contains a cache of authentication information that is used to authenticate the client device. If authentication fails, the local network device attempts to authenticate to a remote authentication server. If this authentication is successful, the locally held authentication information is updated.

There is a need to provide an improved approach to verifying an authentication feature when a connection to an authentication service cannot be secured. This need is taken into account by devices and methods according to the independent claims.

Embodiments can achieve this by using multiple authentication options. For example, a device for checking an authentication feature can use a remotely connected authentication entity to perform user authentication. If the connection to the remotely connected authentication entity is not available, for example because a radio network is not available at the location of the device, the device can check the authentication feature locally, based on the same criteria. For this purpose, the authentication entity can, for example, provide the criteria of the device. Since these criteria may be locally outdated, the device can further be designed to verify the local check by a subsequent check by the authentication entity as soon as the connection is available again. Until then, for example, authentication may be subject to reservations or, for example, only a subset of functionality may be available.

Embodiments create a device for checking an authentication feature. The device includes a communication module designed to communicate with an authentication entity via a communication connection. The device further comprises a control module designed to control the communication module. The control module is further designed to determine an availability of the communication connection with the authentication entity. The control module is further designed to remotely check the authentication feature by providing information about the authentication feature to the authentication entity and receiving information about a result of checking the authentication feature from the authentication entity if the communication connection with the authentication entity is available, or to locally check the authentication fication feature based on information about a check of the authentication feature if the communication link with the authentication entity is not available. The remote checking of the authentication feature and the local checking of the authentication feature by the control module are based on the information about the authentication feature. By locally checking the authentication feature, a (preliminary) check of the authentication feature is made possible if the connection to the authentication service is not available, for example if a radio connection is not available at this time.

In some exemplary embodiments, the control module is designed to receive the information about the verification of the authentication feature from the authentication entity. Alternatively or additionally, the control module can be designed to determine the information about the verification of the authentication feature based on the authentication feature if the remote verification is successful. Receiving the authentication feature from the authentication entity makes it possible to check whether the criteria used to check the authentication feature match; for example, a transmission of the information about the verification of the authentication feature can be combined with the transmission of the information about the result of the check. Determining the information about the verification of the authentication feature based on a successful verification of the authentication feature can reduce additional communication effort for the transmission and can be used, for example, with unique authentication methods, such as passwords or pin codes.

In some embodiments, the control module may be configured to determine the availability of communication after local testing. The control module may further be configured to verify the local checking by remotely checking the authentication feature when the communication link with the authentication entity is available. Additional verification of the local check when the communication connection to the authentication service is available further increases security, as this enables the authentication feature to be checked based on current check criteria.

In some embodiments, the control module is designed to determine authorization for a plurality of functions based on checking the authentication feature. The control module can be designed to grant authorization for the majority of functions if the remote check is successful. The control module can also be designed to grant authorization for a subset of the plurality of functions in the event of a successful local check. The control module can also be designed to grant authorization for the majority of functions after successful verification of the local check. Security can be increased through a multi-level system of authorizations, as security-critical areas, such as changing settings, can be additionally protected through verification.

In some embodiments, the control module may be configured to grant authorization for the subset of the plurality of functions for a predefined period of time, up to an event, for a trip, for a trip with a break up to a predefined length, or for a calendar period of time . In some embodiments, the control module may be configured to grant authorization for the plurality of functions for a predefined period of time, up to an event, for a trip, for a trip with a break up to a predefined length, or for a calendar period of time. Granting permissions for a limited time can increase security and create a balance between security and convenience.

In some embodiments, the control module may be configured to check the authentication feature by remote checking and by local checking if the communication link with the authentication service is available. The control module can be designed to receive the information about the verification of the authentication feature again based on the remote verification if the remote verification and the local verification give different results. Receiving the information about the verification of the authentication feature again in the event of a difference in the checks can reduce additional effort for transmitting the information about the verification of the authentication feature.

In at least some embodiments, the information about the verification of the authentication feature may be based on at least one of the group of personal identification number, PIN, password, visual pattern, biometric feature, fingerprint, voice signature and retinal image. The authentication feature can correspond to at least one element of the group of PIN, password, input of a visual pattern, input of a biometric feature, image of a fingerprint, processing of a finder's print, recording of a voice and recording of a retina. The information about the verification of the authentication feature enables the local verification of the authentication feature.

In at least some exemplary embodiments, the device can be designed to provide verification of the authentication feature for an information system of a vehicle. Due to their mobility, in some cases vehicles cannot establish a communication connection with the authentication service, for example in tunnels or underground car parks - the alternative local test can still enable the authentication feature to be checked.

In some embodiments, the device may be designed to provide the authentication feature for at least one element of the group of mobile device, pocket computer, smartphone, wearable, tablet computer or notebook. In the event of a temporarily unavailable communication connection to the authentication service, the device can enable a local check of the authentication feature.

Embodiments further provide an authentication entity device for remotely verifying an authentication feature. Remote probing refers to an entity separate from the authentication entity using remote probing by the device for the authentication entity. The device includes a communication module. The device further comprises a control module designed to control the communication module. The control module is further designed to receive information about an authentication feature via the communication module. The control module is further designed to check the authentication feature based on information about a check of the authentication feature. The control module is further designed to provide information about a result of checking the authentication feature via the communication module. By checking the authentication feature by the authentication entity, the verification of the authentication feature can be provided to a variety of devices and credentials can be used for different devices of the same user.

In at least some exemplary embodiments, the control module is further designed to verify a local check of a device for checking an authentication feature based on the information about the check of the authentication feature. Additional verification of the local check when the communication connection to the authentication service is available further increases security, as this enables the authentication feature to be checked based on current check criteria.

In at least some exemplary embodiments, the control module can further be designed to provide the information about the verification of the authentication feature via the communication module. Providing the information about the verification of the authentication feature can enable local verification by the device for checking the authentication feature.

Embodiments further create an information system for a vehicle comprising the device for checking the authentication feature, designed to check the authentication feature for the information system of the vehicle.

Embodiments further provide a method for checking an authentication feature. The method includes determining availability of a communication connection with an authentication entity. The method further includes remotely testing the authentication feature by providing information about the authentication feature to the authentication entity and receiving information about a result of testing the authentication feature from the authentication entity if the communication link with the authentication entity is available. Alternatively or additionally, the check is carried out by locally checking the authentication feature based on information about a check of the authentication feature if the communication connection with the authentication entity is not available. The remote checking of the authentication feature and the local checking of the authentication feature are based on the information about the checking of the authentication feature.

Embodiments further provide a method for an authentication entity to remotely verify an authentication feature. The method includes obtaining information about an authentication feature. The method further includes checking the authentication feature based on information about a check of the authentication feature. The method further includes providing information about a result of checking the authentication feature.

Embodiments further provide a program having program code for performing at least one of the methods when the program code is executed on a computer, a processor, a control module, or a programmable hardware component.

• 1 illustriert ein Blockdiagramm eines Ausführungsbeispiels einer Vorrichtung zum Prüfen eines Authentifikationsmerkmals;
• 1a illustriert ein Blockdiagramm eines weiteren Ausführungsbeispiels einer Vorrichtung zum Prüfen eines Authentifikationsmerkmals, ferner umfassend eine Eingabeeinheit;
• 2 illustriert ein Blockdiagramm eines Ausführungsbeispiels einer Vorrichtung zum entfernten Prüfen eines Authentifikationsmerkmals;
• 3 illustriert ein Blockdiagramm eines Ausführungsbeispiels eines Informationssystems für ein Fahrzeug umfassend eine Vorrichtung zum Prüfen eines Authentifikationsmerkmals;
• 4 illustriert ein Flussdiagramm eines Ausführungsbeispiels eines Verfahrens zum Prüfen eines Authentifikationsmerkmals; und
• 5 illustriert ein Flussdiagramm eines Ausführungsbeispiels eines Verfahrens zum entfernten Prüfen eines Authentifikationsmerkmals.

Further advantageous embodiments are described in more detail below with reference to the exemplary embodiments shown in the drawings, to which exemplary embodiments are generally but not limited overall. Show it:

• 1 illustrates a block diagram of an embodiment of an apparatus for checking an authentication feature;
• 1a illustrates a block diagram of a further exemplary embodiment of a device for checking an authentication feature, further comprising an input unit;
• 2 illustrates a block diagram of an embodiment of an apparatus for remotely verifying an authentication feature;
• 3 illustrates a block diagram of an embodiment of an information system for a vehicle comprising a device for checking an authentication feature;
• 4 illustrates a flowchart of an embodiment of a method for checking an authentication feature; and
• 5 illustrates a flowchart of an embodiment of a method for remotely checking an authentication feature.

Various embodiments will now be described in more detail with reference to the accompanying drawings, in which some embodiments are shown. In the figures, the thickness dimensions of lines, layers and/or regions may be exaggerated for clarity.

In the following description of the attached figures, which only show a few exemplary embodiments, the same reference numbers can designate the same or comparable components. Furthermore, summary reference numerals can be used for components and objects that appear multiple times in an exemplary embodiment or in a drawing, but are described together with regard to one or more features. Components or objects that are described with the same or collective reference symbols can be designed to be the same with regard to individual, several or all features, for example their dimensions, but may also be designed differently, unless something else is explicitly or implicitly stated in the description.

Although embodiments may be modified and varied in various ways, embodiments are shown in the figures as examples and are described in detail herein. It should be understood, however, that it is not intended to limit embodiments to the particular forms disclosed, but rather that embodiments are intended to cover all functional and/or structural modifications, equivalents and alternatives that are within the scope of the invention. The same reference numbers designate the same or similar elements throughout the description of the figures.

Note that an element referred to as "connected" or "coupled" to another element may be directly connected or coupled to the other element, or there may be intermediate elements. On the other hand, when an element is described as “directly connected” or “directly coupled” to another element, there are no intervening elements. Other terms used to describe the relationship between elements should be interpreted in a similar manner (e.g., “between” versus “immediately between,” “adjacent” versus “immediately adjacent,” etc.).

The terminology used herein is intended to describe particular embodiments only and is not intended to limit the embodiments. As used herein, the singular forms "a," "an," "one," and "the" are intended to include the plural forms unless the context clearly indicates otherwise. Further, it is to be clarified that expressions such as " includes", "including", "comprising", "includes", "comprising" and/or "comprising", as used herein, indicate the presence of said features, integers, steps, workflows, elements and/or components, but do not exclude the presence or addition of one or more features, integers, steps, workflows, elements, components and/or groups thereof.

Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meanings as would be assigned to them by one of ordinary skill in the art to which the embodiments pertain. Further, it should be clarified that expressions, such as those defined in commonly used dictionaries, are to be interpreted as having meaning consistent with their meaning in the context of the relevant technology, and not in an idealized or overly formal sense shall be interpreted unless expressly defined herein.

More and more technical devices in everyday life - especially apps on smartphones - are based on an interaction of online Services and local functions in the end devices that remain hidden from the user. Online services are also increasingly being used in vehicles for navigation, information and entertainment functions. However, a vehicle may not be required to have a constant internet connection (e.g. because the car is in a remote area or an underground car park with no cell phone reception). Important functions such as navigation are therefore often not online services (offline functions) or they are designed in such a way that a permanent Internet connection is not required for their use (hybrid functions). Only a few functions are implemented as conventional “pure” online services.

In some cases, the same vehicle may be used by a number of users between whom there is no trust relationship (e.g. car sharing, rental car, shared company car). In such a vehicle, functions that contain personal information of a specific vehicle user could be protected from access by other vehicle users, e.g. the display of the last destinations traveled to, the home address, the last telephone numbers dialed, personal favorite destinations, destinations predicted based on usage habits, etc. A corresponding protection mechanism, such as that provided by exemplary embodiments, can be used independently of the technical implementation of the function as an online service, purely offline function or hybrid function and even in the absence of an Internet connection.

Conventional systems can already enable remote checking of an authentication feature. When the user registers for the online service on the device, a user name and password can, for example, be entered. The online service is thus able to check the authenticity of the user and thus, for example, ensure that the service has been paid for or to prevent unauthorized access to the user's personal data such as emails by unauthorized persons. Since the combination of user name and password is checked by the online service, the solution relies on an existing internet connection at the time.

For online services, in conventional systems it is usually the vehicle that authenticates itself to the backend and not the vehicle user - which, however, has various disadvantages, e.g. when changing vehicles (no transfer of settings and services to other vehicles, no personalization of online services, etc.)

For the use in the vehicle described above, an authentication feature can be used for user authentication to protect all personal data and functions as well as the paid services, regardless of their implementation as an offline, online or hybrid function. Embodiments provide a method for verifying the authentication feature that can be used regardless of whether an Internet connection is currently available.

In at least some exemplary embodiments, the query of the authentication feature for use in the vehicle can be designed in such a way that sufficient security is guaranteed in several usage scenarios of a vehicle at the same time, but the comfort of the user is also impaired as little as possible. For security reasons, it may therefore be necessary for the authentication feature to be changed at a central location without having to have physical access to the vehicle - especially if the user had previously decided that the authentication feature would be stored in the vehicle and not queried again and he no longer has access to the car, for example because he has returned a rental car or sold his car. Changing the authentication feature can therefore take place in the online service (e.g. an authentication entity 200). 1-5 ) via a website, app or similar), the feature can in some embodiments also be checked in the corresponding user's vehicles that are not constantly online, for example by propagating the updated authentication feature.

1 illustrates a block diagram of an exemplary embodiment of a device 10 for checking an authentication feature. The device 10 can, for example, be designed to provide the verification of the authentication feature for an information system 100 of a vehicle. Alternatively or additionally, the device 10 could be designed to provide verification of the authentication feature for at least one element of the group of mobile device, pocket computer, smartphone, wearable, tablet computer or notebook.

The device includes a communication module 12, designed to communicate with an authentication entity 200 via a communication connection. The device 10 further comprises a control module 14, designed to control the communication module 12.

The control module 14 is also designed to determine the availability of the communications connection with the authentication entity 200. Determining the availability can be based, for example, on status information from the communication module 12, which indicates whether the communication connection is available, or, for example, on a connection attempt via the communication module 12.

The control module 14 is further configured to remotely check the authentication feature by providing information about the authentication feature to the authentication entity 200 and receiving information about a result of checking the authentication feature from the authentication entity 200 if the communication link with the authentication entity 200 is available, or locally Checking the authentication feature based on information about a check of the authentication feature if the communication link with the authentication entity 200 is not available. The remote checking of the authentication feature and the local checking of the authentication feature by the control module 14 are based on the information about the checking of the authentication feature.

The authentication feature can, for example, correspond to at least one element of the group of PIN, password, input of a visual pattern, input of a biometric feature, image of a fingerprint, processing of a finder's print, recording of a voice and recording of a retina. The information about the authentication feature can, for example, be based on a digital representation of the authentication feature, and can, for example, include the digital representation itself, a conversion, for example a hash, an extraction of features, and/or can be based on an encryption of the digital representation. The remote checking can be done, for example, by the authentication entity 200.

The information about the result of the test can, for example, indicate whether the test was successful. Furthermore, the information about the result of the check can also include the information about the check of the authentication feature. The control module 14 can be designed to locally store or update the information about the verification of the authentication feature based on the information about the result of the verification, for example based on newly received information about the verification of the authentication feature, on a match of the local and remote verification , or based on a mismatch. The local checking can be based, for example, on a comparison of the authentication feature or a transformation, such as a hash transformation of the authentication feature with the information about the checking of the authentication feature.

In at least some embodiments, the information about the verification of the authentication feature is based on at least one element of the group of personal identification number, PIN, password, visual pattern, biometric feature, fingerprint, voice signature and retinal image. The control module 14 can, for example, be designed to receive the information about the verification of the authentication feature from the authentication entity 200. Alternatively or additionally, the control module 14 can be designed to determine the information about the verification of the authentication feature based on the authentication feature if the remote verification is successful. The control module 14 can, for example, also be designed to receive the information about the verification of the authentication feature from an administrative entity, which further provides the information about the verification of the authentication feature to the authentication entity.

In at least some embodiments, the control module 14 may be configured to check the authentication feature by remote checking and by local checking, for example if the communication link with the authentication service is available. The control module 14 can be designed to receive the information about the verification of the authentication feature again based on the remote verification if the remote verification and the local verification produce different results.

In at least some embodiments, the control module 14 may be designed to determine the availability of the communication connection after local testing. The control module 14 can, for example, be designed to monitor when the communication connection is available again. The control module 14 may further be configured to verify the local checking by remotely checking the authentication feature when the communication link with the authentication entity 200 is available. The verification can, for example, correspond to a new, remote check of the authentication feature and a comparison as to whether the remote check is also successful.

If there is an Internet connection at this time, the authentication feature can be remotely checked against an online reference by the authentication entity 200 (so-called remote check). Otherwise it is checked against a locally stored reference (local check), provided that a suitable reference of the authentication feature is available locally (as information about the verification of the authentication feature). During the local check, the user can, if necessary, be informed of the date from which the reference of the authentication feature used is (“Enter the password you used 2 days ago now”).

The control module 14 can, for example, be designed to store the information about the verification of the authentication feature locally. The storage of the information about the verification of the authentication feature (the reference) and the transmission of the authentication feature to the online service can be protected in exemplary embodiments by security measures, for example a transmission of hash values or by using encryption. In a preferred exemplary embodiment, the information about the authentication feature cannot be provided in plain text, so that the authentication feature cannot be found out by third parties.

If a successful offline check occurs, a (temporary) release, for example a subset of authorizations, can be granted, which can possibly be revoked at a later point in time, for example based on an unsuccessful verification by the authentication entity 200. The control module 24 can for example, be designed to temporarily store the entered authentication feature for a later remote check.

If a remote check is successful, a permanent release of the majority of permissions can be granted. If only a temporary release was previously granted through a successful local check due to a lack of an internet connection, the remote check can now be carried out with the authentication feature used temporarily saved as soon as an internet connection is available.

In some exemplary embodiments, the control module 14 can be designed to also carry out a local check in the event of a remote check in order to ensure that the stored information about the check of the authentication feature is current. For example, the control module 14 can be designed to update and store the information about the verification of the authentication feature in the event of a successful remote verification. The control module 14 can, for example, be designed to determine or derive the information about the verification of the authentication feature based on the entered authentication feature, for example by means of a suitable method.

If the remote check fails but the offline check of the authentication feature is successful, the control module 14 can be designed to remove the stored information about the check of the authentication feature, for example because it is out of date. In at least some exemplary embodiments, an offline test can no longer take place until the next successful online test.

“Sharp” verification mechanisms such as PIN or passwords can be particularly popular as an authentication feature, since such input can be used to derive information about the verification of the authentication feature locally, which will provide the same results as the remote verification in future verifications. Biometric methods such as fingerprints can also be suitable, but due to the measurement inaccuracy in individual measurements, it may be possible to guarantee that the locally stored information derived from such an individual measurement about the verification of the offline reference authentication feature during examinations delivers exactly the same results as the remote verification.

Embodiments further create a device 10a, comprising a control module 14a, designed to check an authentication feature. The testing can, for example, be carried out locally or remotely, for example analogous to the local testing or the remote testing of the control module 14. The device 10a can, for example, be implemented similarly to the device 10, and can optionally also include a communication module 12a that is implemented similarly like the communication module 12. The control module 14a can be implemented similarly to the control module 14.

In at least some embodiments, the control module 14; 14a may be designed to determine authorization for a plurality of functions based on checking the authentication feature. The control module 14; 14a can, for example, be designed to grant authorization for the majority of functions in the event of a successful remote check.

In addition, the control module 14; 14a can be designed to grant authorization for a subset of the plurality of functions in the event of a successful local check. The control module 14; 14a may be designed to grant authorization for the majority of functions after successful verification of the local check. The subset of the plural of Funk For example, functions can exclude those functions that affect changes to settings. In at least some embodiments, the control module 14; 14a be designed to carry out the checking of the authentication features if a user wants to use a function of the plurality of functions and / or the subset of functions.

In at least some embodiments, the control module 14; 14a be designed, the authorization for the plurality of functions for a predefined time frame, for a predetermined event (e.g. for a trip in a vehicle), for a combination (e.g. for a trip that can be interrupted for up to 2 hours), or to be granted until revoked.

In at least some embodiments, the control module 14; 14a may be designed to grant authorization for the subset of the plurality of functions for a predefined period of time, up to an event, for a journey, for a journey with an interruption up to a predefined period of time or for a calendar period of time. Alternatively or additionally, the control module 14; 14a, for example, be designed to grant authorization for the plurality of functions for a predefined period of time, up to an event, for a trip, for a trip with an interruption up to a predefined length or for a calendar period of time. The event can be, for example, a driver change, an end to a rental agreement, a manual clearance of authorizations and/or a remotely initiated clearance of authorizations. The predefined time period can be, for example, 15 minutes, 30 minutes, one hour, two hours, three hours, six hours, twelve hours, 24 hours, or 48 hours. The calendar period can, for example, correspond to a calendar day, several calendar days, a calendar week, a calendar week or a calendar year.

In some embodiments, the control module 14; 14a can be designed to only force the authentication feature to be checked the first time a correspondingly protected function is used, but can also enable the user to check it beforehand. If the check is successful, approval can be granted and the majority of functions can now be used. If the vehicle supports multi-user operation, the clearing can only be valid for the respective user, for example. If the retransmission of an authentication feature is necessary to register with an online service, the previously used authentication feature can, for example, be automatically used again.

Granting permissions can preferably remain valid for the entire journey. In an exemplary implementation, it can then be removed again as soon as the vehicle is stationary for longer than a certain follow-up time (e.g. 2 hours) after the ignition has been switched off or when a user change has been carried out on the car (if multi-user operation is supported by the vehicle).

If the authentication feature has been successfully checked, the user can decide in some exemplary embodiments whether he would like to “remain logged in” in the vehicle. This can suppress the automatic removal of the release at the end of the trip or after a user change. Whether this option can be used may depend on the relationship of the user to the vehicle (owner, regular user, renter, ...) or whether this is permitted for the vehicle (e.g. a rental car company may prohibit it for their cars ).

The communication module 12, and an in 3 The introduced communication module 22 can correspond, for example, to a wireless or wired communication module, designed for communication via a communication protocol. The communication module 12; 22 may, for example, correspond to a communication module for a mobile radio system, for example a cellular mobile radio system, for example one of the mobile radio systems that are standardized by appropriate standardization bodies, such as the 3rd Generation Partnership Project (3GPP) group. For example, these include the Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE Radio Access Network (GERAN), the Universal Terrestrial Radio Access Network (UTRAN) or the Evolved UTRAN (E-UTRAN) , such as B. the Universal Mobile Telecommunication System (UMTS), Long Term Evolution (LTE) or LTE-Advanced (LTE-A), or mobile communications systems of other standards, such as. B. the Worldwide Interoperability for Microwave Access (WIMAX), IEEE802.16 or Wireless Local Area Network (WLAN), IEEE802.11, and generally a system based on a time domain multiple access method (Time Division Multiple Access (TDMA)), frequency domain multiple access method (Frequency Division Multiple Access (FDMA), Code Division Multiple Access (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA) or another technology or multiple access method driving based. The communication connection can, for example, correspond to a wired or wireless data connection, such as a connection via at least one of the above-mentioned communication protocols. The communication connection can, for example, use a plurality of transport media, for example based on wireless and wired sections.

For example, the authentication entity 200 may correspond to a server, a group of servers, a data center, a virtual server instance, a group of virtual server instances, or a backend system of a device or vehicle manufacturer. In exemplary embodiments, the control module 14; 14a, and an in 3 introduced control module 24, any controller or processor or a programmable hardware component. For example, the control module 14; 14a; 24 can also be implemented as software that is programmed for a corresponding hardware component. In this respect, the control module 14; 24 be implemented as programmable hardware with appropriately adapted software. Any processors, such as digital signal processors (DSPs), can be used. Embodiments are not limited to a specific type of processor. There are any processors or even several processors to implement the control module 14; 14a; 24 conceivable. The control module 14 is coupled to the communication module 12.

1a illustrates a block diagram of another embodiment of the device 10. The device 10 is implemented similarly to that in 1 shown. In addition, the device 10 includes 1a an input unit 16 designed to determine the authentication feature, which is coupled to the control module 14. The input unit 16 may, for example, correspond to a keyboard, a touch-sensitive screen, a touchscreen, a fingerprint reader, a camera, a microphone, a voice sensor, or a retina camera. The control module 14 can be designed to receive the information about the authentication feature from the input unit 16 or to determine it based on the authentication feature determined by the input unit 16.

2 illustrates a block diagram of an embodiment of an apparatus 20 for an authentication entity 200 for remotely verifying an authentication feature. The device 20 includes the communication module 22 and the control module 24, designed to control the communication module 22.

The control module 24 is further designed to receive information about an authentication feature via the communication module 22. The control module 24 can, for example, be designed to receive the information about the authentication feature from the device 10 1 ; 1a to obtain. The control module 24 is further designed to check the authentication feature based on information about a check of the authentication feature. The checking can be based, for example, on a comparison of the authentication feature or a transformation, such as a hash transformation of the authentication feature with the information about the checking of the authentication feature.

The control module 24 is further designed to provide information about a result of checking the authentication feature via the communication module 22.

In some embodiments, the control module 24 may further be designed to verify a local check of a device 10 according to the preceding claims based on the information about the check of the authentication feature. In at least some embodiments, verifying the local check corresponds to checking the authentication feature based on information about a check of the authentication feature, and providing information that indicates whether the verification/check is successful, for example as information about the result of the check.

In some embodiments, the control module 24 may further be designed to provide the information about the result of the verification of the authentication feature via the communication module 22, for example the device 10 of 1 and 1a .

3 illustrates a block diagram of an exemplary embodiment of an information system 100 for a vehicle 150 comprising the device 10 designed to check the authentication feature for the information system 100 of the vehicle. The information system 100 can, for example, correspond to an on-board information system of the vehicle 150 (also known as On-Board Unit, OBU), or an infotainment system of the vehicle 150, for example an embedded computer, which has functions for controlling vehicle functions and/or the vehicle entertainment system provides. In at least some embodiments, the vehicle 150 may, for example, be a land vehicle, a watercraft, an aircraft, a rail vehicle, a road vehicle, a car, a Off-road vehicle, motor vehicle, or truck.

4 illustrates a flowchart of an exemplary embodiment of a method for checking an authentication feature. The method includes determining 32 availability of communication with an authentication entity 200 over a communication link. The method further includes remotely checking 34 the authentication feature by providing 34a information about the authentication feature to the authentication entity 200 and receiving 34b information a result of checking the authentication feature from the authentication entity 200 if the communication link with the authentication entity 200 is available, or locally checking 36 of the authentication feature based on information about a check of the authentication feature if the communication link with the authentication entity 200 is not available. The remote checking 34 of the authentication feature and the local checking 36 of the authentication feature is based on the information about the testing of the authentication feature.

5 illustrates a flowchart of an embodiment of a method for an authentication entity 200 for checking an authentication feature. The method includes obtaining 42 information about an authentication feature. The method further includes checking 44 the authentication feature based on information about a check of the authentication feature. The method further includes providing 46 information about a result of checking the authentication feature.

A further exemplary embodiment is a computer program for carrying out at least one of the methods described above when the computer program runs on a computer, a processor or a programmable hardware component. Another embodiment is also a digital storage medium that is machine or computer readable and that has electronically readable control signals that can interact with a programmable hardware component to carry out one of the methods described above.

The features disclosed in the above description, the following claims and the attached figures can be important and implemented both individually and in any combination for the realization of an exemplary embodiment in their various configurations.

Although some aspects have been described in connection with a device, it is understood that these aspects also represent a description of the corresponding method, so that a block or a component of a device is also to be understood as a corresponding method step or as a feature of a method step. Analogously, aspects that have been described in connection with or as a method step also represent a description of a corresponding block or detail or feature of a corresponding device.

Depending on particular implementation requirements, embodiments of the invention may be implemented in hardware or in software. The implementation may be using a digital storage medium such as a floppy disk, a DVD, a Blu-Ray Disc, a CD, a ROM, a PROM, an EPROM, an EEPROM or a FLASH memory, a hard drive or other magnetic or optical memory are carried out on which electronically readable control signals are stored, which can interact or interact with a programmable hardware component in such a way that the respective method is carried out.

A programmable hardware component can be constituted by a processor, a computer processor (CPU = Central Processing Unit), a graphics processor (GPU = Graphics Processing Unit), a computer, a computer system, an application-specific integrated circuit (ASIC = Application-Specific Integrated Circuit), an integrated Circuit (IC = Integrated Circuit), a one-chip system (SOC = System on Chip), a programmable logic element or a field programmable gate array with a microprocessor (FPGA = Field Programmable Gate Array).

The digital storage medium can therefore be machine or computer readable. Some embodiments therefore include a data carrier that has electronically readable control signals that are capable of interacting with a programmable computer system or a programmable hardware component such that one of the methods described herein is carried out. An exemplary embodiment is therefore a data carrier (or a digital storage medium or a computer-readable medium) on which the program for carrying out one of the methods described herein is recorded.

In general, embodiments of the present invention can be implemented as a program, firmware, computer program or computer program product with a program code or as data be mented, wherein the program code or the data is effective to carry out one of the methods when the program runs on a processor or a programmable hardware component. The program code or the data can also be stored, for example, on a machine-readable carrier or data carrier. The program code or data may be in the form of, among other things, source code, machine code or byte code, as well as other intermediate code.

Another exemplary embodiment is also a data stream, a signal sequence or a sequence of signals which represents the program for carrying out one of the methods described herein. The data stream, the signal sequence or the sequence of signals can, for example, be configured to be transferred via a data communication connection, for example via the Internet or another network. Embodiments also include signal sequences representing data that are suitable for transmission via a network or a data communication connection, the data representing the program.

A program according to an exemplary embodiment can implement one of the methods during its implementation, for example by reading out memory locations or writing one or more data into them, whereby switching processes or other processes in transistor structures, in amplifier structures or in other electrical, optical, magnetic or components that work according to a different functional principle. Accordingly, data, values, sensor values or other information can be recorded, determined or measured by a program by reading out a memory location. A program can therefore record, determine or measure quantities, values, measurements and other information by reading out one or more memory locations, as well as cause, initiate or carry out an action by writing to one or more memory locations and control other devices, machines and components .

Reference symbol list

10

Device for checking an authentication feature

10a

Device for checking an authentication feature

12

Communication module

12a

Communication module

14

Control module

14a

Control module

16

Input unit

20

Authentication entity device for remotely verifying an authentication feature

22

Communication module

24

Control module

32

Determine

34

Remote checking

34a

Provide

34b

Recall

36

Local checking

42

Receive

44

Check

100

Information system

150

vehicle

200

Authentication entity

Claims (13)

Device (10) for checking an authentication feature, comprising a communication module (12) designed to communicate with an authentication entity (200) via a communication connection; and a control module (14) designed to: control the communication module (12), determine an availability of the communication connection with the authentication entity (200), and remotely check the authentication feature by providing and obtaining information about the authentication feature for the authentication entity (200). Information about a result of checking the authentication feature from the authentication entity (200) if the communication connection with the authentication entity (200) is available, or locally checking the authentication feature based on information about a check of the authentication feature if the communication connection with the authentication entity (200) is not is available, wherein the control module (14) is designed to determine the availability of the communication connection after local checking, and to verify the local checking by remotely checking the authentication feature when the communication connection with the authentication entity (200) is available again, wherein remote checking of the authentication feature and local checking of the authenticator tion feature by the control module (14) is based on the information about the verification of the authentication feature, wherein the control module (14) is further designed to update the information about the verification of the authentication feature based on the authentication feature if the remote checking is successful. The device (10) according to Claim 1 , wherein the control module (14) is designed to receive the information about the verification of the authentication feature from the authentication entity (200), The device (10) according to one of the preceding claims, wherein the control module (14) is designed to determine authorization for a plurality of functions based on the verification of the authentication feature, wherein the control module (14) is designed, upon a successful remote verification to grant authorization for the plurality of functions, wherein the control module (14) is designed to grant authorization for a subset of the plurality of functions in the event of a successful local check, and wherein the control module (14) is designed to grant authorization for the plurality of Functions to be granted after a successful verification of the local test. The device (10) according to Claim 3 , wherein the control module (14) is designed to grant authorization for the subset of the plurality of functions for a predefined period of time, up to an event, for a trip, for a trip with an interruption up to a predefined length or for a calendar period of time , and/or wherein the control module (14) is designed to provide authorization for the plurality of functions for a predefined period of time, up to an event, for a journey, for a journey with an interruption up to a predefined length or for a calendar period of time to concede. The device (10) according to one of the preceding claims, wherein the control module (14) is designed to check the authentication feature by remote checking and by local checking if the communication connection with the authentication service is available, and wherein the control module (14) is designed to obtain the information about the verification of the authentication feature again based on the remote verification if the remote verification and the local verification produce different results. The device (10) according to one of the preceding claims, wherein the information about the verification of the authentication feature is based on at least one element of the group of personal identification number, PIN, password, visual pattern, biometric feature, fingerprint, voice signature and retinal image, and/or wherein the authentication feature corresponds to at least one element of the group of PIN, password, input of a visual pattern, input of a biometric feature, image of a fingerprint, processing of a finder's print, recording of a voice and recording of a retina. The device (10) according to one of the preceding claims, wherein the device (10) is designed to provide the verification of the authentication feature for an information system (100) of a vehicle, or wherein the device (10) is designed to provide the verification of the authentication feature for at least one element of the group of mobile device, pocket computer, smartphone, wearable, tablet computer or notebook. Device (20) for an authentication entity (200), for remotely checking an authentication feature, comprising the device (20). a communication module (22); and a control module (24), designed to: Controlling the communication module (22), Obtaining information about an authentication feature via the communication module (22), Checking the authentication feature based on information about a check of the authentication feature, Providing information about a result of checking the authentication feature via the communication module (22), and Verifying a local test of a device (10) according to the preceding claims based on the information about the test of the authentication feature. The device (20) according to Claim 8 , wherein the control module (24) is further designed to provide the information about the result of checking the authentication feature via the communication module (22). Information system (100) for a vehicle (150) comprising the device (10) according to Claim 5 , designed to check the authentication feature for the information system (100) of the vehicle. Method for checking an authentication feature, comprising determining (32) an availability of a communication cation with an authentication entity (200) via a communication link; remotely checking (34) the authentication feature by providing (34a) information about the authentication feature for the authentication entity (200) and receiving (34b) information a result of checking the authentication feature from the authentication entity (200) if the communication connection with the authentication entity (200 ) is available, or locally checking (36) the authentication feature based on information about a check of the authentication feature if the communication link with the authentication entity (200) is not available; Determining the availability of the communication connection after the local checking, and verifying the local checking by remotely checking the authentication feature when the communication connection with the authentication entity (200) is available again, wherein the remote checking (34) of the authentication feature and the local checking (36) the authentication feature is based on the information about the verification of the authentication feature; and updating the information about the authentication feature verification based on the authentication feature if the remote verification is successful. Method for an authentication entity (200) for checking an authentication feature, the method comprising: obtaining (42) information about an authentication feature; Checking (44) the authentication feature based on information about a check of the authentication feature; Providing (46) information about a result of checking the authentication feature; and verifying a local check of a method for checking an authentication feature according to Claim 12 based on the information about the verification of the authentication feature. Program with a program code for carrying out at least one of the methods Claim 11 or 12 when the program code is executed on a computer, a processor, a control module or a programmable hardware component.

Images