IP Library Granted Patent US 12,323,789
Granted Patent B2
US 12,323,789 · App. 17/484,246 · Granted Jun 3, 2025

Secure element and method for managing message communication protocols

Inventors: Olivier Van Nieuwenhuyze (Wezembeek-Oppem, BE); Alexandre Charles (Auriol, FR)
Assignees: STMicroelectronics (ROUSSET) SAS; STMicroelectronics Belgium
G06F21/606H04L69/08
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,323,789
App. No.
17/484,246
Granted
Jun 3, 2025
Kind
B2
Abstract

The present description discloses a secure element and a communication method, configured to implement at least one first application, and including a circuit configured to record routing data and a list and parameters of communication protocols compatible with the first application, verify the compatibility of a first communication protocol used by first messages intended for the first application with the protocols of the list, convert the first messages into second messages by using a second communication protocol in response to the first protocol not being compatible with at least one of the protocols of the list, and direct the second messages to the first application by using the routing data of the first application.

Claims (34)

1. A secure element configured to implement at least one first application, the secure element comprising:

a circuit, of the secure element, configured to:

record routing data, and a list and parameters of communication protocols compatible with the first application of the secure element;

verify a compatibility of a first communication protocol used by first messages intended for the first application of the secure element with the communication protocols of the list;

convert the first messages into second messages using a second communication protocol of the secure element in response to the first communication protocol not being compatible with any of the communication protocols of the list, the conversion including modification, in the second messages, of routing information of the first application of the secure element targeted by the first messages; and

direct the second messages to the first application of the secure element by using the routing data of the first application of the secure element;

wherein the secure element is configured to aggregate data of different applications to make a device with which the secure element communicates view the different applications as a single application.

2. The secure element according to claim 1 , wherein each communication protocol in the list is selected from the group consisting of: a virtual network protocol (VNP) defined according to a Global Platform Technology—Virtual Primary Platform—Network Protocol 1.0.1 or subsequent version, 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.

3. The secure element according to claim 1 , wherein each of the different applications is recorded or active.

4. The secure element according to claim 1 , wherein the secure element is configured to detect potential conflicts and implement a resolution mechanism during the recording or modifying of the communication protocols, the parameters, or the routing data of an application.

5. The secure element according to claim 4 , wherein the second communication protocol is a VNP protocol defined according to a Global Platform Technology—Virtual Primary Platform—Network Protocol 1.0.1 or subsequent standard.

6. The secure element according to claim 1 , wherein the secure element is configured to direct the first messages to the first application.

7. The secure element according to claim 1 , wherein the secure element further comprises electronic components and low-level operating systems.

8. The secure element according to claim 7 , wherein the first application is implemented using the electronic components and the low-level operating systems.

9. The secure element according to claim 1 , wherein the secure element is configured to implement at least one second application.

10. The secure element according to claim 9 , wherein the first messages are directed to the first application irrespective of whether the second application uses the same communication protocols as the first application.

11. The secure element according to claim 1 , wherein the list of the routing data and the communication protocols of the first application is erased or modified in response to a request by the first application.

12. A method of communicating with an electronic device by a secure element configured to implement at least a first application, the method comprising:

recording, by the secure element, routing data, and a list and parameters of communication protocols compatible with the first application of the secure element;

verifying, by the secure element, a compatibility of a first communication protocol used by first messages intended for the first application of the secure element with the communication protocols of the list;

converting, by the secure element, the first messages into second messages using a second communication protocol of the secure element in response to the first communication protocol not being compatible with any of the communication protocols of the list, the converting including modifying, in the second messages, routing information of the first application of the secure element targeted by the first messages;

directing, by the secure element, the second messages to the first application of the secure element by using the routing data of the first application of the secure element; and

aggregating, by the secure element, data of different applications to make a device with which the secure element communicates view the different applications as a single application.

13. The method according to claim 12 , wherein each communication protocol in the list is selected from the group consisting of: a virtual network protocol (VNP) defined according to a Global Platform Technology—Virtual Primary Platform—Network Protocol 1.0.1 or subsequent version, 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.

14. The method according to claim 12 , wherein each of the different applications is recorded or active.

15. The method according to claim 12 , further comprising:

detecting, by the secure element, potential conflicts; and

implementing, by the secure element, a resolution mechanism during the recording or modifying of the communication protocols, the parameters, or the routing data of an application.

16. The method according to claim 15 , wherein the second communication protocol is a VNP protocol defined according to a Global Platform Technology—Virtual Primary Platform—Network Protocol 1.0.1 or subsequent standard.

17. The method according to claim 12 , further comprising directing, by the secure element, the first messages to the first application.

18. The method according to claim 12 , wherein the method further comprises implementing the first application using electronic components and low-level operating systems of the secure element.

19. The method according to claim 12 , further comprising implementing, by the secure element, at least one second application.

20. The method according to claim 19 , further comprising directing the first messages to the first application irrespective of whether the second application uses the same communication protocols as the first application.

21. The method according to claim 12 , further comprising erasing or modifying the list of the routing data and the communication protocols of the first application in response to a request by the first application.

Assignments (4)
CHANGE OF NAME Recorded Oct 9, 2024
From: PROTON WORLD INTERNATIONAL
To: STMICROELECTRONICS BELGIUM
Reel/Frame 069174/0847 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 19, 2022
From: CHARLES, ALEXANDRE
To: STMICROELECTRONICS (ROUSSET) SAS
Reel/Frame 061303/0354 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 24, 2021
From: CHARLES, ALEXANDRE
To: STMICROELECTRONICS (ROUSSET) SAS
Reel/Frame 057589/0993 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 24, 2021
From: VAN NIEUWENHUYZE, OLIVIER
To: PROTON WORLD INTERNATIONAL N.V.
Reel/Frame 057590/0076 →
Priority Claims (1)
FR 2010973 · Oct 27, 2020 · national
Continuity (1)
Related Publication 20220129568A1 · Apr 28, 2022
References Cited (30)
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 · 2016 [cited by examiner]
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 20160142109A1 · Kumar · 2016 [cited by applicant]
US 20160309285A1 · Charles · 2016 [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 104115175a · 2014 [cited by examiner]
CN 106060759A · 2016 [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 (Year: 2018). [cited by examiner]
Global Platform Technology, “Virtual Primary Platform—Network Protocol Version 1.0.1”, Document Reference GPC_FST_40, Oct. 2018, 74 pages (Year: 2018). [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]