System, methods, and computer program products for storing and managing program data

• US 9,697,516 B2
• Filed: 09/22/2014
• Issued: 07/04/2017
• Est. Priority Date: 10/10/2013
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Tomczak, Christopher J.
• Primary Examiner(s): Feild, Joseph
• Assistant Examiner(s): Jiang, Yong Hang
• Application Number:
  US14/492,209
• Publication Number:
  US 20150102915A1
• Time in Patent Office: 1,016 Days
• Field of Search: 340 101, 340 102, 340 103, 340 1031, 340 1032, 340 1033, 340 1034, 340 104, 340 1041, 340 1042, 340 105, 340 1051, 340 1052
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: 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

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

1. A system to manage merchant-related program identifier data, comprising:

a storage device comprising a secure element operable to store program data comprising a plurality of program identifiers, each of the program identifiers associated with a service provider identifier (ID), each service provider ID comprising a generic component of the servicer provider ID and a specific component of the servicer provider ID, the generic component and the specific component combining to form the service provider ID; and

a processor communicatively coupled to the storage device, wherein the processor executes application code instructions that are stored in the storage device to cause the system to;

receive a first service provider ID from a merchant computing device, the first service provider ID comprising a first generic component of the first service provider ID and a first specific component of the first service provider ID, the first generic component and the first specific component combining to form the first service provider ID;

determine that the first service provider ID comprising both the first generic component and the first specific component received from the merchant computing device does not match one service provider ID associated with the plurality of program identifiers stored in the storage device;

in response to determining that the first service provider ID comprising both the first generic component and the first specific component does not match one service provider ID associated with the plurality of program identifier stored in the storage device, compare the first generic component of the first service provider ID received from the merchant computing device to each generic component of each service provider ID associated with the program identifiers stored in the storage device;

determine that the first generic component of the first service provider ID matches one generic component of one or more service provider identifiers associated with at least one of the plurality of program identifiers stored in the storage device;

identify the at least one program identifier that comprises the one generic component of the one or more service provider identifiers that match the first generic component of the first service provider ID; and

transmit the at least one identified program identifier to the merchant computing device, the at least one identified program identifier comprising the one generic component of the service provider identifiers that matches the first generic component of the first service provider ID.

2. The system of claim 1, wherein the generic component of the servicer provider ID identifies an enterprise, and wherein the specific component of the servicer provider ID identifies a brand.

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

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

5. The system according to claim 1, wherein the processor is further configured to execute computer-executable instructions stored in the storage device to cause the system to compare the first service provider ID received from the merchant computing device to each service provider ID associated with the plurality of program identifiers stored in the storage device.

6. A method to manage merchant-related program identifier data, comprising:

storing, by a mobile computing device, program data comprising a plurality of program identifiers, each of the program identifiers associated with a service provider identifier (ID), each service provider ID comprising a generic component of the servicer provider ID and a specific component of the servicer provider ID; and

receiving, by the mobile computing device, a first service provider ID from a merchant computing device, the first service provider ID comprising a first generic component of the first service provider ID and a first specific component of the first service provider ID, the first generic component and the first specific component combining to form the first service provider ID;

comparing, by the mobile computing device, the first service provider ID comprising both the first generic component and the first specific component received from the merchant computing device to each service provider ID associated with plurality of program identifiers stored by the mobile computing device;

determining, by the mobile computing device, that the first service provider ID comprising both the first generic component and the first specific component does not match one service provider ID associated with the plurality of program identifiers stored by the mobile computing device;

in response to determining that the first service provider ID comprising both the first generic component and the first specific component does not match one service provider ID associated with the plurality of program identifiers stored by the mobile computing device, comparing, by the mobile computing device, the first generic component of the first service provider ID received from the merchant computing device to each generic component of each service provider ID associated with the program identifiers stored by the mobile computing device;

determining, by the mobile computing device, that the first generic component of the first service provider ID matches one generic component of one or more service provider identifiers associated with the program identifiers stored by the mobile computing device;

identifying, by the mobile computing device, the at least one program identifier that comprises the one generic component of the one or more service provider identifiers that match the first generic component of the first service provider ID; and

transmitting, by the mobile computing device, the at least one identified program identifier to the merchant computing device, the at least one identified program identifier comprising the one generic component of the service provider identifiers that matches the first generic component of the first service provider ID.

7. The method of claim 6, wherein the generic component of the servicer provider ID identifies an enterprise, and wherein the specific component of the servicer provider ID identifies a brand.

8. The method of claim 6, wherein the mobile computing device comprises a secure element that stores the program data.

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

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

11. A non-transitory computer-readable medium, comprising:

computer-readable program instructions embodiment therein that when executed by a computer causes the computer to manage merchant-related program identifier data, the computer-readable program instructions comprising;

computer-readable program instructions to store program data in a secure memory, the program data comprising a plurality of program identifiers, each of the program identifiers associated with a service provider identifier (ID), each service provider ID comprising a generic component of the servicer provider ID and a specific component of the servicer provider ID, the generic component and the specific component combining to form the service provider ID; and

computer-readable program instructions to receive a first service provider ID from a merchant computing device, the first service provider ID comprising a first generic component of the first service provider ID and a first specific component of the first service provider ID, the first generic component and the first specific component combining to form the first service provider ID;

computer-readable program instructions to determine that the first service provider ID comprising both the first generic component and the first specific component does not match one service provider ID associated with the plurality of program identifier stored in the secure memory;

computer-readable program instructions to, in response to determining that the first service provider ID comprising both the first generic component and the first specific component does not match one service provider ID associated with the plurality of program identifiers stored in the secure memory, determine that the first generic component of the first service provider ID matches one generic component of one or more service provider identifiers associated with the program identifiers stored in the secure memory;

computer-readable program instructions to identify the at least one program identifiers that comprise the one generic component of the one or more service provider identifiers that match the first generic component of the first service provider ID; and

computer-readable program instructions to transmit the at least one identified program identifiers to the merchant computing device, the at least one identified program identifiers comprising the one generic component of the service provider identifiers that match the first generic component of the first service provider ID.

12. The computer program product of claim 11, wherein the generic component of the servicer provider ID identifies an enterprise, and wherein the specific component of the servicer provider ID identifies a brand.

13. The computer program product of claim 11, wherein the secure memory comprises a secure element.

14. The computer program product of claim 11, wherein the generic component of the service provider ID is encoded in a first number of consecutive bytes of the service provider ID and the specific component of the service provider ID is encoded in a second number of consecutive bytes of the service provider ID.

15. The computer program product of claim 14, wherein the first number of consecutive bytes is equal to the second number of consecutive bytes.

16. The computer program product of claim 11, further comprising computer-readable program instructions to compare the first service provider ID received from the merchant computing device to each service provider ID associated with the plurality of program identifiers stored in the memory.

17. The computer program product of claim 11, further comprising computer-readable program instructions to compare the first generic component of the first service provider ID received from the merchant computing device to each generic component of each service provider ID associated with the program identifiers stored by the memory.