Mary provides her credentials when accessing a WebRTC-based application provided by her IMS operator to access a broad range of IMS services (these credentials are provided by the operator). The application provides a user interface to the IMS user, Mary, to allow her to invoke her IMS services. Using the application, Mary is able to access the same broad range of capabilities available to a native IMS client, as appropriate to the available access technologies. In particular, Mary is able to originate and terminate calls using any of her IMS public user identities, and may access other rich communication services such as presence and instant messaging sessions. The instant messaging sessions may be integrated with other WebRTC media.

Mary has an IMS subscription and a WebRTC-capable browser on a device that supports an access technology with acceptable QoS (e.g., LTE). Mary might have multiple credentials provided by the operator linked to her IMS subscription (e.g., user name and password). Mary's IMS operator hosts a web site that provides a WebRTC-based portal to Mary's IMS services.

Mary accesses her IMS operator's web site from her browser, which executes an instance of the IMS portal client. The IMS portal arranges to authenticate (based on the offered credentials) and register the IMS/WebRTC client with IMS and provides a user interface to Mary via the browser to access IMS services. Mary can initiate or receive multimedia sessions, access presence information, participate in instant messaging sessions, and initiate any other service expected by a native IMS client.

After invoking IMS services, the browser window remains available for Mary to initiate other services or to accept incoming sessions.

John clicks on a link to a third-party WebRTC-based application that offers access to his IMS services from his IMS operator. The third-party application provides a specialized application to John such as gaming, conferencing, or business services, where the application can benefit if the user has access to IMS services. John provides his IMS credentials in a secure manner to the IMS operator during the scenario before he is able to access his IMS services.

John has an IMS subscription and a WebRTC capable browser on a device that supports an access technology with acceptable QoS (e.g., LTE). A third-party WebRTC-based application provides access to a WebRTC-based portal to the user's IMS. The third party has a business relationship with the IMS operator that allows the third party to incorporate access to IMS services into the experience provided by the third-party application.

John accesses the third-party web site from his browser, which executes the third-party WebRTC-based application along with the WebRTC IMS client functions needed for access to an IMS portal. The IMS portal arranges to authenticate and register the IMS/WebRTC client with IMS and cooperates with the third-party server to provide a user interface to John via the browser to access his IMS services. John has access to IMS services via the third-party WebRTC-based application.

After invoking IMS services, the browser window remains available for John to initiate other services or to accept incoming sessions, if supported.

Mary clicks on a link to a third-party WebRTC-based application that offers access to real time communications services facilitated by an IMS operator. The third-party WebRTC-based application provides enterprise-specific communication services to employee Mary. The third-party WebRTC-based application configures a block of IMS public user identities for use with an IMS operator on behalf of all the users of the web site (e.g., this block may be a domain or sub-domain). An individual user, Mary, logs into the third-party WebRTC-based application but does not have user specific credentials with the IMS operator. Mary receives some communications services directly from the third-party WebRTC-based application and other communications services directly from the IMS operator. For example, the third-party WebRTC-based application may facilitate RTC sessions directly between WebRTC clients, while IMS facilitates sessions with non-WebRTC endpoints.

Mary has a WebRTC capable browser on a device that supports an acceptable access technology. A third-party WebRTC-based application provides access to a WebRTC-based portal to the IMS that has a block of IMS public user identities and subscriptions configured for use with an IMS operator. The WebRTC-based portal maintains the association between the users' credentials and its IMS public user identities. The third party has a business relationship with the IMS operator that allows the third-party WebRTC-based application to incorporate access to IMS services into the experience provided by the third-party WebRTC-based application. The third-party server supports all interworking with the IMS and assigns individual public user identities to the users of its web site so that they can receive IMS services.

Mary accesses the third-party web site from her browser, which executes the third-party WebRTC-based application along with the WebRTC-based client functions needed for access to an IMS portal. The third-party WebRTC-based application registers and authenticates Mary for access to the IMS services associated with an assigned public user identity from the public user identity block used by the third-party WebRTC-based portal to IMS. The IMS portal cooperates with the third-party WebRTC-based application to provide a user interface to Mary via her browser to access IMS services. Mary has access to IMS services via the WebRTC-based application.

After invoking IMS services, the browser window remains available to initiate other services or to accept incoming sessions, if supported.

