Mobile communication device and method for swapping MIFARE applications
View Patent ↗A mobile communication device ( 1 ) comprises a MIFARE memory (MM) being configured as a MIFARE Classic card or an emulated MIFARE Classic memory, a swap memory (SM) and a MIFARE applications manager (MAM) being adapted to swap MIFARE 5 applications between the MIFARE memory (MM) and the swap memory (SM).
1. A mobile communication device comprising:
a first memory, wherein the first memory is organized according to an IS014443 standard protocol;
a second memory that is different from the first memory, wherein the second memory comprises swap memory; and
an applications manager configured to swap applications between the first memory and the swap memory such that a first application that is stored at a first location on the first memory prior to swapping replaces a second application that is stored at a second location on the swap memory, and such that the second application replaces the first application at the first location on the first memory, wherein the first application is different from the second application.
2. The mobile communication device as claimed in claim 1 , wherein the swap memory and the first memory are located in a file system of the mobile communication device.
3. The mobile communication device as claimed in claim 1 , wherein the swap memory is located in a non-volatile memory device arranged in the mobile communication device.
4. The mobile communication device as claimed in claim 3 , wherein the swap memory is located in a secure memory of a smartcard arranged in the mobile communication device, wherein the secure memory of the smartcard is separate from the non-volatile memory device.
5. The mobile communication device as claimed in claim 1 , wherein the swap memory has a greater capacity than the first memory.
6. The mobile communication device as claimed in claim 1 , wherein the applications manager is configured to detect a trigger signal and configured to swap the applications between the first memory and the swap memory in response to detecting the trigger signal.
7. The mobile communication device as claimed in claim 6 , wherein the trigger signal detectable by the applications manager comprises a swapping instruction received from a Radio-frequency identification (RFID) device.
8. The mobile communication device as claimed in claim 6 , wherein the trigger signal detectable by the applications manager comprises one of an infra-sonic sound signal and an ultra-sonic sound signal.
9. The mobile communication device as claimed in claim 6 , wherein the trigger signal detectable by the applications manager comprises a Global Positioning System (GPS) signal.
10. The mobile communication device as claimed in claim 6 , wherein the trigger signal detectable by the applications manager comprises an internal alarm signal generated by one of a calendar application running on the mobile communication device.
11. The mobile communication device as claimed in claim 6 , wherein the trigger signals detectable by the applications manager comprise signals generated by a user interface of the mobile communication device.
12. The mobile communication device as claimed in claim 1 , wherein the applications manager is configured to process swapping of MIFARE applications based on a begin and end time of an application stored on the mobile communication device.
13. The mobile communication device as claimed in claim 1 , wherein the mobile communication device comprises a NFC Near Field Communication (NFC) mobile phone.
14. The mobile communications device defined in claim 1 , wherein the first memory is partitioned into first memory sectors and the swap memory is partitioned into second memory sectors, wherein the applications manager is further configured to:
store the first application at a selected one of the first memory sectors on the first memory; and
search the swap memory to determine whether any of the second memory sectors is free of data after the first application has been stored at the selected one of the first memory sectors.
15. The mobile communications device defined in claim 14 , wherein, in response to identifying that a given one of the second memory sectors is free of data, the applications manager is further configured to:
store the first application at the given one of the second memory sectors on the swap memory.
16. The mobile communications device defined in claim 14 , wherein, in response to identifying that none of the second memory sectors are free of data, the applications manager is further configured to:
swap the first application stored at the first memory sector on the first memory with a selected application stored at a corresponding one of the second memory sectors on the swap memory.
17. The mobile communications device defined in claim 14 , wherein, in response to identifying that none of the second memory sectors are free of data, the applications manager is further configured to:
identify a first validity period associated with the first application;
search the swap memory to identify a second application on the swap memory having a second validity period that is after the first validity period and a corresponding second memory sector on which the identified second application is stored; and
swap the first application with the identified second application so that the first application is stored at the corresponding second memory sector and the identified second application is stored at the first memory sector.
18. A method for managing applications in a mobile communication device that comprises a first memory organized according to an ISO14443 standard protocol, a swap memory that is different from the first memory, and an applications manager, the method comprising:
with the applications manager, swapping a first application stored at a first location on the first memory with a second application that is different from the first application and that is stored at a second location on the swap memory, such that the first application is stored at the second location on the swap memory and the second application is stored at the first location on the first memory after swapping the first and second applications.
19. The method as claimed in claim 18 , wherein the swap memory is located in at least one of a file system of the mobile communication device, a nonvolatile memory device arranged in the mobile communication device, and a secure memory of a smartcard arranged in the mobile communication device.
20. The method as claimed in claim 18 , further comprising:
with the applications manager, detecting a trigger signal and swapping the applications between the first memory and the swap memory in response to detecting the trigger signal.
21. The method as claimed in claim 20 , wherein the detected trigger signals comprise signals generated by a user interface of the mobile communication device.
22. The method as claimed in claim 18 , further comprising swapping the applications according to at least one automated swapping rule.
23. A non-transitory machine-readable medium embodying a computer program product comprising software code portions that, when executed by a mobile communication device, causes the mobile communication device to perform the method of claim 18 .
24. The non-transitory machine-readable medium of claim 23 , wherein the computer program product is downloadable from a remote server via a communication network.
25. A mobile communication device with an arithmetic-logic unit and a memory, wherein the mobile communication device is adapted to process the computer program product as claimed in claim 23 .
26. The mobile communication device as claimed in claim 25 , being configured as a mobile phone having Near Field Communication (NFC) capabilities.