(19)
(11)EP 2 374 261 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
24.07.2019 Bulletin 2019/30

(21)Application number: 08875129.2

(22)Date of filing:  24.12.2008
(51)International Patent Classification (IPC): 
G06F 8/60(2018.01)
H04L 29/08(2006.01)
(86)International application number:
PCT/EP2008/011110
(87)International publication number:
WO 2010/072243 (01.07.2010 Gazette  2010/26)

(54)

METHOD FOR AUTOMATICALLY TRANSFERRING AN APPLICATION IN A MOBILE COMMUNICATION TERMINAL OF TELECOMMUNICATION NETWORKS

VERFAHREN ZUR AUTOMATISCHEN ÜBERTRAGUNG EINER APPLIKATION IN EINEM MOBILKOMMUNIKATIONSENDGERÄT VON TELEKOMMUNIKATIONSNETZEN

PROCÉDÉ DE TRANSFERT AUTOMATIQUE D'UNE APPLICATION DANS UN TERMINAL DE COMMUNICATION MOBILE DE RÉSEAUX DE TÉLÉCOMMUNICATION


(84)Designated Contracting States:
AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

(43)Date of publication of application:
12.10.2011 Bulletin 2011/41

(73)Proprietor: Telecom Italia S.p.A.
20123 Milano (IT)

(72)Inventors:
  • BAIETTO, Francesco
    I-10148 Torino (IT)
  • COLLESEI, Sergio
    I-10090 Buttigliera Alta (TO) (IT)

(74)Representative: Colombo, Stefano Paolo et al
Marchi & Partners S.r.l. Via Vittor Pisani, 13
20124 Milano
20124 Milano (IT)


