# US 2013/0174266 A1 · Data exchange between a secure element and a terminal

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

- Number: US 2013/0174266 A1
- Document ID: US20130174266A1
- Status: Published application
- Kind: A1
- Application number: 13/592,537
- Filed: 2012-08-23
- Published: 2013-07-04
- Earliest claimed: 2011-08-24
- Assignees: T-Mobile Czech Republic a. s.
- Inventors: Petr Smrz
- Web page: https://patentgrep.com/patent/US20130174266A1

## CPC

- H04W 12/08: Access security
- 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]}
- G06F 21/60: Protecting data
- G06F 21/606: {by securing the transmission between two devices or processes}
- H04W 4/60: Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method for data exchange between a secure element and a terminal, the secure element including a CRS (Contactless Registry Service) application, a CREL (Contactless Registry Event Listener), and at least one service application, the terminal including a SEUI (Secure Element User Interface) configured to interact with at least one out of the CRS application, the CREL application, or the service application, includes exchanging, between the secure element and the terminal, an STID (Service Type Identification) information relating to the at least one service application. The STID information indicates the service type of the at least one service application of a predetermined set of different service types.

## Claims

### Claim 1

A method for data exchange between a secure element and a terminal, the secure element comprising a CRS (Contactless Registry Service) application, a CREL (Contactless Registry Event Listener), and at least one service application, and the terminal comprising a SEUI (Secure Element User Interface) configured to interact with at least one of the CRS application, the CREL application, or the at least one service application, the method comprising:
exchanging, between the secure element and the terminal, an STID (Service Type Identification) information relating to the at least one service application, wherein the STID information indicates the service type of the at least one service application of a predetermined set of different service types.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the secure element comprises a further service application, and the method further comprises:
exchanging, between the secure element and the terminal, a further STID information relating to the further service application, wherein the further STID information indicates the service type of the further service application out of the predetermined set of different service types.

### Claim 3 (depends on 1)

The method according to claim 1, wherein the STID information is encoded by a service type bit-mask comprising a plurality of service type bits as a part of an AID (application ID) information, wherein each of the plurality of service type bits of the service type bit-mask (210) relates to a service type.

### Claim 4 (depends on 1)

The method according to claim 1, wherein the predetermined set of different service types comprises any combination of service types up to a maximum of thirty-two different service types.

### Claim 5

A secure element for data exchange with a terminal, the secure element comprising:
a CRS (Contactless Registry Service) application;
a CREL (Contactless Registry Event Listener) application; and
at least one service application;
wherein at least one of the CRS application, the CREL application, or the at least one service application is configured to interact with a SEUI (Secure Element User Interface) of the terminal; and
wherein the secure element is configured to exchange a STID (Service Type Identification) information relating to the at least one service application with the terminal, the STID information indicating the service type of the at least one service application of a predetermined set of different service types.

### Claim 6 (depends on 5)

The secure element according to claim 5, wherein the secure element further comprises:
a further service application;
wherein the secure element is further configured to exchange a further STID information relating to the further service application with the terminal, the further STID information indicating the service type of the further service application out of the predetermined set of different service types.

### Claim 7 (depends on 5)

The secure element according to claim 5, wherein the STID information is encoded by a service type bit-mask comprising a plurality of service type bits as a part of an AID (application ID) information, wherein each of the plurality of service type bits of the service type bit-mask (210) relates to a service type.

### Claim 8 (depends on 5)

The secure element according to claim 5, wherein the predetermined set of different service types comprises any combination of service types up to a maximum of thirty-two different service types.

### Claim 9

A terminal for data exchange with a secure element, the terminal comprising:
a SEUI (Secure Element User Interface), configured to interact with at least one out of a CRS (Contactless Registry Service) application, a CREL (Contactless Registry Event Listener), and at least one service application of a secure element;
wherein the terminal is configured to exchange a STID (Service Type Identification) information relating to the at least one service application with the secure element, the STID information indicating the service type of the at least one service application of a predetermined set of different service types.

### Claim 10 (depends on 9)

The terminal according to claim 9, wherein the STID information is encoded by a service type bit-mask comprising a plurality of service type bits as a part of an AID (application ID) information, wherein each of the plurality of service type bits of the service type bit-mask (210) relates to a service type.

### Claim 11 (depends on 9)

The terminal according to claim 9, wherein the predetermined set of different service types comprises any combination of service types up to a maximum of thirty-two different service types.

### Claim 12

A non-transitory computer-readable medium having processor-executable instructions stored thereon for data exchange between a secure element and a terminal, the secure element comprising a CRS (Contactless Registry Service) application, a CREL (Contactless Registry Event Listener), and at least one service application, the terminal comprising a SEUI (Secure Element User Interface) configured to interact with at least out of the CRS application, the CREL application, or the at least one service application;
wherein the computer-executable instructions, when executed by a processor, cause the following step to be performed:
exchanging, between the secure element and the terminal, an STID (Service Type Identification) information relating to the at least one service application, wherein the STID information indicates the service type of the at least one service application of a predetermined set of different service types.
