WEB NATIVE BRIDGE

• US 20170078452A1
• Filed: 05/07/2014
• Published: 03/16/2017
• Est. Priority Date: 05/07/2014
• Status: Abandoned Application

• Current Assignee: Optum Incorporated (UnitedHealth Group Incorporated)
• Original Assignee: Optum Incorporated (UnitedHealth Group Incorporated)
• Inventors: Verrijt, Joost, Singer, Brian, McGoogan, Matthew, Bellinger, Chris
• Application Number:
  US15/309,284
• Publication Number:
  US 20170078452A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

An HTTP web-native bridge includes an HTTP server that exposes native mobile modules through a RESTful web service. A full HTTP feature set may be utilized to interact with the native mobile modules to access native features and functionalities of a mobile device by a web service. The HTTP web-native bridge may be implemented without including additional libraries in the web service code or requiring web service developers to write application programming interface code.

Claims

1. A method for accessing native features of a computing device, comprising:

receiving a hypertext transfer protocol (HTTP) request from a client application for access to a native feature of the computing device by an HTTP server;

identifying a previously stored native code by the HTTP server in response to receiving the HTTP request, the identified previously stored native code being executable by the computing device to access the native feature;

executing the previously stored native code on the device to access the native feature;

receiving a reply of the native feature by the server; and

generating an HTTP reply by the HTTP server, the HTTP reply including information contained in the reply of the native feature.

2. The method of claim 1, further comprising:

communicating the HTTP reply from the HTTP server to the client application.

3. The method of claim 1, comprising:

initiating operation of the HTTP server on the computing device when the client application begins execution;

monitoring a port of the HTTP server for HTTP requests to access native features of the computing device that correspond to previously stored native code; and

terminating operation of the HTTP server on the computing device when the client application ends execution.

4. The method of claim 1, further comprising:

communicating the identified previously stored native code by the server to a native process of the computing device for executing on the computing device.

5. The method of claim 1, further comprising:

receiving the hypertext transfer protocol (HTTP) request by a RESTful application programming interface on the HTTP server.

6. The method of claim 5, further comprising:

communicating state information from a first client application to a second client application via the RESTful application programming interface.

7. The method of claim 1, further comprising:

storing a plurality of native code modules in memory that is accessible by the HTTP server, the plurality of native code modules corresponding to respective native features of the computing device that are not directly accessible by HTTP requests.

8. A method for accessing native features of a mobile computing device, comprising:

sending a hypertext transfer protocol (HTTP) request to an HTTP server on a mobile computing device, the HTTP request requesting access to a native feature of the mobile computing device; and

receiving an HTTP reply from the HTTP server, the HTTP reply generated by the HTTP server and including information contained in a reply of the native feature in response to implementation of the native feature.

9. The method of claim 8, further comprising:

sending the hypertext transfer protocol (HTTP) request to a RESTful application programming interface on the HTTP server.

10. The method of claim 9, further comprising:

communicating state information to a second client application via the RESTful application programming interface.

11. An apparatus for accessing native features of a computing device, comprising:

means for receiving a hypertext transfer protocol (HTTP) request from a client application for access to a native feature of the computing device;

means for identifying a previously stored native code in response to receiving the HTTP request, the identified previously stored native code being executable by the computing device to access the native feature;

means for executing the previously stored native code on the device to access the native feature;

means for receiving a reply of the native feature by the server; and

means for generating an HTTP reply, the HTTP reply including information contained in the reply of the native feature.

12. The apparatus of claim 11, further comprising:

means for communicating the HTTP reply to the client application.

13. The apparatus of claim 11, comprising:

means for initiating operation of an HTTP server on the computing device when the client application begins execution;

means for monitoring a port of the HTTP server for HTTP requests to access native features of the computing device that correspond to previously stored native code; and

means for terminating operation of the HTTP server on the computing device when the client application ends execution.

14. The apparatus of claim 11, further comprising:

means for communicating the identified previously stored native code by the server to a native process of the computing device for executing on the computing device.

15. The apparatus of claim 11, further comprising:

means for receiving the hypertext transfer protocol (HTTP) request by a RESTful application programming interface on an HTTP server.

16. The apparatus of claim 15, further comprising:

means for communicating state information from a first client application to a second client application via the RESTful application programming interface.

17. The apparatus of claim 11, further comprising:

means for storing a plurality of native code modules in memory that is accessible by the HTTP server, the plurality of native code modules corresponding to respective native features of the computing device that are not directly accessible by HTTP requests.

18. An apparatus for accessing native features of a mobile computing device, comprising:

a server configured for receiving a hypertext transfer protocol (HTTP) request from a web client application for access to a native feature of the mobile computing device, the server including a RESTful application programming interface;

memory in communication with the server and storing previously written native code on the mobile computing device to access the native feature;

a native process of the device in communication with the server and configured to execute the native code to implement the native feature.

19. The apparatus of claim 18, wherein the server is further configured:

to receive a reply of the native process; and

to communicate a HTTP response to the web client application based on the reply.

20. The apparatus of claim 18, further comprising a library of previously written code for accessing native features on a plurality of mobile computing device platforms.