# US 2013/0159710 A1 · System and method for key management for issuer security domain using global platform specifications

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0159710 A1
- Document ID: US20130159710A1
- Status: Published application
- Kind: A1
- Application number: 13/332,201
- Filed: 2011-12-20
- Published: 2013-06-20
- Earliest claimed: 2011-12-20
- Assignees: Apple Inc.
- Inventors: Ahmer A. Khan
- Web page: https://patentgrep.com/patent/US20130159710A1

## CPC

- H04L 63/062: {for key distribution, e.g. centrally by trusted party (cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819)}
- G06F 21/72: in cryptographic circuits
- G06Q 20/3229: {Use of the SIM of a M-device as secure element}
- G06Q 20/3829: {involving key management}
- H04L 9/0877: {using additional device, e.g. trusted platform module [TPM], smartcard, USB or hardware security module [HSM]}
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L 9/3234: {involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token (network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853)}
- H04W 12/04: Key management, e.g. using generic bootstrapping architecture [GBA]
- H04W 12/086: using security domains
- H04W 12/35: {Protecting application or service provisioning, e.g. securing SIM application provisioning}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Disclosed herein are systems, methods, and non-transitory computer-readable storage media for key management for Issuer Security Domain (ISD) using GlobalPlatform Specifications. A client receives from a server an authorization to update a first ISD keyset. The client encrypts, via a client-side secure element, a second ISD keyset with a server public key. The client sends the encrypted second ISD keyset to the server for updating the first ISD keyset with the encrypted second ISD keyset. Prior to updating, the client generates the first ISD keyset at a vendor and sends the first ISD keyset to the client-side secure element and sends the first ISD keyset encrypted with the server public key to the server. The disclosed method allows for updating of an ISD keyset of which only the client-side secure element and a server have knowledge.

## Claims

### Claim 1

A method comprising:
receiving from a server an authorization to update a first Issuer Security Domain encryption keyset;
encrypting, via a secure element on a client device, a second Issuer Security Domain keyset with a server public key to yield an encrypted second Issuer Security Domain keyset; and
sending the encrypted second Issuer Security Domain keyset to the server for updating the first Issuer Security Domain encryption keyset with the encrypted second Issuer Security Domain keyset.

### Claim 2 (depends on 1)

The method of claim 1, wherein the Secure Element has at least one security domain, wherein a security domain is one of an Issuer Security Domain, a Controlling Authority Security Domain and a Supplemental Security Domain.

### Claim 3 (depends on 2)

The method of claim 2, wherein the Issuer Security Domain is a top level security domain that manages at least one other domain.

### Claim 4 (depends on 3)

The method of claim 3, wherein the Issuer Security Domain manages at least one of card content, card life cycle and application life cycle.

### Claim 5 (depends on 1)

The method of claim 1, wherein the Secure Element is implemented according to Global Platform Card specifications.

### Claim 6 (depends on 1)

The method of claim 1, wherein the Secure Element stores at least one cryptographic key relating to a security domain.

### Claim 7 (depends on 6)

The method of claim 6, wherein access to a security domain is limited to processes with access to a cryptographic key for the security domain.

### Claim 8 (depends on 1)

The method of claim 1, wherein the Secure Element comprises a dedicated hardware component on a mobile device.

### Claim 9 (depends on 8)

The method of claim 8, wherein the server communicates with the secure element via the mobile device.

### Claim 10 (depends on 8)

The method of claim 8, wherein the authorization is issued during initial activation of at least one of the mobile device and an application.

### Claim 11

A method comprising:
sending, from a server to a client, an authorization to update a first Issuer Security Domain encryption keyset;
receiving, at the server, an encrypted second Issuer Security Domain keyset, generated by a client within a client-side Secure Element; and
updating the first Issuer Security Domain encryption keyset with the encrypted second Issuer Security Domain keyset.

### Claim 12 (depends on 11)

The method of claim 11, wherein the Secure Element is implemented using Global Platform Card specifications.

### Claim 13 (depends on 11)

The method of claim 11, wherein the authorization is based on an Issuer Security Domain keyset initialization script generated at the server, wherein the initialization script is based on an existing encrypted Issuer Security Domain keyset.

### Claim 14 (depends on 13)

The method of claim 13, wherein the encrypted Issuer Security Domain keyset is decrypted at the server using a server private encryption key prior to sending the authorization.

### Claim 15 (depends on 11)

The method of claim 11, wherein the encrypted second Issuer Security Domain keyset is encrypted using a server public encryption key corresponding to a server private encryption key.

### Claim 16

A system comprising:
a processor;
a memory storing instructions for controlling the processor to perform a method comprising:
generating, at a vendor, an Issuer Security Domain encryption keyset;
sending the Issuer Security Domain encryption keyset and a server public key to a Secure Element at a client, wherein the Secure Element implements at least a portion of Global Platform Card specifications;
encrypting, at the vendor, the Issuer Security Domain encryption keyset with the server public key to yield an encrypted keyset; and
sending the encrypted keyset to the server.

### Claim 17 (depends on 16)

The system of claim 16, wherein the Secure Element comprises a dedicated hardware component on a mobile device.

### Claim 18 (depends on 17)

The system of claim 17, wherein the server services at least one Secure Element on the mobile device identified by a Secure Element identification component.

### Claim 19 (depends on 18)

The system of claim 18, wherein each Secure Element has a different Issuer Security Domain encryption keyset, identified by the Secure Element identification component.

### Claim 20

A non-transitory computer-readable storage medium storing instructions which, when executed by a computing device, cause the computing device to perform steps comprising:
receiving, at a client having a Secure Element, an Issuer Security Domain encryption keyset and a server public key, wherein the keyset is generated at a vendor; and
storing the Issuer Security Domain encryption keyset and server public key.

### Claim 21 (depends on 20)

The non-transitory computer-readable storage medium of claim 20, wherein the Secure Element has at least one security domain, wherein a security domain is one of an Issuer Security Domain, a Controlling Authority Security Domain and a Supplemental Security Domain.

### Claim 22 (depends on 20)

The non-transitory computer-readable storage medium of claim 20, wherein the Secure Element comprises an embedded chip within the client.

### Claim 23 (depends on 20)

The non-transitory computer-readable storage medium of claim 20, wherein the Secure Element is implemented according to Global Platform specifications.

### Claim 24 (depends on 20)

The non-transitory computer-readable storage medium of claim 20, wherein the Issuer Security Domain encryption keyset is generated as part of a pre-personalization stage.

### Claim 25

A non-transitory computer-readable storage medium storing instructions which, when executed by a computing device, cause the computing device to perform steps comprising:
generating an Issuer Security Domain encryption keyset;
sending the Issuer Security Domain encryption keyset and a server public key to a Secure Element embedded within a client;
encrypting the Issuer Security Domain encryption keyset with the server public key to yield an encrypted keyset; and
sending the encrypted keyset to the server.

### Claim 26 (depends on 25)

The non-transitory computer-readable storage medium of claim 25, wherein the Secure Element implements at least a portion of Global Platform Card specifications.