(56)References cited: : 
WO-A-2008/035183
GB-A- 2 431 072
  
      
    Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


    Description

    Technical field of the invention



    [0001] The present invention relates to the field of telecommunications, particularly, of the wireless type. In more detail, the present invention relates to a method for the automatic transfer of an application or service in a mobile terminal of wireless networks.

    Background of the invention



    [0002] At present time, mobile telecom service providers have to control their networks in order to provide their subscribers with relevant and useful services. Such telecom providers usually face a wide range of mobile terminals their subscribers use in their networks. Therefore, a subscriber identification card known as SIM (Subscriber Identity Module) card is associated to each subscriber, to be inserted in the subscriber mobile terminal.

    [0003] The SIM card allows telecom service providers to control the way subscribers access their networks and services. In fact, through the SIM card, telecom providers guarantee to their subscribers: access to the network and services whatever the mobile terminal, authentication mechanism that allows a strong security access to the network, selection of networks when roaming, portability of information (phone-book). At the same time, subscribers may change to a new mobile terminal only by removing the SIM card from one mobile terminal to another and still access the above services they were already subscribed to.

    [0004] However, more recent mobile terminals are increasingly becoming multimedia terminals suitable to manage games, videos, photos, sounds, multimedia applications, e-mails, links to internet browsers, telephone numbers other than simple phone calls. Particularly, each subscriber is able to configure his mobile terminal by downloading different multimedia applications, internet browsers links or other services offered.

    [0005] In order to store such multimedia applications a great storage medium is usually required. As the SIM card is not provided with a great internal memory, the multimedia applications, photos, sounds, provider services which configure the mobile terminal of a subscriber are usually stored into the memory of the mobile terminal itself rather than in the SIM card.

    [0006] Consequently, when a subscriber decides to change his mobile terminal and transfers the SIM card from one mobile terminal to another, the multimedia applications that configured the previous mobile terminal are lost.

    [0007] Document US 2005/0141438 (GEMPLUS) describes a method and system for automatically establishing a configuration of a communication appliance functioning with a subscriber identification card (SIM) in a communication network. The configuration of the appliance is established via the network, following the detection and communication of an identifier of the appliance over the network by means of the card. The method comprises a prior step according to which a configuration requirement is detected by means of events or the absence of events stored in the SIM card.

    [0008] GB 2 431 072 A discloses a mobile communication device that can be controlled by a user. The user accesses a remote server (e.g. a web server) and selects the functions required. These range from call blocking, allowing calls only from/to a specified geographical area and/or within specified times, etc. The required functions are then transmitted to the mobile device (e.g. by SMS) and stored in the SIM card of the device. When a call is received/dialled the SIM card checks a set of rules as defined by the functions stored in the SIM card to see if the call is allowable.

    Summary of the invention



    [0009] The applicant has noticed that in the cited prior art document the SIM card is merely a storing device suitable to be accessed by the appliance during the configuration procedure. The present invention aims to allow the automatical configuration of a telecommunication terminal by simply transferring in such terminal a SIM card previously associated to another telecommunication terminal in order to recover all the applications that configured such another terminal. Particularly, in a preferred embodiment, the present invention relates to a method for transferring an application in a telecommunication terminal, comprising:

    storing in a removable smart card identification data related to the same application;

    connecting said removable smart card to the telecommunication terminal in order to establish an electrical communication between them;

    acquiring by said telecommunication terminal the identification data;

    sending by the telecommunication terminal said identification data to an application storing device for requesting the application;

    downloading in the telecommunication terminal and from the storing device the application corresponding to the identification data.



    [0010] Preferred embodiments of said method are described in the dependent claims.

    Brief description of the drawings



    [0011] To better understand the present invention and appreciate the advantages thereof, a number of non-limiting, exemplary embodiments of the same will be described below, with reference to the annexed figures, in which:

    Fig. 1 shows schematically an exemplary embodiment of a telecommunication terminal including a first application routine and a removable smart card including a second application routine;

    Fig. 2 shows schematically an exemplary embodiment of the second application routine included in the removable smart card;

    Fig. 3 is a block diagram showing a preferred embodiment of a method for transferring an application into the telecommunication terminal in accordance with the invention;

    Fig. 4, 5 and 6 show schematically three different scenarios related to an initialization step of the method of Fig. 3;

    Fig. 7A-7C show schematically an exemplary embodiment of the method related to operations performed by the first application routine to monitor the applications installed in the telecommunication terminal;

    Fig. 8 and 9 shows schematically further steps of the method indicating operations requested to download a missing application from a server.


    Description of preferred embodiments



    [0012] A method for transferring an application into a telecommunication terminal 1 is described with reference to figures 1-9. Particularly, in the following, the word application will be used to indicate: games, videos, photos, sounds, multimedia applications, links to internet browsers and telephone numbers. In addition to such telecommunication terminal 1, the inventive method also involves a removable smart card 2 and an application storing device 3.

    [0013] In accordance with a preferred embodiment, such terminal 1 may be a mobile equipment (such as a mobile phone), a Personal Digital Assistant (PDA), a portable computer or other appliance provided with a communication function and interface.

    [0014] Preferably, the terminal 1 is a GPRS/EDGE/UMTS/HSDPA mobile equipment. As it is known, EDGE (Enhanced Data rates for GSM Evolution) is an evolution of the standard GPRS (General Packet Radio Service) dedicated to the data transfer on a second generation, e.g. GSM (Global System for Mobile Communications), network.
    UMTS (Universal Mobile Telecommunications System) is one of the third-generation (3G) mobile phone technologies. Currently, the most common form of UMTS uses W-CDMA (Wideband Code Division Multiple Access) as the underlying air interface and GSM infrastructures. High-Speed Downlink Packet Access (HSDPA, also known as High-Speed Downlink Protocol Access) is a further 3G mobile telephony communications protocol which allows networks based on Universal Mobile Telecommunications System (UMTS) to have higher data transfer speeds and capacity.

    [0015] In addition, the mobile terminal 1 includes an operating system, for example, Symbian or Windows-Mobile, which allows different applications stored in a suitable memory of the mobile terminal 1 to be run on the same terminal.

    [0016] In accordance with a further preferred embodiment, the removable smart card 2 is a SIM (Subscriber Identity Module) card or a USIM (Universal Subscriber Identity Module) card, i.e. a removable smart card for mobile phones which is associated to a subscriber of a telecommunication service.

    [0017] Reference herein to a SIM card is purely by way of exemplary description of an embodiment and is not to be construed in a limiting sense.

    [0018] As it is known, the SIM card 2 is housed inside the mobile terminal 1 and it securely stores the service-subscriber key used to identify the mobile phone by a service provider. The SIM card 2, usually, comprises a program memory ROM (Read only Memory) comprising in particular an operating system for the card and specific algorithms, a programmable memory and a random access memory (RAM).
    Moreover, the SIM card 2 also comprises a microprocessor connected via a data and control bus to the ROM, the programmable memory and the RAM. Such microprocessor is suitable to execute applications stored therein.

    [0019] As it is known, the SIM card 2 allows users to change phones by simply removing the card from one mobile phone and inserting it into another mobile phone.

    [0020] Preferably, the SIM card 2 is in accordance with the GSM standard 11.14 which defines a SIM application toolkit (SAT) for the SIM, i.e. an application routine that can be executed by the microprocessor included in the SIM itself. In addition, the same standard 11.14 defines a Protocol Data Unit for Applications (APDU) for the SIM - mobile terminal interface. Particularly such APDU comprises a plurality of commands that the SIM card 2 can exchange with the mobile terminal 1.

    [0021] The application storing device 3 comprises a server, i.e. a computer usually located remotely with respect the mobile terminal 1. Particularly, the server 3 includes a microprocessor, a mass storage memory (hard disk), a volatile memory (RAM) and telecommunication means in order to establish a wireless communication with the mobile terminal 1. The server 3 stores, in its mass storage memory, the above indicated applications to be transferred to the mobile terminal 1 when requested.

    [0022] In a preferred embodiment, the mobile terminal 1 and the SIM card 2 can store a first 100 and a second 200 application routine, respectively in their own memories.

    [0023] Figure 1 shows schematically in a block scheme both a preferred embodiment of the first application routine 100 stored in the mobile terminal 1 and the second application routine 200 comprised in the SIM card 2. Particularly, such first 100 and second 200 routines can exchange information between them by accessing to a common file 300 comprised in the SIM card 2 as will be described in detail in the following. Particularly, such file 300 comprises a multiplicity of records each devoted to store a short message SMS (Short Message Service) into the memory of the SIM card 2. For example, such file 300 comprises 30 records.

    [0024] With reference to figure 1, the first routine 100 comprises a first block 101, i.e. a first computer program module acting as a communication interface or Communication Framework between a plurality of service computer program modules 103-107 included in the same first routine 100 and the second routine 200 of the SIM card 2. Particularly, such first computer program module 101 is suitable to manage requests for accessing to the second routine 200 generated by the plurality of service modules 103-107. In addition, the first module 101 performs segmentation-and-reassembly operations on commands sent to the SIM card 2.

    [0025] The first routine 100 also includes a second computer program module 102 acting as a process manager or Background Process Manager to perform in background a multiplicity of operations. In this way, a user of the mobile terminal 1 is not aware of the operations performed. For example, when the mobile terminal 1 is powered on, such second module 102 is suitable to automatically activate the first module 101 (with no intervention of the user) in order to communicate to the SIM card 2 that the mobile terminal 1 comprises the first routine 100.

    [0026] It should be observed that each service module 103-107 performs a different operation within the first routine 100 and the number of such service modules can be increased by adding new functionalities.

    [0027] For example, the first routine 100 comprises a management module 103 (or Application Management) acting to monitor the applications installed in the mobile terminal 1 and to compare them with a list of applications stored in the corresponding SIM card 2. In this way, if one or more applications listed in the SIM card 2 are not included in the mobile terminal 1, the management module 103 performs a request to the server 3 in order to download them. Vice-versa, if module 103 verifies that an application stored in the mobile terminal 1 is not listed in the SIM card 2, such list of applications is upgraded by a reference to the missing application.

    [0028] The first routine 100 also includes a multimedia module 104 (Interactim MM) to realize new services on the mobile terminal 1 by replicating the SAT services performed in the SIM card 2. Such new services are, for example, encoding/decoding reserved data, memorizing such data in protected memory locations, etc.

    [0029] A further service module includes a storage module 105 (SMS Storage Back Up) acting to transfer all the SMSs (Short Message Service) received by the mobile terminal 1 into the corresponding SIM card 2 of the user. Particularly, the storage module 105 operates in background to compress each SMS received on the mobile terminal 1 to subsequently send it to the second routine 200, i.e. to the SIM card 2. In this way, such SMSs can not be lost when the SIM card 2 is transferred inside another mobile terminal.

    [0030] It should be observed that when the memory of the SIM card 2 is full, i.e. no more new SMSs can be stored therein, each new SMSs received by the mobile terminal 1 can be sent to a further external server 3'. Such further server 3' usually differs from the server 3, but in some cases such servers can coincide. In a preferred embodiment, the memory of the SIM card 2 is periodically empty by transferring the SMSs stored therein into the further server 3'. In this way, for each SIM card 2 a SMSs database is created in such server 3'.

    [0031] Moreover, the first routine 100 also comprises a phone book module 106 (Phone Book Syncronization) operating in the same way as the storage module 105 for saving telephone contacts memorized in the mobile terminal 1 into a corresponding phone book of the SIM card 2. In more detail, the word contact is used to indicate not only a telephone number, but also an e-mail address, a home or business address, images, etc.

    [0032] Furthermore, the first routine 100 can also include a further module 107 (Proxy Smart Card Web Server or SCWS) acting to communicate to a web server comprised in the SIM card 2. Such module 107 allows a plurality of functionalities, for example, it can operate to send a SMS generated by a link to a web site.

    [0033] A preferred embodiment of the second application routine 200 stored in the SIM card 2 can be described with reference to Figure 2.

    [0034] Particularly, such second routine 200 includes a further first computer program module 201 acting as a communication interface (Communication Framework) with the corresponding first module 101 of the first routine 100. Such further first module 201 comprises sub-modules (not shown in figure 2) for performing both segmentation-and-reassembly operations on the messages exchanged with the mobile terminal 1 and a transaction message functionality.

    [0035] Transaction message functionality keeps track of the session messages, that can come from more modules (with reference to Figure 1, messages may come to elements 103-107). In particular, it keeps track of who sent the message which began a dialogue that is identified as session.

    [0036] In addition, the second routine 200 comprises an APDU managing module 202 (Event/APDU Manager) which is suitable to alert a corresponding core module 203 when one APDU sent by the mobile terminal 1 has been received. Particularly, such core module 203 or Engine represents a clever portion of the second routine 200 acting to interpret information and messages received and to coordinate actions performed by all other modules of the second routine 200.

    [0037] Furthermore, the second routine 200 also comprises a resource managing module 206 which is suitable to create files located in the memory of the SIM card 2 wherein the information received by the same card can be stored.

    [0038] A further communication module 204 of the second routine 200 is suitable to receive SMS-OTA (SMS - over the air) sent by the service provider to the SIM card 2 in order to activate a new service or to update an existing one. Such module 204 also allows to receive configuration and security messages.

    [0039] A security module 205 interfaces both the core module 203 and the resource managing module 206 to allow them to secure access to a message or information, particularly, when the same are encoded or protected with a digital signature.

    [0040] The second routine 200 can perform further operations implemented by a support module 207. For example, such module 207 can perform a communication with the SCWS module 107 of the first routine 100 or can include a radio interface integrated in the SIM card 2.

    [0041] Figure 3 shows schematically in a flow-chart a preferred embodiment of the inventive method for transferring an application into the mobile terminal 1, provided with the first application routine 100, by connecting the same terminal 1 to the SIM card 2 comprising the respective second routine 200.

    [0042] In the following, we suppose that the SIM card 2 was previously connected to a first mobile terminal 1' (not shown in the figures) having a multiplicity of different applications memorized in its own memory. In other words, such applications defined a user configuration for such first terminal 1'.

    [0043] According to figure 3, the SIM card 2 is suitable to store (phase S1) a list of identifiers i.e. identification data, in respective memory locations, each identifier indicating an application that is stored into the first mobile terminal 1'.

    [0044] Then, the SIM card 2 is separated from the first mobile terminal 1' to be inserted into the mobile terminal 1. Particularly, the method comprises a phase of establishing a communication (phase S2) between the mobile terminal 1 and the SIM card 2 (e.g. by electrically connecting them).

    [0045] Therefore, the inventive method provides a phase of acquisition, by reading (phase S3) the above indicated list of identifiers by the mobile terminal 1 and comparing such list with a further list indicating applications currently stored in the mobile terminal 1 itself.

    [0046] If at least one identifier included in the list is missing in the further list, i.e. the corresponding application is not comprised in the mobile terminal 1, a communication between the same mobile terminal 1 and the server 3 is established (phase S4), and the identification data (i.e. the identifiers) are sent by the telecommunication terminal 1 to the application storing device (server 3).

    [0047] In this way, the application corresponding to the missed identifier can be downloaded (S5) in the mobile terminal 1 from the same server 3.

    [0048] In a preferred embodiment, the above phase of establishing a communication S2 between the mobile terminal 1 and the SIM card 2 comprises an initialization phase preferably performed at the start up of the mobile terminal 1 itself. Advantageously, such initialization phase allows the first application routine 100 of the mobile terminal 1 to verify that the corresponding second application routine 200 is comprised in the SIM card 2 and vice-versa.

    [0049] In a preferred embodiment, the above indicated initialization phase is performed in background, i.e. it is performed automatically when the mobile terminal 1 is started up and it does not involve the user of the mobile terminal itself.

    [0050] Moreover, such initialization phase can be performed in accordance with three different scenarios described with reference to figures 4, 5 and 6. Identical or similar elements will be referred to by the same numerals throughout the figures.

    [0051] According to figure 4, in a first scenario, we assume that the first 100 and the second 200 application routines are included in the mobile terminal 1 and in the SIM card 2, respectively.

    [0052] In this case, when the mobile terminal 1 is switched on, the same terminal 1 activates the SIM card 2, i.e. the second routine 200, by sending a first activation command 4 to it. Such first command 4 is a standard APDU defined "Terminal Profile" by those skilled in the art. At the same time, the mobile terminal 1 activates the first routine 100 by a further activation command 5.

    [0053] After activation, the first routine 100 accesses the common file 300 included in the SIM card 2 to read one of its records. Preferably, the 30th record of such file 300 (corresponding to the last record) is accessed. Advantageously, if the common file 300 is full, i.e. the 30th record contains a SMS message, such message is stored by the first routine 100 in the memory of the mobile terminal 1. Then, the first routine 100 overwrites the message contained in the 30th record by replacing it with a request message 6 addressed to the SIM card 2 in order to verify if such card 2 includes the corresponding second routine 200.

    [0054] Moreover, with the 30th file record overwritten, an update signal 7 generated by the common file 300 is sent to the second routine 200 to indicate that a new message is present in such 30th record.

    [0055] Therefore, the second routine 200 reads the 30th record to verify that the message included therein has been really generated by the first routine 100. In fact, the request message 6 is, usually, a coded message having a respective header indicating the first routine 100 that generated it. In this way, the second routine 200 can verify that the first routine 100 is present in the mobile terminal 1.

    [0056] In addition, the second routine 200 responds to the request message 6 by creating a response message 8 to be written in the same 30th record of the common file 300. Therefore, the first routine 100 is able to read the response message 8 created by periodically accessing to the file 300. In this way, the first routine 100 is, finally, informed that the SIM card 2 is provided with the second routine 200 and a bidirectional communication between them is established.

    [0057] After that, the inventive method of figure 3 can be started.

    [0058] According to figure 5, in a second scenario, we assume that the second application routine 200 is included in the SIM card 2, but in the mobile terminal 1 the corresponding first routine 100 is missing.

    [0059] In this case, after switching on of the mobile terminal 1, the same terminal 1 activates the SIM card 2 by sending the first activation command 4.

    [0060] Then, the mobile terminal 1 generates and sends also a status message 9 to the second routine 200. Such status message 9 is a first of a plurality of status messages received by the second routine 200. Particularly, each status message 9 is a standard APDU defined "request status" in accordance to a GSM standard 11.11 as known by those skilled in the art. The status message 9 is used to inform the mobile terminal 1 when the SIM card 2 is removed from the same terminal.

    [0061] Once received the first activation command 4, the second routine 200 starts to count the number of status messages 9 sent by the mobile terminal 1. Preferably, each status message 9 is generated every 30 seconds. Operatively, after that the second routine 200 has received the third status message 9, if, in the meantime, the same routine 200 has not received the corresponding request message 6 as indicated in the previous scenario, it is assumed that the mobile terminal 1 does not comprise the first routine 100. Therefore, the missing first routine 100 has to be downloaded from the server 3 in order to establish the requested bidirectional communication.

    [0062] To this end, the second routine 200 sends a respective own request message 10 to the mobile terminal 1 in order to know an IMEI (International Mobile Equipment Identity) number which unambiguously identifies such terminal. Once received, such IMEI number is written in a short message (SMS) 11 to be sent by the mobile terminal 1 to the server 3 for requesting the missing first routine 100.

    [0063] By reading the received IMEI number, the server 3 firstly verify that the mobile terminal 1 is properly provided with an operating system which allows the missing first routine 100 to be installed therein. Advantageously, the server 3 includes a plurality of first routines 100 that can be associated to different operating systems of different mobile terminals.

    [0064] The server 3 replies to the mobile terminal request by providing to it the first application routine 100. In a preferred embodiment, the server 3 replies to the mobile terminal request by sending a further message 12 which includes a URL (Uniform Resource Locator) . Particularly, such URL is a browser link for allowing the user to a rapid download of the first application routine 100 by internet. In a further embodiment, the further message 12 sent by the server 3 comprises a MMS (Multimedia Messaging Service) suitable to store the whole first application routine 100 to be sent to the mobile terminal 1.

    [0065] In both cases, the first routine 100 received by the mobile terminal 1 is, subsequently, installed in the terminal itself.

    [0066] According to figure 5, further steps of the method correspond to the ones described with reference to figure 4.

    [0067] Particularly, after being installed, the first routine 100 accesses for reading the 30th record of the common file 300. Particularly, the request message 6 addressed to the SIM card 2 is written in such record.

    [0068] Moreover, the update signal 7 generated by the common file 300 is sent to the second routine 200 to indicate that a message is present in the 30th record. Therefore, the second routine 200 reads such record to verify the authenticity of the message included therein, i.e. to verify that the first routine 100 is really included in the mobile terminal 1.

    [0069] Moreover, the second routine 200 responds to the request message 6 by writing the response message 8 in the same 30th record of the common file 300. As indicated above, the first routine 100 reads the response message 8 by periodically accessing to the common file 300. In this way, the first routine 100 is informed that the second routine 200 is included in the SIM card 2 and a bidirectional communication between them can be established.

    [0070] Also in this case, the inventive method can be started.

    [0071] According to figure 6, in a third scenario, we assume that the first 100 routine is included in the mobile terminal 1, but the SIM card 2 is deprived of the corresponding second routine 200.

    [0072] In this case, at the switching on, the mobile terminal 1 activates the first routine 100 by the further activation command 5. Then, the same first routine 100 reads the 30th record of the common file 300 and writes therein the request message 6 addressed to the SIM card 2.

    [0073] After a first time interval t1, the routine 100 reads the 30th record of the common file 300 to verify whether the expected answer generated by the second routine 200, i.e. the response message 8, is contained therein. Particularly, the first routine 100 performs a first access r1 to the common file 300. Receiving no answer from the SIM card 2, the first routine 100 reads again the 30th record after at least a second t2 and a third t3 time intervals, i.e. the routine 100 performs a second r2 and a third r3 accesses. Whether the response message 8 is still missing after the third t3 time interval, the first routine 100 deducts that the respective second routine 200 is not provided within the SIM card 2.

    [0074] In this case, the inventive method of figure 3 cannot be started, but the first routine 100 can, advantageously, generate an alert message to inform the user. In any case, the first routine 100 can still provide the services connected to the storage module 105 and to the phone book module 106.

    [0075] Therefore, the inventive method described with reference to figure 3 can be performed only whether the second routine 200 is included in the SIM card 2.

    [0076] In the following, a detailed description of an exemplary preferred embodiment of the method of figure 3 will be furnished with reference to figures 7A-7C.

    [0077] Particularly, it will be assumed that the first 100 and the second 200 routine are comprised in the mobile terminal 1 and in the SIM card 2, respectively. Furthermore, it will be assumed that both the mobile terminal 1 and the SIM card 2 are new appliances, i.e. no further applications are installed therein other than such routines 100 and 200 .

    [0078] In addition, the following exemplary embodiment refers to operations performed by the application management module 103 of the first routine 100 which acts to monitor the applications installed in the mobile terminal 1.

    [0079] As indicated in the previous figure 1, it should be observed that both the management module 103 and each other module 104-107 included in the first routine 100 operate as "client" processes suitable to interact with the second routine 200 through the communication interface module 101 acting as a "server". Particularly, such modules 103-107, each representing a different service offered to the user, address their requests to the interface module 101 in order to exchange data or information with the SIM card 2. Such interface module 101 responds to different incoming requests in order to coordinate the access of each module 103-107 to the second routine 200.

    [0080] With reference to figure 7A, when the mobile terminal 1 is switched on, the same terminal 1 activates the second routine 200, by sending the first activation command or "Terminal Profile" 4 to it. At the same time, the mobile terminal 1 activates the first routine 100 and, particularly, the application management module 103 by the further activation command 5. Subsequently, the same management module 103 sends a respective identification command or information request 50 (Get Version) to the first routine 100, particularly to its interface module 101, in order to know whether the second routine 200 is included in the SIM card 2. By the interface module 101, such first request 50 is sent to the second routine 200 which replies giving a respective identification response 60 to confirm to be present.

    [0081] For example, as indicated with reference to figure 1, such request/response exchanged between the first 100 and the second 200 routine is performed by interposition of the common file 300 in the same way as described above with reference to the initialization phase.

    [0082] In this way, the application management module 103 is aware of the second routine 200.

    [0083] Then, the application management module 103 sends a first information request 55 to the second routine 200 in order to know the list of applications installed in the SIM card 2. As the SIM card 2 is new, the second routine 200 reply by a first information response 65 indicating that such list is not present.

    [0084] Therefore, the application management module 103 creates a first file F1 on the mobile terminal 1 (stored in the memory of the same terminal) for storing identification data related to all applications included SIM card 2. For example, for each application, the first file F1 can store: an identifier of the application, a name indicating the application, a memory location where it is stored, etc.

    [0085] In addition, the first file F1 also includes a first counter for indicating the number of applications stored therein. In this case, since no applications are installed in the SIM 2, the first file F1 remains empty and first counter=0.

    [0086] Subsequently, the same management module 103 performs a first scanning of the File System of the mobile terminal 1 searching for applications installed therein.

    [0087] Then, the management module 103 creates a second file F2, analogous to the first one, memorized in the mobile terminal 1 for storing identification data of the applications included in the mobile terminal itself. Such second file F2 includes a respective second counter for indicating the number of applications stored in the mobile terminal 1. As such mobile terminal 1 is also new, i.e. no applications are installed, this second file F2 remains empty and second counter=0.

    [0088] Further, the management module 103 compares the first F1 and second F2 files. Both files are empty, therefore no updating of such files F1 and F2 is requested.

    [0089] Moreover, a third file F3 can be created in the SIM card 2 by the application management module 103 with the aim to include in the same card data related to the list of applications installed in the mobile terminal 1, i.e. to include identification data of said applications. In more detail, in a preferred embodiment described with reference to figure 7B, the management module 103 sends an activation command A1 to the second routine 200 in order to create such third file F3. The second routine 200 replies with an activation response AR1 after that the requested third file F3 has been created.

    [0090] Subsequently, the management module 103 sends a writing command W1 to the second routine 200. Such writing command W1, advantageously, includes the list of applications (i.e. identification data of said applications) installed in the mobile terminal 1, i.e. the content of the second file F2 (in this case no applications are listed). The second routine 200 responds to such writing command W1 by a suitable writing response WR1 to indicate that the list of applications (particularly their identification data) has been correctly received.

    [0091] After a wait period, for example, twenty minutes, the management module 103 performs a second scanning of the File System of the mobile terminal 1 searching for new applications installed therein. Each new application found during such operation is listed in the second file F2 by including its identification data into the same file F2. If no new applications have been installed, the content of second file F2 remains unchanged. Therefore, by comparing the first F1 and second F2 file, no further operations are requested as the two files coincide.

    [0092] After a further wait period, the application management module 103 performs a further scanning of the File System in the mobile terminal 1 repeating the same operations above indicated. It should be observed that such operations are evenly repeated in background without any intervention of the user until a new application is installed in the mobile terminal 1.

    [0093] In the following, we suppose that the user wants to assent a service promoted by his/her telecommunication service provider. Particularly, we assume that one new application (referred as application AP in the following of the description) is installed in the mobile terminal 1 in order to use all functionalities provided by the proposed service.

    [0094] In this case, performing a new scanning of the File System in the mobile terminal 1, the application management module 103 detects such application AP and updates the corresponding second file F2. In more detail, the new application AP installed is indicated by incrementing the second counter and by listing its identification data, for example, the application identifier, its name, medium storing it, etc.

    [0095] Then, the first F1 and the second F2 files are compared so that the application AP installed in the mobile terminal 1 can be detected.

    [0096] Particularly, the changed list of applications stored in the second file F2 has to be transferred also to the SIM card 2.

    [0097] In a preferred embodiment, with reference to figures 7C, the management module 103 sends a first writing command W2 to the second routine 200 requesting to modify the list of applications contained in the third file F3. In more detail, identification data related to the new application comprised in the second file F2 are copied also in such third file F3. The second routine 200 responds to the first writing command W2 by a suitable first writing response WR2 indicating that the list of applications in the third file F3 has been correctly updated.

    [0098] Then, the management module 103 modify the content of the first file F1 so that it contains the same identification data comprised in the third file F3.

    [0099] After a wait period, the management module 103 performs a further scanning of the File System in the mobile terminal 1 searching for new applications installed therein. As no more applications have been installed, the second file F2 contains only the application AP previously installed. Therefore, by comparing the first F1 and second F2 files among them, no further operations are requested as the two files coincide.

    [0100] By periodically repeating such scanning operation, the method remains unchanged until a further new application is installed in the mobile terminal 1 by the user.

    [0101] If the user desires to change his/her mobile terminal 1, for example by replacing it with a new further mobile terminal 1a, the SIM card 2 previously located in the terminal 1 is inserted in such new further terminal 1a.

    [0102] In this case, a preferred embodiment of the inventive method can be described with reference to figures 8 and 9.

    [0103] As indicated above, the SIM card 2 contains in the third file F3 identification data related to all applications previously stored in the old mobile terminal 1 and particularly, data related to the application AP. Moreover, it is assumed that such further mobile terminal 1a is provided by the respective first routine 100 which includes the application management module 103.

    [0104] When the further mobile terminal 1a is switched on, the application management module 103 is activated by the further activation command 5. Moreover, the second routine 200 is also activated by the "Terminal Profile" command 4. Subsequently, the same management module 103 sends the information request 50 (Get Version) to the first routine 100 in order to know whether the second routine 200 is included in the SIM card 2. The second routine 200 replies giving a respective identification response 60 to confirm to be present in the SIM.

    [0105] Subsequently, the first application routine (100), in particular the application management module 103 sends the first information request 55 to the second routine 200 requesting to read the list of applications (i.e. identification data of the applications) installed in the SIM card 2. Particularly, the SIM card 2 includes the third file F3 previously created, therefore the second routine 200 sends the first information response 65 including the list of applications stored in such third file F3.

    [0106] The application management module 103 creates a further first file F1a on the further mobile terminal 1a for storing identification data comprised in the third file F3. Such further first file F1a is analogous to the first file F1 and, for example, can store: an identifier of the application, a name indicating the application, a memory location where it is stored, etc. In addition, the further first file F1a includes a respective counter for indicating the number of applications listed therein.

    [0107] After that, the management module 103 performs a first scanning of the File System of the further mobile terminal 1a searching for applications installed therein. As the further mobile terminal 1a does not contains applications, the management module 103 creates a further second file F2a, located in the memory of the further mobile terminal 1a. Such further second file F2a includes a respective second counter for indicating the total number of applications stored in the further mobile terminal 1a. In this case such second counter=0.

    [0108] By comparing the content of further first F1a and further second F2a files, the management module 103 is suitable to detect that the application AP was stored in the mobile terminal 1 which previously housed the SIM card 2. Now, such application AP is not included in the further mobile terminal 1a.

    [0109] In order to recover the missing application AP, the application management module 103 activates a bidirectional communication (PDP Context) between the further mobile terminal 1a and the server 3. For example, such bidirectional communication is a data transmission according to one of GPRS, EDGE, UMTS. HSDPA communication standards.

    [0110] In more detail, with reference to figure 9, the management module 103 firstly reads in the third file F3 of the SIM card 2 the identifier (UID) corresponding to the missing application AP to be recovered.

    [0111] Then, the management module 103, through the further mobile terminal 1a, sends a first message M1 to the server 3 to request the application AP. Particularly, such first message M1 is a binary message comprising in a first field the identifier of the requested application AP and in a second field the IMEI number of the new further terminal 1a which unambiguously identifies it.

    [0112] Starting from the information contained in the first message M1, the server 3 searches in its own database the file containing data of the requested application AP. Particularly, the server 3 searches for the updated version of the application AP that has to be compatible with the further terminal 1a. For example, the file searched can be a .ZIP file.

    [0113] Then, in a preferred embodiment, the server 3 replies to the request of the management module 103 by sending a second message M2 which includes the URL indicating the browser link which allows to a rapid download of the. ZIP file by internet.

    [0114] In a further embodiment, the application management module 103 sends a downloading message M3 to the server 3 to directly download the .ZIP file above indicated. Preferably, such downloading message M3 is sent to a separated storing medium 3a (repository), not shown in figure 9, which is suitable to include the .ZIP files of the available application AP.

    [0115] The server 3 (or the storing medium 3a) replies by providing the .ZIP file requested to the further mobile terminal 1a. Data related to the requested application are extracted by the management module 103 from such .ZIP file in order to install the recovered application AP in the further mobile terminal 1a.

    [0116] Advantageously, starting from information and data listed in the third file F3, the method of the invention allows to automatically re-establish on the further mobile terminal 1a all applications that were present in the previous mobile terminal 1.

    [0117] After a wait period, the management module 103 scans the File System of the further mobile terminal 1a searching for new applications installed therein. As the application AP has been installed, the further second file F2a is updated by including the identifier of such application AP, its corresponding name, where the same application is stored etc. Moreover, the second counter of the further second file F2a is incremented, i.e. second counter = 1.

    [0118] Therefore, by comparing the contents of the further first F1a and further second F2a files, no further operations are requested as the two files coincide.

    [0119] Advantageously, the inventive method allows the multimedia applications that usually require a heavy memory occupation to be stored into the memory of the mobile terminal 1 or 1a which is greater than the corresponding memory of the SIM card 2.

    [0120] Moreover, by providing the SIM card 2 with the second application routine 200 suitable to cooperate with the corresponding first routine 100 of the mobile terminal 1 or 1a, the same SIM card 2 has only to store the identification data of such applications in the third file F3. In addition, in accordance with the inventive method, the SIM card 2 is suitable to control the applications installed in the mobile, including activation, upgrading and downloading of the applications from the server 3. Particularly, the SIM card 2 can periodically verify if an application is present in the mobile terminal 1 in order to reactivate it as consequence of a terminal changing or after a deletion of the application itself.

    [0121] In addition, advantageously, the multimedia applications for mobile terminals 1, 1a can be downloaded from a server 3 via GPRS/EDGE/UMTS/HSDPA. In this way, obtaining applications or services is made faster with respect a solution in which such application are recovered by OTA-SMS procedures.

    [0122] Another advantage of the inventive method is that it works even if the communication between the mobile terminal 1 and the SIM card 2 employs a data bus with a reduced communication rate. For example, to load a 1MByte application one should upload on the SIM 1000000 of Byte. By this invention, needed communication with the SIM will reduce to no more than 500 bytes, to store information identifying the application on the terminal. So you have a saving of 200000% on the bus. In fact, as the multimedia applications are stored in the mobile terminal 1 (or 1a), the number of byte that the same SIM card 2 has to provide to the terminal 1 is strongly reduced.

    [0123] In addition, the method of the invention can be applied to SIM cards 2 having a reduced memory resources and employing standard interfaces, for example IS07816-3. In this way, costs to acquire such cards are reduced for the service provider. At the same time, with such method the service provider is able to increase the number of mobile terminals including the multimedia applications by which the users can provide revenues when they use different services.


    Claims

    1. Method for automatically transferring an application (AP) into a telecommunication terminal (1, 1a) from a further telecommunication terminal (1'), said application being defined in a user configuration for said further telecommunication terminal (1', 1), the method comprising:

    storing (S1) in a removable smart card (2) connected to said further telecommunication terminal (1', 1) identification data related to said application (AP);

    separating said removable smart card (2) from said further telecommunication terminal (1', 1);

    electrically connecting (S2) said removable smart card (2) to said telecommunication terminal (1, 1a) in order to establish a communication between them;

    acquiring (S3) by said telecommunication terminal (1, 1a) said identification data, wherein said acquiring (S3) comprises comparing said identification data with further identification data stored in said telecommunication terminal;

    if said identification data are not comprised in said further identification data, sending (S4) by the telecommunication terminal (1, 1a) said identification data to an application storing device (3) for requesting the application;

    downloading (S5) in the telecommunication terminal (1) and from said storing device (3) the application corresponding to the identification data,

    wherein the method further comprises providing a respective first application routine (100) memorized in each of said telecommunication terminal (1, 1a) and said further telecommunication terminal (1', 1) and a second application routine (200) memorized in said removable smart card (2), said first application routines (100) being configured to exchange information with the second application routine (200) for performing said steps of storing (S1) and acquiring (S3), and
    wherein the method further comprises, at the switching-on of the telecommunication terminal (1, 1a), an initialization phase to be performed in background without intervention by the user of said telecommunication terminal (1, 1a), to verify by said first application routine (100) that said second application routine (200) is comprised in said removable smart card (2) and vice-versa.
     
    2. Method according to claim 1 wherein said first application routine (100) is suitable to exchange information with the second application routine (200) by accessing to a common file (300) comprised in the removable smart card (2).
     
    3. Method according to claim 2, wherein said step of storing (S1) further comprises generating by the first application routine (100) a file (F3) comprised in the removable smart card (2) to store therein the identification data of said application (AP).
     
    4. Method according to claim 3, wherein the step of generating said file (F3) further comprises:

    sending by the first routine (100) an activation command (A1) to the second routine (200) requesting to create the file (F3);

    sending by the second routine (200) an activation response (AR1) indicative that the requested file (F3) has been created;

    sending by the first routine (100) a writing command (W1) to the second routine (200) including the identification data of applications (AP) installed in the further telecommunication terminal (1', 1);

    sending by the second routine (200) a writing response (WR1) indicative that the said identification data have been received.


     
    5. Method according to claim 2, wherein at the switching on of the telecommunication terminal (1, 1a), following said phase of electrically connecting (S2), the method comprises:

    sending by the telecommunication terminal a first activation command (4) to said second routine (200) to activate it;

    sending by the telecommunication terminal a further activation command (5) to the first routine (100) to activate it;

    sending by the first application routine (100) an identification command (50) to the second routine (200) to verify that said routine is present in the removable smart card (2);

    sending by said second application routine (200) an identification response (60) to the first routine to confirm to be present.


     
    6. Method according to claim 3, wherein said step of acquiring (S3) the identification data further comprises:

    sending by the first application routine (100) a first information request (55) to the second application routine (200) requesting to read identification data of the application (AP) comprised in said file (F3);

    sending by the second application routine (200) a first information response (65) to the first routine including the identification data of the application (AP) stored in said file (F3);

    generating by the first application routine (100) a first file (F1, F1a) memorized in the telecommunication terminal (1, 1a) for storing the identification data comprised in the file (F3);

    generating by the first application routine (100) a second file (F2, F2a) memorized in the telecommunication terminal (1, 1a) for storing identification data of further applications stored in the telecommunication terminal (1, 1a);

    comparing by the first application routine (100) said first (F1, F1a) and second (F2, F2a) file to detect whether the requested application (AP) is stored in the telecommunication terminal (1, 1a).


     
    7. Method according to claim 6, wherein said step of sending (S4) further comprises:

    sending by the first application routine (100) a first message (M1) to the application storing device (3) to request the application (AP), said message being a binary message comprising both identification data of the requested application (AP) and an identification number (IMEI) of the telecommunication terminal (1, 1a);

    searching by the application storing device (3) in its own database data of the requested application (AP) that are compatible with the telecommunication terminal.


     
    8. Method according to claim 1, wherein said step of downloading (S5) comprises sending by the application storing device (3) a second message (M2) including the browser link which allows to a download of the application (AP) by internet.
     
    9. Method according to claim 2, wherein said initialization phase comprises:

    sending by the telecommunication terminal (1, 1a) a first activation command (4) to the second application routine (200) to activate it;

    sending by the same telecommunication terminal (1, 1a) a further activation command (5) to the first application routine (100) to activate it;

    accessing by the first routine (100) a common file (300) included in the removable smart card (2) to read one of its records;

    overwriting by the first routine (100) a message contained in such record by replacing it with a request message (6) addressed to the removable smart card (2);

    generating, based on said common file (300), an update signal (7) and sending it to the second routine (200) to indicate that a new message is present in the record;

    reading by the second routine (200) said modified record to verify that the message included therein has been generated by the first routine (100);

    creating by the second routine (200) a response message (8) to be written in the same record of the common file (300);

    reading by the first routine (100) said response message created by periodically accessing to the common file (300).


     
    10. Method according to claim 9, wherein assuming that the second (200) application routine is comprised in the removable smart card (2) but the first application routine (100) is missing in the telecommunication terminal (1, 1a), the method further comprising:

    generating by the telecommunication terminal (1, 1a) a plurality of status messages (9) to be sent to the second application routine (200);

    counting by the second application routine (200) the number of status messages (9) received;

    evaluating by the second application routine (200) that the first application routine is missing in the telecommunication terminal (1, 1a) if none request message (6) has been received before the third status message (9);

    providing (11) by the second application routine (200) a request to the application storing device (3) for requesting the missing first application routine (100);

    providing (12) by the application storing device (3) the requested first application routine (100) to the telecommunication terminal (1, 1a), said routine being subsequently installed in the terminal itself.


     
    11. Method according to claim 10, wherein said step of providing a request further comprises:

    sending by the second application routine (200) a request message (10) to the telecommunication terminal (1, 1a) to know an IMEI number which identifies said terminal;

    writing by the second application routine (200) said IMEI number in a short message to be sent (11) to the application storing device (3).


     
    12. Method according to claim 10, wherein said step of providing the requested first application routine (100), further comprises:
    generating by the application storing device (3) a further message (12) which includes a URL, i.e. a browser link for allowing a rapid download of the first application routine (100) by internet.
     
    13. Method according to claim 2, wherein said first application routine (100) comprises:

    a first computer program module (101) acting as a communication interface between a plurality of service computer program modules (103-107) included in the same first routine and the second application routine (200);

    a second computer program module (102) acting as a process manager to perform in background a multiplicity of operations.


     
    14. Method according to claim 13, wherein said plurality of service computer program modules (103-107) comprises:

    a management module (103) acting to monitor the applications installed in the telecommunication terminal (1, 1a) and to compare them with a list of applications stored in the corresponding removable smart card (2);

    a multimedia module (104) to realize one of: encoding/decoding reserved data, memorizing such data in protected memory locations;

    a storage module (105) acting to transfer all the SMSs received by the telecommunication terminal (1, 1a) into the corresponding removable smart card (2); a phone book module (106) operating for saving telephone contacts memorized in the telecommunication terminal (1, 1a) into a corresponding phone book of the removable smart card (2);

    a further module (107) allowing to send a SMS generated by a link to a web site.


     
    15. Method according to claim 2, wherein said second application routine (200) comprises:

    a further first computer program module (201) acting as a communication interface with the first routine (100);

    an APDU managing module (202) suitable to alert a corresponding core module (203) when one APDU sent by the telecommunication terminal (1, 1a) has been received, said core module (203) acting to interpret information and messages received and to coordinate actions performed by all other modules of the second application routine;

    a resource managing module (206) suitable to create files located in the memory of the removable smart card (2) wherein the information received by the same smart card can be stored;

    a further communication module (204) which is suitable to receive a SMS over-the-air sent by the service provider to the removable smart card (2) in order to activate a new service or to update an existing one, said module also allowing to receive configuration and security messages;

    a security module (205) to interface both the core module (203) and the resource managing module (206) to allow them to secure access to a message or information, particularly, when the same are encoded or protected with a digital signature;

    a support module (207) to communicate with the first application routine (100).


     


    Ansprüche

    1. Verfahren zum automatischen Übertragen einer Anwendung (AP) in ein Telekommunikationsendgerät (1, 1a) von einem weiteren Telekommunikationsendgerät (1'), wobei die Anwendung in einer Benutzerkonfiguration für das weitere Telekommunikationsendgerät (1', 1) definiert ist, wobei das Verfahren Folgendes umfasst:

    Speichern (S1) von Identifikationsdaten, die die Anwendung (AP) betreffen, auf einer entfernbaren Smartcard (2), die mit dem weiteren Telekommunikationsendgerät (1', 1) verbunden ist;

    Trennen der entfernbaren Smartcard (2) von dem weiteren Telekommunikationsendgerät (1', 1);

    elektrisches Verbinden (S2) der entfernbaren Smartcard (2) mit dem Telekommunikationsendgerät (1, 1a), um eine Kommunikation zwischen diesen herzustellen;

    Erfassen (S3) der Identifikationsdaten durch das Telekommunikationsendgerät (1, 1a), wobei das Erfassen (S3) ein Vergleichen der Identifikationsdaten mit weiteren Identifikationsdaten, die im Telekommunikationsendgerät gespeichert sind, umfasst;

    wenn die Identifikationsdaten nicht in den weiteren Identifikationsdaten umfasst sind, Senden (S4) der Identifikationsdaten durch das Telekommunikationsendgerät (1, 1a) an eine Anwendungsspeichervorrichtung (3) zum Anfordern der Anwendung;

    Herunterladen (S5) der Anwendung, die den Identifikationsdaten entspricht, in das Telekommunikationsendgerät (1) und von der Speichervorrichtung (3),

    wobei das Verfahren ferner das Bereitstellen einer zugehörigen ersten Anwendungsroutine (100), die in jedem des Telekommunikationsendgeräts (1, 1a) und des weiteren Telekommunikationsendgeräts (1', 1) abgespeichert ist, und einer zweiten Anwendungsroutine (200), die in der entfernbaren Smartcard (2) abgespeichert ist, umfasst, wobei die ersten Anwendungsroutinen (100) dazu ausgelegt sind, zum Durchführen der Schritte des Speicherns (S1) und des Erfassens (S3) Informationen mit der zweiten Anwendungsroutine (200) auszutauschen, und

    wobei das Verfahren beim Einschalten des Telekommunikationsendgeräts (1, 1a) ferner eine Initialisierungsphase umfasst, die im Hintergrund ohne Eingriff des Benutzers des Telekommunikationsendgeräts (1, 1a) durchzuführen ist, um durch die erste Anwendungsroutine (100) zu verifizieren, dass die zweite Anwendungsroutine (200) auf der entfernbaren Smartcard (2) umfasst ist und umgekehrt.


     
    2. Verfahren nach Anspruch 1, wobei die erste Anwendungsroutine (100) durch Zugreifen auf eine gemeinsame Datei (300), die auf der entfernbaren Smartcard (2) umfasst ist, geeignet ist, um Informationen mit der zweiten Anwendungsroutine (200) auszutauschen.
     
    3. Verfahren nach Anspruch 2, wobei der Schritt des Speicherns (S1) ferner ein Erzeugen einer Datei (F3), die auf der entfernbaren Smartcard (2) umfasst ist, durch die erste Anwendungsroutine (100) umfasst, um darin die Identifikationsdaten der Anwendung (AP) zu speichern.
     
    4. Verfahren nach Anspruch 3, wobei der Schritt des Erzeugens der Datei (F3) ferner Folgendes umfasst:

    Senden eines Aktivierungsbefehls (A1) durch die erste Routine (100) an die zweite Routine (200), der das Erstellen der Datei (F3) anfordert;

    Senden einer Aktivierungsantwort (AR1), die anzeigt, dass die angeforderte Datei (F3) erstellt wurde, durch die zweite Routine (200);

    Senden eines Schreibbefehls (W1), der die Identifikationsdaten von Anwendungen (AP), die im weiteren Telekommunikationsendgerät (1', 1) installiert sind, enthält, durch die erste Routine (100) an die zweite Routine (200) ;

    Senden einer Schreibantwort (WR1), die anzeigt, dass die Identifikationsdaten empfangen wurden, durch die zweite Routine (200).


     
    5. Verfahren nach Anspruch 2, wobei das Verfahren beim Einschalten des Telekommunikationsendgeräts (1, 1a) nach der Phase des elektrischen Verbindens (S2) Folgendes umfasst:

    Senden eines ersten Aktivierungsbefehls (4) durch das Telekommunikationsendgerät an die zweite Routine (200), um sie zu aktivieren;

    Senden eines weiteren Aktivierungsbefehls (5) durch das Telekommunikationsendgerät an die erste Routine (100), um sie zu aktivieren;

    Senden eines Identifikationsbefehls (50) durch die erste Anwendungsroutine (100) an die zweite Routine (200), um zu verifizieren, dass die Routine auf der entfernbaren Smartcard (2) vorhanden ist;

    Senden einer Identifikationsantwort (60) durch die zweite Anwendungsroutine (200) an die erste Routine, um zu bestätigen, vorhanden zu sein.


     
    6. Verfahren nach Anspruch 3, wobei der Schritt des Erfassens (S3) der Identifikationsdaten ferner Folgendes umfasst:

    Senden einer ersten Informationsanforderung (55), die anfordert, Identifikationsdaten der Anwendung (AP), die in der Datei (F3) umfasst sind, zu lesen, durch die erste Anwendungsroutine (100) an die zweite Anwendungsroutine (200) ;

    Senden einer ersten Informationsantwort (65), die die Identifikationsdaten der Anwendung (AP), die in der Datei (F3) gespeichert sind, enthält, durch die zweite Anwendungsroutine (200) an die erste Routine;

    Erzeugen einer ersten Datei (F1, F1a), die im Telekommunikationsendgerät (1, 1a) abgespeichert ist, zum Speichern der Identifikationsdaten, die in der Datei (F3) umfasst sind, durch die erste Anwendungsroutine (100);

    Erzeugen einer zweiten Datei (F2, F2a), die im Telekommunikationsendgerät (1, 1a) abgespeichert ist, zum Speichern von Identifikationsdaten von weiteren Anwendungen, die im Telekommunikationsendgerät (1, 1a) gespeichert sind, durch die erste Anwendungsroutine (100);

    Vergleichen der ersten (F1, F1a) und der zweiten (F2, 2a) Datei durch die erste Anwendungsroutine (100), um zu detektieren, ob die angeforderte Anwendung (AP) im Telekommunikationsendgerät (1, 1a) gespeichert ist.


     
    7. Verfahren nach Anspruch 6, wobei der Schritt des Sendens (S4) ferner Folgendes umfasst:

    Senden einer ersten Nachricht (M1) durch die erste Anwendungsroutine (100) an die Anwendungsspeichervorrichtung (3), um die Anwendung (AP) anzufordern, wobei die Nachricht eine binäre Nachricht ist, die sowohl Identifikationsdaten der angeforderten Anwendung (AP) als auch eine Identifikationsnummer (IMEI) des Telekommunikationsendgeräts (1, 1a) umfasst;

    Suchen nach Daten der angeforderten Anwendung (AP), die mit dem Telekommunikationsendgerät kompatibel sind, durch die Anwendungsspeichervorrichtung (3) in ihrer eigenen Datenbank.


     
    8. Verfahren nach Anspruch 1, wobei der Schritt des Herunterladens (S5) ein Senden einer zweiten Nachricht (M2), die den Browserlink enthält, der es erlaubt, die Anwendung (AP) per Internet herunterzuladen, durch die Anwendungsspeichervorrichtung (3) umfasst.
     
    9. Verfahren nach Anspruch 2, wobei die Initialisierungsphase Folgendes umfasst:

    Senden eines ersten Aktivierungsbefehls (4) durch das Telekommunikationsendgerät (1, 1a) an die zweite Anwendungsroutine (200), um sie zu aktivieren;

    Senden eines weiteren Aktivierungsbefehls (5) durch dasselbe Telekommunikationsendgerät (1, 1a) an die erste Anwendungsroutine (100), um sie zu aktivieren;

    Zugreifen auf eine gemeinsame Datei (300), die auf der entfernbaren Smartcard (2) enthalten ist, durch die erste Routine (100), um einen ihrer Datensätze zu lesen;

    Überschreiben einer Nachricht, die in einem derartigen Datensatz enthalten ist, durch Ersetzen dieser durch eine Anforderungsnachricht (6), die an die entfernbare Smartcard (2) adressiert ist, durch die erste Routine (100);

    Erzeugen eines Aktualisierungssignals (7) auf Basis der gemeinsamen Datei (300) und Senden von diesem an die zweite Routine (200), um anzuzeigen, dass im Datensatz eine neue Nachricht vorhanden ist;

    Lesen des modifizierten Datensatzes durch die zweite Routine (200), um zu verifizieren, dass die Nachricht, die darin enthalten ist, von der ersten Routine (100) erzeugt wurde;

    Erstellen einer Antwortnachricht (8), die im selben Datensatz der gemeinsamen Datei (300) zu schreiben ist, durch die zweite Routine (200);

    Lesen der erstellten Antwortnachricht durch die erste Routine (100) durch regelmäßiges Zugreifen auf die gemeinsame Datei (300).


     
    10. Verfahren nach Anspruch 9, wobei unter der Annahme, dass die zweite (200) Anwendungsroutine auf der entfernbaren Smartcard (2) umfasst ist, die erste Anwendungsroutine (100) im Telekommunikationsendgerät (1, 1a) aber fehlt, das Verfahren ferner Folgendes umfasst:

    Erzeugen einer Vielzahl von Statusnachrichten (9), die an die zweite Anwendungsroutine (200) zu senden sind, durch das Telekommunikationsendgerät (1, 1a);

    Zählen der Anzahl von empfangenen Statusnachrichten (9) durch die zweite Anwendungsroutine (200);

    Beurteilen durch die zweite Anwendungsroutine (200), dass die erste Anwendungsroutine im Telekommunikationsendgerät (1, 1a) fehlt, wenn vor der dritten Statusnachricht (9) keine Anforderungsnachricht (6) empfangen wurde;

    Bereitstellen (11) einer Anforderung zum Anfordern der fehlenden ersten Anwendungsroutine (100) durch die zweite Anwendungsroutine (200) für die Anwendungsspeichervorrichtung (3);

    Bereitstellen (12) der angeforderten ersten Anwendungsroutine (100) durch die Anwendungsspeichervorrichtung (3) für das Telekommunikationsendgerät (1, 1a), wobei die Routine nachfolgend im Endgerät selbst installiert wird.


     
    11. Verfahren nach Anspruch 10, wobei der Schritt des Bereitstellens einer Anforderung ferner Folgendes umfasst:

    Senden einer Anforderungsnachricht (10) durch die zweite Anwendungsroutine (200) an das Telekommunikationsendgerät (1, 1a), um eine IMEI-Nummer, die das Endgerät identifiziert, zu erfahren;

    Schreiben der IMEI-Nummer durch die zweite Anwendungsroutine (200) in eine Kurznachricht, die an die Anwendungsspeichervorrichtung (3) zu senden (11) ist.


     
    12. Verfahren nach Anspruch 10, wobei der Schritt des Bereitstellens der angeforderten ersten Anwendungsroutine (100) ferner Folgendes umfasst:
    Erzeugen einer weiteren Nachricht (12), die eine URL enthält, d. h. einen Browserlink zum Erlauben eines schnellen Herunterladens der ersten Anwendungsroutine (100) per Internet, durch die Anwendungsspeichervorrichtung (3).
     
    13. Verfahren nach Anspruch 2, wobei die erste Anwendungsroutine (100) Folgendes umfasst:

    ein erstes Computerprogrammmodul (101), das als eine Kommunikationsschnittstelle zwischen einer Vielzahl von Dienstcomputerprogrammmodulen (103-107), die in derselben ersten Routine und der zweiten Anwendungsroutine (200) enthalten sind, agieren;

    ein zweites Computerprogrammmodul (102), das als ein Prozessverwalter agiert, um im Hintergrund eine Mehrzahl von Operationen durchzuführen.


     
    14. Verfahren nach Anspruch 13, wobei die Vielzahl von Dienstcomputerprogrammmodulen (103-107) Folgendes umfasst:

    ein Verwaltungsmodul (103), das agiert, um die Anwendungen, die im Telekommunikationsendgerät (1, 1a) installiert sind, zu überwachen und sie mit einer Liste von Anwendungen, die auf der entsprechenden entfernbaren Smartcard (2) gespeichert sind, zu vergleichen;

    ein Multimediamodul (104) um eines von Folgendem zu realisieren: Codieren/Decodieren von reservierten Daten, Abspeichern von derartigen Daten an geschützten Speicherorten;

    ein Speichermodul (105), das agiert, um alle SMSs, die vom Telekommunikationsendgerät (1, 1a) empfangen werden, zur entsprechenden entfernbaren Smartcard (2) zu übertragen; ein Telefonbuchmodul (106), das zum Speichern von Telefonkontakten, die im Telekommunikationsendgerät (1, 1a) abgespeichert sind, in einem entsprechenden Telefonbuch der entfernbaren Smartcard (2) betrieben wird;

    ein weiteres Modul (107), das es erlaubt, eine erzeugte SMS über einen Link an eine Website zu senden.


     
    15. Verfahren nach Anspruch 2, wobei die zweite Anwendungsroutine (200) Folgendes umfasst:

    ein weiteres erstes Computerprogrammmodul (201), das als eine Kommunikationsschnittstelle mit der ersten Routine (100) agiert;

    ein APDU-Verwaltungsmodul (202), das geeignet ist, einem entsprechenden Kernmodul (203) zu melden, wenn eine APDU, die vom Telekommunikationsendgerät (1, 1a) gesendet wurde, empfangen wurde, wobei das Kernmodul (203) agiert, um empfangene Informationen und Nachrichten zu interpretieren und Aktionen, die von allen anderen Modulen der zweiten Anwendungsroutine durchgeführt werden, zu koordinieren;

    ein Ressourcenverwaltungsmodul (206), das geeignet ist, Dateien, die sich im Speicher der entfernbaren Smartcard (2) befinden, zu erstellen, wobei die Informationen, die von derselben Smartcard empfangen werden, gespeichert werden können;

    ein weiteres Kommunikationsmodul (204), das geeignet ist, eine SMS, die vom Dienstanbieter an die entfernbare Smartcard (2) gesendet wurde, um einen neuen Dienst zu aktivieren oder einen bestehenden zu aktualisieren, über die Luft zu empfangen, wobei es das Modul auch erlaubt, Konfigurations- und Sicherheitsnachrichten zu empfangen;

    ein Sicherheitsmodul (205) zum Koppeln sowohl des Kernmoduls (203) als auch des Ressourcenverwaltungsmoduls (206), um es diesen zu erlauben, einen Zugriff auf eine Nachricht oder Information zu sichern, insbesondere wenn dieselben codiert sind oder durch eine digitale Signatur geschützt werden;

    ein Unterstützungsmodul (207) zum Kommunizieren mit der ersten Anwendungsroutine (100).


     


    Revendications

    1. Procédé de transfert automatique d'une application (AP) dans un terminal de télécommunication (1, 1a) à partir d'un terminal de télécommunication supplémentaire (1'), ladite application étant définie dans une configuration utilisateur pour ledit terminal de télécommunication supplémentaire (1', 1), le procédé comprenant les étapes ci-dessous consistant à :

    stocker (S1), dans une carte à puce amovible (2) connectée audit terminal de télécommunication supplémentaire (1', 1), des données d'identification connexes à ladite application (AP) ;

    séparer ladite carte à puce amovible (2) dudit terminal de télécommunication supplémentaire (1', 1) ;

    connecter électriquement (S2) ladite carte à puce amovible (2) audit terminal de télécommunication (1, 1a) afin d'établir une communication entre eux ;

    acquérir (S3), par le biais dudit terminal de télécommunication (1, la), lesdites données d'identification, dans lequel ladite étape d'acquisition (S3) comprend l'étape consistant à comparer lesdites données d'identification à des données d'identification supplémentaires stockées dans ledit terminal de télécommunication ;

    si lesdites données d'identification ne sont pas comprises dans lesdites données d'identification supplémentaires, envoyer (S4), par le biais du terminal de télécommunication (1, la), lesdites données d'identification, à un dispositif de stockage d'applications (3) en vue de demander l'application ;

    télécharger (S5), dans le terminal de télécommunication (1), et à partir dudit dispositif de stockage (3), l'application correspondant aux données d'identification ; dans lequel le procédé comprend en outre l'étape consistant à fournir une première routine d'application respective (100) mémorisée dans chaque terminal parmi ledit terminal de télécommunication (1, 1a) et ledit terminal de télécommunication supplémentaire (1', 1), ainsi qu'une seconde routine d'application (200) mémorisée dans ladite carte à puce amovible (2), lesdites premières routines d'application (100) étant configurées de manière à échanger des informations avec la seconde routine d'application (200) en vue de mettre en oeuvre ladite étape de stockage (S1) et ladite étape d'acquisition (S3) ; et

    dans lequel le procédé comprend en outre, lors de la mise sous tension du terminal de télécommunication (1, la), une phase d'initialisation devant être mise en oeuvre en arrière-plan sans intervention de l'utilisateur dudit terminal de télécommunication (1, la), visant à vérifier, par le biais de ladite première routine d'application (100), que ladite seconde routine d'application (200) est comprise dans ladite carte à puce amovible (2) et inversement.
     
    2. Procédé selon la revendication 1, dans lequel ladite première routine d'application (100) est pertinente pour échanger des informations avec la seconde routine d'application (200) en accédant à un fichier commun (300) compris dans la carte à puce amovible (2).
     
    3. Procédé selon la revendication 2, dans lequel ladite étape de stockage (S1) comprend en outre l'étape consistant à générer, par le biais de la première routine d'application (100), un fichier (F3) compris dans la carte à puce amovible (2), en vue d'y stocker les données d'identification de ladite application (AP).
     
    4. Procédé selon la revendication 3, dans lequel l'étape de génération dudit fichier (F3) comprend en outre les étapes ci-dessous consistant à :

    envoyer, par le biais de la première routine (100), une commande d'activation (A1), à la seconde routine (200), demandant la création du fichier (F3) ;

    envoyer, par le biais de la seconde routine (200), une réponse d'activation (AR1) indiquant que le fichier demandé (F3) a été créé ;

    envoyer, par le biais de la première routine (100), une commande d'écriture (W1), à la seconde routine (200), incluant les données d'identification d'applications (AP) installées dans le terminal de télécommunication supplémentaire (1', 1) ;

    envoyer, par le biais de la seconde routine (200), une réponse d'écriture (WR1) indiquant que lesdites données d'identification ont été reçues.


     
    5. Procédé selon la revendication 2, dans lequel, lors de la mise sous tension du terminal de télécommunication (1, la), suite à ladite phase de connexion électrique (S2), le procédé comprend les étapes ci-dessous consistant à :

    envoyer, par le biais du terminal de télécommunication, une première commande d'activation (4) à ladite seconde routine (200), en vue de l'activer ;

    envoyer, par le biais dudit terminal de télécommunication, une commande d'activation supplémentaire (5), à la première routine (100), en vue de l'activer ;

    envoyer, par le biais de la première routine d'application (100), une commande d'identification (50), à la seconde routine (200), en vue de vérifier que ladite routine est présente dans la carte à puce amovible (2) ;

    envoyer, par le biais de ladite seconde routine d'application (200), une réponse d'identification (60), à la première routine, en vue de confirmer sa présence.


     
    6. Procédé selon la revendication 3, dans lequel ladite étape d'acquisition (S3) des données d'identification comprend en outre les étapes ci-dessous consistant à :

    envoyer, par le biais de la première routine d'application (100), une première demande d'information (55), à la seconde routine d'application (200), demandant de lire des données d'identification de l'application (AP) comprises dans ledit fichier (F3);

    envoyer, par le biais de la seconde routine d'application (200), une première réponse d'information (65), à la première routine, incluant les données d'identification de l'application (AP) stockées dans ledit fichier (F3) ;

    générer, par le biais de la première routine d'application (100), un premier fichier (F1, F1a) mémorisé dans le terminal de télécommunication (1, la), en vue de stocker les données d'identification comprises dans le fichier (F3) ;

    générer, par le biais de la première routine d'application (100), un second fichier (F2, F2a) mémorisé dans le terminal de télécommunication (1, la), en vue de stocker des données d'identification d'applications supplémentaires stockées dans le terminal de télécommunication (1, 1a) ;

    comparer, par le biais de la première routine d'application (100), ledit premier fichier (F1, F1a) et ledit second fichier (F2, F2a), en vue de détecter si l'application demandée (AP) est stockée dans le terminal de télécommunication (1, 1a).


     
    7. Procédé selon la revendication 6, dans lequel ladite étape d'envoi (S4) comprend en outre les étapes ci-dessous consistant à :

    envoyer, par le biais de la première routine d'application (100), un premier message (M1), au dispositif de stockage d'applications (3), en vue de demander l'application (AP), ledit message étant un message binaire comprenant à la fois des données d'identification de l'application demandée (AP) et un numéro d'identification (IMEI) du terminal de télécommunication (1, 1a) ; et

    rechercher, par le biais du dispositif de stockage d'applications (3), dans sa propre base de données, des données de l'application demandée (AP) qui sont compatibles avec le terminal de télécommunication.


     
    8. Procédé selon la revendication 1, dans lequel ladite étape de téléchargement (S5) comprend l'étape consistant à envoyer, par le biais du dispositif de stockage d'applications (3), un second message (M2) incluant le lien de navigateur qui permet un téléchargement de l'application (AP) par Internet.
     
    9. Procédé selon la revendication 2, dans lequel ladite phase d'initialisation comprend les étapes ci-dessous consistant à :

    envoyer, par le biais du terminal de télécommunication (1, la), une première commande d'activation (4), à la seconde routine d'application (200), en vue de l'activer ;

    envoyer, par le biais du même terminal de télécommunication (1, la), une commande d'activation supplémentaire (5), à la première routine d'application (100), en vue de l'activer ;

    accéder, par le biais de la première routine (100), à un fichier commun (300) inclus dans la carte à puce amovible (2), en vue de lire l'un de ses enregistrements ;

    écraser, par le biais de la première routine (100), un message contenu dans un tel enregistrement, en le remplaçant par un message de demande (6) adressé à la carte à puce amovible (2) ;

    générer, sur la base dudit fichier commun (300), un signal de mise à jour (7), et l'envoyer à la seconde routine (200), en vue d'indiquer qu'un nouveau message est présent dans l'enregistrement ;

    lire, par le biais de la seconde routine (200), ledit enregistrement modifié, en vue de vérifier que le message inclus dans celui-ci a été généré par la première routine (100) ;

    créer, par le biais de la seconde routine (200), un message de réponse (8) devant être écrit dans le même enregistrement du fichier commun (300) ; et

    lire, par le biais de la première routine (100), ledit message de réponse créé, en accédant périodiquement au fichier commun (300).


     
    10. Procédé selon la revendication 9, dans lequel, en supposant que la seconde routine d'application (200) est comprise dans la carte à puce amovible (2), mais que la première routine d'application (100) est absente dans le terminal de télécommunication (1, la), le procédé comprend en outre les étapes ci-dessous consistant à :

    générer, par le biais du terminal de télécommunication (1, la), une pluralité de messages d'état (9) à envoyer à la seconde routine d'application (200) ;

    compter, par le biais de la seconde routine d'application (200), le nombre de messages d'état (9) reçus ;

    évaluer, par le biais de la seconde routine d'application (200), que la première routine d'application est absente dans le terminal de télécommunication (1, 1a) si aucun message de demande (6) n'a été reçu avant le troisième message d'état (9) ;

    fournir (11), par le biais de la seconde routine d'application (200), une demande, au dispositif de stockage d'applications (3), pour demander la première routine d'application manquante (100) ;

    fournir (12), par le biais du dispositif de stockage d'applications (3), la première routine d'application demandée (100), au terminal de télécommunication (1, la), ladite routine étant subséquemment installée dans le terminal lui-même.


     
    11. Procédé selon la revendication 10, dans lequel ladite étape de fourniture d'une demande comprend en outre les étapes ci-dessous consistant à :

    envoyer, par le biais de la seconde routine d'application (200), un message de demande (10), au terminal de télécommunication (1, la), en vue de connaître un numéro IMEI qui identifie ledit terminal ;

    écrire, par le biais de la seconde routine d'application (200), ledit numéro IMEI, dans un message court à envoyer (11) au dispositif de stockage d'applications (3).


     
    12. Procédé selon la revendication 10, dans lequel ladite étape de fourniture de la première routine d'application demandée (100), comprend en outre l'étape ci-dessous consistant à :
    générer, par le biais du dispositif de stockage d'applications (3), un message supplémentaire (12) qui comprend une adresse URL, à savoir un lien de navigateur pour permettre un téléchargement rapide de la première routine d'application (100) par Internet.
     
    13. Procédé selon la revendication 2, dans lequel ladite première routine d'application (100) comprend :

    un premier module de programme informatique (101) agissant en qualité d'interface de communication entre une pluralité de modules de programme informatique de service (103-107) inclus dans ladite même première routine et dans la seconde routine d'application (200) ;

    un second module de programme informatique (102) agissant en qualité de gestionnaire de processus pour mettre en oeuvre, en arrière-plan, une multiplicité d'opérations.


     
    14. Procédé selon la revendication 13, dans lequel ladite pluralité de modules de programme informatique de service (103-107) comprend :

    un module de gestion (103) agissant pour surveiller les applications installées dans le terminal de télécommunication (1, 1a) et pour les comparer à une liste d'applications stockées dans la carte à puce amovible correspondante (2) ;

    un module multimédia (104) destiné à mettre en oeuvre l'une des opérations suivantes : le codage/décodage de données réservées, et la mémorisation de telles données dans des emplacements de mémoire protégés ;

    un module de stockage (105) agissant pour transférer tous les messages SMS reçus par le terminal de télécommunication (1, 1a) dans la carte à puce amovible correspondante (2) ;

    un module d'annuaire téléphonique (106) fonctionnant pour sauvegarder des contacts téléphoniques mémorisés dans le terminal de télécommunication (1, 1a) dans un annuaire téléphonique correspondant de la carte à puce amovible (2) ;

    un module supplémentaire (107) permettant d'envoyer un message SMS généré par un lien à un site web.


     
    15. Procédé selon la revendication 2, dans lequel ladite seconde routine d'application (200) comprend :

    un premier module de programme informatique supplémentaire (201) agissant en qualité d'interface de communication avec la première routine (100) ;

    un module de gestion d'unités de données de protocole d'application, APDU, (202), pertinent pour alerter un module central correspondant (203) lorsqu'une unité APDU envoyée par le terminal de télécommunication (1, 1a) a été reçue, ledit module central (203) agissant pour interpréter des informations et des messages reçus et pour coordonner des actions mises en oeuvre par tous les autres modules de la seconde routine d'application ;

    un module de gestion de ressources (206) pertinent pour créer des fichiers situés dans la mémoire de la carte à puce amovible (2), dans lequel les informations reçues par la même carte à puce peuvent être stockées ;

    un module de communication supplémentaire (204) qui est pertinent pour recevoir un message SMS, par voie hertzienne, envoyé par le fournisseur de services, à la carte à puce amovible (2), afin d'activer un nouveau service ou de mettre à jour un service existant, ledit module permettant également de recevoir des messages de configuration et de sécurité ;

    un module de sécurité (205) pour interfacer à la fois le module central (203) et le module de gestion de ressources (206), en vue de leur permettre de sécuriser l'accès à un message ou à des informations, en particulier, lorsque ceux-ci sont codés ou protégés par une signature numérique ; et

    un module de prise en charge (207) pour communiquer avec la première routine d'application (100).


     




    Drawing






































    Cited references

    REFERENCES CITED IN THE DESCRIPTION



    This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

    Patent documents cited in the description