Passthrough Mobile Application Policy

2. The system of claim 1, wherein the remote procedure call requested by the first vehicle-enabled application is received over a first data flow provided over the first connection, the remote procedure call requested by the second vehicle-enabled application is received over a second data flow provided over the first connection, and the second data flow is encrypted by the secondary mobile device to prevent the primary mobile device from gaining access to contents of the second data flow.

4. The system of claim 1, wherein the remote procedure call requires predefined permissions, the first vehicle-enabled application lacks the predefined permissions, and the second vehicle-enabled application has the predefined permissions.

5. The system of claim 4, wherein the predefined permissions include permission to utilize one or more of: driving characteristics, vehicle location data, vehicle navigation destinations, keyboard input, touch input, and vehicle information.

6. The system of claim 1, wherein the first vehicle-enabled application is a music application having music permissions but not navigation permissions, and the second vehicle-enabled application is a navigation application having navigation permissions, and the remote procedure call is a send location navigation request requiring navigation permissions.

8. The method of claim 7, wherein the remote procedure call requested by the first vehicle-enabled application is received over a first data flow provided over the first connection, the remote procedure call requested by the second vehicle-enabled application is received over a second data flow provided over the first connection, and the second data flow is encrypted by the secondary mobile device to prevent the primary mobile device from gaining access to contents of the second data flow.

10. The method of claim 7, wherein the remote procedure call requires predefined permissions, the first vehicle-enabled application lacks the predefined permissions, and the second vehicle-enabled application has the predefined permissions.

11. The method of claim 10, wherein the predefined permissions include permission to utilize one or more of: driving characteristics, vehicle location data, vehicle navigation destinations, keyboard input, touch input, and vehicle information.

13. The medium of claim 12, wherein the remote procedure call requested by the first vehicle-enabled application is received over a first data flow provided over the first connection, the remote procedure call requested by the second vehicle-enabled application is received over a second data flow provided over the first connection, and the second data flow is encrypted by the secondary mobile device to prevent the primary mobile device from gaining access to contents of the second data flow.

15. The medium of claim 12, wherein the remote procedure call requires navigation permissions, the first vehicle-enabled application lacks navigation permissions, and the second vehicle-enabled application has navigation permissions.