IP Library › Granted Patent US 12,443,717
Granted Patent B2
US 12,443,717 · App. 17/756,835 · Granted Oct 14, 2025

Methods and processes to securely update secure elements

Inventors: Kapil Sachdeva (Round Rock, TX); Sylvain Jacques Prevost (Austin, TX); Philip Hill (Cardiff, GB)
Assignee: ASSA ABLOY AB
G06F21/572G06F21/44G06F21/602G06F2221/033
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,443,717
App. No.
17/756,835
Granted
Oct 14, 2025
Kind
B2
Abstract

This disclosure describes techniques for updating firmware of a secure element. The techniques include operations comprising: receiving, by a gateway device, from a remote source, a firmware file; receiving, by a processing element implemented on the gateway device, ephemeral session specific key material for a first secure element implemented on the gateway device; dividing the firmware file into a plurality of data chunks; applying, by the processing element, the ephemeral session specific key material to a first data chunk of the plurality of data chunks to generate a first data packet; and sending, by the processing element, the first data packet to the first secure element.

Claims (65)

1. A method for updating firmware on a secure element, the method comprising:

receiving, by a gateway device, from a remote source, a firmware file, the gateway device comprising a plurality of secure elements including a first secure element and a second secure element;

securely receiving, by a processing element implemented on the gateway device, an ephemeral session specific key material for the first secure element of the plurality of secure elements implemented on the gateway device, wherein the ephemeral session specific key material is generated in response to mutual authentication with the first secure element using a key associated with the first secure element;

dividing, by the gateway device, the firmware file into a plurality of data chunks;

causing, by the processing element, the second secure element to encrypt packets of the plurality of data chunks of the firmware file using the ephemeral session specific key material and to send the encrypted packets of the plurality of data chunks of the firmware file to the first secure element of the plurality of secure elements;

after the encrypted packets of the plurality of data chunks of the firmware file have been sent to the first secure element of the plurality of secure elements, securely receiving, by the processing element, a subsequent ephemeral session specific key material for the second secure element of the plurality of secure elements implemented on the gateway device, wherein the subsequent ephemeral session specific key material is generated in response to mutual authentication with the second secure element using another key associated with the second secure element; and

causing, by the processing element, the first secure element to subsequently encrypt packets of the plurality of data chunks of the firmware file using the subsequent ephemeral session specific key and to send the subsequently encrypted packets to the second secure element.

2. The method of claim 1 , further comprising:

after performing the mutual authentication, encrypting a first data chunk using the ephemeral session specific key material to generate a first data packet, wherein the ephemeral session specific key material comprises an encryption key and a signature key, the encryption key being used to encrypt underlying data and the signature key being used to sign the encrypted data, wherein the ephemeral session specific key material is invalidated after a session between the processing element and the first secure element ends.

3. The method of claim 2 , wherein the first data packet is generated by encrypting and signing the first data chunk using the encryption key and the signature key in the ephemeral session specific key material.

4. The method of claim 1 , further comprising:

performing mutual authentication between the remote source and the first secure element to generate the ephemeral session specific key material; and

transmitting, from the remote source to the processing element, the ephemeral session specific key material that has been generated in response to performing the mutual authentication between the remote source and the first secure element.

5. The method of claim 1 , wherein the processing element comprises a security enclave, further comprising:

establishing the ephemeral session specific key material between the first secure element and the remote source, the establishing being performed based on a master firmware key pair associated with the first secure element, wherein the firmware file is divided by the processing element.

6. The method of claim 5 , wherein the security enclave is a trusted execution environments device, and wherein the master firmware key pair is stored on the remote source, further comprising:

establishing a processing element key pair between the remote source and the processing element; and

sending the ephemeral session specific key material from the remote source to the processing element using the processing element key pair.

7. The method of claim 5 , further comprising:

establishing a processing element key pair between the first secure element and the processing element; and

sending the ephemeral session specific key material from the first secure element to the processing element using the processing element key pair.

8. The method of claim 1 , wherein the processing element comprises a security enclave, and wherein the firmware file is divided by the processing element, further comprising:

selecting, by the processing element, the second secure element as a manager and the first secure element as a target;

establishing the ephemeral session specific key material between the first secure element and the second secure element, the establishing being performed based on a first master firmware key pair associated with the first secure element;

establishing a processing element key pair between the second secure element and the processing element; and

sending the ephemeral session specific key material from the second secure element to the processing element using the processing element key pair, wherein the security enclave is a trusted execution environments device, wherein the first master firmware key pair is stored on the second secure element, and wherein a second master firmware key pair associated with the second secure element is stored on the first secure element.

9. The method of claim 8 , further comprising:

