Abstract: A Trusted Service Manager (TSM) receives installation requests (INST) from Service Providers (SPx) comprising an application (APPx), a Service Provider identifier (SPx-ID) and an identifier (MOx-ID) of a target mobile communication device (MOx) that is equipped with a memory device (MIF) to store the application (APPx). The Trusted Service Manager (TSM) transmits the application (APPx) to the target mobile communication device (MOx) and keeps a repository (REP) of the received applications (APPx), their associated service provider identifiers (SPx-ID) and their associated target mobile communication device identifiers (MOx-ID). If the Trusted Service Manager (TSM) receives queries (QU) from a Mobile Network Operator (MNO) asking for the Service Providers associated with a specific mobile communication device identifier (MOx-ID) it retrieves from the repository (REP) those Service Providers (SPx) that are associated with the queried mobile communication device identifier (MOx-ID).

Abstract: A method for server-based managing of unique memory device identifications, such as serial numbers, of memory devices having unique memory device identifications, such as emulated MIFARE devices like SmartMX cards, which memory devices are arranged in mobile communication devices, comprises keeping a repository (DB) of available memory device identifications; fetching a memory device identification from the repository and sending it to a specific mobile communication device; and instructing the mobile communication device to change the memory device identification of its associated memory device from its present value to the received new value. Further, the server instructs the mobile communication device to return the previous value of the memory device identification of its associated memory device. Finally, the server will add the returned memory device identification value to the repository of memory device identifications.

Abstract: A method for server-based managing of unique memory device identifications, such as serial numbers, of memory devices having unique memory device identifications, like MIFARE devices, preferably emulated MIFARE devices like SmartMX cards, which memory devices are arranged in mobile communication devices, comprises keeping a repository of available memory device identifications; fetching a memory device identification from the repository and sending it to a specific mobile communication device; and instructing the mobile communication device to change the memory device identification of its associated memory device from its present value to the received new value. Further, the server instructs the mobile communication device to return the previous value of the memory device identification of its associated memory device. Finally, the server will add the returned memory device identification value to the repository of memory device identifications.

Abstract: A method for managing expired or consumed applications (app1, app2 . . . appx) that have been provided by a Service Provider (SP) and are stored in a memory element (SE) of a mobile communication device (MOB), e.g. a NFC mobile phone, comprises storing a representation (RP) of expired or consumed applications (app1, app2 . . . appx) in or on a storage medium that is separate from the memory element (SE).

Abstract: MIFARE applications (MIA) are organized in at least one sector comprising sector data being arranged in data blocks and a sector trailer. A compressing method for MIFARE application comprises: searching for consecutive occurrences of same data values in the sector data and replacing the detected consecutive data having the same data value by a sequence comprising said data value and a number indicating the number of consecutive sector data having that data value; and/or searching for all different sector trailer values and replacing all sector trailers by references to respective ones of the different sector trailer values.

Abstract: A Trusted Service Manager (TSM) receives via a first communication channel from a Service Provider (SP) a request (REQ(MIA)) that contains an application (MIA) together with a unique identifier of a mobile phone (MOB), particularly its telephone number. The mobile phone (MOB) is equipped with a memory device (MIF) that comprises multiple memory sectors being protected by sector keys. Preferably the memory device (MIF) is a MIFARE device. The TSM extracts the application (MIA) and the unique identifier from the received request, assigns destination sector(s) and associated sector key(s) of the memory device (MIF), compiles the application (MIA), the sector key(s) and the sector number(s) of the destination sector(s) into a setup-message (SU(MIA)), encrypts the setup-message and transmits it to either the mobile phone via a second communication channel or the Service Provider via the first communication channel (CN).

Abstract: In a method for processing top-up data, a server (8) receives data related to a request for issuing an NFC application (9). The data were sent by an NFC mobile device (3) and are intended for a Service Provider (2). At the server (8) transformed data are generated by transforming the data related to the request into a format complying with the Server Provider (2). The transformed data are sent to the Service Provider (2) for further processing and issuing the NFC application (9) to the mobile device (3) particularly utilizing a Trusted Service Manager (1).

