EP2342641A1 - Speichervergabeverfahren und verfahren zum verwalten von daten in bezug auf eine anwendung, die auf ein mit einem endgerät assoziierten sicherheitsmodul aufgezeichnet werden, und diesbezügliches sicherheitsmodul und endgerät - Google Patents

Speichervergabeverfahren und verfahren zum verwalten von daten in bezug auf eine anwendung, die auf ein mit einem endgerät assoziierten sicherheitsmodul aufgezeichnet werden, und diesbezügliches sicherheitsmodul und endgerät

Info

Publication number
EP2342641A1
EP2342641A1 EP09748415A EP09748415A EP2342641A1 EP 2342641 A1 EP2342641 A1 EP 2342641A1 EP 09748415 A EP09748415 A EP 09748415A EP 09748415 A EP09748415 A EP 09748415A EP 2342641 A1 EP2342641 A1 EP 2342641A1
Authority
EP
European Patent Office
Prior art keywords
memory
application
request
terminal
read
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP09748415A
Other languages
English (en)
French (fr)
Inventor
Guillaume Duc
Philippe Raipin
Olivier Rochecouste
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Orange SA
Original Assignee
France Telecom SA
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by France Telecom SA filed Critical France Telecom SA
Publication of EP2342641A1 publication Critical patent/EP2342641A1/de
Ceased legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/62Protecting access to data via a platform, e.g. using keys or access control rules
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/70Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
    • G06F21/78Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure storage of data

