Seamless Web Real-Time Communication Support On Mobile Appliances

• US 20150373056A1
• Filed: 06/20/2014
• Published: 12/24/2015
• Est. Priority Date: 06/20/2014
• Status: Active Grant

• Current Assignee: T-Mobile USA, Inc. (Deutsche Telekom AG)
• Original Assignee: T-Mobile USA, Inc. (Deutsche Telekom AG)
• Inventors: Bouthemy, Jean-Luc
• Granted Patent: US 10,298,623 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 65/1033 Signalling gateways
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/306 User profiles

Abstract

Techniques pertaining to seamless WebRTC support on mobile appliances are described. In one aspect, a method includes one or more processors of one or more gateway servers receiving from a browser-based application executed by a mobile device a request for access to multimedia provided by a multimedia access platform. The method also includes the one or more processors retrieving information related to a profile associated with a user of the mobile device from an identity and access management server. The method further includes the one or more processors enabling the browser-based application to receive from the multimedia access platform one or more types of multimedia based at least in part on the profile associated with the user of the mobile device.

Claims

1. A method, comprising:

receiving, by one or more processors, from a browser-based application executed by a mobile device a request for access to multimedia provided by a multimedia access platform;

retrieving information related to a profile associated with a user of the mobile device from an identity and access management (IAM) server; and

enabling the browser-based application to receive from the multimedia access platform one or more types of multimedia based at least in part on the profile associated with the user of the mobile device.

2. The method of claim 1, wherein the enabling the browser-based application to receive from the multimedia access platform one or more types of multimedia comprises enabling the browser-based application to receive from the multimedia access platform the one or more types of multimedia after the user of the mobile device is authenticated by the IAM server.

3. The method of claim 1, wherein the enabling the browser-based application to receive from the multimedia access platform one or more types of multimedia comprises communicating with the multimedia access platform in accordance with a signaling protocol of the multimedia access platform, and wherein the multimedia access platform comprises either or both of an IP Multimedia Subsystem (IMS) and an extensible messaging and presence protocol (XMPP) platform.

4. The method of claim 1, wherein the enabling the browser-based application to receive from the multimedia access platform one or more types of multimedia comprises translating media between the browser-based application and domains of the multimedia access platform.

5. The method of claim 1, wherein the browser-based application comprises a Web Real-Time Communication (WebRTC) application in accordance with a World Wide Web Consortium (W3C), and wherein the browser-based application comprises a native or hybrid web application.

6. The method of claim 1, further comprising:

enabling the browser-based application to retrieve from a data management server information of contacts associated with the user of the mobile device.

7. The method of claim 6, wherein the data management server comprises an extensible markup language (XML) data management server (XDMS).

8. The method of claim 1, further comprising:

communicating to the browser-based application; and

receiving a query from the browser-based application in response to the communicating.

9. The method of claim 8, wherein the communicating comprises communicating by a push mechanism.

10. The method of claim 8, wherein the communicating to the browser-based application comprises communicating to the browser-based application in response to receiving a notification regarding an event.

11. The method of claim 10, wherein the event comprises an incoming call for the user of the mobile device, an incoming message for the user of the mobile device, a presence state, or network degradation.

12. A computing device, comprising:

memory configured to store at least a set of instructions; and

one or more processors coupled to the memory and configured to execute the set of instructions to perform operations comprising;

receiving from a browser-based application executed by a mobile device a request for access to multimedia provided by a multimedia access platform comprising either or both of an IP Multimedia Subsystem (IMS) and extensible messaging and presence protocol (XMPP) platform;

retrieving information related to a profile associated with a user of the mobile device from an identity and access management (IAM) server; and

enabling the browser-based application to receive from the multimedia access platform one or more types of multimedia based at least in part on the profile associated with the user of the mobile device.

13. The computing device of claim 12, wherein the one or more processors are further configured to perform operations comprising:

enabling the browser-based application to receive from the multimedia access platform the one or more types of multimedia after the user of the mobile device is authenticated by the IAM server.

14. The computing device of claim 12, wherein the one or more processors are further configured to perform operations comprising:

communicating with the multimedia access platform in accordance with a Session Initiation Protocol (SIP).

15. The computing device of claim 12, wherein, in enabling the browser-based application to receive from the multimedia access platform one or more types of multimedia, the one or more processors are configured to translate media between the browser-based application and domains of the multimedia access platform.

16. The computing device of claim 12, wherein the one or more processors are further configured to perform operations comprising:

enabling the browser-based application to retrieve from an extensible markup language (XML) data management server (XDMS) information of contacts associated with the user of the mobile device.

17. The computing device of claim 12, wherein the one or more processors are further configured to perform operations comprising:

communicating to the browser-based application by a push mechanism; and

receiving a query from the browser-based application in response to the communicating.

18. The computing device of claim 17, wherein the communicating to the browser-based application comprises communicating to an operating system of the mobile device to wake up the browser-based application from a sleep mode.

19. The computing device of claim 17, wherein the communicating to the browser-based application comprises communicating to the browser-based application in response to receiving a notification regarding an event.

20. The computing device of claim 19, wherein the event comprises an incoming call for the user of the mobile device, an incoming message for the user of the mobile device, a presence state, or network degradation.

21. A method, comprising:

communicating, by a browser-based application executed by a mobile device, with an identity and access management (IAM) server for authentication by the IAM server;

transmitting to a gateway server a request for access to multimedia provided by a multimedia access platform; and

receiving from the multimedia access platform one or more types of multimedia.

22. The method of claim 21, wherein the browser-based application comprises a Web Real-Time Communication (WebRTC) application in accordance with a World Wide Web Consortium (W3C), and wherein the browser-based application comprises a native or hybrid web application.

23. The method of claim 21, further comprising:

retrieving from a data management server information of contacts associated with a user of the mobile device.

24. The method of claim 23, wherein the data management server comprises an extensible markup language (XML) data management server (XDMS).

25. The method of claim 21, further comprising:

receiving a communication from the gateway server; and

transmitting a query to the gateway server in response to receiving the communication.

26. The method of claim 25, wherein the receiving the communication comprises receiving the communication by a push mechanism.

27. The method of claim 25, wherein the receiving the communication from the gateway server comprises receiving the communication from the gateway server in response to the gateway server receiving a notification regarding an event.

28. The method of claim 27, wherein the event comprises an incoming call for the user of the mobile device, an incoming message for the user of the mobile device, a presence state, or network degradation.

29. The method of claim 21, further comprising:

transmitting a notification to the gateway server in response to a change of an IP address associated with the mobile device.

30. The method of claim 21, further comprising:

transmitting a notification to the gateway server in response to a change of a network associated with the mobile device.

31. A method, comprising:

registering, by a browser-based application executed by a mobile device, with an identity and access management (IAM) server of a network upon the browser-based application being launched; and

transmitting to the gateway server one or more messages each of which having a respective level of a plurality of levels of quality of service (QoS).

32. The method of claim 31, wherein the plurality of levels of QoS comprise a first QoS level for IP multimedia subsystem (IMS) signaling with non-guaranteed bit rate (non-GBR) and a delay budget of 150 ms and 10⁻

6 packet loss rate, a second QoS level for voice calls with guaranteed bit rate (GBR) and a delay budget of 100 ms and 10<sup>−

1</sup> packet loss rate, and a third QoS level for video calls with GBR and a delay budget of 150 ms and 10<sup>−

3</sup> packet loss rate.

33. The method of claim 31, wherein the one or more messages comprises one or more signaling messages and one or more bearer messages.

34. The method of claim 33, wherein the one or more bearer messages comprise at least a bear message with guaranteed bit rate (GBR) or a bear message with non-GBR.

35. The method of claim 31, wherein the registering comprises:

retrieving credential information from a universal integrated circuit card (UICC) of the mobile device;

transmitting the credential information to the IAM server for authentication by the IAM server; and

receiving one or more messages from the IAM server indicating authorization to access multimedia provided by a multimedia access platform comprising either or both of an IP Multimedia Subsystem (IMS) and an extensible messaging and presence protocol (XMPP) platform.

36. The method of claim 31, further comprising:

communicating with a data input or output device of the mobile device.

37. The method of claim 36, wherein the data input or output device of the mobile device comprises a camera, a microphone, or both.

38. The method of claim 31, further comprising:

receiving from a multimedia access platform one or more types of multimedia,

wherein at least one of the one or more messages comprises a request for access to multimedia provided by the multimedia access platform.

39. A mobile device, comprising:

memory configured to store at least a set of instructions; and

one or more processors coupled to the memory and configured to execute the set of instructions to perform operations comprising;

executing a browser-based application to communicate with an identity and access management (IAM) server for authentication by the IAM server;

transmitting to a gateway server a request for access to multimedia provided by a multimedia access platform; and

receiving from the multimedia access platform one or more types of multimedia.

40. The mobile device of claim 39, wherein the browser-based application comprises a Web Real-Time Communication (WebRTC) application in accordance with a World Wide Web Consortium (W3C), and wherein the browser-based application comprises a native or hybrid web application.

41. The mobile device of claim 39, wherein the one or more processors are further configured to perform operations comprising:

retrieving from an extensible markup language (XML) data management server (XDMS) information of contacts associated with a user of the mobile device.

42. The mobile device of claim 39, wherein the one or more processors are further configured to perform operations comprising:

receiving a communication from the gateway server; and

transmitting a query to the gateway server in response to receiving the communication.

43. The mobile device of claim 42, wherein the receiving the communication comprises receiving the communication by a push mechanism.

44. The mobile device of claim 42, wherein the receiving the communication from the gateway server comprises receiving the communication from the gateway server in response to the gateway server receiving a notification regarding an event.

45. The mobile device of claim 44, wherein the event comprises an incoming call for the user of the mobile device, an incoming message for the user of the mobile device, a presence state, or network degradation.

46. The mobile device of claim 39, wherein the one or more processors are further configured to perform operations comprising:

accessing one or more input devices or one or more output devices of the mobile device to support the browser-based application; and

accessing a universal integrated circuit card (UICC) of the mobile device to support the browser-based application.

47. The mobile device of claim 39, wherein the one or more processors are further configured to perform operations comprising:

receiving periodically a wake-up message from the gateway server; and

transmitting a response message to the gateway server in response to receiving the wake-up message.

48. The mobile device of claim 39, wherein the one or more processors are further configured to perform operations comprising:

transmitting a notification to the gateway server in response to a change of an IP address or a network associated with the mobile device.