Recording Resource Usage

• US 20090254465A1
• Filed: 04/10/2007
• Published: 10/08/2009
• Est. Priority Date: 04/11/2006
• Status: Abandoned Application

• Current Assignee: Giesecke & Devrient GmbH
• Original Assignee: Giesecke & Devrient GmbH
• Inventors: Oester, Heiko
• Application Number:
  US12/297,169
• Publication Number:
  US 20090254465A1
• Time in Patent Office: Days
• US Class Current: 705/34
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/552 involving long-term monitoring or reporting
• CPC Class Codes: G06F 21/77 in smart cards
• CPC Class Codes: G06F 21/79 in semiconductor storage media, e.g. directly-addressable memories
• CPC Class Codes: G06F 2221/2135 Metering
• CPC Class Codes: G06F 2221/2153 Using hardware token as a secondary aspect
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

A security module with a processor, on which applications from various providers are installed, includes a recording device for recording the access of the applications to resources of the security module, recording the total resource usage caused by an application and allocates the relevant applications to a charging station for subsequent charging. The recorded usage data are allocated to usage data sets and/or data sets on the security module directly connected to the relevant application and/or the provider thereof and thus permits billing of total resource use of each application or all the applications of a provider.

Claims

1. A method of operating a security module, comprising the steps of:

recording usage data representing a usage of resources of the security module;

storing the usage data in a non-volatile memory of the security module;

transferring the stored usage data to an accounting center; and

determining an application stored on the security module that is causing the resource usage represented by the usage data and by the usage data being stored, in the storing step, in their assignment to the determined application.

2. The method according to claim 1, wherein there is present in the non-volatile memory a usage data record linked to the application and to which the determined usage data are assigned and which is transferred to the accounting center.

3. The method according to claim 1, wherein the application is an application provided on the security module by a supplier independent of a provider of the data carrier, and in the non-volatile memory there is present as a usage data record a supplier data record linked to the supplier and to which the usage data caused by the application are assigned.

4. The method according to claim 1, wherein the determined application comprises two mutually linked partial applications, one of the partial applications realizing a service utilized by a user of the data carrier and the other of the partial applications causing the resource usage.

5. The method according to claim 1, wherein there is present in the non-volatile memory a user data record linked to the user and to which an extent of utilization of the service is assigned.

6. The method according to claim 1, wherein a separate usage data record and/or a separate supplier data record and/or a separate user data record is created for each recorded resource usage.

7. The method according to claim 6, wherein the usage data record and/or the supplier data record and/or the user data record is actively transferred to the supplier and/or the provider as the accounting center, or made available on the security module for retrieval by the accounting center.

8. The method according to claim 1, wherein the usage data record is stored in separate memory areas for each application and/or each supplier or in a common memory area.

9. The method according to claim 1, wherein there is present on the security module for at least one application and/or for at least one supplier a configuration data record stating the resource usages to be recorded for the corresponding application.

10. The method according to claim 1, wherein the resources comprise hardware components of the data carrier, said hardware comprising a processor, memory, data-transmission capacity and/or communication interfaces, and/or software components of the data carrier.

11. The method according to claim 1, wherein usage data are recorded that represent a proportionate consumption of a resource by the application, including a duration and/or an extent and/or a number of resource accesses of the application.

12. The method according to claim 1, wherein usage data are recorded that comprise an execution priority of the executed application.

13. The method according to claim 1, wherein the usage data record is prepared in the form of accounting data, and the resource usage caused by the application is billed to the corresponding supplier with the help of the accounting data.

15. The security module according to claim 14, adapted to execute a method according to claim 1.

14. A security module, comprising a non-volatile memory, resources, a recording device arranged to record usage data representing a usage of the resources caused by an application present on the security module and to store them in the non-volatile memory;

a communication device arranged to transfer the stored usage data to an accounting center, wherein the recording device is adapted to determine the application that is causing the resource usage represented by the usage data, and to store the usage data in the non-volatile memory in their assignment to the determined application.

16. A security module according to claim 14, wherein the recording device comprises a protected runtime environment that checks the execution of the application by a processor of the data carrier.

17. The security module according to claim 16, wherein the protected runtime environment is integrated into an operating system of the data carrier.

18. The security module according to claim 16, wherein the operating system of the data carrier is a Java operating system, and the protected runtime environment is integrated in a Java runtime environment of the Java operating system.

19. The security module according to claim 16, wherein the protected runtime environment is adapted to allow, upon execution of the application, only usages of resources that are reserved or released for the application.

20. The security module according to claim 14, including a high-speed data communication interface.

21. The security module according to claim 14, wherein the security module is a (U)SIM mobile communication card and/or the non-volatile memory is a mass memory for storing applications.

22. The security module according to claim 14, wherein the security module is firmly installed in a terminal.

23. A system comprising an accounting server, a terminal and a security module according to claim 14.