John clicks on a link to a third-party WebRTC-based application that offers access to real time communications services facilitated by an IMS operator. The third-party WebRTC-based application provides a specialized application to the user such as a customer services portal for a retail establishment. The third-party WebRTC-based application registers a public user identity with an IMS operator on behalf of all its users of. John does not log into the third-party WebRTC-based application and does not have user specific credentials with IMS. John is unknown (anonymous) to both the third-party WebRTC-based application and IMS. John receives very limited origination services from IMS, as allowed by the third-party WebRTC-based application. In particular, John is not reachable via any public user identity via this third-party WebRTC-based application. This capability might be used to allow a user to initiate a call to a customer representative but to no one else, or to join a conference, for example.

John has a WebRTC capable browser on a device that supports an acceptable access technology. A third-party has a subscription with an IMS operator and provides a web site that provides access to a WebRTC-based portal to the IMS. The third-party has a business relationship with the IMS operator that allows the third-party to incorporate access to IMS services into the features provided by the third-party WebRTC-based application. The third-party WebRTC-based portal to the IMS maintains its registration with IMS and allows (potentially anonymous) users of its web site (e.g., John) to access IMS services using its (the third-party WebRTC-based portal to the IMS) identity so that they can receive IMS services.

John accesses the third-party web site from his browser, which executes the third-party WebRTC-based application along with the WebRTC-based client functions needed for access to an IMS portal. The third-party WebRTC-based application may not register or authenticate John, but instead treats him as an anonymous guest with limited privileges to access IMS services using the portal's IMS identity. The IMS portal cooperates with the third-party WebRTC-based application to provide a user interface to John via his browser to access IMS services. John has access to limited IMS services via his browser user interface, e.g., John may not be reachable since no unique IMS public user identity is assigned to him, and there may be limitations on which other parties he can contact.

After invoking IMS services, the browser window remains available for John to initiate other available IMS services.

Jane is doing her taxes using an online tool and encounters a complexity with which she would like some help. Her tax tool website includes a big red HELP button which connects her to a tax advisor associated with the tool. Associated with the HELP button is a link to a third-party WebRTC-based application that offers access to communications services facilitated by an IMS operator. The third-party WebRTC-based application provides a specialized application to the user such as a customer services portal for a tax advisor. In addition to being able to utilize IMS capabilities, the tax advisor has an agreement with their IMS operator to use a WebRTC based codec as its preferred audio codec and, as an enterprise service, to provide secure chat to communicate with WebRTC IMS client users. The IMS operator is able to convey the audio and chat session without bearer level protocol conversion which might interfere with quality and maintains the end to end security between Jane's device and third party WebRTC-based application. Figure H.6.1-1 illustrates the configuration allowing end to end communication between WebRTC IMS clients.

Jane has a WebRTC capable browser on a device that supports a WebRTC codec and an end to end WebRTC security protocol. Her tax advisor has a subscription with an IMS operator and provides a web site that provides access to a WebRTC-based portal to the IMS; the IMS does not support the WebRTC codec. The tax advisor has a business relationship with the IMS operator that allows the tax advisor to incorporate access to specialized non-IMS capabilities (e.g., use of WebRTC codec, secure chat) into the features provided by the tax advisor's WebRTC-based application. The tax advisor's web site provides customers the ability to select from various options (e.g., voice, chat, video, secure/unsecure channels) when they request online HELP. The tax advisor has their WebRTC browser up and is registered with IMS and is able initiate services or to accept incoming sessions.

Jane accesses the tax advisor web site from her browser by clicking on the HELP button, which executes the WebRTC-based application along with the WebRTC IMS client functions needed for access to IMS. Jane engages in an unsecured chat session with her tax advisor to resolve a question on completing her tax forms. This chat session is hosted by IMS and does not provide end to end security. While continuing the chat session, Jane opens an audio connection with her tax advisor as the discussion becomes more complex. Since both endpoints are WebRTC IMS clients supporting the same WebRTC codec, and the tax advisor's subscription allows it, the bearer path is conveyed without protocol conversion, allowing Jane and the tax advisor to experience very high quality audio. While discussing the tax issue, Jane and her tax advisor decide it would be helpful to share figures, calculations, and personal tax information. To do this securely, they select a secure chat line that utilizes the WebRTC end to end security.

Jane is satisfied with the quality and security of her exchange with her tax advisor.