Abstract: In a method for transmitting an NFC application (9), a secure channel (14) is establishing by means of a proxy (11) between a Trusted Service Manager (1) and an NFC device (3) via a computing device (10) comprising the proxy (11) and via an RFID reader (12) being a part of the computing device (10). The NFC application (9) received at the computing device (10) from the Trusted Service Manager (1) is channeled through the secure channel (14) to the NFC device (3) utilizing the proxy (11).

Abstract: A method for providing fast and secure access to MIFARE applications installed in a MIFARE memory (MM) being configured as a MIFARE Classic card or an emulated MIFARE Classic memory, comprises: keeping a repository (5) of MIFARE memories (MM) and user identifications (UID) assigned to said MIFARE memories (MM) as well as of all MIFARE applications installed in the MIFARE memories (MM), wherein, when a new MIFARE application (TK2) is to be installed in a MIFARE memory (MM) identified by a user identification (UID) the present memory allocation of said MIFARE memory (MM) is retrieved, an appropriate sector (S) of said MIFARE memory (MM) is calculated, a key (K) is calculated for said MIFARE application (TK2) and the MIFARE application (TK2) together with the assigned sector (S) and key (K) are linked to the user identification (UID) and are stored in the repository (5).

Abstract: A method of accessing in a mobile communication device (4) an application (5, 14, 26), the application (5, 14, 26) being issued by a Service Provider (2), from a trusted application, also known as wallet (12), in which mobile device (4) a secure element (7) such as a SmartMX device is comprised that comprises a service manager (8) that manages the application (5, 14, 26), comprising managing by the service manager (8) a link between the application (5, 14, 26) and an application-codec (6, 15) also being issued by the Service Provider (2), wherein the application-codec (6, 15) is designed for interfacing between the service manager (8) and the application (5, 14, 26) and for processing an access request requesting access to the application (5, 14, 26) received from the service manager (8) and triggered by the wallet (12), and, triggered by the wallet (12), accessing the application (5, 14, 26) via the service manager (8) by means of utilization of the link between the application (5, 14, 26) and the applicatio

Abstract: A method for installing linked MIFARE applications (TK1-A, TK1-B, TK1-C) in a MIFARE memory (MM) being configured as a MIFARE Classic card or an emulated MIFARE Classic memory comprises storing the first linked MIFARE application (TK1-A) in a first free sector of the MIFARE memory, storing the second linked MIFARE application (TK1-B) in a second free sector of the MIFARE memory and writing link information (LK) indicating this second sector in a link information memory location of the first sector where first linked MIFARE application (TK1-A) has been stored, and repeating the steps of storing linked MIFARE applications and writing link information (LK) until the last linked MIFARE application (TK1-C) has been stored.

Abstract: A method for installing a NFC application (APP) that includes a picture (PIC) in a mobile communication device (3) comprises: at a Service Provider (1) transmitting the NFC application (APP) together with the picture (PIC) to a Trusted Service Manager (2); at the Trusted Service Manager (2), separating the picture (PIC) from the NFC application (APP) and storing it and transmitting the NFC application (APP) together with a reference (REF) to a storage location of the picture (PIC) to the mobile communication device (3); at the mobile communication device (3), installing the NFC application (APP) together with the reference (REF) and retrieving the picture (PIC) by sending the reference (REF) to the Trusted Service Manager (2) requesting download of the picture (PIC); at the Trusted Service Manager (2), fetching the picture (PIC) from the storage location indicated by the reference (REF) and downloading it to the mobile communication device (3).

Abstract: In an NFC mobile communication device (3) an operating system, such as a JAVA operating system (J2ME), is able to start software applications (6) identifiable by application identifications (AID). The mobile communication device (3) is equipped with a secure memory device (2), e.g. configured as a SmartMX card, which comprises a first memory portion (2a) configured as a MIFARE memory. The mobile communication device (3) comprises NFC means (5) adapted to trigger a hardware interruption (INT), when the first memory portion (2a) has been accessed by an external RFID reader (1). The hardware interruption (INT) is detected by the operating system (J2ME) and causes it to access a pre-defined sector (5) of the first memory portion (2a), to read information from said sector (5) which is representative for an application identification (AID) and to start the software applications (6) associated to it.

