# US 2015/0102915 A1 · Systems, methods, and computer program products for storing and managing program data

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

- Number: US 2015/0102915 A1
- Document ID: US20150102915A1
- Status: Published application
- Kind: A1
- Application number: 14/492,209
- Filed: 2014-09-22
- Published: 2015-04-16
- Earliest claimed: 2013-10-10
- Assignees: Jvl Ventures, LLC
- Applicants: Jvl Ventures, LLC
- Inventors: Christopher J. Tomczak
- Web page: https://patentgrep.com/patent/US20150102915A1

## CPC

- G06Q 20/3278: {RFID or NFC payments by means of M-devices}
- G06Q 20/3227: {using secure elements embedded in M-devices}
- H04L 63/0853: {using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234)}
- 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
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems, methods, and computer program products are provided for storing and managing program data. A service provider ID having both generic and specific components is sent from a terminal to a mobile device. The mobile device determines whether the service provider ID sent from the terminal matches a service provider ID stored on the mobile device. If there is a match, the mobile device transmits, to the terminal, program data stored on the mobile device associated with the matched service provider ID. If no match is determined, the mobile device determines whether the generic component of the service provider ID sent from the terminal matches the generic component of a service provider ID stored on the mobile device. If there is a generic match, the mobile device transmits, to the terminal, program data stored on the mobile device associated with the generically matched service provider ID.

## Claims

### Claim 1

A system for managing program data, comprising:
a memory operable to store program data, the program data including one or more program identifiers (IDs) each associated with one or more service provider IDs, each service provider ID having a generic component and a specific component; and
a processor coupled to the memory, the processor being operable to:
receive, from a reader terminal, a first service provider ID, the first service provider ID having a first generic component and a first specific component;
determine whether the first service provider ID matches one of the one or more service provider IDs stored in the memory;
transmit, to the reader terminal, in the event that the first service provider ID matches one of the one or more service provider IDs stored in the memory, the one or more program IDs associated with the one or more service provider IDs that match the first service provider ID;
determine, in the event that the first service provider ID does not match one of the one or more service provider IDs stored in the memory, whether the first generic component of the first service provider ID matches the generic component of the one or more service provider IDs stored in the memory; and
transmit, to the reader terminal, in the event that the first service provider ID does not match one of the one or more service provider IDs stored in the memory and in the event that the first generic component of the first service provider ID matches the generic component of the one or more service provider IDs stored in the memory, the one or more program IDs associated with the one or more service provider IDs having a generic component that matches the first generic component of the first service provider ID.

### Claim 2 (depends on 1)

The system according to claim 1, wherein the generic component identifies an enterprise and wherein the specific component identifies a brand.

### Claim 3 (depends on 1)

The system according to claim 1, wherein the memory is included in a secure element.

### Claim 4 (depends on 1)

The system according to claim 1, wherein the generic component of each service provider ID is encoded in a first number of consecutive bytes, and the specific component of each service provider ID is encoded in a second number of consecutive bytes.

### Claim 5 (depends on 4)

The system according to claim 4, wherein the first number of consecutive bytes is equal to the second number of consecutive bytes.

### Claim 6 (depends on 1)

The system according to claim 1, wherein the processor is further operable to determine whether the first service provider ID matches one of the one or more service provider IDs stored in the memory by comparing the value of the first service provider ID to the values of the one or more service provider IDs stored in the memory and determining whether the values are equal.

### Claim 7

A method for managing program data, comprising:
storing program data in a memory, the program data including one or more program identifiers (IDs) each associated with one or more service provider IDs, each servicer provider ID having a generic component and a specific component; and
receiving, from a reader terminal, a first service provider ID, the first service provider ID having a first generic component and a first specific component;
determining whether the first service provider ID matches one of the one or more service provider IDs stored in the memory;
transmitting, to the reader terminal, in the event that the first service provider ID matches one of the one or more service provider IDs stored in the memory, the one or more program IDs associated with the one or more service provider IDs that match the first service provider ID;
determining, in the event that the first service provider ID does not match one of the one or more service provider IDs stored in the memory, whether the first generic component of the first service provider ID matches the generic component of the one or more service provider IDs stored in the memory; and
transmitting, to the reader terminal, in the event that the first service provider ID does not match one of the one or more service provider IDs stored in the memory and in the event that the first generic component of the first service provider ID matches the generic component of the one or more service provider IDs stored in the memory, the one or more program IDs associated with the one or more service provider IDs having a generic component that matches the first generic component of the first service provider ID.

### Claim 8 (depends on 7)

The method according to claim 7, wherein the generic component identifies an enterprise and wherein the specific component identifies a brand.

### Claim 9 (depends on 7)

The method according to claim 7, wherein the memory is included in a secure element.

### Claim 10 (depends on 7)

The method according to claim 7, wherein the generic component of each service provider ID is encoded in a first number of consecutive bytes and the specific component of each service provider ID is encoded in a second number of consecutive bytes.

### Claim 11 (depends on 10)

The method according to claim 10, wherein the first number of consecutive bytes is equal to the second number of consecutive bytes.

### Claim 12 (depends on 7)

The method according to claim 7, wherein the step of determining whether the first service provider ID matches one of the one or more service provider IDs stored in the memory further comprises the steps of comparing the value of the first service provider ID to the values of the one or more service provider IDs stored in the memory and determining whether the values are equal.

### Claim 13

A non-transitory computer-readable medium having stored thereon sequences of instructions, the sequences of instructions including instructions which when executed by a computer system causes the computer to perform:
storing program data in a memory, the program data including one or more program identifiers (IDs) each associated with one or more service provider identifiers, each service provider ID having a generic component and a specific component; and
receiving, from a reader terminal, a first service provider ID, the first service provider ID having a first generic component and a first specific component;
determining whether the first service provider ID matches one of the one or more service provider IDs stored in the memory;
transmitting, to the reader terminal, in the event that the first service provider ID matches one of the one or more service provider IDs stored in the memory, the one or more program IDs associated with the one or more service provider IDs that match the first service provider ID;
determining, in the event that the first service provider ID does not match one of the one or more service provider IDs stored in the memory, whether the first generic component of the first service provider ID matches the generic component of the one or more service provider IDs stored in the memory; and
transmitting, to the reader terminal, in the event that the first service provider ID does not match one of the one or more service provider IDs stored in the memory and in the event that the first generic component of the first service provider ID matches the generic component of the one or more service provider IDs stored in the memory, the one or more program IDs associated with the one or more service provider IDs having a generic component that matches the first generic component of the first service provider ID.

### Claim 14 (depends on 13)

The system according to claim 13, wherein the generic component identifies an enterprise, and wherein the specific component identifies a brand.

### Claim 15 (depends on 13)

The computer-readable medium according to claim 13, wherein the memory is included in a secure element.

### Claim 16 (depends on 13)

The computer-readable medium according to claim 13, wherein the generic component of each service provider ID is encoded in a first number of consecutive bytes and the specific component of each service provider ID is encoded in a second number of consecutive bytes.

### Claim 17 (depends on 16)

The computer-readable medium according to claim 16, wherein the first number of consecutive bytes is equal to the second number of consecutive bytes.

### Claim 18 (depends on 13)

The computer-readable medium according to claim 13, wherein it is determined whether the first service provider ID matches one of the one or more service provider IDs stored in the memory by comparing the value of the first service provider ID to the values of the one or more service provider IDs stored in the memory and determining whether the values are equal.