Definitions

  • the invention relates to the field of mobile telecommunications, and more particularly to the management of applications of a mobile terminal.
  • a user of a mobile terminal type mobile phone is faced with an increasingly rich service offer.
  • a range of diverse and varied services such as payment and transport services are offered to the user. These services are accessible either locally or via a mobile phone network (GSM, GPRS %) or even in a proximity situation, for example via dialogue protocols such as Bluetooth, RFID, etc.
  • US 7,263,383 discloses a method for increasing the memory size of an address book stored on a SIM card of a mobile terminal equipped with a flash memory card.
  • some of the information is stored on the SIM card and additional information is stored in The flash memory in association with an identification number of the SIM.
  • the mobile terminal finds the record corresponding to that recorded on the SIM card after reading the identification number in the SIM card. This method can not work if the application is installed on the SIM card because the SIM card has no means to manage resources that are not unique to it.
  • the present invention improves the situation.
  • the present invention proposes a memory allocation method associated with an application stored in a security module associated with a terminal, characterized in that it comprises: a step of receiving a request for allocation of memory external to the security module from said application,
  • a step of storing the memory allocation information received in association with an identifier of said application a step of storing the memory allocation information received in association with an identifier of said application.
  • a security module such as a SIM card of a mobile terminal having a reduced memory size can reserve one or more memory area accessible by this terminal.
  • the reserved memory area may be located in a flash memory of the terminal, an internal memory area of the terminal, a memory area on a remote server accessible by the terminal via a telecommunications network or any other memory area accessible by the terminal.
  • the allocation control comprises at least one access characteristic and the memory allocation information is determined according to said at least one characteristic.
  • An access characteristic is, for example, information relating to the latency (or access time) of the memory. If the application or the security module requires the shortest possible access time, the terminal will if possible choose an internal memory zone to the terminal rather than a memory zone on a remote server. Another access characteristic is, for example, information relating to the volatility of the memory. Thus, the terminal can select a volatile memory zone, for example in RAM, to store temporary application data or on the contrary a memory zone in EEPROM if the data must be kept.
  • the allocation method further comprises a step of determining at least one security parameter and a step of storing said at least one security parameter in association with the application identifier.
  • a security parameter is for example an encryption key to ensure the confidentiality of data during their transfer and storage outside the security module.
  • Another security parameter is for example a key used for the signature of the data and thus to control their integrity.
  • the security parameter (s) are generated and stored by the security module. The fact that these keys are known only to the security module makes it possible to reinforce the security of the system and to guarantee a level of data security identical to that obtained if they were stored in an internal memory of the security module.
  • the invention also relates to a method for managing data associated with an application stored on a security module associated with a terminal, characterized in that memory allocation information is stored in association with an identifier of said application, the method comprises the following steps: receiving a read or write request from an external memory, said request comprising the application identifier,
  • an application having reserved an external memory zone to the security module can access this memory to store and read application data. It thus has an additional memory zone.
  • the step of determining a write command comprises a step of applying said at least one security parameter to data to write.
  • One or more security parameters which are for example secret keys, generated and stored during the prior allocation phase, are then used to ensure the security of the data stored outside the security module.
  • the method further comprises a step of applying said at least one security parameter to read data.
  • one or more security settings applied to the data read from an external memory before any use by the application ensures the security of the data.
  • this key can then be used to encrypt the data before transmission of these data out of the security module. to the allocated memory.
  • This key will also be used by the security module to decrypt the encrypted data read in the external memory. Storing the data in an encrypted way helps to ensure the confidentiality of the data.
  • the invention also relates to a terminal comprising means for receiving a memory allocation command from the security module, means for allocating a memory area according to the received allocation command, means for determining a memory allocation information relative to said allocated area, means for transmitting said allocation information memory, means for receiving a read or write command in said allocated memory area, means for accessing said allocated area and data transmission means read in said allocated area.
  • the allocation means are able to determine a memory area according to at least one access characteristic contained in the allocation command received.
  • the terminal when it has several types of memory, it can select the most appropriate memory according to one or more criteria provided by the security module and / or by the application.
  • the at least one access characteristic relates to the speed of access to the memory.
  • the invention also relates to a security module comprising means for receiving an external memory allocation request from an application, means for transmitting a memory allocation command according to said request, means for receiving memory allocation information determined from the allocation command, means for storing the memory allocation information received in association with an identifier of said application, reception means for a read or write request in an external memory, said request comprising the application identifier, means for determining a read or write command according to said request and allocation information memory associated with the application identifier and means for transmitting said read or write command for reading or writing data to the external memory.
  • the invention also relates to a system comprising a terminal and a security module as described above.
  • FIG. 1 is a diagram illustrating a system according to a first embodiment embodiment of the invention
  • FIG. 2 is a flowchart illustrating the various steps of an allocation method according to a first embodiment of the invention
  • FIG. 3 is a flowchart illustrating the various steps of a method of management following the execution of an installation method according to a first embodiment of the invention
  • FIG. 1 is a diagram illustrating a system according to a first embodiment embodiment of the invention
  • FIG. 2 is a flowchart illustrating the various steps of an allocation method according to a first embodiment of the invention
  • FIG. 3 is a flowchart illustrating the various steps of a method of management following the execution of an installation method according to a first embodiment of the invention
  • FIG. 1 is a diagram illustrating a system according to a first embodiment embodiment of the invention
  • FIG. 2 is a flowchart illustrating the various steps of an allocation method according to a first embodiment of the invention
  • FIG. 3 is a flowchart illustrating the various steps of a method of
  • FIG. 4 is a diagram illustrating a system according to a second embodiment of the invention
  • FIG. 5 is a flowchart illustrating the various steps of an allocation method according to a second embodiment of the invention
  • - Figure 6 is a flowchart illustrating the different steps performed for writing data following the execution of an installation method according to a second embodiment of the invention
  • FIG. 7 is a flowchart illustrating the various steps performed for reading data as a result of the execution of an installation method according to a second embodiment of the invention
  • FIG. 8 is a block diagram representing a system able to carry out the steps of an allocation method and / or a management method according to one embodiment of the invention.
  • FIGS. 1 to 3 A first embodiment of a memory allocation method for an application and a data management method according to the invention will now be described with reference to FIGS. 1 to 3.
  • a user has a Tl terminal that is, for example a mobile phone or a PDA (for "Personal Digital Assistant").
  • the terminal T1 is a computer type PC (for "Personal Computer”).
  • the terminal T1 has a storage memory M and a management module SM1 of this memory.
  • the memory M is for example a flash type external memory inserted into a port of the terminal.
  • the memory M is a memory area of the terminal.
  • the management module SM1 is able to access the memory M to write or read data.
  • the terminal T1 also comprises a security module C1.
  • the security module Cl is for example a removable medium type SlM or UICC (for "Universal Integrated Circuit Card”), or a memory card hosting a secure element (SD card, Embedded Secure control ).
  • the security module Cl comprises an application APl.
  • the APl application is for example a protected application, ie an application where at least part of the data must not be modifiable by a user.
  • the APl application is for example an application requiring the storage of a large volume of data.
  • the application AP1 is an application dedicated to transport and a data record is made at each input of the user in the means of transport.
  • the security module C1 also comprises a control module SC1.
  • This control module SC1 is able to communicate with the management module SM1 of the terminal T1.
  • the application AP1 transmits to the control module SC1 an allocation request RA1.
  • This allocation request contains in particular an identifier IA1 of the application, for example its AID (for "application identifier") and a value N representing the size of the requested external memory.
  • This value N is for example a number of bytes.
  • the request RA1 is received by the control module SC1 during a step E 102, then, during a step E 104, the control module SC1 transmits to the management module SM1 of the terminal T1 an allocation command CAl.
  • the allocation command CA1 is the request RA1 received.
  • the allocation command CA1 is received by the management module SM1 of the terminal T1 during a step E106.
  • the management module SM1 determines a memory zone ZM1 in the memory M.
  • This memory zone ZM1 is an unused area of the memory M that satisfies the size criterion contained in the allocation command CAl.
  • the management module SM1 stores in a management table TM1 of the terminal T1 the address AD1 of the beginning of the zone ZM1 determined and the address AD2 of the end of the zone ZM1 determined in association. with the identifier IAl of the APl application.
  • the start address AD1 and the end address AD2 of the zone ZM1 constitute a memory allocation information AL1.
  • the memory allocation information AL1 is retransmitted to the control module SC1.
  • the control module SC1 records, during a step El 16, this memory allocation information AL1, in a correspondence table TC1 of the security module C1, in association with the application identifier IAl.
  • This management method is implemented following the allocation of a memory zone
  • the application AP1 transmits, to the control module SC1 of the security module C1, a request RQ1 read or write.
  • This request RQl includes the type of access (read or write), the identifier IAl of the application AP1 and information relating to the area to be read or written.
  • This information relating to the zone to be read or written consists for example of a value corresponding to an offset Ol with respect to the beginning of the reserved zone ZM1 and secondly of the number of bytes NA to be read. or to write. If the request RQ1 is a write request, it also contains the data to be written.
  • This request RQ1 is received by the control module SC1 during a step E122. Then, during a step E 124, the control module SC1 determines a command CQ1 for reading or writing corresponding to the request RQ1 received. .
  • the command CQ1 for reading or writing contains the type of access (read or write) contained in the request RQ1, the identifier IA1, an address AD and the number of bytes NA to be read and to write. If the request is a write request, the CQl command also contains the data to write.
  • the address AD is determined by the control module SC1 on the one hand from the memory allocation information AL1 recorded in the correspondence table TC1 in association with the identifier IA1 and on the other hand from the offset Ol received in the request RQl.
  • step E 126 the command CQ1 is transmitted to the management module SM1 of the terminal T1, which receives it during a step El28.
  • the step E128 is followed by a step E130 during which the management module SM1 verifies in the management table TM1 that the requested area is reserved for the application AP1. Then, if this is the case, it controls the writing or reading of the data in the zone ZM1 (step 132).
  • Step E132 is followed by step E134 in which the management module
  • This response contains the data read if the CQl command is a read command. It contains information about the execution of the command if the CQl command is a write command.
  • the response RC1 is then transmitted by the control module SC1 to the application AP1 (step El 36).
  • a second embodiment of a memory allocation method for an application and a data management method according to the invention will now be described with reference to FIGS. 4 to 7.
  • a user has a terminal T2 which is, for example a mobile phone or a PDA (for "Personal Digital Assistant").
  • a terminal T2 which is, for example a mobile phone or a PDA (for "Personal Digital Assistant").
  • the terminal T2 comprises a first storage memory Ml which is an internal memory zone at the terminal T2 and a second memory M2 which is a removable external memory, such as a flash memory, inserted in the terminal.
  • the terminal T2 also comprises a communication module COM allowing the terminal to access a memory zone M3 of a remote server S via a telecommunications network R.
  • the terminal T2 also includes a management module SM2 for the management of memories M1, M2 and M3. The role of the management module SM2 is explained in the following description.
  • the terminal T2 also comprises a security module C2.
  • the security module C2 is for example a removable medium type SIM or UICC (for "Universal Integrated Circuit Card”), or a memory card hosting a secure element (SD card, Embedded Secure control ).
  • the security module C2 comprises an application AP2. As an alternative, it has several applications.
  • the AP2 application is, for example, a payment application.
  • the security module C2 also comprises a control module SC2.
  • This control module SC2 in charge of security and whose role is described below, is able to communicate with the management module SM2 of the terminal T2. Since the control module SC2 of the security module C2 is not capable of initiating communications with the management module SM2 of the terminal T2, a command is regularly sent by the management module SM2 to the control module SC2. When the control module SC2 has a request to be transmitted to the management module SM2, it includes this request in a response message to this command.
  • FIG. 5 an embodiment of the allocation method in which application AP2 reserves an external memory area will now be described.
  • the application AP2 is registered with the control module SC2. For this purpose, it transmits to the control module SC2 a registration request RE2 comprising an application identifier IA2, for example its AID (for "Application Identifier"). Following reception of this request, during a step E202, the control module SC2 verifies that this application is not already registered and generates, during a step E204, an ID2 control identifier for this application AP2.
  • control identifier ID2 is the application identifier IA2 transmitted by the application AP2.
  • the control module determines an encryption key kc and a signature key ks for this application AP2.
  • the encryption key kc allows the encryption and decryption of data from the application AP2 and thus ensures the confidentiality of this data.
  • the signature key ks makes it possible to sign data of the application AP2 and thus makes it possible to ensure the integrity of this data.
  • the keys ks and kc are generated randomly.
  • the keys kc and ks are security parameters.
  • control module SC2 stores, in a correspondence table TC2 of the security module C2, the control identifier ID2 and the keys kc and ks in association with the identifier IA2 of the application AP2.
  • the application AP2 then transmits, during a step E210, the control module SC2 a memory allocation request RA2.
  • This allocation request RA2 contains in particular the identifier IA2 of the application AP2 and a number NE of records.
  • a record here represents a predetermined number of bytes, for example 128 bytes.
  • the number NE determines the size of the memory to be reserved.
  • the request RA2 also includes one or more access characteristics enabling the application AP2 to specify the type of memory to be allocated.
  • three access characteristics are used.
  • an access characteristic Pl indicates whether the memory to be allocated must be a memory area reserved for the application AP2 or a memory area shared between several applications.
  • a second P2 access feature is latency information and indicates whether the memory area should be accessed quickly or not.
  • a third characteristic P3 indicates whether the data must be stored on a persistent medium or on a volatile medium, a volatile memory being adapted to record temporary data.
  • the request RA2 also includes two security features P4 and P5 relating to data security.
  • a security feature P4 indicates whether confidentiality of the data is required.
  • a security feature P5 specifies the type of integrity required for the data. For example, P5 may specify that the required integrity is simple or that an anti-replay mechanism must be used.
  • the set of characteristics P1 to P5 used are coded in the form of a byte.
  • the number and type of access characteristics and security features used are different.
  • the request RA2 is received by the control module SC2 during a step E212, and then, during a step E214, the control module SC2 determines an allocation command CA2 as a function of the request RA2 received.
  • This allocation command CA2 comprises the control identifier ID2 determined during the step E204, the access characteristics P1, P2 and P3 as well as the number NE of requested records.
  • the access and / or security characteristics are transmitted by the application AP2. This configuration allows management adapted to each application.
  • all or part of the access and / or security characteristics is determined by the management module SC2 of the security module C2.
  • the determined allocation command CA2 is then transmitted to the management module SM2 of the terminal T2 during a step E216.
  • the allocation command CA2 is received by the management module SM2 of the T2 terminal during a step E218.
  • the management module SM2 determines a memory zone ZM2 as a function of the access characteristics P1 to P3 and the number N0 of requested records.
  • Zone ZM2 is an area of memory M1, memory M2 or memory M3.
  • the latency characteristic P2 is set to 0 if the latency characteristic P2 is set to 0 if the latency characteristic P2 is set to 0 if the latency characteristic P2 is set to 0 if the latency characteristic P2 is set to 0 if the latency characteristic P2 is set to 0 if the latency characteristic P2 is set to 0 if the latency characteristic P2 is set to 0 if the latency characteristic P2 is set to 0, this means that the memory access time must be as short as possible. In this case, the memory M1 is preferentially chosen to the memory M3. On the other hand, the remote memory M3 is chosen if there is not enough space available in the memories M1 and M2.
  • the management module SM2 stores in a management table TM2 of the terminal T2, a zone start address AD3 ZM2, which represents a memory allocation information AL2, and an end address AD4.
  • zone ZM2 in association with the ID2 control identifier of the application AP2.
  • the zone start address AD3 ZM2 and address AD4 end zone ZM2 are physical addresses allowing the management module SM2 to access the memory zone ZM2.
  • the management module SM2 stores in the management table TM2 the address AD3 of zone start ZM2 and the number NE of reserved records.
  • the memory allocation information AL2 consists of the zone start address AD3 and the end of zone address AD4.
  • the memory allocation information AL2 is an identifier enabling the management module SM2 to retrieve the physical address of the zone ZM2.
  • step E224 the memory allocation information AL2 is retransmitted to the control module SC2 of the security module C2. Following reception of this information (step E226), the control module SC2 records, during a step
  • this memory allocation information AL2 in the correspondence table TC2 of the security module C2, in association with the application identifier IA2.
  • the control module SC2 transmits the memory allocation information AL2 to the application AP2.
  • the application AP2 transmits a registration request RE2 and an allocation request RA2.
  • the application transmits only an allocation request and the steps of determining a control identifier, determining the security and storage parameters in a correspondence table are performed by the control module when receipt of this allocation request.
  • the application AP2 transmits to the control module SC2 a write request RW2.
  • the write request RW2 comprises the application identifier IA2 of the application AP2, an access type (read or write), the security characteristics (P4, P5), an address ADW relating to the allocated zone ZM2 as well as DW data to write.
  • the transmitted ADW address is the address of a record to be written and is calculated by the application AP2 from the memory allocation information AL2, which here is the AD3 address of the start of the area.
  • ZM2 received in response to the allocation request RA2.
  • the request RW2 is received by the control module SC2 during a step E242.
  • control module SC2 verifies that the application AP2 is registered by searching for the application identifier IA2 in the correspondence table TC2 and that a memory area has been allocated for this application.
  • control module SC2 can not process the received request. It then returns to the AP2 application an error message. As an alternative, he does not answer. If a memory area has been allocated, the control module SC2 then verifies that the ADW address contained in the request corresponds to the address of a record accessible by the application AP2 by using the stored AL2 memory allocation information. in the table TC2 in association with the application identifier IA2 of the application AP2.
  • the control module SC2 encrypts the data at write with the key kc read in the correspondence table TC2 in association with the application identifier IA2. It obtains the encrypted data DCW.
  • the application AP2 wishes a simple integrity check on the data and, during a step E248, the control module SC2 calculates a signature SW of DW data to be written using the key ks registered in the correspondence table TC2 in association with the application identifier IA2.
  • the module SC2 determines a write command CW2 as a function of the request RW2 received. More precisely, the write command CW2 contains the type of the command (write command), the control identifier ID2, the address ADW, the encrypted data DCW and the signature SW.
  • the write command CW2 is transmitted to the management module SM2 of the terminal T2 which receives it during a step E254.
  • Step E254 is followed by step E256 in which the management module
  • SM2 verifies in the management table TM2 of the terminal T2 that the area requested for writing is reserved for the application AP2. Then, if this is the case, it controls the writing of the encrypted data DCW and the signature SW in the zone ZM2 to the address ADW (step E258).
  • step E258 is followed by a step E260 during which the management module SM2 sends back to the control module SC2 ACK information relating to the execution of the command CW2.
  • the ACK information is then transmitted by the management module SC2 to the application AP2 (step E262).
  • This management method is implemented following the allocation of a memory zone ZM2 associated with the application AP2 and external to the security module C2, according to for example an allocation method as described above.
  • the application AP2 transmits to the control module SC2 of the security module C2, a read request RR2.
  • This read request RR2 comprises the application identifier IA2 of the application AP2, the security characteristics (P4, P5) and the address ADR of a record of the external memory zone
  • the address ADR of the record is computed by the application AP2 from the address AD3 of zone start received in response to the allocation request RA2.
  • the read request RR2 is received by the control module SC2 during a step E272.
  • the control module SC2 verifies that the address ADR contained in the request RR2 corresponds to the address of a record accessible by the application AP2 by using the memory allocation information AL2 recorded in the correspondence table TC2 of the security module C2, for the AP2 application.
  • the control module SC2 determines a read command CR2 as a function of the read request RR2. More precisely, the read command CR2 contains the type of the command (read command), the control identifier ID2 read in the correspondence table TC2 and the address ADR of the record to be read. In a next step E278, the read command CR2 is transmitted to the management module SM2 of the terminal T2 which receives it during a step E280.
  • Step E280 is followed by step E282 in which the management module
  • the management module SM2 verifies in the management table TM2 that the address ADR received is an address of the allocated area ZM2 for the application AP2. Then, if this is the case, the management module SM2 controls the reading in the zone ZM2 and obtains the data D (step
  • the step E284 is followed by a step E286 during which the management module SM2 sends back to the control module SC2 the data D.
  • the control module SC2 receives these data D during a step E288. If the security feature P5 is set, the data D includes DCR data and a signature SW.
  • the control module SC2 decrypts the received data DCR with the key kc read in the correspondence table TC2 in association with the control identifier ID2. He thus obtains the decrypted data DR.
  • the application AP2 wishes a simple integrity check on the data and, during a step E292, the control module SC2 calculates a signature SR of the data decrypted DR using the key ks registered in the correspondence table TC2 in association with the control identifier ID2 and verifies that the calculated SR signature corresponds to the signature SW received with the data. This check verifies the integrity of the data received.
  • a response message containing the decrypted data DR is then transmitted by the control module SC2 to the application AP2.
  • the application AP2 is an application contained in the security module SC2.
  • the invention can also be applied to an application stored in the terminal T2.
  • the allocation method then comprises, in addition to the steps described above, an additional step in which the control module SC2 generates a key Kv, stores the key kv generated in the correspondence table TC2 in association with the control identifier ID2 and pass this kv key to the application. All the exchanges between the application and the control module are then signed with this key Kv thus allowing the application on the one hand and the security module on the other hand to verify the integrity of the exchanged data.
  • a system implementing an allocation method and / or a management method according to the invention consists, for example, of a mobile terminal 500 and a security module 520.
  • the mobile terminal 500 comprises, in a known manner, in particular a processing unit 502 equipped with a microprocessor, a read-only memory of the ROM or EEPROM type 503, an additional memory of the EEPROM type 504, a random access memory of the RAM 505 type and a module receive broadcast 506 to communicate with the security module 520 inserted into the terminal.
  • the terminal 500 may comprise in a conventional and non-exhaustive manner the following elements: a communication interface with a communication network, a keyboard, a screen, a microphone, a speaker, a disk drive, a storage means. .
  • the read-only memory 503 of the terminal 500 comprises registers storing a PGT computer program including program instructions adapted to receive a memory allocation command from a security module, to allocate a memory area according to the received allocation command, determining memory allocation information relating to said allocated area, transmitting said memory allocation information, receiving a read or write command in said allocated memory area, accessing said area allocated and transmit the read data to said allocated area.
  • the PGT program stored in the read-only memory 503 is transferred into the terminal's RAM, which will then contain executable code and registers for storing the variables necessary for the implementation of the invention.
  • a storage means readable by a computer or by a microprocessor, integrated or not into the device, possibly removable, stores a program implementing the invention.
  • the secure module 520 is for example a subscriber card which comprises, in a known manner, in particular a processing unit 521 equipped with a microprocessor, a read-only memory of the ROM 522 type, a random access memory of the RAM 523 type, a module of receive broadcast 525 to communicate with the mobile terminal 500.
  • the read-only memory 522 of the security module 520 includes registers storing one or more computer programs having program instructions adapted to execute one or more applications (AP1, AP2, ). It also includes registers storing a computer program PGC including program instructions adapted to implement an allocation method and / or management according to the invention as described with reference to Figures 1 to 7.
  • This program is and adapted to receive an external memory allocation request from an application, to transmit a memory allocation command according to said request, to receive memory allocation information determined from the control of allocation, storing the memory allocation information received in association with an identifier of said application, receiving a read or write request in an external memory, said request including the application identifier, determining a command reading or writing according to said request and the memory allocation information associated with the application identifier and transme the said read or write command for reading or writing data to the external memory.
  • the PGC program stored in the read-only memory 522 of the security module 520 is transferred to the RAM of the module of the module.
  • security which will then contain executable code and registers for storing the variables necessary for the implementation of the invention.
  • a storage means readable by a computer or by a microprocessor, integrated or not into the device, possibly removable, stores a program implementing the invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Storage Device Security (AREA)
EP09748415A 2008-09-22 2009-09-21 Speichervergabeverfahren und verfahren zum verwalten von daten in bezug auf eine anwendung, die auf ein mit einem endgerät assoziierten sicherheitsmodul aufgezeichnet werden, und diesbezügliches sicherheitsmodul und endgerät Ceased EP2342641A1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
FR0856345 2008-09-22
PCT/FR2009/051766 WO2010031976A1 (fr) 2008-09-22 2009-09-21 Procède d'allocation de mémoire et procède de gestion de données associe a une application enregistrée dans un module de sécurité associe a un terminal, module de sécurité et terminal associes

Publications (1)

Publication Number Publication Date
EP2342641A1 true EP2342641A1 (de) 2011-07-13

Family

ID=40456838

Family Applications (1)

Application Number Title Priority Date Filing Date
EP09748415A Ceased EP2342641A1 (de) 2008-09-22 2009-09-21 Speichervergabeverfahren und verfahren zum verwalten von daten in bezug auf eine anwendung, die auf ein mit einem endgerät assoziierten sicherheitsmodul aufgezeichnet werden, und diesbezügliches sicherheitsmodul und endgerät

Country Status (3)

Country Link
US (1) US20120042147A1 (de)
EP (1) EP2342641A1 (de)
WO (1) WO2010031976A1 (de)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9332060B2 (en) * 2009-12-04 2016-05-03 Telefonaktiebolaget L M Ericsson (Publ) Methods, secure element, server, computer programs and computer program products for improved application management

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060289659A1 (en) * 2005-06-24 2006-12-28 Nagamasa Mizushima Storage device

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2683357A1 (fr) * 1991-10-30 1993-05-07 Philips Composants Microcircuit pour carte a puce a memoire programmable protegee.
JP3778593B2 (ja) * 1995-06-23 2006-05-24 富士通株式会社 システム資源管理装置および管理方法
JP3745800B2 (ja) * 1995-09-29 2006-02-15 富士通株式会社 共有資源の排他制御方式
US6292874B1 (en) * 1999-10-19 2001-09-18 Advanced Technology Materials, Inc. Memory management method and apparatus for partitioning homogeneous memory and restricting access of installed applications to predetermined memory ranges
WO2004032039A1 (ja) * 2002-10-04 2004-04-15 Sony Corporation データ管理システム及びデータ管理方法、仮想メモリ装置及び仮想メモリの制御方法、リーダ/ライタ装置、並びにicモジュール・アクセス装置及びicモジュールのアクセス制御方法
FR2849233B1 (fr) * 2002-12-24 2005-05-20 Trusted Logic Procede de securisation des systemes informatiques par confinement logiciel
JP2004334542A (ja) * 2003-05-08 2004-11-25 Dainippon Printing Co Ltd Icカード、icカードプログラム及びicカードのメモリ領域の割当方法
JP2005122402A (ja) * 2003-10-15 2005-05-12 Systemneeds Inc Icカードシステム
JP4717381B2 (ja) * 2004-06-11 2011-07-06 株式会社エヌ・ティ・ティ・ドコモ 移動機、及び、アクセス制御方法
WO2008084154A2 (fr) * 2006-12-19 2008-07-17 France Telecom Traitement de donnee relative a un service numerique
TWI332664B (en) * 2007-06-13 2010-11-01 Phison Electronics Corp Data accessing system, controller and store device having the same and operation method thereof
US8839030B2 (en) * 2011-09-09 2014-09-16 Lsi Corporation Methods and structure for resuming background tasks in a clustered storage environment

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060289659A1 (en) * 2005-06-24 2006-12-28 Nagamasa Mizushima Storage device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of WO2010031976A1 *

Also Published As

Publication number Publication date
WO2010031976A1 (fr) 2010-03-25
US20120042147A1 (en) 2012-02-16

Similar Documents

Publication Publication Date Title
US8200281B2 (en) Secure removable card and a mobile wireless communication device
EP1687953B1 (de) Verfahren zur authentifikation von anwendungen
EP1903746B1 (de) Verfahren zur Sicherung von Sitzungen zwischen einem Funkendgerät und einer Einrichtung in einem Netz
US8788849B2 (en) Method and apparatus for protecting cached streams
US9262594B2 (en) Tamper evidence per device protected identity
US7979717B2 (en) Secure removable card having a plurality of integrated circuit dies
US20130173916A1 (en) Secure storage system for distributed data
US20150089247A1 (en) Storage medium having security function and security method thereof
WO2002073930A1 (fr) Dispositif portable pour securiser le trafic de paquets dans une plate-forme hote
CN1889426A (zh) 一种实现网络安全存储与访问的方法及系统
FR3006082A1 (fr) Procede de mise en œuvre d'un droit sur un contenu
JP2009543211A5 (de)
EP1376367A2 (de) Überprüfung der Integrität von auf einem integrierten Prozessor laufenden Programmkodes
WO2007066039A2 (fr) Recouvrement de cles de dechiffrement perimees
EP1645070A1 (de) Verfahren zum sichern eines elektronischen zertifikats
EP2342641A1 (de) Speichervergabeverfahren und verfahren zum verwalten von daten in bezug auf eine anwendung, die auf ein mit einem endgerät assoziierten sicherheitsmodul aufgezeichnet werden, und diesbezügliches sicherheitsmodul und endgerät
US20050021469A1 (en) System and method for securing content copyright
WO2006035159A1 (fr) Systeme et procede cryptographique a cle publique et serveur de certification, memoires adaptees pour ce systeme
KR100608604B1 (ko) 객체 식별자를 이용하여 이동형 저장 장치에서 권리객체를 검색하는 방법 및 장치
KR102485722B1 (ko) 분산 스토리지를 기반으로 적응형 스트리밍 서비스를 제공하기 위한 장치, 방법, 및 시스템
WO2019216847A2 (en) A sim-based data security system
WO2003013063A1 (fr) Methode pour creer un reseau virtuel prive utilisant un reseau public
EP2005703A1 (de) Einrichtung zur wiedergabe von digitalem inhalt, sichere elektronische entität, system mit diesen elementen und verfahren zum wiedergeben von digitalem inhalt
EP1636767B1 (de) Verfahren zur zuweisung von gesicherten ressourcen in einem sicherheitsmodul
FR3119471A1 (fr) Démarrage d'une application

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20110407

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Extension state: AL BA RS

RIN1 Information on inventor provided before grant (corrected)

Inventor name: ROCHECOUSTE, OLIVIER

Inventor name: DUC, GUILLAUME

Inventor name: RAIPIN PARVEDY, PHILIPPE

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20130823

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ORANGE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20171208