22.2283GPPRelease 16Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS)Stage 1TS
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.
H.5.3 Service flows
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.