Mobile device pass through for signaling messages

1. A method, comprising:

establishing a first channel of communications between a web browser executing on a user terminal and an application programming interface (API) on a mobile device, wherein:

the user terminal is unable to independently generate signaling messages without using the mobile device;

the user terminal and the mobile device are both connected to a particular local area network;

the first channel of communications is established via the particular local area network;

the web browser executing on the user terminal accesses a web application; and

the web application utilizes the API on the mobile device to generate a signaling message directed to an intended recipient device related to the web application;

receiving a request, by the mobile device from the web browser executing on the user terminal and via the established first channel of communications, to generate the signaling message directed to the intended recipient device related to the web application via the API on the mobile device;

generating, by the mobile device and in response to the received request, the requested signaling message related to the web application via the API on the mobile device; and

transmitting, by the mobile device, the generated signaling message directed to the intended recipient device, wherein:

the generated signaling message relates to control of media content related to the web application; and

receipt, by the intended recipient device, of the generated signaling message causes a second channel of communications to be established between the intended recipient device and the user terminal, wherein, when the second channel of communications is established, the media content related to the web application is communicated at least to or from the web browser executing on the user terminal without passing via the established first channel of communications between the web browser executing on the user terminal and the mobile device.

2. The method of claim 1 , wherein the mobile device receives the request to generate the signaling message from the web browser executing on the user terminal implementing a Web Real Time Communication (WebRTC) API.

3. The method of claim 1 , wherein the established first channel of communications is a WebSocket.

4. The method of claim 1 , wherein establishing the first channel of communications further comprises:

authenticating, by the mobile device, the web browser executing on the user terminal; and

authorizing, by the mobile device, the web browser executing on the user terminal to request the API on the mobile device to generate signaling messages.

5. The method of claim 1 , wherein:

generating the signaling message related to the web application via the API on the mobile device further comprises:

establishing a third channel of communications between the API on the mobile device and a signal core related to the API; and

transmitting the generated signaling message further comprises:

delivering, via the signal core related to the API, the generated signaling message to the intended recipient device.

6. The method of claim 5 , wherein establishing the third channel of communications further comprises:

registering, by the API on the mobile device, the API on the mobile device with the signal core related to the API; and

receiving, from the signal core related to the API, authorization for the API on the mobile device to deliver the generated signaling message via the signal core related to the API.

7. The method of claim 1 , wherein:

the API on the mobile device is a Session Initiation Protocol (SIP) API, IP Multimedia Subsystem (IMS) API, or other device level system or framework API specific to the mobile device; and

the API is available on the mobile device but not available on the user terminal.

8. The method of claim 1 , further comprising:

accessing, by the mobile device and prior to establishing the first channel of communications, the web application; and

discontinuing accessing, by the mobile device after establishing the first channel of communications and after the web browser executing on the user terminal begins accessing the web application, the web application.

9. A mobile device, comprising:

a wireless transceiver configured to provide communications through a network via a wireless link;

a processor configured to control operations of the mobile device;

a memory;

an application programming interface (API) in the memory; and

an application program in the memory for execution by the processor, wherein the processor executes the application program to cause the mobile device to:

establish a first channel of communications with a web browser executing on a user terminal, wherein:

the user terminal is unable to independently generate signaling messages without using the mobile device;

the mobile device and the user terminal are both connected to a particular local area network;

the first channel of communications is established via the particular local area network;

the web browser executing on the user terminal accesses a web application; and

the web application utilizes the API on the mobile device to generate a signaling message directed to an intended recipient device related to the web application;

receive a request, from the web browser executing on the user terminal via the established first channel of communications, to generate the signaling message directed to the intended recipient device related to the web application via the API on the mobile device;

generate the requested signaling message directed to the intended recipient device related to the web application via the API on the mobile device; and

transmit the generated signaling message directed to the intended recipient device, wherein:

the generated signaling message relates to control of media content related to the web application; and

receipt, by the intended recipient device, of the generated signaling message causes a second channel of communications to be established between the intended recipient device and the user terminal, wherein, when the second channel of communications is established, the media content related to the web application is communicated at least to or from the web browser executing on the user terminal without passing via the established first channel of communications.

10. The mobile device of claim 9 , wherein the processor further executes the application program to cause the mobile device to receive the request to generate the signaling message from the web browser executing on the user terminal implementing a Web Real Time Communication (WebRTC) API.

11. The mobile device of claim 9 , wherein the established first channel of communications is a Web Socket.

12. The mobile device of claim 9 , wherein, when generating the requested signaling message related to the web application via the API on the mobile device, the processor further executes the application program to cause the mobile device to:

establish a third channel of communications between the API on the mobile device and a signal core related to the API; and

wherein, when transmitting the generated signaling message, the processor further executes the application program to cause the mobile device to:

deliver, via the signal core related to the API, the generated signaling message to the intended recipient device.

13. The mobile device of claim 12 , wherein, when establishing the third channel of communications, the processor further executes the application program to cause the mobile device to:

register the API on the mobile device with the signal core related to the API; and

receive, from the signal core related to the API, authorization to deliver the generated signaling message via the signal core related to the API.

14. The mobile device of claim 9 , wherein:

the API is a Session Initiation Protocol (SIP) API, IP Multimedia Subsystem (IMS) API, or other device level system or framework API specific to the mobile device; and

the API is available on the mobile device but not available on the user terminal.

15. The mobile device of claim 9 , wherein the processor further executes the application program to cause the mobile device to:

access the web application, prior to establishing the first channel of communications with the web browser executing on the user terminal; and

discontinue accessing the web application, after establishing the first channel of communications and the web browser executing on the user terminal initiates access to the web application.

16. A method, comprising:

establishing a first channel of communications between a web browser executing on a user terminal and an application programming interface (API) on a mobile device, wherein:

the user terminal is unable to independently generate signaling messages without using the mobile device;

the user terminal and the mobile device are each connected to a particular local area network;

the first channel of communications is established via the particular local area network;

the web browser executing on the user terminal accesses a web application; and

the web application utilizes the API on the mobile device to generate a signaling message directed to an intended recipient device related to the web application;

requesting, by the web browser executing on the user terminal and via the established first channel of communications, the API on the mobile device to generate and transmit the signaling message directed to the intended recipient device, wherein receipt, by the intended recipient device, of the signaling message causes a second channel of communications to be established between the intended recipient device and the user terminal; and

receiving or sending, by the web browser executing on the user terminal and in response to the signaling message generated by the API on the mobile device, media content related to the web application, wherein:

the signaling message generated by the API on the mobile device relates to control of the media content related to the web application; and

the media content related to the web application is communicated at least to or from the web browser executing on the user terminal via the second channel of communications without passing via the established first channel of communications.

17. The method of claim 16 , wherein the web browser executing on the user terminal implements a Web Real Time Communication (WebRTC) API.

18. The method of claim 16 , wherein the established first channel of communications is a Web Socket.

19. The method of claim 16 , wherein:

the API on the mobile device is a Session Initiation Protocol (SIP) API, IP Multimedia Subsystem (IMS) API, or other device level system or framework API specific to the mobile device; and

the API is available on the mobile device but not available on the user terminal.

20. The method of claim 16 , further comprising:

requesting, by the web browser executing on the user terminal and via the established first channel of communications, the mobile device to discontinue accessing the web application currently being accessed by the web browser executing on the user terminal,

wherein the mobile device accessed the web application prior to establishing the first channel of communications.