IP Library Granted Patent US 12,418,600
Granted Patent B2
US 12,418,600 · App. 17/487,580 · Granted Sep 16, 2025

Secure element and method

Inventors: Olivier Van Nieuwenhuyze (Wezembeek-Oppem, BE); Alexandre Charles (Auriol, FR)
Assignees: STMicroelectronics Belgium; STMicroelectronics (Rousset) SAS
H04L69/08G06F21/85H04L67/565
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,418,600
App. No.
17/487,580
Granted
Sep 16, 2025
Kind
B2
Abstract

The present description discloses a secure element and a communication method comprising at least one operating system including at least one application having a register associated therewith, a buffer memory, and a router having a software layer. The software layer is configured to directing first messages using a first protocol and intended for the application to the buffer memory, and directing second messages using a second protocol different from the first protocol and intended for the application to the register.

Claims (51)

1. A secure element comprising:

at least one operating system in the secure element, comprising an application, and configured to link the application to a register in the secure element;

a buffer memory in the secure element, wherein the buffer memory is separate from the register; and

a router in the secure element, the router having a software layer configured to:

receive first messages intended for the application, using a first protocol compatible with a secure element protocol;

process contents of and direct the first messages to the buffer memory in the secure element;

receive second messages intended for the application, using a second protocol different from the first protocol;

determine that the second protocol is incompatible with the secure element protocol; and

after determining the second protocol is incompatible with the secure element protocol, pass through and direct the second messages to the register in the secure element.

2. The secure element according to claim 1 , wherein the first protocol is implemented by a device external to the secure element.

3. The secure element according to claim 1 , wherein the first protocol is a Virtual Network Protocol (VNP) protocol defined according to a Global Platform Technology-Virtual Primary Platform-Network Protocol 1.0.1 or subsequent standard.

4. The secure element according to claim 1 , wherein the second protocol is selected from the group consisting of: a Host Controller Interface (HCI) protocol, a Single Wire Protocol (SWP) protocol, a Contactless Tunneling (CLT) protocol, a packet communication protocol defined by an International Organization for Standardization 7816 (ISO7816) standard, a simplified High-Level Data Link Control (sHDLC) protocol, or a communication protocol using an internal timing memory.

5. The secure element according to claim 1 , wherein the first and second messages contain data packets of a packet communication method.

6. The secure element according to claim 1 , wherein the second messages originate from a near-field communication device.

7. The secure element according to claim 1 , wherein a high-level operating system of the secure element implements the application.

8. The secure element according to claim 7 , wherein the secure element is configured to implement at least two applications.

9. The secure element according to claim 8 , wherein the software layer is further configured to direct, via the register, the second messages to a selected application among the at least two applications for which the second messages are intended.

10. The secure element according to claim 9 , wherein the software layer is configured to manage a list of patterns provided by the applications for routing the protocols.

11. The secure element according to claim 1 , wherein the secure element is embedded in an electronic system.

12. The secure element according to claim 1 , wherein the secure element is integrated in an electronic system.

13. A method of communication with an electronic device by a secure element comprising at least one operating system including an application having a register in the secure element, a buffer memory separate from the register, and a router associated therewith, the router implementing a software layer, the method comprising:

linking, by the secure element, the application with the register;

receiving, by the software layer in the secure element, first messages intended for the application, using a first protocol compatible with a secure element protocol;

processing contents of and directing, by the software layer in the secure element, the first messages to the buffer memory in the secure element;

receiving, by the software layer, second messages intended for the application, using a second protocol different from the first protocol;

determining, by the software layer in the secure element, that the second protocol is incompatible with the secure element protocol; and

after determining the second protocol is incompatible with the secure element protocol, passing through and directing, by the software layer in the secure element, the second messages to the register in the secure element.

14. The method according to claim 13 , wherein the first protocol is implemented by the electronic device, and the electronic device is external to the secure element.

15. The method according to claim 13 , wherein the first protocol is a Virtual Network Protocol (VNP) protocol defined according to a Global Platform Technology-Virtual Primary Platform-Network Protocol 1.0.1 or subsequent standard.

16. The method according to claim 13 , wherein the second protocol is selected from the group consisting of: a Host Controller Interface (HCI) protocol, a Single Wire Protocol (SWP) protocol, a Contactless Tunneling (CLT) protocol, a packet communication protocol defined by an International Organization for Standardization 7816 (ISO7816) standard, a simplified High-Level Data Link Control (sHDLC) protocol, or a communication protocol using an internal timing memory.

17. The method according to claim 13 , wherein the first and second messages contain data packets of a packet communication method.

18. The method according to claim 13 , wherein the second messages originate from a near-field communication device.

19. The method according to claim 13 , wherein a high-level operating system of the secure element implements the application.

20. The method according to claim 19 , wherein the secure element implements at least two applications.

21. The method according to claim 20 , further comprising directing, by the software layer via the register, the second messages to a selected application among the at least two applications for which the second messages are intended.

