Secure element, trusted mechanism, device, key management server, backend, method and computer program
By binding user information on the security elements of the user equipment and using trusted organization verification, the attack and user experience problems during digital key sharing are solved, and safe and efficient generation and use of authorized keys are achieved.
Patent Information
- Application Number
- CN202380034365.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-07-01
- Filing Date
- 2023-03-01
- Publication Date
- 2024-11-26
AI Technical Summary
During the existing digital key sharing process, an attacker may use the communication channel to attack, resulting in the digital key being rerouted. The existing authorization process uses a second factor (such as a PIN or a one-time password), affecting the user experience and failing to cover all use cases. .
By binding user information on the security element of the user device, generating an authorization key, and verifying the identification information of the security element using a trusted organization and a key management server, ensuring that the authorization key can only be generated and used by the intended device.
Improves security of the digital key sharing process, reduces attack risk, enhances user experience, and is suitable for all use cases including server application-based key deployment.
Smart Images

Figure CN119032543A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of digital identity authorization. Embodiments relate to a secure element, a trusted authority, a device, a key management server, a backend, a method and a computer program. Background Art
[0002] The authorization process enables the user of a device to enable a certain function using their device, e.g. verifying a bank transfer, verifying the generation of a digital key, etc. For example, using a digital key enables a user of a vehicle to open the vehicle particularly easily. In particular, smart access can be used to configure a user device to act as a digital key for a vehicle. To this end, the user device can pass an invitation for a digital key (also called a data key) to a friend device to configure the friend device. This allows configuring / verifying the friend device in such a way that access to the vehicle (e.g. opening, starting, etc.) is enabled via wireless communication (e.g. Bluetooth or ultra-wideband technology (UWB)).
[0003] Currently, the digital car key solution defined in the Car Connectivity Consortium (CCC) standard version 3 ([1]) standardizes an access system consisting of:
[0004] a) user equipment, such as smartphones, tablets, and software;
[0005] i) Carry a digital key embedded in a secure storage device on a smart device;
[0006] ii) providing an interface from the secure storage device to the smartphone operating system; and
[0007] iii) providing an interface from the smartphone operating system to other applications (e.g., original equipment manufacturer (OEM) applications) running on the smartphone;
[0008] b) Vehicle, allowing the user / owner of the Digital Key to operate certain vehicle functions; and
[0009] c) Backend systems that interconnect smart devices with vehicles, allowing digital keys to be shared and managed and providing additional services.
[0010] Under the CCC standard, version 2, a digital key for a specific vehicle can be shared by an entity with appropriate administrative rights over that vehicle (also known as a “sharer” / “owner”) to entities that meet the digital key specification and have been whitelisted / authenticated as recipients by the vehicle OEM (device certificate authority (CA) signed by the device OEM CA and cross-signed by the vehicle CA).
[0011] Key sharing is a multi-step process where the sharer first configures the parameters of the digital key to be created (a "key creation request") and passes it to a friend's device (also called a "sharee"). After the sharee creates the key and exports an "endpoint certificate" that includes the parameters for creating the digital key, the sharer proves that the key has been created according to the key creation request by signing the endpoint certificate with its private key (a "key sharing proof"). However, before the sharer signs the proof, only verification is performed on specific key configuration parameters. Therefore, an attacker could potentially reroute the digital key to the attacker device by exploiting an attack on the sharee or on the communication channel used to transmit the invitation / key creation request.
[0012] The currently defined authorization process to prevent these attacks uses a second factor (e.g., a PIN / one-time password entered by the vehicle or device) that has to be delivered out-of-band (e.g., via a voice call) from the sharer to the sharee. However, this may negatively impact the user experience and does not cover all use cases (e.g., app-based key provisioning via a server). Therefore, the authorization process between the sharer and the sharee may need to be improved.
[0013] Therefore, it is found that authorization can be improved by using a signal including information indicating that the user is bound to the (shared) security element. For example, a trusted institution can perform user binding so that the security element is associated with the user. For example, user binding is performed by identifying the security element of the user's smartphone as the user's security element. In this way, an invitation to generate an authorization key can be bound to the security element. For example, a sharer can receive information about a (shared) security element associated with a user (e.g., a friend) who should receive a digital key, and can generate and transmit an invitation that can only be used to generate a signable authorization key by a security element associated with the friend. Therefore, the sharer can check whether the key is indeed created by the intended sharee, for example, on a device associated with the intended recipient. Summary of the invention
[0014] The example provides a security element for a user device for improving the authorization process, including an interface circuit system configured to communicate with a trusted institution and a processing circuit system configured to control the interface circuit system and receive a signal from the trusted institution. The signal includes information indicating that the user is bound to the security element. In this way, the security element can be associated with the user and / or the user's unique data, for example, associated with an identity, a phone number, a bank account, and the security element can be notified of the user binding that has been performed.
[0015] In an example, the processing circuit system may also be configured to receive an invitation signal from a device, the invitation signal including information indicating an invitation to generate an authorization key, and generate an authorization key based on the received signal. The authorization key may be a digital key. In this way, the authorization key, for example, a digital key for a vehicle, may be generated by a security element. The check on the generated authorization key may be performed by utilizing the identification information bound by the user.
[0016] The example provides a trusted mechanism for improving the authorization process, including an interface circuit system configured to communicate with a security element and a processing circuit system configured to control the interface circuit system and receive an identifier signal from the security element. The identifier signal includes information indicating an identifier of the security element. In addition, the processing circuit system is configured to perform user binding of the security element. In this way, the security element can be bound to different users.
[0017] In an example, the processing circuit system may be further configured to store information about the user binding in an instance certificate authority certificate. In this way, the instance certificate authority certificate may be used to check the secure element used to generate the authorization key.
[0018] The example provides a device for improving the authorization process, including an interface circuit system configured to communicate with a database and a processing circuit system configured to control the interface circuit system. In addition, the processing circuit system is configured to transmit a request for identification information of a security element to the database and receive an identification signal including information indicating the identification information from the database. The identification information may include at least one of an identifier of the security element (e.g., a public key of a key pair (also including a private key) generated by the security element) or user binding information (e.g., an identifier associated with a user / owner). In this way, the device can request identification information from a database (e.g., a trusted authority), which can be used to verify the generation process of the authorization key.
[0019] In an example, the interface circuit system may also be configured to communicate with a security element (e.g., a security element as described above). The processing circuit system may also be configured to transmit an invitation signal to the security element, the invitation signal including information indicating an invitation to generate an authorization key; receive a key signature request from the security element, the key signature request including information about the security element for generating the authorization key; and check whether the information about the security element matches the identification information, and if the information matches, then indicate the authorization key as valid. In this way, the device (e.g., a sharer) can verify the generated authorization key for the security element used to generate the authorization key.
[0020] In an example, the device may further include a storage device. The database from which identification information is to be requested may be stored in the storage device. In this way, the device may request identification information in an easy manner, for example, without wirelessly connecting to an external database (such as a server).
[0021] In an example, the interface circuit system may also be configured to communicate with a key management server. The processing circuit system may also be configured to transmit a request to create an invitation signal to the key management server. The request includes information indicating the identification information, and receives a request response signal from the key management server including information indicating the invitation signal. In this way, the task of generating the invitation signal may be transferred to the key management server.
[0022] The example provides a key management server for improving the authorization process, including an interface circuit system configured to communicate with a security element and a device according to one of claims 5-8 and a processing circuit system configured to control the interface circuit system. In addition, the processing circuit system is configured to receive a request to create an invitation signal from the device. The request includes information indicating identification information. In addition, the processing circuit system is configured to transmit a request response signal including information indicating the invitation signal, receive a key signature request including information about the security element for generating an authorization key from the security element, and compare the security element information with the identification information. In this way, the key management server can perform a signature of an authorization key generated by the security element.
[0023] The example provides a backend for improving the authorization process, including an interface circuit system configured to communicate with a security element device and a device according to one of claims 5-8 and a processing circuit system configured to control the interface circuit system. In addition, the processing circuit system is configured to receive an identification signal including information indicating identification information from the device, receive a key signature request including information about the security element for generating an authorization key from the security element, and compare the security element information with the identification information. In this way, the backend can perform a signature of an authorization key generated by the security element.
[0024] An example provides a method for improving an authorization process, comprising transmitting a request for identification information of a security element to a database, and receiving an identification signal including information indicating the identification information from the database. The identification information may include at least one of an identifier of the security element (e.g., a public key of a key pair (also including a private key) generated by the security element) or user binding information. In addition, the method includes receiving a key signature request including information about the security element used to generate an authorization key from the security element, and comparing the security element information with the identification information. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Some examples of apparatus, methods and / or computer programs will be described below, by way of example only, and with reference to the accompanying drawings, in which:
[0026] Figure 1 A block diagram illustrating an example of a secure element;
[0027] Figure 2 A block diagram illustrating an example of a trusted authority;
[0028] Figure 3 A block diagram showing an example of a device;
[0029] Figure 4 A block diagram illustrating an example of a key management server;
[0030] Figure 5 A block diagram showing an example of a backend;
[0031] Figure 6a-6c A flow chart illustrating an example of a method 600 for authorizing a key sharing process; and
[0032] Figure 7 An example of a method is shown. DETAILED DESCRIPTION
[0033] Various example embodiments will now be described more fully with reference to the accompanying drawings, in which some example embodiments are illustrated. In the accompanying drawings, the thickness of lines, layers or regions may be exaggerated for clarity. Optional components may be illustrated using broken lines, dashed lines or dotted lines.
[0034] Thus, while the example embodiments are capable of various modifications and alternative forms, embodiments thereof are shown by way of example in the drawings and will be described in detail herein. However, it should be understood that there is no intent to limit the example embodiments to the particular forms disclosed, but on the contrary, the example embodiments are intended to cover all modifications, equivalents, and alternatives within the scope of the invention. Throughout the entire description of the drawings, like reference numerals refer to like or similar elements.
[0035] As used herein, the term "or" refers to a non-exclusive or, unless otherwise indicated (e.g., "otherwise" or "or alternatively"). In addition, as used herein, words used to describe relationships between elements should be broadly interpreted to include direct relationships or the presence of intermediate elements, unless otherwise indicated. For example, when an element is referred to as being "connected" or "coupled" to another element, the element may be directly connected or coupled to the other element, or there may be intermediate elements. In contrast, when an element is referred to as being "directly connected" or "directly coupled" to another element, there are no intermediate elements. Similarly, words such as "between," "adjacent," etc. should be interpreted in a similar manner.
[0036] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. As used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that when used herein, the terms "include" or "comprise" specify the presence of the features, integers, steps, operations, elements, or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or groups thereof.
[0037] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the example embodiments belong. It will also be understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning consistent with the meaning of the terms in the context of the relevant art, and should not be interpreted as an idealized or overly formal meaning unless explicitly defined herein.
[0038] Figure 1 A block diagram of an example of a security element 30 is shown. The security element 30 of a user device for improving the authorization process includes an interface circuit system 32 configured to communicate with a trusted authority and a processing circuit system 34 configured to control the interface circuit system and receive a signal from the trusted authority. The signal includes information indicating that the user is bound to the security element 30. In this way, the security element 30 can be associated with the user and / or the user's unique data, for example, associated with an identity, a phone number, a bank account, and the security element 30 can be notified of the user binding that has been performed.
[0039] For example, user binding can be a binding process in which a user of a security element 30 (e.g., a user of a user device including the security element 30, e.g., a sharee) can be bound to the security element 30. For example, user binding can allow the user of the user device to be clearly identified. For example, during user binding, a key pair (e.g., including a public key and a private key) can be generated in the security element 30. The security element can transmit the public key to a trusted authority. The trusted authority can generate a certificate to indicate that the public key (and the corresponding private key) has been generated by the processing circuit system 34 of the security element 30.
[0040] The user of the user device may be the owner of the user device. Optionally or alternatively, the user of the user device may be a person who can use the user device, for example by unlocking the user device, storing personal information on the user device. For example, multiple persons may be designated as users of the user device. In this case, the user binding will include information about each of the multiple persons.
[0041] For example, to perform user binding, unique information about the user of the user device may be required, such as an email address, a phone number, an identity certificate. Using this information, the user binding can assign the security element 30 of the user device to the user. Thus, the user binding can allow the user (or users), such as the owner, of the user device to be clearly identified.
[0042] Therefore, by utilizing user binding, the security element 30 can be assigned to the user, and it can be checked whether the security element 30 used to generate the authorization key is the security element 30 that is intended to generate the authorization key. In addition, by transmitting a reception signal from a trusted institution, the user device can be notified of the executed user binding. In this way, when an invitation signal including information indicating an invitation to generate the authorization key is received, the user device can be enabled to generate the authorization key.
[0043] In an example, the processing circuit system 34 may also be configured to receive an invitation signal from a device including information indicating an invitation to generate an authorization key, and generate an authorization key based on the received signal. The authorization key may be a digital key. In this way, the security element 30 may generate an authorization key, for example, a digital key for a vehicle.
[0044] For example, the user device may be a communication device within the meaning of a corresponding communication standard for mobile communication, e.g. a mobile phone such as a smartphone, or another type of mobile communication device such as a smart watch, a notebook, a tablet or autonomous augmented reality glasses.
[0045] like Figure 1 As shown in , the corresponding interface circuit system 32 is coupled to the corresponding processing circuit system 34 at the security element 30. In the example, the processing circuit system 34 can be implemented using one or more processing units, one or more processing devices, any components for processing (such as processors, computers, or programmable hardware components that can operate with corresponding adapted software). Similarly, the functions of the processing circuit system 34 can also be implemented with software, which is then executed on one or more programmable hardware components. Such hardware components may include general-purpose processors, digital signal processors (DSPs), microcontrollers, etc. The processing circuit system 34 is capable of controlling the interface circuit system 32 so that any data transmission occurring through the interface circuit system 32 and / or any interaction that the interface circuit system 32 may involve can be controlled by the processing circuit system 34.
[0046] In an embodiment, the secure element 30 may include a memory and at least one processing circuitry 34 operably coupled to the memory.
[0047] In an example, the interface circuit system 32 may correspond to any component for obtaining, receiving, transmitting or providing analog or digital signals or information, for example, any connector, contact, pin, register, input port, output port, conductor, channel, etc. that allows providing or obtaining signals or information. The interface circuit system 32 may be wireless or wired, and it may be configured to communicate with another internal or external component, for example, to transmit or receive signals, information.
[0048] The secure element 30 may be a microprocessor, a graphics processor unit (GPU), an application specific integrated circuit (ASIC), an integrated circuit (IC), or the like.
[0049] Further details and aspects will be mentioned in conjunction with the embodiments described below. Figure 1 The examples shown in may include one or more optional additional features corresponding to one or more aspects mentioned in conjunction with the proposed concept or below (e.g., Figure 2-7 ) described in one or more examples.
[0050] Figure 2 A block diagram of an example of a trusted authority 10 is shown. The trusted authority 10 for improving the authorization process includes an interface circuit system 12 configured to communicate with a security element, and a processing circuit system 14 configured to control the interface circuit system 12 and receive an identifier signal from the security element. The identification information may include at least one of an identifier of the security element (e.g., a public key of a key pair (also including a private key) generated by the security element) or user binding information. In addition, the processing circuit system 14 is configured to perform user binding of the security element. In this way, the user binding of the security element can be performed by the trusted authority 10. By sharing information about user binding, the trusted authority 10 can make (e.g., as described in detail about the user binding) Figure 3 The device is capable of checking whether the secure element intends to generate an authorization key (e.g., by transmitting an invitation signal to the intended secure element) or not to generate an authorization key (e.g., because the invitation signal has been redirected or forwarded). The trusted authority 10 (also called a trusted third party) can be an entity, such as a server, a backend, a facilitator between two parties (e.g., Figure 3 equipment and Figure 1 devices that interact with each other using a secure element (a third party).
[0051] In an example, the processing circuit system 14 can also be configured to store information about user binding in an instance certificate authority certificate. The instance CA certificate can include an identifier of a user of a user device. The identifier can be associated with information (such as an email address, a phone number, an ID card) that allows identification of the owner of the security element. The identifier can be obtained by user account binding. The processing circuit system 14 can perform user account binding before performing user binding. For example, an identifier from a user account binding can be used for user binding, for example, to associate a public key received from a security element with an identifier (for example, information that allows identification of the owner of the security element). For example, the processing circuit system 14 can perform user account binding by generating an identifier that allows association with the user based on the user's information (for example, an email address, a phone number, an ID card). In this way, the security element used to generate an authorization key can be checked by using an instance CA certificate. The instance CA certificate can include a public key and an identifier (information related to the user) of a security element.
[0052] For example, in the context of a digital key for a vehicle, information about the user binding may be incorporated into the instance CA certificate described in [3] (e.g., in FIG. 6-5 : key creation data is transmitted to the device). The instance CA certificate may be signed by the device OEM CA, as described in Listing 15-15 in [1]. In this way, the trusted authority 10 may incorporate the user binding information of the secure element to the user into the instance CA certificate known from [1]. Thus, the (new) instance CA certificate may be used to check whether an authorized key has been generated by the intended user (bound to the secure element).
[0053] Optionally, the trusted authority 10 may communicate information about the user binding (e.g., an instance CA certificate) to other entities (e.g., a backend, a smartphone, etc.) to allow the other entities to act as the trusted authority 10, for example, using a whitelist including the information received from the trusted authority 10. In this way, the other entities may be configured in advance, for example, by storing a whitelist of secure elements with associated users.
[0054] like Figure 2As shown in , the corresponding interface circuit system 12 is coupled to the corresponding processing circuit system 14 at the trusted institution 10. In the example, the processing circuit system 14 can be implemented using one or more processing units, one or more processing devices, any component for processing (such as a processor, a computer, or a programmable hardware component that can operate with corresponding adapted software). Similarly, the functions of the processing circuit system 14 can also be implemented in software, which is then executed on one or more programmable hardware components. Such hardware components may include a general-purpose processor, a digital signal processor (DSP), a microcontroller, etc. The processing circuit system 14 is capable of controlling the interface circuit system 12 so that any data transmission occurring through the interface circuit system 12 and / or any interaction that the interface circuit system 12 may involve can be controlled by the processing circuit system 14.
[0055] In an embodiment, trusted authority 10 may include a memory and at least one processing circuitry 14 operatively coupled to the memory and configured to perform the methods mentioned below.
[0056] In an example, the interface circuit system 12 may correspond to any component for obtaining, receiving, transmitting or providing analog or digital signals or information, such as any connector, contact, pin, register, input port, output port, conductor, channel, etc. that allows providing or obtaining signals or information. The interface circuit system 12 may be wireless or wired, and may be configured to communicate with another internal or external component, such as transmitting or receiving signals, information.
[0057] The trusted authority 10 may be a computer, a server, a processor, a control unit, a (field) programmable logic array ((F)PLA), a (field) programmable gate array ((F)PGA), a graphics processor unit (GPU), an application specific integrated circuit (ASIC), an integrated circuit (IC), or a system on a chip (SoC) system.
[0058] Further details and aspects will be mentioned in conjunction with the embodiments described above and / or below. Figure 2 The examples shown in may include one or more optional additional features corresponding to one or more aspects mentioned in conjunction with the proposed concept or above (e.g., Figure 1 ) and / or below (for example, Figure 3-7 ) described in one or more examples.
[0059] Figure 3An example of a block diagram of a device 50 is shown. The device 50 for improving the authorization process includes an interface circuit system 52 configured to communicate with a database and a processing circuit system 54 configured to control the interface circuit system 52. In addition, the processing circuit system 54 is configured to transmit a request for identification information of the security element to the database and receive an identification signal including information indicating the identification information from the database. The identification information may include at least one of an identifier of the security element (e.g., a public key of a key pair (also including a private key) generated by the security element) or user binding information. The identifier of the security element may be a public key in a key pair with a private key generated by the security element. The user binding information may include information of a user binding that has been performed, for example, by a trusted authority, as referenced in Figure 2 Thus, by incorporating user binding information into the signal, it is possible to enable the device 50 (eg, the sharer) to check whether the authorization key has been received by the expected security element (eg, reference Figure 1 The security element described above is generated.
[0060] For example, the device may be a communication device for mobile communication within the meaning of a corresponding communication standard, for example a mobile phone, such as a smartphone, or another type of mobile communication device, such as a smart watch, a notebook computer, a tablet computer or autonomous augmented reality glasses. Alternatively, the device may be a server, such as a backend.
[0061] The database may be an identity management database. The identity management database may be implemented by, for example, a device OEM or a third party of the device 50. For the identity management database, user information (e.g., email address, phone number, identity certificate, etc.) may be mapped to an account ID. In this way, a clear assignment of a user to a security element may be provided. The database may be used for specific use cases, for example, for generating authorized keys, such as digital keys for vehicles. Alternatively, an existing identity management database may be reused, for example, by extending the database by incorporating new account IDs. For example, a user may have purchased a smartphone with a security element. Information about the smartphone and the assigned user (e.g., determined by user binding) may be stored in the identity management database. Therefore, a database may be used to introduce identification information, such as account ID, that is specific to a use case (e.g., digital car key generation for a vehicle).
[0062] The database may consist of a trusted authority, or may be a trusted authority, e.g. Figure 2 Alternatively, the database may be stored on the smartphone, in a backend, for example, to act as a whitelist.
[0063] The device 50 can request identification information from the database. Therefore, the device 50 can request identification information as needed. For example, the user of the device 50 (e.g., the sharer) may want to provide a friend with access to a vehicle, so that an authorization key (e.g., a digital key) may need to be generated. Therefore, before transmitting an invitation signal to the user device of the friend (e.g., the sharee), the sharer 50 can request an account ID token (e.g., onetimeAccountldHash (one-time account ID hash value) from the identity management database. The requested account ID token can be associated with the intended use case (e.g., generating a digital car key for a vehicle). The request can be transmitted through a trusted channel. The sharer 50 can receive the sharee's account ID, especially the account ID of the sharee's security element, which can be used to sign the received digital key after receiving the generated digital key from the sharee. In this way, the sharer 50 can check the generated digital key before signing the digital key based on the user binding information of the security element. Therefore, a check can be performed to see whether the digital key has been generated by the intended sharee.
[0064] After receiving the identification signal, the sharer 50 may initiate a key sharing process including generating a digital key. The key sharing process may be performed according to FIG. 11-1: “Details of the key sharing process between the owner and the friend device after establishing a channel in [1]”.
[0065] In an example, the interface circuit system can be further configured to communicate with a security element (e.g., as described in reference Figure 1 Processing circuit system 54 may be further configured to transmit an invitation signal including information indicating an invitation to generate an authorization key to the security element, receive a key signature request including information about the security element for generating the authorization key from the security element, and check whether the information about the security element matches the identification information, and if the information matches, indicate the authorization key as valid.
[0066] The invitation signal may be the same as step 3. Sending invitation=urlLink and receiving the key signing request may be the same as step 6. UpdateMailbox(payload=sharingKeySigningRequest, notificationToken) is from Figure 11-1 in [1]. Therefore, the process from sending the invitation signal to the sharee to receiving the generated digital key at the sharer 50 may be the same as the process described in [1].
[0067] In addition, before signing the key signing request, the sharer 50 can verify whether the sharee instanceCA certificate has been signed by a database, for example, a device OEM CA cross-signed by a vehicle OEM. In this way, the sharer 50 can check whether the accountID in the sharee instanceCA certificate matches the account ID of the intended recipient. Therefore, only the authorization key generated by the intended sharee can be signed by the sharer 50. Therefore, a forwarded invitation signal received by another security element that does not include the correct user binding (and is therefore not associated with the instance CA certificate of the database) will not result in the generation of an authorization key to be signed by the sharer 50, because the information received from the database does not match the information received from the key signing request. In this way, a security element that is more difficult to attack than a communication channel or a separate device can be used to additionally protect uncertain communications between different devices.
[0068] In the example, the device 50 may also include a storage device. The database from which identification information is requested may be stored in the storage device. Thus, a third party may utilize information generated by user binding. For example, user binding for digital key deployment by a third-party application (e.g., a car sharing application) installed on the smart device of the sharer may utilize identification information generated, for example, by a trusted authority. The third-party application may generate and retrieve an instance CA certificate from the database through a dedicated application programming interface (API) in the smartphone operating system. In addition, the third-party application may link this instance CA certificate to the user account of the application. Whenever an authorized key is to be deployed to a device on which a third-party application is installed, an instance CA certificate or accountID may be used to ensure that the authorized key is deployed to the correct device.
[0069] In an example, the interface circuit system can be further configured to communicate with a key management server. The processing circuit system 54 can be further configured to transmit a request to create an invitation signal to the key management server. The request includes information indicating identification information, and receives a request response signal including information indicating the invitation signal from the key management server. In this way, the task of generating the invitation signal can be transferred to the key management server (see also FIG. 6).
[0070] Alternatively, to provide adequate privacy, a use case specific accountID hash value and a one-time accountID hash value calculated from the account ID and a random number can be used instead of using the accountID. In this way, privacy can be increased.
[0071] like Figure 3As shown in , the corresponding interface circuit system 52 is coupled to the corresponding processing circuit system 54 at the trusted institution 50. In the example, the processing circuit system 54 can be implemented using one or more processing units, one or more processing devices, any component for processing (such as a processor, a computer, or a programmable hardware component that can operate with corresponding adapted software). Similarly, the functions of the processing circuit system 54 can also be implemented in software, which is then executed on one or more programmable hardware components. Such hardware components may include a general-purpose processor, a digital signal processor (DSP), a microcontroller, etc. The processing circuit system 54 is capable of controlling the interface circuit system 52 so that any data transmission occurring through the interface circuit system 52 and / or any interaction that the interface circuit system 52 may involve can be controlled by the processing circuit system 54.
[0072] In an embodiment, trusted authority 50 may include a memory and at least one processing circuitry 54 operably coupled to the memory and configured to perform the methods mentioned below.
[0073] In an example, the interface circuit system 52 may correspond to any component for obtaining, receiving, transmitting or providing analog or digital signals or information, such as any connector, contact, pin, register, input port, output port, conductor, channel, etc. that allows providing or obtaining signals or information. The interface circuit system 52 may be wireless or wired, and it may be configured to communicate with another internal or external component, such as transmitting or receiving signals, information.
[0074] The trusted authority 50 may be a computer, a server, a processor, a control unit, a (field) programmable logic array ((F)PLA), a (field) programmable gate array ((F)PGA), a graphics processor unit (GPU), an application specific integrated circuit (ASIC), an integrated circuit (IC), or a system on a chip (SoC) system.
[0075] Further details and aspects will be mentioned in conjunction with the embodiments described above and / or below. Figure 3 The examples shown in may include one or more optional additional features corresponding to one or more aspects mentioned in conjunction with the proposed concept or above (e.g., Figure 1-2 ) and / or below (for example, Figure 4-7 ) described in one or more examples.
[0076] Figure 4 1 shows a block diagram of an example of a key management server 90. The key management server 90 for improving the authorization process includes a key management server configured to communicate with (for example, as shown in reference Figure 1 The safety element and (for example, as described in reference Figure 3The interface circuit system 92 for communicating with the device described above, and the processing circuit system 94 configured to control the interface circuit system 92. In addition, the processing circuit system 94 is configured to receive a request to create an invitation signal from the device. The request includes information indicating identification information. In addition, the processing circuit system 94 is configured to transmit a request response signal including information indicating the invitation signal, receive a key signature request including information about the security element for generating an authorization key from the security element, and compare the security element information with the identification information. In this way, the key management server can perform a signature on the authorization key generated by the security element. Therefore, it is not only the reference Figure 3 The described device (e.g., the sharer) can sign the authorization. Moreover, the key management server 90 is enabled to check whether the authorization key has been generated by the expected security element of the sharee. In addition, if the check matches, the key management server can sign the generated authorization key.
[0077] like Figure 4 As shown in , the corresponding interface circuit system 92 is coupled to the corresponding processing circuit system 94 at the trusted institution 90. In the example, the processing circuit system 94 can be implemented using one or more processing units, one or more processing devices, any components for processing (such as processors, computers, or programmable hardware components that can operate with corresponding adapted software). Similarly, the functions of the processing circuit system 94 can also be implemented in software, which is then executed on one or more programmable hardware components. Such hardware components may include general-purpose processors, digital signal processors (DSPs), microcontrollers, etc. The processing circuit system 94 is capable of controlling the interface circuit system 92 so that any data transmission occurring through the interface circuit system 92 and / or any interaction that the interface circuit system 92 may involve can be controlled by the processing circuit system 94.
[0078] In an embodiment, trusted authority 90 may include a memory and at least one processing circuitry 94 operatively coupled to the memory and configured to perform the methods mentioned below.
[0079] In an example, the interface circuit system 92 may correspond to any component for obtaining, receiving, transmitting or providing analog or digital signals or information, such as any connector, contact, pin, register, input port, output port, conductor, channel, etc. that allows providing or obtaining signals or information. The interface circuit system 92 may be wireless or wired, and it may be configured to communicate with another internal or external component, such as sending or receiving signals, information.
[0080] The trusted authority 90 may be a computer, a server, a processor, a control unit, a (field) programmable logic array ((F)PLA), a (field) programmable gate array ((F)PGA), a graphics processor unit (GPU), an application specific integrated circuit (ASIC), an integrated circuit (IC), or a system on a chip (SoC) system.
[0081] Further details and aspects will be mentioned in conjunction with the embodiments described above and / or below. Figure 4 The examples shown in may include one or more optional additional features corresponding to one or more aspects mentioned in conjunction with the proposed concept or above (e.g., Figure 1-3 ) and / or below (for example, Figure 5-7 ) described in one or more examples.
[0082] Figure 5 A block diagram of an example of a backend 70 is shown. The backend 70 for improving the authorization process includes a backend configured to communicate with (e.g., as shown in reference Figure 1 The safety element and (for example, as described in reference Figure 3 The backend 70 includes an interface circuit system 72 for communicating with a device (described above), and a processing circuit system 74 configured to control the interface circuit system 72. In addition, the processing circuit system 74 is configured to receive an identification signal including information indicating identification information from a security element from the device, receive a key signature request including information about the security element for generating an authorization key from the security element, and compare the security element information with the identification information. In this way, the backend 70 can perform a signature on the authorization key generated by the security element. For example, the backend can be an alternative to the key management server as described above.
[0083] like Figure 5 As shown in , the corresponding interface circuit system 72 is coupled to the corresponding processing circuit system 74 at the trusted institution 70. In the example, the processing circuit system 74 can be implemented using one or more processing units, one or more processing devices, any components for processing (such as processors, computers, or programmable hardware components that can operate with corresponding adapted software). Similarly, the functions of the processing circuit system 74 can also be implemented in software, which is then executed on one or more programmable hardware components. Such hardware components may include general-purpose processors, digital signal processors (DSPs), microcontrollers, etc. The processing circuit system 74 is capable of controlling the interface circuit system 72 so that any data transmission occurring through the interface circuit system 72 and / or any interaction that the interface circuit system 72 may involve can be controlled by the processing circuit system 74.
[0084] In an embodiment, trusted authority 70 may include a memory and at least one processing circuitry 74 operably coupled to the memory and configured to perform the methods mentioned below.
[0085] In an example, the interface circuit system 72 may correspond to any component for obtaining, receiving, transmitting or providing analog or digital signals or information, such as any connector, contact, pin, register, input port, output port, conductor, channel, etc. that allows providing or obtaining signals or information. The interface circuit system 72 may be wireless or wired, and it may be configured to communicate with another internal or external component, such as sending or receiving signals, information.
[0086] The trusted authority 70 may be a computer, a server, a processor, a control unit, a (field) programmable logic array ((F)PLA), a (field) programmable gate array ((F)PGA), a graphics processor unit (GPU), an application specific integrated circuit (ASIC), an integrated circuit (IC), or a system on a chip (SoC) system.
[0087] Further details and aspects will be mentioned in conjunction with the embodiments described above and / or below. Figure 5 The examples shown in may include one or more optional additional features corresponding to one or more aspects mentioned in conjunction with the proposed concept or above (e.g., Figure 1-4 ) and / or one or more of the examples described below (e.g., Figures 6-7).
[0088] Figure 6a-6c A flow chart illustrating an example of a method 600 of authorizing a key sharing process. Figure 6a An example of an authorized key sharing process is shown, which involves a sharer 610a (e.g., as shown in FIG. Figure 3 Devices described), (account) database 620a (e.g., as referenced Figure 2 The described trusted authorities, such as device OEMs) and sharees 630 (eg, user devices including smartphones).
[0089] Before starting the authorization key generation by transmitting the invitation signal, the sharer 610a may request information about the sharee 630 to which the sharer 610a wishes to direct the authorization key. In this way, the sharer 630 may receive information about the intended sharee 630 from the database 620a. In 640, the sharer 610a may transmit a request for identification information of the security element of the sharee 630 to the database 620a. The request may include data indicating getAccountldHash, or may be getAccountldHash. The user data of the security element of the sharee 630 that may be requested by the request may be determined by the user binding as described above. For example, the requested data may include information indicating the user's email address, the user's phone number, the user's ID number, the public key of the sharee 630, a specific use case, and the vehicle OEM. The database 620a may respond to the request by transmitting an identification signal including information indicating the identification information to the sharer 610a in 650. The identification signal may include or may be OnetimeAccountldHash, nonce (random number) (to increase privacy) or InstanceCACert, such as AccountIDHash. For example, OnetimeAccountldHash=hash(AccountIdHash, nonce), where AccountldHash=hash(iCouldAccountId, vehicleOEM=vehicle manufacturer). The identification information may include at least one of an identifier of a security element (e.g., a public key of a key pair (also including a private key) generated by the security element) or user binding information. Thus, the sharer 610a receives identification information from the database 620a, which may be used to improve the authorization key signature.
[0090] In 660, according to [1], the sharer 610a transmits an invitation signal to the sharee 630. In addition, in 665, authorization key creation is performed, for example, the sharee generates an authorization key, such as a digital key, according to [1]. In 670, the sharee 630 transmits a key signing request to the sharer 610a according to [1].
[0091] In 675, the sharer 610a can check whether the information about the security element matches the identification information received from the database 620. For example, the sharer can check whether the hash (accountIdHash, nonce) from the instanceCA matches the OnetimeAccountldHash. If the two match, the sharer 610 can proceed as usual, such as signing the generated authorization key from the sharee 630, otherwise the sharer 610 may not sign the authorization key and can end the key generation process without signing the generated authorization key. Therefore, by verifying the information about the security element using the identification information provided by the database 620a, the signature of the generated authorization key (e.g., a digital key) can be improved. If the identification information matches the information about the security element, the generated authorization key can be indicated as valid, for example, the signature can be performed by the sharer 610a. In this way, the sharer can use the identification information received from the database 620a to compare the generated authorized security element with the expected security element that the invitation signal has addressed.
[0092] In 680, according to [1], a MailboxImportRequest is transmitted from the sharer 610a to the sharee 630.
[0093] Figure 6b Another example of an authorized key sharing process is shown, which involves a sharer 610b (e.g., a backend of a car sharing provider), an (account) database 620 (e.g., as shown in FIG. Figure 2 The described trusted authority, such as a device operating system (OS), a sharee 630 (eg, a user device including a smart phone), and a user device 635 including a storage device storing a car sharing application. Figure 6a In contrast, at 640, a request for identification information is transmitted from the user's smartphone to the device OS 620b. The device OS 620b may have a storage medium in which a database (e.g., a lookup table) is stored, the database including information about the secure element and the user bound to the secure element. For example, the device OS may have received the database from a trusted authority, such as reference Figure 2 As described, and thus can act as a trusted authority, for example based on a whitelist.
[0094] Thus, the device OS 620 may transmit an identification signal including information indicating identification information to the user device 635 in 650. The user device 635 may forward the identification information to the sharer 620b in 655. In this way, the sharer 620b (e.g., backend 620b) may be enabled to check whether the information about the security element matches the identification information received from the database. Thus, user binding for digital key deployment by a third-party application (e.g., a car sharing application) installed on the sharer's user device 635 may utilize identification information generated, for example, by a trusted authority.
[0095] Figure 6a An example of an authorized key sharing process is shown, which involves a sharer 610a (e.g., as shown in FIG. Figure 3 Devices described), (account) database 620a (e.g., as referenced Figure 2 The described trusted authority, such as a device OEM) and a sharee 630 (eg, a user device including a smartphone). Figure 6c In comparison, a repeater 632 and a key management server 634 are also involved. In 651, the sharer 630 transmits a requestKey (including, for example, OnetimeAccountldHash, nonce) to the key management server 634. The key management server 634 can relay this request to the repeater 632 in 652, and can receive a requestKey response signal from the repeater 632 in 653. In 654, the key management server 634 transmits the requestKey response to the sharer. The sharer 610 sends an invitation signal to the sharee 630 in 660, and a key signature request is transmitted from the sharee 630 to the key management server 634 in 670. In 675, the key management server 634 can check whether the information about the security element matches the identification information received from the database 620, and in 680, a MailboxImportRequest is transmitted from the key management server 634 to the sharee 630 according to [1]. Therefore, the check on the authorization key generated by the signature can be performed by the key management server 634 instead of the sharer 610.
[0096] More details and aspects will be mentioned in conjunction with the embodiments described above and / or below. The example shown in FIG. 6 may include one or more optional additional features, which correspond to one or more aspects mentioned in conjunction with the proposed concept or above (e.g., Figure 1-5 ) and / or below (for example, Figure 7 ) described in one or more examples.
[0097] Figure 7An example of a method 100 is shown. The method 100 for improving an authorization process comprises transmitting 110 a request for identification information of a security element to a database, and receiving 120 an identification signal from the database comprising information indicating the identification information. The identification information may comprise at least one of an identifier of the security element (e.g. a public key of a key pair (also comprising a private key) generated by the security element) or user binding information. Furthermore, the method 100 comprises receiving 130 a key signature request from the security element, the key signature request comprising information about the security element used to generate the authorization key, and comparing 140 the security element information with the identification information. For example, the method 100 may be performed by reference to Figure 3 The device described performs the following.
[0098] Further details and aspects are mentioned in conjunction with the embodiments described above. Figure 7 The examples shown in may include one or more optional additional features corresponding to one or more aspects mentioned in conjunction with the proposed concept or above (e.g., Figure 1 -6) One or more examples of the description.
[0099] Reference numerals
[0100] 10 Trusted Institutions
[0101] 12Interface circuit system
[0102] 14 Processing circuit system
[0103] 30 safety elements
[0104] 32 interface circuit system
[0105] 34 Processing circuit system
[0106] 50 devices
[0107] 52 interface circuit system
[0108] 54 Processing circuit system
[0109] 70 Backend
[0110] 72 interface circuit system
[0111] 74 Processing circuit system
[0112] 90 key management system
[0113] 92 interface circuit system
[0114] 94 Processing circuit system
[0115] 610, 610a, 610b Shared by
[0116] 630 people shared
[0117] 640 Request AccountldHash
[0118] 650 Receive OnetimeAccountldHash, nouce or AccountIDHash
[0119] 651 Transmit requestKey
[0120] 652 relay requestKey
[0121] 653 Transmit requestKey response signal
[0122] 654 Relay requestKey response signal
[0123] 655 Forwarding identification information
[0124] 660 Transmission invitation signal
[0125] 665 Authorization key creation
[0126] 670 Transmission Key Signature Request
[0127] 675 Check whether the information about the secure element matches the identification information
[0128] 680 Transmit MailboxImportRequest
Claims
1. A security element (50) of a user device for improving an authorization process, comprising: An interface circuit system (52) configured to communicate with a trusted authority; as well as The processing circuit system (54) is configured to control the interface circuit system (52) and receive a signal from a trusted authority, the signal including information indicating that the user is bound to the secure element.
2. The security element (50) according to claim 1, wherein The processing circuit system (52) is also configured to: receiving an invitation signal from a device, the invitation signal including information indicating an invitation to generate an authorization key; and An authorization key is generated based on the received invitation signal, the authorization key being a digital key.
3. A trusted authority (10) for improving the authorization process, comprising: An interface circuit system (12) configured to communicate with a secure element; as well as The processing circuit system (14) is configured to control the interface circuit system (12) and: receiving an identifier signal from a secure element, the identifier signal comprising information indicative of an identifier of the secure element; as well as Perform user binding of the secure element.
4. A trusted authority (10) according to claim 3, wherein The processing circuitry (14) is further configured to store information about the user binding in an instance certificate authority certificate.
5. A device (30) for improving an authorization process, comprising: an interface circuit system (32) configured to communicate with a database; as well as Processing circuitry (34) configured to control the interface circuitry (32) and: transmitting a request for identification information of the secure element to a database; and An identification signal including information indicating the identification information is received from a database, wherein the identification information includes at least one of an identifier of a security element or user binding information.
6. The device (30) according to claim 5, wherein The interface circuit system (32) is further configured to communicate with a secure element; and the processing circuit system (34) is further configured to: transmitting an invitation signal to a secure element, the invitation signal including information indicating an invitation to generate an authorization key; receiving a key signing request from a secure element, the key signing request including information about the secure element for generating an authorization key; and It is checked whether the information about the secure element matches the identification information, and if the information matches, the authorization key is indicated as valid.
7. The device (30) according to any one of claims 5-6, wherein: The device (30) further comprises a storage device, and The database from which the identification information is to be requested is stored in the storage device.
8. The device (30) according to claims 5-7, wherein The interface circuit system (32) is also configured to communicate with a key management server; and The processing circuit system (34) is also configured to: transmitting a request to create an invitation signal to a key management server, the request including information indicating identification information; and A request response signal including information indicating the invitation signal is received from the key management server.
9. A key management server (90) for improving the authorization process; include an interface circuit system (92) configured to communicate with a secure element and a device according to any one of claims 5 to 8; and Processing circuitry (94) configured to control the interface circuitry (92) and: receiving a request from a device to create an invitation signal, the request including information indicating identification information; transmitting a request response request including information indicative of the invitation signal; receiving a key signing request from a secure element, the key signing request including information about the secure element for generating an authorization key; as well as The secure element information is compared with the identification information.
10. A backend (70) for improving the security of digital key generation; include an interface circuit system (72) configured to communicate with a secure element and a device according to any one of claims 5 to 8; and Processing circuitry (74) configured to control the interface circuitry (72) and: receiving an identification signal from a device, the identification signal including information indicative of identification information; receiving a key signing request from a secure element, the key signing request including information about the secure element for generating an authorization key; as well as The secure element information is compared with the identification information.
11. A method (100) for improving an authorization process, comprising: transmitting a request for identification information of the security element to a database; receiving, from a database, an identification signal including information indicating identification information, the identification information including an identifier of a security element and user binding information; receiving, from a secure element, a key signing request including information about the secure element for generating an authorization key; as well as It is checked whether the information about the security element matches the identification information. 12 . A computer program having a program code for carrying out the method ( 100 ) according to claim 11 , when the computer program is executed on a computer, a processor or a programmable hardware component.