updating firmware of the second secure element after the firmware file is transmitted to the first secure element.

10. The method of claim 9 , wherein the ephemeral session specific key material is a first ephemeral session specific key material, further comprising:

selecting, by the processing element, the second secure element as the target and the first secure element as the manager;

establishing a second ephemeral session specific key material between the first secure element and the second secure element, the establishing being performed based on a second master firmware key pair associated with the second secure element;

establishing a processing element key pair between the first secure element and the processing element; and

sending the second ephemeral session specific key material from the first secure element to the processing element using the processing element key pair.

11. The method of claim 10 , further comprising sending, by the processing element, a first data packet to the second secure element based on the second ephemeral session specific key material.

12. The method of claim 1 , wherein the processing element comprises a second secure element, and wherein the firmware file is divided by a processor on the gateway device, further comprising:

receiving by the processor the firmware file;

selecting, by the processor, the second secure element as a manager and the first secure element as a target;

establishing the ephemeral session specific key material between the first secure element and the second secure element, the establishing being performed based on a first master firmware key pair associated with the first secure element;

providing a first data chunk from the processor to the second secure element; and

instructing the second secure element to apply the ephemeral session specific key material to the first data chunk to send a first data packet, directly or indirectly, to the first secure element.

13. The method of claim 12 , further comprising:

updating firmware of the second secure element after the firmware file is transmitted to the first secure element, wherein the ephemeral session specific key material is a first ephemeral session specific key material;

selecting, by the processor, the second secure element as the target and the first secure element as the manager;

establishing a second ephemeral session specific key material between the first secure element and the second secure element, the establishing being performed based on a second master firmware key pair associated with the second secure element;

providing the first data chunk from the processor to the first secure element; and

instructing the first secure element to apply the second ephemeral session specific key material to the first data chunk to send the first data packet, directly or indirectly, to the second secure element.

14. The method of claim 13 , further comprising sending, by the processing element, the first data packet to the second secure element based on the second ephemeral session specific key material.

15. A system for updating firmware on a secure element, the system comprising:

a gateway device configured to receive, from a remote source, a firmware file and divide the firmware file into a plurality of data chunks, the gateway device comprising a plurality of secure elements including a first secure element and a second secure element; and

a processing element implemented on the gateway device and configured to:

securely receive an ephemeral session specific key material for the first secure element implemented on the gateway device, wherein the ephemeral session specific key material is generated in response to mutual authentication with the first secure element using a key associated with the first secure element;

cause, by the processing element, the second secure element to encrypt packets of the plurality of data chunks of the firmware file using the ephemeral session specific key material and to send encrypted packets of the plurality of data chunks of the firmware file to the first secure element of the plurality of secure elements; and

after the encrypted packets of the plurality of data chunks of the firmware file have been sent to the first secure element of the plurality of secure elements, securely receive, by the processing element, a subsequent ephemeral session specific key material for the second secure element of the plurality of secure elements implemented on the gateway device, wherein the subsequent ephemeral session specific key material is generated in response to mutual authentication with the second secure element using another key associated with the second secure element; and

cause, by the processing element, the first secure element to subsequently encrypt packets of the plurality of data chunks of the firmware file using the subsequent ephemeral session specific key material and to send the subsequently encrypted packets of the plurality of data chunks of the firmware file to the second secure element of the plurality of secure elements.

16. The system of claim 15 , wherein the ephemeral session specific key material comprises an encryption key and a signature key, the encryption key being used to encrypt underlying data and the signature key being used to sign the encrypted data.

17. The system of claim 16 , wherein the first data packet is generated by encrypting and signing a first data chunk using the encryption key and the signature key in the ephemeral session specific key material.

18. The system of claim 15 , wherein the processing element comprises a security enclave and is configured to:

establish the ephemeral session specific key material between the first secure element and the remote source, the establishing being performed based on a master firmware key pair associated with the first secure element, wherein the firmware file is divided by the processing element.

19. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, configure the one or more processors to perform operations for updating firmware on a secure element comprising:

receiving, by a gateway device, from a remote source, a firmware file, the gateway device comprising a plurality of secure elements including a first secure element and a second secure element;

securely receiving, by a processing element implemented on the gateway device, an ephemeral session specific key material for the first secure element implemented on the gateway device, wherein the ephemeral session specific key material is generated in response to mutual authentication with the first secure element using a key associated with the first secure element;

dividing, by the gateway device, the firmware file into a plurality of data chunks;

causing, by the processing element, the second secure element to encrypt packets of the plurality of data chunks of the firmware file using the ephemeral session specific key material and to send the encrypted packets of the plurality of data chunks of the firmware file to the first secure element of the plurality of secure elements;

