Content for TR 23.706 Word version: 13.0.0
5 WebRTC support of IMS subscriptions corresponding to users managed by third parties
6 Third-party realization of communication services
7 Interworking of Rel-12 or earlier IMS services with WebRTC
8 Architectural aspects for minimizing the need for bearer level protocol conversion
9 Architectural aspects to support for end to end WebRTC security
10 Conclusion
$ Change History
5 WebRTC support of IMS subscriptions corresponding to users managed by third parties p. 8
5.0 General description p. 8
5.1 Architectural requirements p. 8
5.2 Solutions p. 8
5.2.1 Solution 1: Single HSS subscription for an unbounded number of users p. 8
5.2.1.1 Principles p. 8
5.2.1.2 Architecture p. 10
5.2.1.3 Flows p. 11
5.2.1.3.1 Flows related with the registration p. 11
5.2.1.3.2 Flows related with the session set-up, modification and release p. 15
5.2.1.3.3 Support of Multi-registration and forking p. 16
5.2.1.3.4 Service resiliency at the failure of a CSCF p. 16
5.2.1.4 Impacts p. 16
5.2.2 Solution 2: wIMPU Single HSS subscription p. 17
5.2.2.1 Principles p. 17
5.2.2.2 Architecture p. 17
5.2.2.3 Functional entities p. 19
5.2.2.4 Reference points p. 19
5.2.2.5 Flows p. 20
5.2.2.5.1 Block Registration of the wIMPU Range p. 20
5.2.2.5.2 WIC Registration procedure p. 20
5.2.2.5.3 Origination p. 21
5.2.2.5.4 Termination p. 22
5.2.2.6 Solution Impacts p. 22
5.2.3 Solution 3: HSS supports IMS subscriptions corresponding to users managed by third parties p. 23
5.2.3.1 Solution Principles p. 23
5.2.3.2 Reference Architecture p. 24
5.2.3.3 Procedures p. 24
5.2.3.3.1 WIC Registration for subscriptions belonging to a class of users p. 24
5.2.3.3.2 WIC Registration when two or more WICs sharing the same IMPU p. 25
5.2.3.3.3 WIC Session management related procedures for a class of users p. 26
5.2.3.3.4 WIC De-Registration for subscriptions belonging to a class of users p. 26
5.2.3.3.5 HSS keeps correct registration states for interworking with existing application services p. 26
5.2.3.4 Impacts p. 26
5.2.4 Solution 4: Single HSS subscription and enhanced AS p. 26
5.2.4.1 Solution Principles p. 26
5.2.4.2 Architecture p. 27
5.2.4.3 Procedures p. 28
5.2.4.3.1 Registration procedure p. 28
5.2.4.3.2 MT procedure p. 29
5.2.4.3.3 Other session related procedure p. 30
5.2.4.3.4 Service resiliency, Multi-registration and forking p. 30
5.2.4.4 Impacts and evaluation p. 30
5.2.5 Solution 5: Decomposed architecture supports IMS subscriptions corresponding to users managed by third parties p. 30
5.2.5.1 Principles p. 30
5.2.5.2 Reference Architecture p. 30
5.2.5.4 W8 interface p. 31
5.2.5.5 Procedures p. 31
5.2.5.5.1 WIC Registration for subscriptions belonging to a class of users p. 31
5.2.5.5.2 WIC Session management related procedures for a class of users p. 33
5.2.5.5.3 WIC De-Registration for subscriptions belonging to a class of users p. 33
5.2.5.6 Impacts p. 33
5.3 Evaluation p. 33
5.4 Conclusion p. 38
6 Third-party realization of communication services p. 39
6.0 General description p. 39
6.1 Architectural requirements p. 39
6.2 Solutions p. 39
6.2.1 Solution 1: WTPF interworking with IMS p. 39
6.2.1.1 Overview p. 39
6.2.1.2 W8 interface p. 40
6.2.2 Solution 2: Decomposed Architecture for PBX p. 40
6.2.2.1 Overview p. 40
6.2.2.2 W8 interface p. 41
6.2.2.3 Decomposed architecture for business trunking p. 41
6.2.2.4 Procedures p. 42
6.3 Evaluation p. 42
6.4 Conclusion p. 42
7 Interworking of Rel-12 or earlier IMS services with WebRTC p. 42
7.0 General description p. 42
7.1 Architectural requirements p. 42
7.2 Solutions p. 43
7.2.1 Solution 1: WebRTC service control p. 43
7.2.1.1 Solution Principles p. 43
7.2.1.2 Reference Architecture p. 43
7.2.1.3 Procedures p. 43
7.2.1.4 Impacts p. 44
7.2.2 Solution 2: Avoiding SRVCC false trigger p. 45
7.2.3 Solution 3: WebRTC with SMSMI p. 45
7.2.3.1 Solution Principles p. 45
7.2.3.2 Reference Architecture with SMSMI p. 45
7.2.3.3 Procedures p. 46
7.2.3.4 Impacts p. 47
7.2.4 Solution 4: WebRTC with Inter-UE Transfer (IUT) p. 47
7.3 Evaluation p. 50
7.4 Conclusion p. 50
8 Architectural aspects for minimizing the need for bearer level protocol conversion p. 50
8.0 General description p. 50
8.1 Architectural requirements p. 50
8.2 Solutions p. 51
8.2.1 Solution 1: Transmit of WebRTC specific SDP information to establish e2e media path p. 51
8.2.1.1 Reference Architecture p. 51
8.2.1.2 Solution Principles p. 51
8.2.1.3 Signalling Procedures p. 52
8.2.1.4 Media plane related procedures p. 54
8.2.2 Solution 2: OMR-based e2e media transport p. 57
8.2.3 Solution 3: OMR-based e2ae media transport p. 59
8.3 Evaluation p. 61
8.4 Conclusion p. 61
9 Architectural aspects to support for end to end WebRTC security p. 61
9.0 General description p. 61
9.1 Architectural requirements p. 61
9.2 Solutions p. 61
9.3 Evaluation p. 61
9.4 Conclusion p. 61
10 Conclusion p. 61
$ Change History p. 63
