Methods, systems and computer readable media for enabling a downloadable service to access components in a mobile device

1. A system for enabling a downloadable service to access components in a mobile device, the system comprising:

a mobile device including a mobile wallet application configured to determine at least one hardware component or software component provisioned on the mobile device and to generate a capabilities object containing information identifying a most recent state of capabilities of the at least one hardware or software component, wherein the most recent state of the capabilities of the at least one hardware or software component comprises a current state of user changeable capabilities of the mobile wallet application exposable to a web application; and

a network server supporting a downloadable service configured to receive the capabilities object from the mobile device, to generate personalized downloadable service content based on the current state of the user changeable capabilities of the mobile wallet application in the received capabilities object, to provide the personalized downloadable service content to the mobile device, wherein the personalized downloadable service content is configured to access the at least one hardware component or software component on the mobile device, and wherein the personalized downloadable service content includes personalized web page content including one or more displayed web page interface options for utilizing the at least one hardware or software component.

2. The system of claim 1 wherein the personalized downloadable service content includes software code that contains at least one protocol handler that is configured to access the at least one hardware component or software component on the mobile device.

3. The system of claim 2 wherein the mobile wallet application receives, from the at least one protocol handler, a request to provide an interface option to access the at least one hardware component or software component.

4. The system of claim 3 wherein the mobile wallet application is configured to display a personalized web page that includes the interface option to access the at least one hardware component or software component.

5. The system of claim 2 wherein the at least one protocol handler includes at least one of: a wallet protocol handler and a local protocol handler.

6. The system of claim 1 wherein the mobile wallet application utilizes application programming interfaces (APIs) to determine the at least one hardware component or software component included in the mobile device.

7. The system of claim 1 wherein the at least one hardware component includes at least one of: a near field communication (NFC) hardware circuit chip, a still camera, a video camera, a quick response (QR) code scanner, a secure element, a mobile device memory, an accelerometer, and an add-on peripheral device.

8. The system of claim 1 wherein the at least one hardware component or software component is accessed by the mobile wallet application irrespective of the operating system platform supported by the mobile device and without the emulation of software code.

9. The system of claim 1 wherein the capabilities object is sent to the network server via communication between an application programming interface (API) associated with the mobile wallet application and an API associated with the network server.

10. A method for enabling a downloadable service to access components in a mobile device, the system comprising:

determining at least one hardware component or software component provisioned on a mobile device;

generating a capabilities object containing information identifying a most recent state of capabilities of the at least one hardware component or software component, wherein the most recent state of the capabilities of the at least one hardware or software component comprises a current state of user changeable capabilities of the mobile wallet application exposable to a web application;

providing the capabilities object from the mobile device to a network server supporting a downloadable service;

generating personalized downloadable service content based on the the current state of user changeable capabilities in the received capabilities object; and

providing the personalized downloadable service content to the mobile device, wherein the personalized downloadable service content is configured to access the at least one hardware component or software component on the mobile device, and wherein the personalized downloadable service content includes personalized web page content including one or more displayed web page interface options for utilizing the at least one hardware or software component.

11. The method of claim 10 wherein the personalized downloadable service content includes software code that contains at least one protocol handler that is configured to access the at least one hardware component or software component on the mobile device.

12. The method of claim 11 comprising receiving, from the at least one protocol handler, a request to provide an interface option to access the at least one hardware component or software component.

13. The method of claim 12 comprising displaying a personalized web page that includes the interface option to access the at least one hardware component or software component.

14. The method of claim 11 wherein the at least one protocol handler includes at least one of: a wallet protocol handler and a local protocol handler.

15. The method of claim 10 wherein at least one hardware component or software component includes utilizing application programming interfaces (APIs) to determine the at least one hardware component or software component included in the mobile device.

16. The method of claim 10 wherein the at least one hardware component includes at least one of: a near field communication (NFC) hardware circuit chip, a still camera, a video camera, a quick response (QR) code scanner, a secure element, a mobile device memory, an accelerometer, and an add-on peripheral device.

17. The method of claim 10 comprising accessing the at least one hardware component or software components irrespective of the operating system platform supported by the mobile device and without the emulation of software code.

18. The method of claim 10 wherein sending the capabilities object includes communicating the capabilities object by utilizing an application programming interface (API) associated with the mobile wallet application and an API associated with the network server.

19. A non-transitory computer readable medium having stored thereon executable instructions that when executed by the processor of a computer control the computer to perform steps comprising:

determining at least one hardware component or software component provisioned on a mobile device;

generating a capabilities object containing information identifying a most recent state of capabilities of the at least one hardware component or software component, wherein the most recent state of the capabilities of the at least one hardware or software component comprises a current state of user changeable capabilities of a mobile wallet application exposable to a web application;

providing the capabilities object from the mobile device to a network server supporting a downloadable service;

generating personalized downloadable service content based on the current state of the user changeable capabilities of the mobile wallet application in the received capabilities object; and

providing the personalized downloadable service content to the mobile device, wherein the personalized downloadable service content is configured to access the at least one hardware component or software component on the mobile device, and wherein the personalized downloadable service content includes personalized web page content including one or more displayed web page interface options for utilizing the at least one hardware or software component.

20. The computer readable medium of claim 19 wherein the personalized downloadable service content includes software code that contains at least one protocol handler that is configured to access the at least one hardware component or software component on the mobile device.

21. The computer readable medium of claim 20 comprising receiving, from the at least one protocol handler, a request to provide an interface option to access the at least one hardware component or software component.

22. The computer readable medium of claim 21 comprising displaying a personalized web page that includes the interface option to access the at least one hardware component or software component.

23. The method of claim 19 wherein sending the capabilities object includes communicating the capabilities object by utilizing an application programming interface (API) associated with the mobile wallet application and an API associated with the network server.