Seamless web real-time communication support on mobile appliances

• US 10,298,623 B2
• Filed: 06/20/2014
• Issued: 05/21/2019
• 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
• Primary Examiner(s): Srivastava, Vivek
• Assistant Examiner(s): Khan, Atta
• Application Number:
  US14/310,924
• Publication Number:
  US 20150373056A1
• Time in Patent Office: 1,796 Days
• Field of Search: 709203
• 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 one or more IP Multimedia Subsystem (IMS) clients through a multimedia access platform;

retrieving information from a profile associated with a user of the mobile device from an identity and access management (IAM) server, the profile indicating at least one IP Multimedia Subsystem (IMS) client of the one or more IP IMS clients associated with the request for access as being accessible to the browser-based application;

establishing, within a traffic flow template, a dedicated bearer for signaling via the one or more IP IMS clients, the traffic flow template including one or more Quality of Service (QoS) parameters, wherein the one or more QoS parameters include a first QoS level for IP IMS signaling with non-guaranteed bit rate (non-GBR) and a first delay budget of 150 ms and 10<sup>−

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

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

3</sup> packet loss rate;

determining an acceptable user experience, based at least in part on the one or more QoS parameters; and

providing access to the at least one IP IMS client of the one or more IP IMS clients from the multimedia access platform through the browser-based application, based at least in part on the acceptable user experience.

2. The method of claim 1, wherein providing access to the at least one IP IMS client further includes providing access to one or more types of multimedia, in response to an authentication by the IAM server of an identity of the user of the mobile device.

3. The method of claim 1, wherein providing access to the at least one IP IMS client further includes sending communication from the browser-based application to the multimedia access platform in accordance with a signaling protocol of the multimedia access platform, and wherein the multimedia access platform comprises at least one of an IP Multimedia Subsystem (IMS) or an extensible messaging and presence protocol (XMPP) platform.

4. The method of claim 2, further comprising:

transcoding the one or more types of multimedia from a first codec associated with a domain of the multimedia access platform to a second codec associated with the browser-based application, and

wherein providing access to the at least one IP IMS client further includes providing the mobile device with the one or more types of multimedia that is transcoded to the browser-based application.

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 providing, to the browser-based application, information of contacts associated with the user of the mobile device from a data management server.

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 communicating to the browser-based application comprises communicating to the browser-based application in response to receiving a notification regarding an event, the event comprising one of an incoming call for the user of the mobile device, an incoming message for the user of the mobile device, a presence state, or a network degradation.

42. The method of claim 1, wherein the IAM server is further configured to authenticate a user identity that is associated with the mobile device for access to one or more types of multimedia from the multimedia access platform.

43. The method of claim 1, further comprising:

receiving a first signal of an event media that is directed towards the mobile device, the event media corresponding to one of an incoming voice call or an incoming video call; and

transmitting, a second signal to an operating system of the mobile device that causes an execution of the browser-based application on the mobile device.

44. The method of claim 43, further comprising:

determining that the event media is anchored in a service provider network associated with the at least one IP IMS client; and

translating the event media from a first codec of the at least one IP IMS client to a second codec of the browser-based application.

45. The method of claim 1, wherein the traffic flow template is defined as packet filters that are associated with at least on a protocol, an IP packet destination, or a source IP address.

46. The method of claim 45, wherein the packet filters are further associated with an Encapsulated PostScript (EPS) bearer, the EPS bearer including one or more Quality of Service (QoS) parameters, and further comprising:

determining at least one of a GBR resource, a non-GBR resource, a packet delay budget, or a packet loss rate, based at least in part on the one or more QoS parameters.

10. 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 an IP Multimedia Subsystem (IMS);

retrieving information from a profile associated with a user of the mobile device from an identity and access management (IAM) server, the profile indicating at least one IP Multimedia Subsystem (IMS) client of a plurality of IMS clients that are associated with the multimedia access platform as being accessible to the browser-based application;

establishing, within a traffic flow template, a dedicated bearer for signaling via the at least one IP IMS client, the traffic flow template including one or more Quality of Service (QoS) parameters, wherein the one or more QoS parameters include a first QoS level for IP IMS signaling with non-guaranteed bit rate (non-GBR) and a first delay budget of 150 ms and 10<sup>−

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

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

3</sup> packet loss rate; and

providing access to one or more types of multimedia associated with the at least one IP IMS client from the multimedia access platform to the browser-based application based at least in part on the QoS parameters and information in the profile associated with the user of the mobile device.

11. The computing device of claim 10, wherein the providing includes providing the one or more types of multimedia after the user of the mobile device is authenticated by the IAM server.

12. The computing device of claim 10, 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).

