SYSTEM AND METHOD FOR DYNAMICALLY CONFIGURING A MOBILE DEVICE APPLICATION

• US 20130067208A1
• Filed: 09/08/2011
• Published: 03/14/2013
• Est. Priority Date: 09/08/2011
• Status: Abandoned Application

• Current Assignee: Brinkman Financial Company LP
• Original Assignee: Brinkman Financial Company LP
• Inventors: BRINKMAN, Mark, MIMICK, Raymond J., KELLOGG, Kary B.
• Application Number:
  US13/228,110
• Publication Number:
  US 20130067208A1
• Time in Patent Office: Days
• US Class Current: 713/1
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

An improved system and method are disclosed for configuring a behavior of an application on a mobile device via configuration parameters maintained by an application control program provided on a network accessible platform that is separate from the mobile device. In one example, the method enables the application control program to configure and dynamically modify parameters for a particular application that may also be used as a stand-alone application on the mobile device.

Claims

1. A method for configuring a behavior of an application on a mobile device via configuration parameters maintained by an application control program supported by a system operating on a network accessible platform, the method comprising:

receiving, by the system, the application;

receiving, by the system, a program name to be assigned to the application;

assigning, by the system, a network address, a user name, and a password to the program name, wherein the network address, user name, and password are to be used by the application on the mobile device to communicate with the application control program;

receiving, by the system, at least one file containing configuration parameters to be used by the application control program in controlling the application on the mobile device;

building, by the system, at least one database table based on the at least one file, wherein the at least one database table is accessible to the application control program;

building, by the system, an entry screen based on the at least one database table; and

linking, by the system, the entry screen to login information corresponding to an account on the system, wherein the entry screen is configured to provide access to the configuration parameters when the system is provided with the login information.

2. The method of claim 1 further comprising:

receiving, by the application control program from the application on the mobile device, authentication information including the user name and password; and

sending, by the application control program, the configuration parameters to the application on the mobile device.

3. The method of claim 2 further comprising:

receiving, by the application control program, a request from the application on the mobile device for a service not provided by the system; and

sending, by the application control program, information to the service for the application on the mobile device.

4. The method of claim 3 further comprising:

receiving, by the application control program, information from the service for the application on the mobile device; and

sending, by the application control program, the information from the service to the application on the mobile device.

5. The method of claim 4 wherein all communications between the application on the mobile device and the service pass through the application control program.

6. The method of claim 1 further comprising receiving, by the system, instructions for the creation of a multi-level hierarchy having at least a first level of authority and a second level of authority, wherein the first level of authority is authorized to set and lock a first configuration parameter and wherein the second level of authority cannot modify the first configuration parameter if the first configuration parameter has been locked by the first level of authority.

7. The method of claim 6 wherein the instructions for the creation of the multi-level hierarchy are included in the at least one file.

8. The method of claim 1 wherein at least one of the received configuration parameters identifies a service not provided by the system, and wherein the method further comprises formatting the at least one received configuration parameter pursuant to an application programming interface corresponding to the service.

9. The method of claim 1 further comprising providing, by the system, a second set of configuration parameters for the application on a second mobile device, wherein the second set of parameters alters the behavior of the application on the second mobile device compared to the behavior of the application on the first mobile device.

10. A method for dynamically modifying a behavior of an application on a mobile device via configuration parameters accessible to an application control program provided on a network accessible platform separate from the mobile device, the method comprising:

linking, on the network accessible platform, authentication information with a plurality of accounts, wherein each account is associated with a financial identifier and unique presentation information that customizes an appearance of the application on a display of the mobile device for each account;

receiving, by the network accessible platform, the authentication information from the application on the mobile device, wherein the authentication information identifies the application as being authorized to access the plurality of accounts on the network accessible platform;

receiving, by the network accessible platform, identifying information from the application;

identifying, by the network accessible platform, a first account of the plurality of accounts based on a comparison of the identifying information with configuration parameters for the application stored on the network accessible platform;