Abstract: A Trusted Service Manager (TSM) receives installation requests (INST) from Service Providers (SPx) comprising an application (APPx), a Service Provider identifier (SPx-ID) and an identifier (MOx-ID) of a target mobile communication device (MOx) that is equipped with a memory device (MIF) to store the application (APPx). The Trusted Service Manager (TSM) transmits the application (APPx) to the target mobile communication device (MOx) and keeps a repository (REP) of the received applications (APPx), their associated service provider identifiers (SPx-ID) and their associated target mobile communication device identifiers (MOx-ID). If the Trusted Service Manager (TSM) receives queries (QU) from a Mobile Network Operator (MNO) asking for the Service Providers associated with a specific mobile communication device identifier (MOx-ID) it retrieves from the repository (REP) those Service Providers (SPx) that are associated with the queried mobile communication device identifier (MOx-ID).

Abstract: A method for server-based managing of unique memory device identifications (MUID1, MUID2), such as serial numbers, of memory devices (MIF1, MIF2) having unique memory device identifications, like MIFARE devices, preferably emulated MIFARE devices like SmartMX cards, which memory devices are arranged in mobile communication devices (U1, U2), comprises keeping a repository (DB) of available memory device identifications (MUIDx); fetching a memory device identification from the repository (DB) and sending it to a specific mobile communication device (U1, U2); and instructing the mobile communication device (U1, U2) to change the memory device identification (MUID1, MUID2) of its associated memory device (MIF1, MIF2) from its present value to the received new value. Further, the server instructs the mobile communication device (U1, U2) to return the previous value of the memory device identification (MUID1, MUID2) of its associated memory device (MIF1, MIF2).

Abstract: A mobile communication device (1) is connectable to a memory device (MIF) that comprises a plurality of memorysectors (0-F), wherein at least one application is stored in at least one memory sector. the memory sectors are protected against unauthorized access 5 by sector keys (key A, key B, 4). The mobile communication device (1) comprises an applications manager (MAM) being adapted to disable the stored applications (TK1, AC1, AC2, TR2, TR3, CP1, TR4, AC3, TK3) when triggered by an external trigger event.

Abstract: A method for sharing applications (APPI, APP2, APPx; APP4) being stored in a source mobile communication device (MOx; MOI) with a destination mobile communication device (MO1; MOx) comprises: transmitting a sharing request (SR) from the source mobile communication device (MOx; MO1) to a Trusted Service Manager (TSM) with information about the application and the destination mobile communication device (MO1; MOx); at the Trusted Service Manager (TSM), retrieving the Service Provider (SP1, SP2, SPx) that has provided said application and sending a query (QU) to it; at the Service Provider (SP1, SP2, SPx), sending an installation request (INST) to the Trusted Service Manager (TSM) with an adapted version (APPx?) of the application and update instructions (UPD) for the source mobile communication device (MOx; MO1); at the Trusted Service Manager (TSM), getting the adapted application (APPx?) installed in the destination mobile communication device (MO1; MOx) and updating the source mobile communication device (MO

Abstract: 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).

Abstract: A Trusted Service Manager (TSM) receives via a first communication channel from a Service Provider (SP) a request (REQ(MIA)) that contains an application (MIA) together with a unique identifier of a mobile phone (MOB), particularly its telephone number. The mobile phone (MOB) is equipped with a memory device (MIF) that comprises multiple memory sectors being protected by sector keys. Preferably the memory device (MIF) is a MIFARE device. The TSM extracts the application (MIA) and the unique identifier from the received request, assigns destination sector(s) and associated sector key(s) of the memory device (MIF), compiles the application (MIA), the sector key(s) and the sector number(s) of the destination sector(s) into a setup-message (SU(MIA)), encrypts the setup-message and transmits it to either the mobile phone via a second communication channel or the Service Provider via the first communication channel (CN).

Abstract: MIFARE applications (MIA) are organized in at least one sector comprising sector data being arranged in data blocks and a sector trailer. A compressing method for MIFARE application comprises: searching for consecutive occurrences of same data values in the sector data and replacing the detected consecutive data having the same data value by a sequence comprising said data value and a number indicating the number of consecutive sector data having that data value; and/or searching for all different sector trailer values and replacing all sector trailers by references to respective ones of the different sector trailer values.