IP Library Granted Patent US 12,341,815
Granted Patent B2
US 12,341,815 · App. 17/484,308 · Granted Jun 24, 2025

Secure element and method for converting message communication protocols

Inventors: Olivier Van Nieuwenhuyze (Wezembeek-Oppem, BE); Alexandre Charles (Auriol, FR)
Assignees: STMICROELECTRONICS (ROUSSET) SAS; STMICROELECTRONICS BELGIUM
H04L63/18H04L45/42H04L63/0236H04L63/20
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,341,815
App. No.
17/484,308
Granted
Jun 24, 2025
Kind
B2
Abstract

The present description discloses a secure element and a communication method comprising a router managing first messages using a first communication protocol between applications of the secure element and the outside of the secure element, and a software layer performing a processing at the level of the router. The software layer is adapted to verify the compatibility of a second communication protocol, different from the first one, with which second messages are received, in the absence of a compatibility, convert the second messages into the first communication protocol, and transmit the second messages to the router.

Claims (36)

1. A secure element comprising:

a router, of the secure element, configured to manage first messages using a first communication protocol between a first application of the secure element and an outside of the secure element; and

a software layer, of the secure element, configured to, at a level of the router:

inform a second device, on the outside of the secure element, of a first presence of the first application of the secure element, in response to a first pipe to the software layer being created;

inform the second device of a second presence of a second application of the secure element, in response to a second pipe to the software layer being created;

enable respective links between the second device and the first and second applications, wherein the software layer is a virtual destination host for the applications;

prior to transmitting second messages to the router, determine a compatibility of a second communication protocol, with which the second messages are received from the second device, with the first communication protocol;

in an absence of the compatibility, convert the second messages into the first communication protocol;

direct the converted second messages to either the first application or the second application in accordance with a recipient intended by the second device; and

transmit the converted second messages to the router.

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

3. The secure element according to claim 1 , wherein the first communication 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 communication 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, 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 5 , wherein the software layer is configured to modify headers of the data packets of the second messages.

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

8. The secure element according to claim 1 , wherein the first and second messages are intended for applications configured to be implemented by a high-level operating system of the secure element.

9. The secure element according to claim 1 , wherein the software layer has a routing table enabling conversion of a given message intended for a given application.

10. The secure element according to claim 1 , wherein the software layer uses an injective function enabling conversion of a given message intended for a given application.

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 by a secure element with an outside of the secure element, the secure element comprising a router managing first messages using a first communication protocol between a first application of the secure element and the outside of the secure element, the method comprising:

informing, by a software layer of the secure element, at a level of the router, a second device, on the outside of the secure element, of a first presence of the first application of the secure element, in response to a first pipe to the software layer being created;

informing, by the software layer of the secure element, at the level of the router, the second device of a second presence of a second application of the secure element, in response to a second pipe to the software layer being created;

enable, by the software layer of the secure element, at the level of the router, respective links between the second device and the first and second applications, the software layer being a virtual destination host for the applications;

prior to transmitting second messages to the router, determining, by the software layer of the secure element, at the level of the router, a compatibility of a second communication protocol, with which the second messages are received from the second device, with the first communication protocol;

in an absence of the compatibility, converting, by the software layer of the secure element, at the level of the router, the second messages into the first communication protocol;

directing, by the software layer of the secure element, at the level of the router, the converted second messages to either the first application or the second application in accordance with a recipient intended by the second device; and

transmitting, by the software layer of the secure element, at the level of the router, the converted second messages to the router.

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

15. The method according to claim 13 , wherein:

the first communication 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 communication 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, 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.

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

17. The method according to claim 16 , further comprising modifying, by the software layer, headers of the data packets of the second messages.

18. The method according to claim 13 , wherein the first and second messages are intended for applications configured to be implemented by a high-level operating system of the secure element.

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 THE ASSIGNEMTN AND PROVIDE A WET SIGNATURE PREVIOUSLY RECORDED AT REEL: 057590 FRAME: 0559. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Aug 19, 2022
From: CHARLES, ALEXANDRE
To: STMICROELECTRONICS (ROUSSET) SAS
Reel/Frame 061269/0434 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 24, 2021
From: VAN NIEUWENHUYZE, OLIVIER
To: PROTON WORLD INTERNATIONAL N.V.
Reel/Frame 057590/0493 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 24, 2021
From: CHARLES, ALEXANDRE
To: STMICROELECTRONICS (ROUSSET) SAS
Reel/Frame 057590/0559 →
Priority Claims (1)
FR 2010975 · Oct 27, 2020 · national
Continuity (1)
Related Publication 20220131899A1 · Apr 28, 2022
References Cited (31)
US 7012893B2 · Bahadiroglu · 2006 [cited by examiner]
US 7188191B1 · Hovell · 2007 [cited by examiner]
US 7500047B1 · Tyndall · 2009 [cited by examiner]
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 · Pravin et al. · 2006 [cited by applicant]
US 20100274712A1 · Mestre′et al. · 2010 [cited by applicant]
US 20120042157A1 · Leclercq · 2012 [cited by applicant]
US 20120150601A1 · Fisher · 2012 [cited by examiner]
US 20140020114A1 · Bhatia · 2014 [cited by applicant]
US 20150271677A1 · Van Nieuwenhuyze et al. · 2015 [cited by applicant]
US 20160142109A1 · Kumar · 2016 [cited by applicant]
US 20160309285A1 · Charles · 2016 [cited by applicant]
US 20170055109A1 · Van Nieuwenhuyze et al. · 2017 [cited by applicant]
US 20170329921A1 · Willard · 2017 [cited by examiner]
US 20180376333A1 · Chen · 2018 [cited by examiner]
US 20190005284A1 · Hueber · 2019 [cited by applicant]
US 20190197267A1 · Stoilov et al. · 2019 [cited by applicant]
US 20200279059A1 · Courtiade et al. · 2020 [cited by applicant]
CN 101023420A · 2007 [cited by applicant]
CN 102687123A · 2012 [cited by applicant]
CN 104115175A · 2014 [cited by examiner]
CN 104936129A · 2015 [cited by applicant]
CN 106060759A · 2016 [cited by applicant]
CN 106470049A · 2017 [cited by applicant]
CN 211509119U · 2020 [cited by applicant]
FR 3090947A1 · 2020 [cited by applicant]
JP 6517926B2 · 2019 [cited by applicant]
Globalplatform Technology, “Virtual Primary Platform—Network Protocol Version 1.0.1”, Document Reference GPC_FST_140, Oct. 2018, 74 pages. [cited by applicant]
Cited By (1)
US 12,530,179