sending, by the network accessible platform, the presentation information corresponding to the selected first account to the application on the mobile device;

receiving, by the network accessible platform, financial transaction information corresponding to a financial transaction from the application;

associating, by the network accessible platform, the financial transaction information with the first account and the financial identifier associated with the first account;

creating, by the network accessible platform, a financial transaction record based on the financial transaction information; and

sending, by the network accessible platform, at least a portion of the financial transaction record to a financial transaction server for processing.

11. The method of claim 10 wherein the identifying information includes location information identifying a location of the mobile device, wherein each of the accounts is associated with a unique location, and wherein the first account is identified based on a proximity of its location to the location of the mobile device compared to the locations of the other accounts.

12. The method of claim 10 further comprising:

receiving, by the network accessible platform, a request from the application for accounts corresponding to an account identified in the request;

identifying, by the network accessible platform, at least a subset of the accounts corresponding to the identified account that the application is authorized to access; and

sending, by the network accessible platform, the subset of accounts to the mobile device,

wherein the identifying information received from the application identifies user selection of the first account.

13. The method of claim 10 further comprising determining, by the network accessible platform, whether the financial transaction information indicates that the financial transaction exceeds a transaction limitation defined by at least one configuration parameter.

14. The method of claim 13 wherein the transaction limitation is a maximum total transaction value for a defined period of time.

15. The method of claim 13 wherein the transaction limitation is defined to allow the financial transaction only within a defined geographic area.

16. The method of claim 13 wherein the transaction limitation is defined to allow the financial transaction only within a defined period of time.

17. The method of claim 13 further comprising sending, by the network accessible platform to the application, a rejection message if the financial transaction exceeds the transaction limitation.

18. The method of claim 13 further comprising sending, by the network accessible platform to the application, an approval message if the financial transaction does not exceed the transaction limitation.

19. The method of claim 10 wherein the unique presentation information includes branding information.

20. The method of claim 10 wherein the configuration parameters for the application stored on the network accessible platform correspond to one of a plurality of hierarchical authorization levels for the application defined on the network accessible platform.

21. A method for verifying a payment for an electronic transaction comprising:

receiving access, by a gateway server, to authentication information corresponding to an electronic wallet account that stores a plurality of payment types that are available to an application on a mobile device, wherein the authentication information includes identification information that is uniquely linked to the mobile device;

receiving, by the gateway server, an approval request for an electronic transaction from a merchant, wherein the approval request indicates that the application has supplied payment information corresponding to one of the payment types to the merchant, and wherein the approval request includes the identification information linked uniquely to the mobile device;

verifying, by the gateway server, that the payment information and the identification information received with the approval request match the payment information and identification information corresponding to the electronic wallet account; and

sending, by the gateway server, an authorization request to the application on the mobile device, wherein the authorization request identifies the electronic transaction for which the authorization request is being sent.

22. The method of claim 21 further comprising:

receiving, by the gateway server, an approval from the application in response to the authorization request; and

notifying, by the gateway server, the merchant that the electronic transaction has been approved in response to receiving the approval from the application.

23. The method of claim 21 wherein the identification information received with the approval request represents at least one information type of bar code information, near-field communication (NFC) information, radio-frequency identification (RFID) information, or Smart Chip information.

24. The method of claim 21 wherein the identification information includes location information identifying a current location of the mobile device and wherein verifying, by the gateway server, that the identification information received with the approval request matches the identification information corresponding to the electronic wallet account further includes determining whether the application is permitted to perform the electronic transaction at the current location of the mobile device.

25. The method of claim 24 further comprising:

providing, by the gateway server, a plurality of accounts to the application, wherein the electronic wallet account is one of the plurality of accounts; and

providing, by the gateway server, the plurality of the payment types to the application in response to receiving a selection indicator from the application that the electronic wallet account has been selected.

26. The method of claim 25 further comprising providing only a subset of the payment types to the application based on the current location.