EP1793313A1 - External memory management apparatus and external memory management method - Google Patents
External memory management apparatus and external memory management method Download PDFInfo
- Publication number
- EP1793313A1 EP1793313A1 EP06019185A EP06019185A EP1793313A1 EP 1793313 A1 EP1793313 A1 EP 1793313A1 EP 06019185 A EP06019185 A EP 06019185A EP 06019185 A EP06019185 A EP 06019185A EP 1793313 A1 EP1793313 A1 EP 1793313A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- application
- external memory
- identifier
- identification information
- wireless communication
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/14—Protection against unauthorised use of memory or access to memory
- G06F12/1458—Protection against unauthorised use of memory or access to memory by checking the subject access rights
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/02—Constructional features of telephone sets
- H04M1/0202—Portable telephone sets, e.g. cordless phones, mobile phones or bar type handsets
- H04M1/0254—Portable telephone sets, e.g. cordless phones, mobile phones or bar type handsets comprising one or a plurality of mechanically detachable modules
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
- H04M1/72412—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories using two-way short-range wireless interfaces
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72406—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by software upgrading or downloading
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2250/00—Details of telephonic subscriber devices
- H04M2250/14—Details of telephonic subscriber devices including a card reading device
Definitions
- the present invention relates to an external memory management apparatus and external memory management method for controlling access of an application downloaded in a wireless communication terminal, to a removable external memory.
- wireless communication terminals e.g., cell phones increase diversity of their functionality in recent years, a required storage capacity is also increasing in order to implement the diversity of multiple functions.
- the wireless communication terminals are also being downsized, and there are thus cases where the whole required storage capacity cannot be located inside the wireless communication terminal. For this reason, for example, an external memory device has been and is being used in order to accept the increased storage capacity.
- Patent Document 1 Japanese Patent Application Laid-Open No. 2004-40717
- wireless communication terminals the Internet-related functionality of wireless communication terminals is also becoming diversified in recent years, and applications used therein are also being diversified.
- applications are downloaded via the Internet from an unspecified large number of distributors.
- an external memory device or the like is used in order to secure a storage capacity necessary for storage of data handled by the applications.
- the present invention has been accomplished in view of the above circumstances and an object of the invention is to provide an external memory management apparatus and external memory management method capable of preventing an unauthorized application from assuming an encrypted key for access to an external memory and achieving safer management of the access to the external memory.
- an external memory management apparatus for controlling access of an application downloaded in a wireless communication terminal, to a removable external memory, comprising: acquiring means for acquiring an identifier from the application downloaded; generating means for generating specific information to specify the application, based on identification information designated by the identifier acquired by the acquiring means; reserving means for reserving a predetermined area of the external memory as a storage area available for the application; and writing means for writing the specific information generated by the generating means, in attribute information of the storage area reserved by the reserving means.
- An external memory management method is an external memory management method of controlling access of an application downloaded in a wireless communication terminal, to a removable external memory, comprising: an acquiring step wherein acquiring means acquires an identifier from the application downloaded; a generating step wherein generating means generates specific information to specify the application, based on identification information designated by the identifier acquired in the acquiring step; a reserving step wherein reserving means reserves a predetermined area of the external memory as a storage area available for the application; and a writing step wherein writing means writes the specific information generated in the generating step, in attribute information of the storage area reserved in the reserving step.
- the external memory management apparatus and external memory management method according to the present invention are arranged to acquire only an identifier, i.e., only a type of relevant identification information from an application downloaded in the wireless communication terminal. Then the generating means generates the specific information peculiar to the application, based on the identification information designated by this identifier.
- the specific information peculiar to the application is not generated by the application, but generated by the generating means in the present invention as described above, it becomes feasible, for example, to prevent another application not sharing data with the application of interest, from falsifying and assuming this specific information without permission.
- the writing means After the reserving means reserves the storage area for the application in the external memory, the writing means writes the specific information in the attribute information of the storage area reserved. Therefore, this enables the information restricted to the application only to be written in the attribute information of the reserved storage area, whereby use of the storage area with the attribute information can be limited to the application only.
- the acquiring means acquires from the application an application identifier to identify the application, and a wireless communication terminal identifier to identify the wireless communication terminal, and the generating means generates specific information to specify the application and the wireless communication terminal, based on application identification information designated by the application identifier and based on wireless communication terminal identification information designated by the wireless communication terminal identifier.
- the external memory management apparatus uses the application identification information and the wireless communication terminal identification information as the identification information being a basis for generation of the specific information. For this reason, the writing means becomes able to write the specific information limited to the application and the wireless communication terminal only, in the attribute file in the external memory. Therefore, use of the storage area specified by the specific information can be limited to the application and the wireless communication terminal only.
- the present invention prevents an unauthorized application from falsifying and assuming the specific information generated for access to the external memory, without permission, and enables safer management of access to the external memory.
- Fig. 1 is a schematic diagram to illustrate a configuration of cell phone 1 incorporating external memory function module 15 according to an embodiment of the present invention.
- Fig. 2 is a drawing to illustrate an example of data stored in ADF 102A.
- Fig. 3 is a drawing to illustrate an example of data stored in UIM 13 or in management information storage 14.
- Fig. 4 is a schematic diagram to illustrate a configuration of external memory function module 15 in Fig. 1.
- Fig. 5 is a flowchart to illustrate an operation of external memory function module 15 in Fig. 1.
- Fig. 6 is a flowchart to illustrate an operation of external memory function module 15 in Fig. 1.
- Fig. 7 is a sequence diagram to illustrate an operation of external memory function module 15 in Fig. 1.
- Fig. 8 is a sequence diagram to illustrate an operation of external memory function module 15 in Fig. 1.
- Fig. 1 is a schematic diagram of the configuration of cell phone 1.
- the cell phone 1 is composed of internal memory 10, VM 11 (Virtual Machine), implementation request API (Application Program Interface) 12, UIM 13 (User Identity Module), management information storage 14, and external memory function module 15.
- VM 11 Virtual Machine
- implementation request API Application Program Interface
- UIM 13 User Identity Module
- management information storage 14 external memory function module 15.
- This internal memory 10 Stored in the internal memory 10 are applications 101A and 101B, and ADFs (Attribute Definition Files) 102A and 102B corresponding to the applications 101A and 101B.
- This internal memory 10 is configured to be able to transmit and receive information to and from the external memory function module 15.
- the applications 101A and 101B stored in the internal memory 10 are applications that were downloaded via the Internet from an unspecified large number of contents providers, for example, by a downloading means (not shown) of cell phone 1 and that are stored in an operable state in cell phone 1. Namely, the applications downloaded are supplied from different distributors and data handled by each application is not shared, for example, between application 101A and application 101B. These applications 101A and 101B are implemented so as to operate on VM 11 and implementation request API 12.
- VM 11 is software, for example, that performs transformation of formats so that the applications 101A and 101B are workable on an OS (Operating System) of cell phone 1.
- API 12 is so-called middleware that provides functionality of common use among applications.
- ADFs 102A and 102B contain data about attributes of the applications 101A and 101B. Specifically, each of the ADFs 102A and 102B contains a record of an AP-ID for identification of the application, a CP-ID for identification of a contents provider having produced and distributed the application, and so on.
- Fig. 2 shows an example of data recorded in the ADF 102A.
- the AP-ID is identification information for the application 101A, for example, a URL (e.g., "www.aplication-a.com/download.html") of a download source of the application 101A, in the form of digitized data of the URL according to a predetermined arithmetic.
- the CP-ID is identification information for the contents provider, e.g., a name of the contents provider having produced and distributed the application 101A (e.g., "Corp. AAA”), in the form of digitized data of the name according to a predetermined arithmetic.
- the UIM 13 is constructed, for example, of an IC card and is removably mounted in a card slot (not shown) of cell phone 1.
- the management information storage 14 is, for example, a storage device in cell phone 1 and is constructed, for example, of a ROM (Read Only Memory).
- Stored in the UIM 13 or in the management information storage 14 is data about attributes of the cell phone 1 such as subscriber information.
- Fig. 3 shows an example of data stored in UIM 13 or in management information storage 14. As shown in Fig.
- the UIM 13 or management information storage 14 stores digital data such as a model ID ("MOBILE101 ”) indicating a model of the cell phone 1, a series ID ("1234") indicating a series number of the cell phone 1, a UIM-ID (“UIM-MOBILE101-1234”) for identification of UIM 13, and so on.
- the UIM 13 and management information storage 14 are implemented so as to be able to transmit and receive information to and from the external memory function module 15.
- the above-described model ID, series ID, UIM-ID, and so on as names of types of information correspond to the wireless communication terminal identifier in the present invention.
- "MOBILE101,” “1234,” “UIM-MOBILE101-1234,” and so on as actual contents of information designated by the wireless communication terminal identifier correspond to the wireless communication terminal identification information in the present invention.
- the external memory function module 15 is a function module that controls access of the downloaded applications 101A and 101B to the removable external memory 2.
- Fig. 4 is a schematic diagram of a configuration of this external memory function module 15. As shown in Fig. 4, the external memory function module 15 is composed of identifier acquirer (acquiring means) 151, identification information acquirer 152, generator (generating means) 153, reserving section (reserving means) 154, writing section (writing means) 155, controller 156, and notifier 157. Each of the components of the external memory function module 15 will be described below in detail.
- the identifier acquirer 151 is a part that acquires an identifier such as an application identifier or a wireless communication terminal identifier designated by the applications 101A and 101B. Namely, when the applications 101A and 101B designate, for example, one or more of the AP-ID, CP-ID, model ID, series ID, and UIM-ID as an application identifier or wireless communication terminal identifier, the identifier acquirer 151 acquires the identifier designated and outputs it to the identification information acquirer 152. Which identifier is designated by the applications 101A and 101B is determined according to a predetermined rule between the applications and the external memory function module 15. In order to ensure the security, none except for the applications is informed of this rule.
- the identification information acquirer 152 accepts input of the identifiers designated by the applications 101A and 101B, from the identifier acquirer 151, and acquires the identification information corresponding to the input of identifiers from the ADFs 102A and 102B, UIM 13, or management information storage 14. More specifically, for example, supposing the application 101A designates the AP-ID and CP-ID as the application identifier, the identification information acquirer 152 acquires the digital data of "www.aplication-a.com/download.html" and "Corp. AAA" recorded in the ADF 102A, as the application identification information corresponding to the AP-ID and CP-ID.
- the identification information acquirer 152 acquires the digital data of "MOBILE101,” “1234,” and “UIM-MOBILE101-1234" stored in UIM 13 or in management information storage 14, as the wireless communication terminal identification information corresponding to the model ID, series ID, and UIM-ID. Then the identification information acquirer 152 outputs to the generator 153 the application identification information and the wireless communication terminal identification information acquired in this manner.
- the generator 153 generates a bind ID (specific information) to specify the application and the cell phone 1 on which the application is mounted, based on the application identification information and the wireless communication terminal identification information fed from the identification information acquirer 152.
- the present embodiment adopts a well-known hash function as a generation algorithm for the bind ID used in this operation. Namely, in a case where the application identification information and the wireless communication terminal identification information supplied is "www.aplication-a.com/download.html,” “Corp. AAA,” “MOBILE101,” “1234,” and “UIM-MOBILE101-1234,” the generator 153 uses the identification information as arguments of the hash function to obtain a hash value and defines the hash value as a bind ID of the application. This hash function is appropriately selected, for example, in view of a security level of the external memory management or simplicity of implementation.
- the generator 153 outputs the bind ID generated in this manner, to the writing section 155 and to the controller 156.
- the reserving section 154 is a part that reserves a predetermined area in the external memory 2 as a directory (storage area) available for each of the applications 101A and 101B.
- the external memory 2 to be used in the present embodiment is, for example, a general-purpose removable memory device such as the SD memory card (Secure Digital Memory Card), SmartMedia (registered trademark), or Compact Flash (registered trademark).
- SD memory card Secure Digital Memory Card
- SmartMedia registered trademark
- Compact Flash registered trademark
- a number of directories e.g., directories 20A and 20B
- the reserving section 154 reserves the directories thus made, as storage areas for the respective applications.
- the reserving section 154 reserves directory 20A as a storage area available for the application 101A, and reserves directory 20B as a storage area available for the application 101B.
- the writing section 155 is a part that writes the bind ID generated by the generator 153, as a discrimination ID of each directory in an attribute file (attribute information) 21 of the external memory 2. Namely, for example, when the reserving section 154 reserves the directory 20A as a storage area available for the application 101A, the writing section 155 writes the bind ID generated by the generator 153 on the basis of the identification information corresponding to the identifier designated by the application 101A, as a discrimination ID of the directory 20A in the attribute file 21.
- the controller 156 is a part that controls access of the applications 101A and 101B downloaded via the Internet from an unspecified large number of contents providers, to the directories 20A and 20B in the external memory 2. Specifically, when there arises a request for decryption of electronic data stored in the external memory 2, the controller 156 checks the bind ID generated by the generator 153, against the directory discrimination ID recorded in the attribute file 21. When the result of this check is that the directory discrimination ID coincides with the bind ID, the controller 156 performs such control as to permit access of the application to the directory. Namely, the controller 156 extracts, for example, the electronic data under the request for decryption by the application from the directory in the external memory 2 and outputs the data to the application.
- the external memory function module 15 further comprises decryption requested data importing means (not shown).
- This decryption requested data importing means is a means for importing information to specify electronic data as an object under a request for decryption, from the application and for exporting it to the controller 156.
- the controller 156 performs such control as to inhibit access of the application to the directory. Namely, the controller 156 does not extract, for example, the electronic data under the request for decryption by the application from the directory in the external memory 2, and outputs information to indicate the inhibition of access of the application to the directory, to notifier 157.
- the notifier 157 is a part that imports information indicating permission/inhibition of access of the application to the directory from the controller 156 and that notifies the application of the information.
- the application receiving the notification can determine which area it is allowed to access in the external memory 2.
- Fig. 5 is a flowchart for explaining the operation of the external memory function module 15 in a situation in which the directory 20A is reserved as a storage area for the application 101A.
- the application 101A designates the AP-ID, CP-ID, model ID, series ID, and UIM-ID as the application identifier and the wireless communication terminal identifier, and then the identifier acquirer 151 acquires the identifiers thus designated. Then the identifiers thus acquired are fed to the identification information acquirer 152 (step S101).
- the identification information acquirer 152 acquires the identification information corresponding to the identifiers acquired at step S101, from the ADF 102A, UIM 13, or management information storage 14. Specifically, the identification information acquirer 152 acquires from the ADF 102A, the digital data of "www.aplication-a.com/download.html" corresponding to the AP-ID of the application identifier and the digital data of "Corp. AAA" corresponding to the CP-ID, as the application identification information.
- the identification information acquirer 152 acquires from the UIM 13 or from the management information storage 14, the digital data of "MOBILE101” corresponding to the model ID of the wireless communication terminal identifier, the digital data of "1234" corresponding to the series ID, and the digital data of "UIM-MOBILE101-1234" corresponding to the UIM-ID, as the wireless communication terminal identification information. Then the acquirer 152 feeds the application identification information and the wireless communication terminal identification information acquired in this manner, to the generator 153 (step S 102).
- the generator 153 generates the bind ID to specify the application 101A and the cell phone 1, based on the identification information acquired at step S102, using the predetermined hash function. On this occasion, the identification information fed to the generator 153 at step S 102 is used as arguments in the hash function, and a hash value calculated is defined as the bind ID. Then the bind ID generated in this manner is fed to the writing section 155 (step S103).
- the reserving section 154 reserves the directory 20A in the external memory 2 not allocated yet to another application, as a storage area available for the application 101A (step S104).
- the writing section 155 writes the bind ID generated at step S103, as a discrimination ID of the directory 20A reserved at step S104, in the attribute file 21 of the external memory 2 (step S105). This associates the directory 20A with only the application 101A. Furthermore, since the bind ID is not generated by the application 101A but generated by the generator 153, it is feasible, for example, to prevent another application not sharing data with the application 101A, from falsifying and assuming this bind ID without permission.
- Fig. 6 is a flowchart for explaining the operation of the external memory function module 15 in the case where the application 101A is allowed to access the directory 20A.
- the application 101A designates the AP-ID, CP-ID, model ID, series ID, and UIM-ID as the application identifier and the wireless communication terminal identifier, and then the identifier acquirer 151 acquires the identifiers thus designated. Then the identifiers thus acquired are fed to the identification information acquirer 152 (step S201).
- the identification information acquirer 152 acquires the identification information corresponding to the identifiers acquired at step S201, from the ADF 102A, UIM 13, or management information storage 14. Specifically, the identification information acquirer 152 acquires from the ADF 102A, the digital data of "www.aplication-a.com/download.html" corresponding to the AP-ID of the application identifier and the digital data of "Corp. AAA" corresponding to the CP-ID, as the application identification information.
- the identification information acquirer 152 acquires from the UIM 13 or from the management information storage 14, the digital data of "MOBILE101” corresponding to the model ID of the wireless communication terminal identifier, the digital data of "1234" corresponding to the series ID, and the digital data of "UIM-MOBILE101-1234" corresponding to the UIM-ID, as the wireless communication terminal identification information. Then the acquirer 152 feeds the application identification information and the wireless communication terminal identification information acquired in this manner, to the generator 153 (step S202).
- the generator 153 generates the bind ID to specify the application 101A and the cell phone 1, on the basis of the identification information acquired at step S202, using the predetermined hash function. On this occasion, the identification information fed to the generator 153 at step S202 is used as arguments in the hash function, and a hash value calculated is defined as the bind ID. Then the bind ID generated in this manner is fed to the controller 156 (step S203).
- step S204 the directory discrimination ID recorded in the attribute file 21 of the external memory 2 is checked against the bind ID peculiar to the application 101A (step S204), which was generated at step S203.
- the directory discrimination ID recorded in the attribute file 21 refers to the directory discrimination ID written in the attribute file 21 at the aforementioned steps S101-S105.
- the controller 156 performs such control as to permit access of the application 101A to the directory 20A (step S205). This permits the application 101A to access and decrypt the data stored in the directory 20A.
- the controller 156 performs such control as to inhibit access of the application 101A to the directory 20A. Then the notifier 157 notifies the application 101A of notification information to indicate the inhibition of access of the application 101A to the directory 20A (step S206).
- Fig. 7 is a sequence diagram for explaining the operation of the external memory function module 15, for example, in a situation in which the directory 20A is reserved as a storage area for the application 101A.
- the identifier i.e., only the type of relevant identification information is acquired from the application 101A downloaded in the cell phone 1 (step S301).
- the external memory function module 15 generates the bind ID, based on the identification information designated by this identifier (step S302).
- the bind ID as the specific information peculiar to the application 101A and the cell phone 1 is not generated by the application 101A side but generated by the external memory function module 15 side of the present embodiment as described above, it is feasible, for example, to prevent another application not sharing data with the application 101A, from falsifying and assuming this bind ID without permission.
- the external memory function module 15 reserves the directory 20A for the application 101A in the external memory 2 (step S303) and writes the bind ID as a discrimination ID for the directory 20A in the attribute file 21 (step S304). Therefore, it becomes feasible to write the information restricted to the application 101A only, in the attribute file 21, and thus the use of the directory 20A with the attribute file 21 can be limited to the application 101A only.
- Fig. 8 is a sequence diagram for explaining the operation of the external memory function module 15, for example, in a situation in which the application 101A is allowed to access the directory 20A.
- the application 101A designates electronic data as an object for decryption and an identifier for generation of the bind ID (step S401), and then the external memory function module 15 checks the directory discrimination ID recorded in the attribute file 21 of the external memory 2, against the bind ID generated by the external memory function module 15 itself on the basis of the identifier designated at step S401 (step S402 and step S403).
- the directory discrimination ID preliminarily contains a record of information to specify the application permitted to access the directory 20A with the directory discrimination ID.
- the external memory function module 15 is able to perform such control as to permit the application 101A to access only the directory with the directory discrimination ID coinciding with the bind ID (step S404).
- the control on this occasion is carried out, for example, in such a manner that the external memory function module 15 extracts the electronic data under the request for decryption from the directory 20A and transfers it to the application 101A. Therefore, it is feasible to prevent a downloaded application from extracting data in the external memory 2 unrelated to the application and from becoming able to decrypt the data.
- the present embodiment uses the application identification information such as the AP-ID and CP-ID, and the wireless communication terminal identification information such as the model ID, series ID, and UIM-ID, as the identification information being a basis for generation of the bind ID. For this reason, the external memory function module 15 becomes able to write the bind ID limited to the application and cell phone 1 only, in the attribute file 21 in the external memory 2. Therefore, the use of the directory specified by the directory discrimination ID can be limited to the application and the cell phone only.
- the present embodiment used the cell phone 1 as a wireless communication terminal, but, without having to be limited to it, the present invention can also be readily applied to so-called portable terminals such as PDA (Personal Digital Assistance).
- portable terminals such as PDA (Personal Digital Assistance).
- the present embodiment was provided with one attribute file 21 corresponding to the whole of the external memory 2, but it is also possible to provide separate attribute files for a large number of respective directories in the external memory 2.
- the directory discrimination ID may also be configured to further contain a memory address or the like on the external memory 2 for each directory reserved by the reserving section 154, in addition to the information contained in the bind ID.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mobile Radio Communication Systems (AREA)
- Storage Device Security (AREA)
- Telephone Function (AREA)
Abstract
Description
- The present invention relates to an external memory management apparatus and external memory management method for controlling access of an application downloaded in a wireless communication terminal, to a removable external memory.
- As wireless communication terminals, e.g., cell phones increase diversity of their functionality in recent years, a required storage capacity is also increasing in order to implement the diversity of multiple functions. On the other hand, the wireless communication terminals are also being downsized, and there are thus cases where the whole required storage capacity cannot be located inside the wireless communication terminal. For this reason, for example, an external memory device has been and is being used in order to accept the increased storage capacity.
- In use of such an external memory device, it is necessary to ensure security of data stored in the memory device and to implement such control that the data stored in the external memory device is available for a registered cell phone only, for example, as in the technology described in
Patent Document 1 below. ThisPatent Document 1 describes that it is determined whether a key held by the cell phone coincides with a key held by the memory device and that use of the data stored in the specific memory device is limited to only the specific cell phone.
[Patent Document 1]Japanese Patent Application Laid-Open No. 2004-40717 - Incidentally, the Internet-related functionality of wireless communication terminals is also becoming diversified in recent years, and applications used therein are also being diversified. In general, such applications are downloaded via the Internet from an unspecified large number of distributors. In a situation where a number of applications from different distributors are downloaded and used in a wireless communication terminal, it is also contemplated that an external memory device or the like is used in order to secure a storage capacity necessary for storage of data handled by the applications.
- In such a situation, it is often the case that an identical external memory device is used among different types of applications downloaded from different creators, in view of simplicity of implementation and convenience of use. At this time, it is undesirable to unconditionally permit the different types of applications downloaded, to access the same external memory, from the aspect of safety management of the data stored in the external memory.
- It is thus necessary to implement safe management of access to the external memory device, for example, based on matching of encrypted keys or the like, so as to restrict access to the memory to only specific authorized applications. However, the encrypted keys or the like might be falsified and assumed by another unauthorized application and in that case there arises a problem of failure in restriction on the access.
- The present invention has been accomplished in view of the above circumstances and an object of the invention is to provide an external memory management apparatus and external memory management method capable of preventing an unauthorized application from assuming an encrypted key for access to an external memory and achieving safer management of the access to the external memory.
- In order to solve the above problem, an external memory management apparatus according to the present invention is an external memory management apparatus for controlling access of an application downloaded in a wireless communication terminal, to a removable external memory, comprising: acquiring means for acquiring an identifier from the application downloaded; generating means for generating specific information to specify the application, based on identification information designated by the identifier acquired by the acquiring means; reserving means for reserving a predetermined area of the external memory as a storage area available for the application; and writing means for writing the specific information generated by the generating means, in attribute information of the storage area reserved by the reserving means.
- An external memory management method according to the present invention is an external memory management method of controlling access of an application downloaded in a wireless communication terminal, to a removable external memory, comprising: an acquiring step wherein acquiring means acquires an identifier from the application downloaded; a generating step wherein generating means generates specific information to specify the application, based on identification information designated by the identifier acquired in the acquiring step; a reserving step wherein reserving means reserves a predetermined area of the external memory as a storage area available for the application; and a writing step wherein writing means writes the specific information generated in the generating step, in attribute information of the storage area reserved in the reserving step.
- The external memory management apparatus and external memory management method according to the present invention are arranged to acquire only an identifier, i.e., only a type of relevant identification information from an application downloaded in the wireless communication terminal. Then the generating means generates the specific information peculiar to the application, based on the identification information designated by this identifier. When the specific information peculiar to the application is not generated by the application, but generated by the generating means in the present invention as described above, it becomes feasible, for example, to prevent another application not sharing data with the application of interest, from falsifying and assuming this specific information without permission.
- After the reserving means reserves the storage area for the application in the external memory, the writing means writes the specific information in the attribute information of the storage area reserved. Therefore, this enables the information restricted to the application only to be written in the attribute information of the reserved storage area, whereby use of the storage area with the attribute information can be limited to the application only.
- In the external memory management apparatus of the present invention, preferably, the acquiring means acquires from the application an application identifier to identify the application, and a wireless communication terminal identifier to identify the wireless communication terminal, and the generating means generates specific information to specify the application and the wireless communication terminal, based on application identification information designated by the application identifier and based on wireless communication terminal identification information designated by the wireless communication terminal identifier.
- According to the present invention, the external memory management apparatus uses the application identification information and the wireless communication terminal identification information as the identification information being a basis for generation of the specific information. For this reason, the writing means becomes able to write the specific information limited to the application and the wireless communication terminal only, in the attribute file in the external memory. Therefore, use of the storage area specified by the specific information can be limited to the application and the wireless communication terminal only.
- The present invention prevents an unauthorized application from falsifying and assuming the specific information generated for access to the external memory, without permission, and enables safer management of access to the external memory.
- Fig. 1 is a schematic diagram to illustrate a configuration of
cell phone 1 incorporating externalmemory function module 15 according to an embodiment of the present invention. - Fig. 2 is a drawing to illustrate an example of data stored in ADF 102A.
- Fig. 3 is a drawing to illustrate an example of data stored in
UIM 13 or inmanagement information storage 14. - Fig. 4 is a schematic diagram to illustrate a configuration of external
memory function module 15 in Fig. 1. - Fig. 5 is a flowchart to illustrate an operation of external
memory function module 15 in Fig. 1. - Fig. 6 is a flowchart to illustrate an operation of external
memory function module 15 in Fig. 1. - Fig. 7 is a sequence diagram to illustrate an operation of external
memory function module 15 in Fig. 1. - Fig. 8 is a sequence diagram to illustrate an operation of external
memory function module 15 in Fig. 1. - The present invention can be readily understood in view of the following detailed description with reference to the accompanying drawings presented by way of illustration only. Subsequently, embodiments of the present invention will be described with reference to the accompanying drawings. An embodiment of the present invention will be described below using an example of a situation where the external memory management apparatus of the present invention is mounted and used as an external memory function module in a cell phone as a wireless communication terminal. This external memory function module operates as a function module to control access of an application downloaded in a cell phone, to a removable external memory. The same portions will be denoted by the same reference symbols as much as possible, without redundant description.
- First, a configuration of
cell phone 1 in which the externalmemory function module 15 according to the embodiment of the present invention is mounted, will be described with reference to Fig. 1. Fig. 1 is a schematic diagram of the configuration ofcell phone 1. As shown in Fig. 1, thecell phone 1 is composed ofinternal memory 10, VM 11 (Virtual Machine), implementation request API (Application Program Interface) 12, UIM 13 (User Identity Module),management information storage 14, and externalmemory function module 15. Each of the components of thecell phone 1 will be described below in detail. - Stored in the
internal memory 10 areapplications applications internal memory 10 is configured to be able to transmit and receive information to and from the externalmemory function module 15. - The
applications internal memory 10 are applications that were downloaded via the Internet from an unspecified large number of contents providers, for example, by a downloading means (not shown) ofcell phone 1 and that are stored in an operable state incell phone 1. Namely, the applications downloaded are supplied from different distributors and data handled by each application is not shared, for example, betweenapplication 101A andapplication 101B. Theseapplications VM 11 andimplementation request API 12. VM 11 is software, for example, that performs transformation of formats so that theapplications cell phone 1. API 12 is so-called middleware that provides functionality of common use among applications. - ADFs 102A and 102B contain data about attributes of the
applications ADFs - Fig. 2 shows an example of data recorded in the ADF 102A. As shown in Fig. 2, the AP-ID is identification information for the
application 101A, for example, a URL (e.g., "www.aplication-a.com/download.html") of a download source of theapplication 101A, in the form of digitized data of the URL according to a predetermined arithmetic. The CP-ID is identification information for the contents provider, e.g., a name of the contents provider having produced and distributed theapplication 101A (e.g., "Corp. AAA"), in the form of digitized data of the name according to a predetermined arithmetic. The above-described AP-ID and CP-ID as names of types of information correspond to the application identifier in the present invention. Furthermore, "www.aplication-a.com/download.html" and "Corp. AAA" as actual contents of information designated by the application identifier correspond to the application identification information in the present invention. - The
UIM 13 is constructed, for example, of an IC card and is removably mounted in a card slot (not shown) ofcell phone 1. Themanagement information storage 14 is, for example, a storage device incell phone 1 and is constructed, for example, of a ROM (Read Only Memory). Stored in theUIM 13 or in themanagement information storage 14 is data about attributes of thecell phone 1 such as subscriber information. Fig. 3 shows an example of data stored inUIM 13 or inmanagement information storage 14. As shown in Fig. 3, theUIM 13 ormanagement information storage 14 stores digital data such as a model ID ("MOBILE101 ") indicating a model of thecell phone 1, a series ID ("1234") indicating a series number of thecell phone 1, a UIM-ID ("UIM-MOBILE101-1234") for identification ofUIM 13, and so on. TheUIM 13 andmanagement information storage 14 are implemented so as to be able to transmit and receive information to and from the externalmemory function module 15. The above-described model ID, series ID, UIM-ID, and so on as names of types of information correspond to the wireless communication terminal identifier in the present invention. Furthermore, "MOBILE101," "1234," "UIM-MOBILE101-1234," and so on as actual contents of information designated by the wireless communication terminal identifier correspond to the wireless communication terminal identification information in the present invention. - Returning to Fig. 1, the external
memory function module 15 is a function module that controls access of the downloadedapplications external memory 2. Fig. 4 is a schematic diagram of a configuration of this externalmemory function module 15. As shown in Fig. 4, the externalmemory function module 15 is composed of identifier acquirer (acquiring means) 151,identification information acquirer 152, generator (generating means) 153, reserving section (reserving means) 154, writing section (writing means) 155,controller 156, andnotifier 157. Each of the components of the externalmemory function module 15 will be described below in detail. - The
identifier acquirer 151 is a part that acquires an identifier such as an application identifier or a wireless communication terminal identifier designated by theapplications applications identifier acquirer 151 acquires the identifier designated and outputs it to theidentification information acquirer 152. Which identifier is designated by theapplications memory function module 15. In order to ensure the security, none except for the applications is informed of this rule. - The
identification information acquirer 152 accepts input of the identifiers designated by theapplications identifier acquirer 151, and acquires the identification information corresponding to the input of identifiers from theADFs UIM 13, ormanagement information storage 14. More specifically, for example, supposing theapplication 101A designates the AP-ID and CP-ID as the application identifier, theidentification information acquirer 152 acquires the digital data of "www.aplication-a.com/download.html" and "Corp. AAA" recorded in theADF 102A, as the application identification information corresponding to the AP-ID and CP-ID. In a case where theapplication 101A designates the model ID, series ID, and UIM-ID as the wireless communication terminal identifier, theidentification information acquirer 152 acquires the digital data of "MOBILE101," "1234," and "UIM-MOBILE101-1234" stored inUIM 13 or inmanagement information storage 14, as the wireless communication terminal identification information corresponding to the model ID, series ID, and UIM-ID. Then theidentification information acquirer 152 outputs to thegenerator 153 the application identification information and the wireless communication terminal identification information acquired in this manner. - The
generator 153 generates a bind ID (specific information) to specify the application and thecell phone 1 on which the application is mounted, based on the application identification information and the wireless communication terminal identification information fed from theidentification information acquirer 152. The present embodiment adopts a well-known hash function as a generation algorithm for the bind ID used in this operation. Namely, in a case where the application identification information and the wireless communication terminal identification information supplied is "www.aplication-a.com/download.html," "Corp. AAA," "MOBILE101," "1234," and "UIM-MOBILE101-1234," thegenerator 153 uses the identification information as arguments of the hash function to obtain a hash value and defines the hash value as a bind ID of the application. This hash function is appropriately selected, for example, in view of a security level of the external memory management or simplicity of implementation. Thegenerator 153 outputs the bind ID generated in this manner, to thewriting section 155 and to thecontroller 156. - The reserving
section 154 is a part that reserves a predetermined area in theexternal memory 2 as a directory (storage area) available for each of theapplications external memory 2 to be used in the present embodiment is, for example, a general-purpose removable memory device such as the SD memory card (Secure Digital Memory Card), SmartMedia (registered trademark), or Compact Flash (registered trademark). As shown in Fig. 1, a number of directories, e.g.,directories external memory 2, and the reservingsection 154 reserves the directories thus made, as storage areas for the respective applications. In the present embodiment, the reservingsection 154reserves directory 20A as a storage area available for theapplication 101A, andreserves directory 20B as a storage area available for theapplication 101B. - The
writing section 155 is a part that writes the bind ID generated by thegenerator 153, as a discrimination ID of each directory in an attribute file (attribute information) 21 of theexternal memory 2. Namely, for example, when the reservingsection 154 reserves thedirectory 20A as a storage area available for theapplication 101A, thewriting section 155 writes the bind ID generated by thegenerator 153 on the basis of the identification information corresponding to the identifier designated by theapplication 101A, as a discrimination ID of thedirectory 20A in theattribute file 21. - The
controller 156 is a part that controls access of theapplications directories external memory 2. Specifically, when there arises a request for decryption of electronic data stored in theexternal memory 2, thecontroller 156 checks the bind ID generated by thegenerator 153, against the directory discrimination ID recorded in theattribute file 21. When the result of this check is that the directory discrimination ID coincides with the bind ID, thecontroller 156 performs such control as to permit access of the application to the directory. Namely, thecontroller 156 extracts, for example, the electronic data under the request for decryption by the application from the directory in theexternal memory 2 and outputs the data to the application. The externalmemory function module 15 further comprises decryption requested data importing means (not shown). This decryption requested data importing means is a means for importing information to specify electronic data as an object under a request for decryption, from the application and for exporting it to thecontroller 156. - On the other hand, when the result of the above check is that the directory discrimination ID does not coincide with the bind ID, the
controller 156 performs such control as to inhibit access of the application to the directory. Namely, thecontroller 156 does not extract, for example, the electronic data under the request for decryption by the application from the directory in theexternal memory 2, and outputs information to indicate the inhibition of access of the application to the directory, tonotifier 157. - The
notifier 157 is a part that imports information indicating permission/inhibition of access of the application to the directory from thecontroller 156 and that notifies the application of the information. The application receiving the notification can determine which area it is allowed to access in theexternal memory 2. - Subsequently, the operation (external memory management method) carried out by the external
memory function module 15 of the present embodiment as described above will be described in detail with reference to the flowcharts of Fig. 5 and Fig. 6. Fig. 5 is a flowchart for explaining the operation of the externalmemory function module 15 in a situation in which thedirectory 20A is reserved as a storage area for theapplication 101A. - In Fig. 5, first, the
application 101A designates the AP-ID, CP-ID, model ID, series ID, and UIM-ID as the application identifier and the wireless communication terminal identifier, and then theidentifier acquirer 151 acquires the identifiers thus designated. Then the identifiers thus acquired are fed to the identification information acquirer 152 (step S101). - Next, the
identification information acquirer 152 acquires the identification information corresponding to the identifiers acquired at step S101, from theADF 102A,UIM 13, ormanagement information storage 14. Specifically, theidentification information acquirer 152 acquires from theADF 102A, the digital data of "www.aplication-a.com/download.html" corresponding to the AP-ID of the application identifier and the digital data of "Corp. AAA" corresponding to the CP-ID, as the application identification information. Furthermore, theidentification information acquirer 152 acquires from theUIM 13 or from themanagement information storage 14, the digital data of "MOBILE101" corresponding to the model ID of the wireless communication terminal identifier, the digital data of "1234" corresponding to the series ID, and the digital data of "UIM-MOBILE101-1234" corresponding to the UIM-ID, as the wireless communication terminal identification information. Then theacquirer 152 feeds the application identification information and the wireless communication terminal identification information acquired in this manner, to the generator 153 (step S 102). - The
generator 153 generates the bind ID to specify theapplication 101A and thecell phone 1, based on the identification information acquired at step S102, using the predetermined hash function. On this occasion, the identification information fed to thegenerator 153 at step S 102 is used as arguments in the hash function, and a hash value calculated is defined as the bind ID. Then the bind ID generated in this manner is fed to the writing section 155 (step S103). - Next, the reserving
section 154 reserves thedirectory 20A in theexternal memory 2 not allocated yet to another application, as a storage area available for theapplication 101A (step S104). - Next, the
writing section 155 writes the bind ID generated at step S103, as a discrimination ID of thedirectory 20A reserved at step S104, in theattribute file 21 of the external memory 2 (step S105). This associates thedirectory 20A with only theapplication 101A. Furthermore, since the bind ID is not generated by theapplication 101A but generated by thegenerator 153, it is feasible, for example, to prevent another application not sharing data with theapplication 101A, from falsifying and assuming this bind ID without permission. - Fig. 6 is a flowchart for explaining the operation of the external
memory function module 15 in the case where theapplication 101A is allowed to access thedirectory 20A. - In Fig. 6, first, the
application 101A designates the AP-ID, CP-ID, model ID, series ID, and UIM-ID as the application identifier and the wireless communication terminal identifier, and then theidentifier acquirer 151 acquires the identifiers thus designated. Then the identifiers thus acquired are fed to the identification information acquirer 152 (step S201). - Next, the
identification information acquirer 152 acquires the identification information corresponding to the identifiers acquired at step S201, from theADF 102A,UIM 13, ormanagement information storage 14. Specifically, theidentification information acquirer 152 acquires from theADF 102A, the digital data of "www.aplication-a.com/download.html" corresponding to the AP-ID of the application identifier and the digital data of "Corp. AAA" corresponding to the CP-ID, as the application identification information. Furthermore, theidentification information acquirer 152 acquires from theUIM 13 or from themanagement information storage 14, the digital data of "MOBILE101" corresponding to the model ID of the wireless communication terminal identifier, the digital data of "1234" corresponding to the series ID, and the digital data of "UIM-MOBILE101-1234" corresponding to the UIM-ID, as the wireless communication terminal identification information. Then theacquirer 152 feeds the application identification information and the wireless communication terminal identification information acquired in this manner, to the generator 153 (step S202). - The
generator 153 generates the bind ID to specify theapplication 101A and thecell phone 1, on the basis of the identification information acquired at step S202, using the predetermined hash function. On this occasion, the identification information fed to thegenerator 153 at step S202 is used as arguments in the hash function, and a hash value calculated is defined as the bind ID. Then the bind ID generated in this manner is fed to the controller 156 (step S203). - Next, the directory discrimination ID recorded in the
attribute file 21 of theexternal memory 2 is checked against the bind ID peculiar to theapplication 101A (step S204), which was generated at step S203. The directory discrimination ID recorded in theattribute file 21 refers to the directory discrimination ID written in theattribute file 21 at the aforementioned steps S101-S105. When the result of the check at step S204 is that the directory discrimination ID coincides with the bind ID, thecontroller 156 performs such control as to permit access of theapplication 101A to thedirectory 20A (step S205). This permits theapplication 101A to access and decrypt the data stored in thedirectory 20A. - On the other hand, when the result of the check at step S204 is that the directory discrimination ID does not coincide with the bind ID, the
controller 156 performs such control as to inhibit access of theapplication 101A to thedirectory 20A. Then thenotifier 157 notifies theapplication 101A of notification information to indicate the inhibition of access of theapplication 101A to thedirectory 20A (step S206). - Subsequently, the action and effect of the present embodiment will be described with reference to Figs. 7 and 8. Fig. 7 is a sequence diagram for explaining the operation of the external
memory function module 15, for example, in a situation in which thedirectory 20A is reserved as a storage area for theapplication 101A. As shown in Fig. 7, only the identifier, i.e., only the type of relevant identification information is acquired from theapplication 101A downloaded in the cell phone 1 (step S301). Then the externalmemory function module 15 generates the bind ID, based on the identification information designated by this identifier (step S302). Since the bind ID as the specific information peculiar to theapplication 101A and thecell phone 1 is not generated by theapplication 101A side but generated by the externalmemory function module 15 side of the present embodiment as described above, it is feasible, for example, to prevent another application not sharing data with theapplication 101A, from falsifying and assuming this bind ID without permission. - The external
memory function module 15 reserves thedirectory 20A for theapplication 101A in the external memory 2 (step S303) and writes the bind ID as a discrimination ID for thedirectory 20A in the attribute file 21 (step S304). Therefore, it becomes feasible to write the information restricted to theapplication 101A only, in theattribute file 21, and thus the use of thedirectory 20A with theattribute file 21 can be limited to theapplication 101A only. - Fig. 8 is a sequence diagram for explaining the operation of the external
memory function module 15, for example, in a situation in which theapplication 101A is allowed to access thedirectory 20A. As shown in Fig. 8, theapplication 101A designates electronic data as an object for decryption and an identifier for generation of the bind ID (step S401), and then the externalmemory function module 15 checks the directory discrimination ID recorded in theattribute file 21 of theexternal memory 2, against the bind ID generated by the externalmemory function module 15 itself on the basis of the identifier designated at step S401 (step S402 and step S403). The directory discrimination ID preliminarily contains a record of information to specify the application permitted to access thedirectory 20A with the directory discrimination ID. For this reason, the externalmemory function module 15 is able to perform such control as to permit theapplication 101A to access only the directory with the directory discrimination ID coinciding with the bind ID (step S404). The control on this occasion is carried out, for example, in such a manner that the externalmemory function module 15 extracts the electronic data under the request for decryption from thedirectory 20A and transfers it to theapplication 101A. Therefore, it is feasible to prevent a downloaded application from extracting data in theexternal memory 2 unrelated to the application and from becoming able to decrypt the data. - The present embodiment uses the application identification information such as the AP-ID and CP-ID, and the wireless communication terminal identification information such as the model ID, series ID, and UIM-ID, as the identification information being a basis for generation of the bind ID. For this reason, the external
memory function module 15 becomes able to write the bind ID limited to the application andcell phone 1 only, in theattribute file 21 in theexternal memory 2. Therefore, the use of the directory specified by the directory discrimination ID can be limited to the application and the cell phone only. - The preferred embodiment of the present invention was described above, but it is needless to mention that the present invention is by no means limited to the above embodiment.
- For example, the present embodiment used the
cell phone 1 as a wireless communication terminal, but, without having to be limited to it, the present invention can also be readily applied to so-called portable terminals such as PDA (Personal Digital Assistance). - The present embodiment was provided with one
attribute file 21 corresponding to the whole of theexternal memory 2, but it is also possible to provide separate attribute files for a large number of respective directories in theexternal memory 2. - The directory discrimination ID may also be configured to further contain a memory address or the like on the
external memory 2 for each directory reserved by the reservingsection 154, in addition to the information contained in the bind ID.
Claims (3)
- An external memory management apparatus for controlling access of an application downloaded in a wireless communication terminal, to a removable external memory, comprising:acquiring means for acquiring an identifier from said application downloaded;generating means for generating specific information to specify the application, based on identification information designated by the identifier acquired by the acquiring means;reserving means for reserving a predetermined area of the external memory as a storage area available for the application; andwriting means for writing the specific information generated by the generating means, in attribute information of the storage area reserved by the reserving means.
- The external memory management apparatus according to Claim 1,
wherein the acquiring means acquires from the application an application identifier to identify the application, and a wireless communication terminal identifier to identify the wireless communication terminal, and
wherein the generating means generates specific information to specify the application and the wireless communication terminal, based on application identification information designated by the application identifier and based on wireless communication terminal identification information designated by the wireless communication terminal identifier. - An external memory management method of controlling access of an application downloaded in a wireless communication terminal, to a removable external memory, comprising:an acquiring step wherein acquiring means acquires an identifier from said application downloaded;a generating step wherein generating means generates specific information to specify the application, based on identification information designated by the identifier acquired in the acquiring step;a reserving step wherein reserving means reserves a predetermined area of the external memory as a storage area available for the application; anda writing step wherein writing means writes the specific information generated in the generating step, in attribute information of the storage area reserved in the reserving step.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2005268472A JP4361522B2 (en) | 2005-09-15 | 2005-09-15 | External memory management device and external memory management method |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1793313A1 true EP1793313A1 (en) | 2007-06-06 |
EP1793313B1 EP1793313B1 (en) | 2010-11-17 |
Family
ID=37855846
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP06019185A Expired - Fee Related EP1793313B1 (en) | 2005-09-15 | 2006-09-13 | External memory management apparatus and external memory management method |
Country Status (7)
Country | Link |
---|---|
US (1) | US7738854B2 (en) |
EP (1) | EP1793313B1 (en) |
JP (1) | JP4361522B2 (en) |
CN (1) | CN100576225C (en) |
DE (1) | DE602006018244D1 (en) |
ES (1) | ES2353809T3 (en) |
TW (1) | TW200729010A (en) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101376883B1 (en) * | 2007-03-05 | 2014-03-21 | 엘지전자 주식회사 | Notification message moving method and terminal |
JP5112924B2 (en) * | 2008-03-27 | 2013-01-09 | 株式会社Kddiテクノロジー | Application moving system, application moving method, program, and portable terminal |
US20140317704A1 (en) * | 2013-03-15 | 2014-10-23 | Openpeak Inc. | Method and system for enabling the federation of unrelated applications |
KR102032182B1 (en) * | 2013-03-25 | 2019-10-15 | 삼성전자주식회사 | Data sharing control method and data sharing control terminal |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2795583A1 (en) * | 1999-06-24 | 2000-12-29 | Cit Alcatel | Telecommunications terminal security application module access unit having detector associating security profile and access command authorising application module access when match found. |
EP1089156A2 (en) * | 1999-09-30 | 2001-04-04 | M-Systems Flash Disk Pioneers Ltd. | Device, system and method for data access control |
EP1383351A2 (en) * | 2002-07-08 | 2004-01-21 | Matsushita Electric Industrial Co., Ltd. | Device authentication system |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH11143840A (en) | 1997-11-05 | 1999-05-28 | Hitachi Ltd | System and method for distributed object |
FR2785135B1 (en) * | 1998-10-22 | 2000-12-29 | Sfr Sa | METHOD FOR LAUNCHING AN APPLICATION BY A TERMINAL, UNDER THE CONTROL OF A SUBSCRIBER IDENTIFICATION MODULE, SUBSCRIBER IDENTIFICATION MODULE AND CORRESPONDING TERMINAL |
JP4045333B2 (en) | 2000-02-16 | 2008-02-13 | 株式会社リコー | Imaging equipment |
JP4675547B2 (en) * | 2000-07-07 | 2011-04-27 | アルカテル−ルーセント | Security module |
WO2002071219A2 (en) * | 2001-03-07 | 2002-09-12 | Matchtip Limited | System for replicating data of a mobile station |
CA2742139C (en) * | 2001-05-14 | 2012-03-27 | Ntt Docomo, Inc. | System for managing program stored in storage block of mobile terminal |
JP4007873B2 (en) | 2002-07-09 | 2007-11-14 | 富士通株式会社 | Data protection program and data protection method |
JP2004102698A (en) * | 2002-09-10 | 2004-04-02 | Ntt Docomo Inc | Downloading method, area management device, portable communication terminal, program, and recording medium |
JP2004302995A (en) | 2003-03-31 | 2004-10-28 | Fujitsu Ltd | File access limiting program |
US20040209651A1 (en) * | 2003-04-16 | 2004-10-21 | Nec Corporation | Mobile terminal, management method of information in the same, and a computer program for the information management |
US20050091535A1 (en) | 2003-10-24 | 2005-04-28 | Microsoft Corporation | Application identity for software products |
JP2005167463A (en) * | 2003-12-01 | 2005-06-23 | Sony Ericsson Mobilecommunications Japan Inc | Subscriber identification module and data access blocking method therefor |
JP4622334B2 (en) * | 2004-06-23 | 2011-02-02 | 日本電気株式会社 | Content data utilization system and method, mobile communication terminal and program |
-
2005
- 2005-09-15 JP JP2005268472A patent/JP4361522B2/en not_active Expired - Fee Related
-
2006
- 2006-09-13 US US11/519,884 patent/US7738854B2/en not_active Expired - Fee Related
- 2006-09-13 EP EP06019185A patent/EP1793313B1/en not_active Expired - Fee Related
- 2006-09-13 ES ES06019185T patent/ES2353809T3/en active Active
- 2006-09-13 DE DE602006018244T patent/DE602006018244D1/en active Active
- 2006-09-13 TW TW095133890A patent/TW200729010A/en not_active IP Right Cessation
- 2006-09-15 CN CN200610154219A patent/CN100576225C/en not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2795583A1 (en) * | 1999-06-24 | 2000-12-29 | Cit Alcatel | Telecommunications terminal security application module access unit having detector associating security profile and access command authorising application module access when match found. |
EP1089156A2 (en) * | 1999-09-30 | 2001-04-04 | M-Systems Flash Disk Pioneers Ltd. | Device, system and method for data access control |
EP1383351A2 (en) * | 2002-07-08 | 2004-01-21 | Matsushita Electric Industrial Co., Ltd. | Device authentication system |
Non-Patent Citations (1)
Title |
---|
MENEZES, OORSCHOT, VANSTONE: "Handbook of Applied Cryptography", HANDBOOK OF APPLIED CRYPTOGRAPHY, CRC PRESS SERIES ON DISCRETE MATHEMATICS AND ITS APPLICATIONS, 1997, , BOCA RATON, FL, US, pages 386-390, 400 - 405, XP002431402, ISBN: 0-8493-8523-7 * |
Also Published As
Publication number | Publication date |
---|---|
ES2353809T3 (en) | 2011-03-07 |
EP1793313B1 (en) | 2010-11-17 |
US7738854B2 (en) | 2010-06-15 |
JP2007080054A (en) | 2007-03-29 |
CN1932833A (en) | 2007-03-21 |
DE602006018244D1 (en) | 2010-12-30 |
JP4361522B2 (en) | 2009-11-11 |
TW200729010A (en) | 2007-08-01 |
TWI330326B (en) | 2010-09-11 |
CN100576225C (en) | 2009-12-30 |
US20070060116A1 (en) | 2007-03-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1764721B1 (en) | Apparatus and method for controlling access to an external memory | |
US8321923B2 (en) | Secure sharing of resources between applications in independent execution environments in a retrievable token (e.g. smart card) | |
JP4464455B2 (en) | Information processing device | |
US20070271446A1 (en) | Application Execution Device and Application Execution Device Application Execution Method | |
US20100049988A1 (en) | Method for access to a portable memory data support with auxiliary module and portable memory data support | |
CN102422256A (en) | Method for accessing a portable data storage medium with auxiliary module and portable data storage medium | |
KR100619657B1 (en) | Memory managing unit, code verifying device, and code decoder | |
EP1793313B1 (en) | External memory management apparatus and external memory management method | |
WO2007119594A1 (en) | Secure device and read/write device | |
JP4350962B2 (en) | Secure device | |
KR101297527B1 (en) | Circuit card data protection | |
CN1150494C (en) | Device and method for intialising an applicative programme of an integrated circuit card | |
CN105574425B (en) | Access the method and device of storage data | |
JPH10301854A (en) | Chip card and method for importing information on the same | |
US20060242274A1 (en) | Protecting system for data used by java applications | |
EP3683708A1 (en) | Method for managing a package of an application | |
KR100517730B1 (en) | Smart card limited use of memory | |
KR101264305B1 (en) | File securing apparatus, file securing method, and computer readable medium recorded thereon a program for file securing method | |
CN118171262A (en) | Mirror image data organization method and device for secure startup and electronic equipment | |
WO2010083931A1 (en) | Versatile electronic storage device |
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: 20060913 |
|
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 HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL BA HR MK YU |
|
17Q | First examination report despatched |
Effective date: 20070808 |
|
AKX | Designation fees paid |
Designated state(s): DE ES FR GB IT |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G06F 12/14 20060101AFI20100512BHEP Ipc: H04L 9/32 20060101ALI20100512BHEP |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): DE ES FR GB IT |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REF | Corresponds to: |
Ref document number: 602006018244 Country of ref document: DE Date of ref document: 20101230 Kind code of ref document: P |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FG2A Effective date: 20110223 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20110818 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602006018244 Country of ref document: DE Effective date: 20110818 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20140910 Year of fee payment: 9 Ref country code: ES Payment date: 20140812 Year of fee payment: 9 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: IT Payment date: 20140912 Year of fee payment: 9 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20140906 Year of fee payment: 9 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20150913 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20150913 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20160531 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20150913 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20150930 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20150914 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20170905 Year of fee payment: 12 |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FD2A Effective date: 20180706 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 602006018244 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190402 |