22. The method according to claim 21 , further comprising managing, by the software layer, a list of patterns provided by the applications for routing the protocols.

23. A system on a chip (SOC), comprising:

a communication bus on the SOC;

at least one processor on the SOC connected to the communication bus; and

a secure element on the SOC connected to the communication bus, the secure element comprising:

at least one operating system comprising an application, and configured to link the application to a register in the secure element;

a buffer memory separate from the register; and

a router having a software layer configured to:

receive first messages intended for the application, using a first protocol compatible with a secure element protocol;

process contents of and direct the first messages to the buffer memory;

receive second messages intended for the application, using a second protocol different from the first protocol;

determine that the second protocol is incompatible with the first protocol; and

after determining the second protocol is incompatible with the secure element protocol, pass through and direct the second messages to the register.

24. The SOC according to claim 23 , wherein:

the first protocol is a Virtual Network Protocol (VNP) protocol defined according to a Global Platform Technology-Virtual Primary Platform-Network Protocol 1.0.1 or subsequent standard; and

the second protocol is selected from the group consisting of: a Host Controller Interface (HCI) protocol, a Single Wire Protocol (SWP) protocol, a Contactless Tunneling (CLT) protocol, a packet communication protocol defined by an International Organization for Standardization 7816 (ISO7816) standard, a simplified High-Level Data Link Control (sHDLC) protocol, or a communication protocol using an internal timing memory.

Assignments (4)
CHANGE OF NAME Recorded Oct 9, 2024
From: PROTON WORLD INTERNATIONAL
To: STMICROELECTRONICS BELGIUM
Reel/Frame 069174/0847 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNMENT AND PROVIDE A WET SIGNATURE FOR INVENTORS PREVIOUSLY RECORDED AT REEL: 057626 FRAME: 0273. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Aug 19, 2022
From: CHARLES, ALEXANDRE
To: STMICROELECTRONICS (ROUSSET) SAS
Reel/Frame 061264/0632 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 28, 2021
From: VAN NIEUWENHUYZE, OLIVIER
To: PROTON WORLD INTERNATIONAL N.V.
Reel/Frame 057626/0206 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 28, 2021
From: CHARLES, ALEXANDRE
To: STMICROELECTRONICS (ROUSSET) SAS
Reel/Frame 057626/0273 →
Priority Claims (1)
FR 2010974 · Oct 27, 2020 · national
Continuity (1)
Related Publication 20220131837A1 · Apr 28, 2022
References Cited (34)
US 7012893B2 · Bahadiroglu · 2006 [cited by applicant]
US 7188191B1 · Hovell · 2007 [cited by examiner]
US 7500047B1 · Tyndall et al. · 2009 [cited by applicant]
US 9088433B2 · Roettgermann et al. · 2015 [cited by applicant]
US 9338059B1 · Ainsworth et al. · 2016 [cited by applicant]
US 11303745B2 · Van Nieuwenhuyze · 2022 [cited by applicant]
US 20020194389A1 · Worley · 2002 [cited by applicant]
US 20060106941A1 · Singhal · 2006 [cited by examiner]
US 20100274712A1 · Mestre · 2010 [cited by examiner]
US 20120042157A1 · Leclercq · 2012 [cited by applicant]
US 20120150601A1 · Fisher · 2012 [cited by examiner]
US 20140020114A1 · Bhatia · 2014 [cited by applicant]
US 20150111495A1 · Van Nieuwenhuyze · 2015 [cited by examiner]
US 20150271677A1 · Van Nieuwenhuyze et al. · 2015 [cited by applicant]
US 20160142109A1 · Kumar · 2016 [cited by examiner]
US 20160309285A1 · Charles · 2016 [cited by applicant]
US 20170055109A1 · Van Nieuwenhuyze et al. · 2017 [cited by applicant]
US 20170329921A1 · Willard et al. · 2017 [cited by applicant]
US 20180376333A1 · Chen · 2018 [cited by examiner]
US 20190005284A1 · Hueber · 2019 [cited by examiner]
US 20190197267A1 · Stoilov · 2019 [cited by examiner]
US 20200279059A1 · Courtiade · 2020 [cited by examiner]
CN 101023420A · 2007 [cited by applicant]
CN 102687123A · 2012 [cited by applicant]
CN 104936129A · 2015 [cited by applicant]
CN 106060759A · 2016 [cited by applicant]
CN 106470049A · 2017 [cited by applicant]
CN 211509119U · 2020 [cited by applicant]
CN 104115175A · 2021 [cited by applicant]
FR 3090947A1 · 2020 [cited by applicant]
JP 6517926B2 · 2019 [cited by examiner]
Globalplatform Technology, “Virtual Primary Platform—Network Protocol Version 1.0.1”, Document Reference GPC_FST_140, Oct. 2018, 74 pages. [cited by applicant]
U.S. Appl. No. 17/484,308, filed Sep. 24, 2021. [cited by applicant]
U.S. Appl. No. 17/484,246, filed Sep. 24, 2021. [cited by applicant]