Secure element and method for starting an application by a low-level operating system

1. A method for starting a first application by at least one low-level operating system of a secure element, the method comprising:

updating first binary data implemented at a reset operation of the secure element, the updated first binary data being associated with the at least one low-level operating system; and

comparing the updated first binary data with a second binary data associated with the first application,

wherein the updated first binary data and the second binary data are related to the reset operation of the secure element; and

updating the second binary data when the updated first binary data are not equal to the second binary data.

2. The method according to claim 1 , wherein comparing the updated first binary data with the second binary data is performed by the at least one low-level operating system.

3. The method according to claim 1 , wherein comparing the updated first binary data with the second binary data is performed by the first application.

4. The method according to claim 1 , further comprising, after updating the second binary data, informing, by the first application, the at least one low-level operating system that the reset operation has occurred.

5. The method according to claim 4 , wherein, after being informed, the first application implements a protocol taking into account that the reset operation has occurred.

6. The method according to claim 1 , wherein the secure element implements the first application and a second application.

7. The method according to claim 1 , wherein the first and second binary data are information about a cold reset operation or a warm reset operation.

8. The method according to claim 1 , wherein the second binary data are updated binary data.

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

a non-transient computer-readable memory; and

a secure processor coupled to the memory and configured to:

update first binary data at a reset operation of the secure element, wherein the updated first binary data are associated with at least one low-level operating system; and

compare the updated first binary data with second binary data associated with the at least one first application,

wherein the updated first binary data and the second binary data are related to the reset operation of the secure element, and

wherein the secure element is configured to implement at least one second application.

10. The secure element according to claim 9 , wherein the at least one low-level operating system is configured to compare the updated first binary data with the second binary data.

11. The secure element according to claim 9 , wherein the at least one first application is configured to compare the updated first binary data with the second binary data.

12. The secure element according to claim 9 , wherein the secure processor is configured to update the second binary data when the updated first binary data are not equal to the second binary data.

13. The secure element according to claim 12 , wherein the at least one low-level operating system is configured to, after updating the second binary data, inform the at least one first application that the reset operation has occurred.

14. The secure element according to claim 13 , wherein the at least one first application is configured to, after being informed, implement a protocol taking into account that the reset operation has occurred.

15. The secure element according to claim 9 , wherein the secure processor is configured to verify binary data at each starting of the at least one first application, and wherein the third binary data are associated with the at least one low-level operating system and are updated after each reset operation of the secure element.

16. The secure element according to claim 15 , wherein the first binary data are associated with a first type of reset operation, and the third binary data are associated with a second type of reset operation.

17. The secure element according to claim 16 , wherein the first type of reset operation is a cold reset operation, in which an electric power supply to the secure element is stopped.

18. The secure element according to claim 16 , wherein the second type of reset operation is a warm reset operation, in which an electric power supply of the secure element is not stopped.

19. The secure element according to claim 9 , wherein the secure element is embedded in an electronic device.

20. The secure element according to claim 9 , wherein the secure element is integrated in an electronic device.

21. The secure element according to claim 9 , wherein the second binary data are updated binary data.

22. A method for starting a first application implemented by at least one low-level operating system of a secure element, the method comprising:

verifying first binary data implemented after a reset operation of the secure element, the first binary data being associated with the at least one low-level operating system,

wherein third binary data, associated with the at least one low-level operating system and updated after each reset operation of the secure element, are verified at each start of the first application,

wherein the first binary data are associated with a first type of reset operation, and wherein the third binary data are associated with a second type of reset operation.

23. The method according to claim 22 , wherein the first type of reset operation is a cold reset operation comprising stopping an electric power supply to the secure element.

24. The method according to claim 22 , wherein the second type of reset operation is a warm reset operation comprising not stopping an electric power supply to the secure element.

25. The method according to claim 22 ,

wherein verifying the first binary data is performed by comparing the first binary data with second binary data associated with the first application, and

wherein the second binary data is updated when the first binary data are not equal to the second binary data.

26. The method according to claim 25 , further comprising, after the second binary data are updated, informing, by the first application, the at least one low-level operating system that the reset operation has occurred.

27. The method according to claim 26 , wherein, after being informed, the first application implements a protocol taking into account that the reset operation has occurred.