Method for transferring user data between two instances of an application

1. A method for transferring applicative data from a first instance of a first package to a second instance of a second package corresponding to an upgraded version of said first package, said first instance being able to get in a locked state where said first instance refuses all service requests except communication with said second instance, wherein said applicative data belongs to said first instance and is specific to said first instance, said method comprises the following steps:

storing by said first instance, the applicative data in a first storage format that includes a plurality of fields, wherein said first and second instances are embedded in a memory of a secure element, wherein said first and second instances comprise a key,

said first and second instances perform a mutual authentication using said key and establish a direct channel within the secure element only if the mutual authentication is successful,

said first instance prepares a pack by formatting said applicative data in a transport format and automatically sends the pack to said second instance through the direct channel, and

said second instance retrieves the applicative data from the pack and stores the applicative data in a second storage format,

wherein said second storage format includes said plurality of fields and at least an additional field storing at least one additional applicative data.

2. The method according to claim 1 , wherein said method comprises the further steps:

said second instance checks that said first instance and said second package are compatible, and

in case of successful check, said second instance requests said first instance to send the applicative data.

3. The method according to claim 1 , wherein said method comprises the further step:

deleting said first instance,

checking to determine if additional instances are linked to said first package,

and if there is no additional instance linked to said first package, deleting said first package.

4. The method according to claim 1 , wherein said first instance has a first identifier and said second instance has a second identifier, and wherein said method comprises the step:

creating an alias from said first identifier to said second identifier.

5. The method according to claim 4 , wherein a third instance of a third package corresponding to an upgraded version of said second package is created in the secure element, wherein said third instance has a third identifier, and wherein said method comprises the step:

transferring the alias from said first identifier to said third identifier.

6. A secure element, the secure element being a device comprising:

a memory and a microprocessor,

the memory containing first and second packages, a first instance of said first package and a second instance of said second package, said first instance being adapted to get in a locked state where it refuses all service requests except communication with said second instance,

wherein said first instance stores a applicative data in a first storage format that includes a plurality of fields, wherein said first and second instances comprise a key, wherein said first and second instances are configured to perform a mutual authentication using said key and to establish a direct channel within the secure element only if the mutual authentication is successful, wherein said first instance is adapted to prepare a pack by formatting said applicative data in a transport format and to automatically send the pack to said second instance through the direct channel, wherein said applicative data belong to said first instance and are specific to said first instance,

wherein said second instance is adapted to retrieve the applicative data from the pack and to store the applicative data in a second storage format,

wherein said second storage format includes said plurality of fields and at least an additional field storing at least one additional applicative data.

7. The secure element according to claim 6 wherein said second instance is adapted to check if said first instance and second package are compatible and to request said first instance to send the applicative data in case of successful check.

8. The secure element according to claim 6 wherein said first instance has a first identifier and said second instance has a second identifier and wherein the secure element is configured to create an alias from said first identifier to said second identifier.

9. The secure element according to claim 6 wherein the secure element is configured to delete an instance, is configured to check existence of remaining instance of a given package and is configured to delete a package.