13. The computing device of claim 10, wherein the providing includes providing media that is translated between the browser-based application and domains of the multimedia access platform.

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

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

15. The computing device of claim 10, 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.

16. The computing device of claim 15, 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.

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

18. The computing device of claim 17, 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.

47. The computing device of claim 10, further comprising:

determining an acceptable user experience, based at least in part on the one or more QoS parameters, and

wherein, providing access to the one or more types of multimedia is further based at least in part on the acceptable user experience.

19. A method, comprising:

sending, by a browser-based application executed by a mobile device a first request to authenticate a user at an identity and access management (IAM) server, the IAM server configured to authenticate a user identity that is associated with the mobile device for access to one or more types of multimedia from a multimedia access platform;

transmitting, by the browser-based application, a second request for access to multimedia provided by the multimedia access platform to a gateway server; and

receiving via a dedicated bearer established within a traffic flow template by the multimedia access platform, access to one or more types of multimedia, the one or more types of multimedia being translated by the gateway server from a first codec in a first domain of the multimedia access platform to a second codec that is in a second domain of the browser-based application, wherein the traffic flow template includes one or more Quality of Service (QoS) parameters, wherein the one or more QoS parameters include a first QoS level for IP IMS signaling with non-guaranteed bit rate (non-GBR) and a first delay budget of 150 ms and 10<sup>−

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

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

3</sup> packet loss rate; and

accessing, at the browser-based application and via the multimedia access platform, the one or more types of multimedia following an authentication of the user by the IAM server, the multimedia access platform providing access based at least in part on the one or more QoS parameters.

20. The method of claim 19, 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.

21. The method of claim 19, further comprising:

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

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

23. The method of claim 19, further comprising:

receiving a communication from the gateway server; and

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

24. The method of claim 23, wherein receiving the communication comprises one of receiving the communication by a push mechanism, or receiving the communication from the gateway server in response to the gateway server receiving a notification regarding an event.

25. The method of claim 24, 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.

26. The method of claim 19, further comprising:

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

27. 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;

transmitting, to a gateway server, one or more messages each of which have a respective level of a plurality of levels of quality of service (QoS), the plurality of levels of QoS including a first QoS level for IP IMS signaling with non-guaranteed bit rate (non-GBR) and a first delay budget of 150 ms and 10<sup>−

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

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

3</sup> packet loss rate; and

receiving, via a dedicated bearer established within a traffic flow template by a multimedia access platform, access to one or more types of multimedia based at least in part on the plurality of levels of QoS and information from a profile associated with a user of the mobile device that is retrieved from an identity and access management (IAM) server, the profile indicating at least one IP Multimedia Subsystem (IMS) client of a plurality of IMS clients that are associated with the multimedia access platform as being accessible to the browser-based application.

28. The method of claim 27, wherein the one or more messages comprises one or more signaling messages and one or more bearer messages, the one or more bearer messages comprising at least a bear message with a guaranteed bit rate (GBR) or a bear message with a non-GBR.

29. The method of claim 27, 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 the multimedia access platform comprising either or both of an IP Multimedia Subsystem (IMS) and an extensible messaging and presence protocol (XMPP) platform.

30. The method of claim 27, further comprising:

communicating with a data input or output device of the mobile device, the data input or output device of the mobile device corresponding to at least one of a camera or a microphone.

31. The method of claim 27, wherein at least one of the one or more messages comprises a request for access to multimedia provided by the multimedia access platform.

32. 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 of a user by the IAM server, the IAM server configured to authenticate a user identity that is associated with the mobile device for access to one or more types of multimedia from a multimedia access platform;

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

receiving, via a dedicated bearer established within a traffic flow template by the multimedia access platform, access to one or more types of multimedia, the one or more types of multimedia being translated by the gateway server from a first codec in a first domain of the multimedia access platform to a second codec that is in a second domain of the browser-based application, wherein the traffic flow template includes one or more Quality of Service (QoS) parameters, wherein the one or more QoS parameters include a first QoS level for IP IMS signaling with non-guaranteed bit rate (non-GBR) and a first delay budget of 150 ms and 10<sup>−

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

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

3</sup> packet loss rate; and

accessing, at the browser-based application and via the multimedia access platform, the one or more types of multimedia following the authentication of the user by the IAM server, the multimedia access platform providing access to the one or more types of multimedia, based at least in part on the one or more QoS parameters.

33. The mobile device of claim 32, 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.

34. The mobile device of claim 32, 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 the user of the mobile device.

35. The mobile device of claim 32, 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.

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

37. The mobile device of claim 35, 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.

38. The mobile device of claim 37, 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.

39. The mobile device of claim 32, 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.

40. The mobile device of claim 32, 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.

41. The mobile device of claim 32, 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.