Abstract: Disclosed is a method for loading, by a manager, a profile into a memory of a secure element, SE. A profile allows the SE to identify itself to a service. The profile includes a profile element created by reference to a template. A template is identified by an OID identifier, which it keeps despite changes. The manager may transmit an audit request or update the operating system of the SE in order to obtain, in response, a piece of information representative of the version of the template stored by the SE. The manager then identifies any difference in version with the corresponding template it holds. In case of difference, the template of the SE or the template of the manager is updated so as to align their versions. Thus, a profile generated on the basis of this version of the template will be loaded, without malfunction, by the SE.

Abstract: Disclosed is a method for loading, by a manager, a profile into a memory of a secure element, SE. A profile allows the SE to identify itself to a service. The profile includes a profile element created by reference to a template. A template is identified by an OID identifier, which it keeps despite changes. The manager may transmit an audit request or update the operating system of the SE in order to obtain, in response, a piece of information representative of the version of the template stored by the SE. The manager then identifies any difference in version with the corresponding template it holds. In case of difference, the template of the SE or the template of the manager is updated so as to align their versions. Thus, a profile generated on the basis of this version of the template will be loaded, without malfunction, by the SE.