after the encrypted packets of the plurality of data chunks of the firmware file have been sent to the first secure element of the plurality of secure elements, securely receiving, by the processing element, a subsequent ephemeral session specific key material for the second secure element of the plurality of secure elements implemented on the gateway device, wherein the subsequent ephemeral session specific key material is generated in response to mutual authentication with the second secure element using another key associated with the second secure element;

causing, by the processing element, the first secure element to subsequently encrypt packets of the plurality of data chunks of the firmware file using the subsequent ephemeral session specific key and to send the subsequently encrypted packets to the second secure element.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 3, 2022
From: SACHDEVA, KAPIL; PREVOST, SYLVAIN JACQUES; HILL, PHILIP
To: ASSA ABLOY AB
Reel/Frame 060095/0883 →
Continuity (2)
Provisional Application 62944588 · Dec 6, 2019
Related Publication 20220414224A1 · Dec 29, 2022
References Cited (29)
US 20180082065A1 · Liu et al. · 2018 [cited by applicant]
US 20180123804A1 · Smith · 2018 [cited by examiner]
US 20190356529A1 · Gulati · 2019 [cited by applicant]
CN 114930327 · 2022 [cited by applicant]
JP 2008118265 · 2008 [cited by applicant]
JP 2017017616 · 2017 [cited by applicant]
JP 2023505251 · 2023 [cited by applicant]
JP 7429780 · 2024 [cited by applicant]
JP 2024028670 · 2024 [cited by applicant]
JP 7583204 · 2024 [cited by applicant]
WO 2018029893 · 2018 [cited by applicant]
WO 2018222281 · 2018 [cited by applicant]
“Canadian Application Serial No. 3,160,260, Response Filed Oct. 30, 2023 to Examiners Rule 86(2) Report mailed Jul. 11, 2023”, 11 pages. [cited by applicant]
“International Application Serial No. PCT/EP2020/082136, International Search Report mailed Jan. 18, 2021”, 5 pgs. [cited by applicant]
“International Application Serial No. PCT/EP2020/082136, Written Opinion mailed Jan. 18, 2021”, 5 pgs. [cited by applicant]
“International Application Serial No. PCT/EP2020/082136, International Preliminary Report on Patentability mailed Jun. 16, 2022”, 7 pgs. [cited by applicant]
“European Application Serial No. 20807376.7, Response Filed Dec. 16, 2022 to Communication pursuant to Rules 161(1) and 162 EPC mailed Jun. 13, 2022”, 13 pgs. [cited by applicant]
“Indian Application Serial No. 202217031274, First Examination Report mailed Jan. 18, 2023”, 6 pgs. [cited by applicant]
“Canadian Application Serial No. 3,160,260, Examiners Rule 86(2) Report mailed Jul. 11, 2023”, 3 pages. [cited by applicant]
“Indian Application Serial No. 202217031274, Response Filed Jul. 19, 2023 to First Examination Report mailed Jan. 18, 2023”, with English claims, 19 pages. [cited by applicant]
“Japanese Application Serial No. 2022-533504, Notification of Reasons for Rejection mailed Aug. 1, 2023”, with English translation, 10 pages. [cited by applicant]
“Japanese Application Serial No. 2022-533504, Response filed Oct. 27, 2023 to Notification of Reasons for Rejection mailed Aug. 1, 2023”, with current English claims, 7 pages. [cited by applicant]
Kohei, Miki, “Proposal and Implementation Evaluation of Secure Beat for Automotive ECU”, Using a Unique ID Generated from a PUF as a Trust Anchor, Cryptography and Information Security security symposium, (Jan. 23, 2018… [cited by applicant]
“Korean Application Serial No. 10-2022-7022613, Response filed Jun. 26, 2024 to Notice of Preliminary Rejection mailed Apr. 26, 2024”, with English claims, 13 pages. [cited by applicant]
“Japanese Application Serial No. 2024-191738, Voluntary Amendment filed Nov. 25, 2024”, with English claims, 19 pages. [cited by applicant]
“Korean Application Serial No. 10-2022-7022613, Notice of Preliminary Rejection mailed Apr. 26, 2024”, with English translation, 7 pages. [cited by applicant]
“Mexican Application Serial No. MX/a/2022/006793, Office Action mailed Mar. 24, 2025”, with manual English translation, 7 pages. [cited by applicant]
“Canadian Application Serial No. 3,160,260, Examiners Rule 86(2) Report mailed Jun. 11, 2025”, 4 pgs. [cited by applicant]
“Mexican Application Serial No. MX a 2022 006793, Response Filed Jun. 2, 2025 to Office Action mailed Mar. 24, 2025”, with English claims, 17 pages. [cited by applicant]