Tech-invite  3GPPspace  IETFspace
◀  ▶  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

TR 23.706
Study on enhancements to
Web Real Time Communication (WebRTC) access to IMS

3GPP‑Page   fToC↓   Partial Content →
V13.0.0 (Wzip)  2015/09  63 p.
Rapporteur:
Dr. Qing, Yu
China Mobile Com. Corporation

full Table of Contents for  TR 23.706  Word version:  13.0.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
1Scope  p. 7
2References  p. 7
3Definitions and abbreviations  p. 7
3.1Definitions  p. 7
3.3Abbreviations  p. 7
4Assumptions and architectural requirements  p. 7
5WebRTC support of IMS subscriptions corresponding to users managed by third parties  p. 8
5.0General description  p. 8
5.1Architectural requirements  p. 8
5.2Solutions  p. 8
5.2.1Solution 1: Single HSS subscription for an unbounded number of users  p. 8
5.2.1.1Principles  p. 8
5.2.1.2Architecture  p. 10
5.2.1.2.1Overview  p. 10
5.2.1.2.2Routing and usage of IMPU  p. 11
5.2.1.3Flows  p. 11
5.2.1.3.1Flows related with the registration  p. 11
5.2.1.3.1.2Registration information flow - User already registered  p. 13
5.2.1.3.2Flows related with the session set-up, modification and release  p. 15
5.2.1.3.3Support of Multi-registration and forking  p. 16
5.2.1.3.4Service resiliency at the failure of a CSCF  p. 16
5.2.1.4Impacts  p. 16
5.2.2Solution 2: wIMPU Single HSS subscription  p. 17
5.2.2.1Principles  p. 17
5.2.2.2Architecture  p. 17
5.2.2.2.1Control of Forking  p. 18
5.2.2.3Functional entities  p. 19
5.2.2.3.1wIMPU Registrar  p. 19
5.2.2.3.2eP-CSCF  p. 19
5.2.2.3.3I-CSCF  p. 19
5.2.2.4Reference points  p. 19
5.2.2.4.1W6 (eP-CSCFto wIMPU Registrar)  p. 19
5.2.2.4.2W7 (I-CSCF to wIMPU Registrar)  p. 20
5.2.2.5Flows  p. 20
5.2.2.5.1Block Registration of the wIMPU Range  p. 20
5.2.2.5.2WIC Registration procedure  p. 20
5.2.2.5.3Origination  p. 21
5.2.2.5.4Termination  p. 22
5.2.2.6Solution Impacts  p. 22
5.2.3Solution 3: HSS supports IMS subscriptions corresponding to users managed by third parties  p. 23
5.2.3.1Solution Principles  p. 23
5.2.3.2Reference Architecture  p. 24
5.2.3.3Procedures  p. 24
5.2.3.3.1WIC Registration for subscriptions belonging to a class of users  p. 24
5.2.3.3.2WIC Registration when two or more WICs sharing the same IMPU  p. 25
5.2.3.3.3WIC Session management related procedures for a class of users  p. 26
5.2.3.3.4WIC De-Registration for subscriptions belonging to a class of users  p. 26
5.2.3.3.5HSS keeps correct registration states for interworking with existing application services  p. 26
5.2.3.4Impacts  p. 26
5.2.4Solution 4: Single HSS subscription and enhanced AS  p. 26
5.2.4.1Solution Principles  p. 26
5.2.4.2Architecture  p. 27
5.2.4.3Procedures  p. 28
5.2.4.3.1Registration procedure  p. 28
5.2.4.3.2MT procedure  p. 29
5.2.4.3.3Other session related procedure  p. 30
5.2.4.3.4Service resiliency, Multi-registration and forking  p. 30
5.2.4.4Impacts and evaluation  p. 30
5.2.5Solution 5: Decomposed architecture supports IMS subscriptions corresponding to users managed by third parties  p. 30
5.2.5.1Principles  p. 30
5.2.5.2Reference Architecture  p. 30
5.2.5.4W8 interface  p. 31
5.2.5.5Procedures  p. 31
5.2.5.5.1WIC Registration for subscriptions belonging to a class of users  p. 31
5.2.5.5.2WIC Session management related procedures for a class of users  p. 33
5.2.5.5.3WIC De-Registration for subscriptions belonging to a class of users  p. 33
5.2.5.6Impacts  p. 33
5.3Evaluation  p. 33
5.3.1High level Description of the solutions  p. 33
5.3.2Evaluation Criteria  p. 34
5.4Conclusion  p. 38
6Third-party realization of communication services  p. 39
6.0General description  p. 39
6.1Architectural requirements  p. 39
6.2Solutions  p. 39
6.2.1Solution 1: WTPF interworking with IMS  p. 39
6.2.1.1Overview  p. 39
6.2.1.2W8 interface  p. 40
6.2.2Solution 2: Decomposed Architecture for PBX  p. 40
6.2.2.1Overview  p. 40
6.2.2.2W8 interface  p. 41
6.2.2.3Decomposed architecture for business trunking  p. 41
6.2.2.4Procedures  p. 42
6.3Evaluation  p. 42
6.4Conclusion  p. 42
7Interworking of Rel-12 or earlier IMS services with WebRTC  p. 42
7.0General description  p. 42
7.1Architectural requirements  p. 42
7.2Solutions  p. 43
7.2.1Solution 1: WebRTC service control  p. 43
7.2.1.1Solution Principles  p. 43
7.2.1.2Reference Architecture  p. 43
7.2.1.3Procedures  p. 43
7.2.1.3.1WIC Registration and service control of individual Public User Identity  p. 43
7.2.1.4Impacts  p. 44
7.2.2Solution 2: Avoiding SRVCC false trigger  p. 45
7.2.2.1Solution Principles  p. 45
7.2.3Solution 3: WebRTC with SMSMI  p. 45
7.2.3.1Solution Principles  p. 45
7.2.3.2Reference Architecture with SMSMI  p. 45
7.2.3.3Procedures  p. 46
7.2.3.3.1WIC Registration with SMSMI capability.  p. 46
7.2.3.4Impacts  p. 47
7.2.4Solution 4: WebRTC with Inter-UE Transfer (IUT)  p. 47
7.2.4.1General  p. 47
7.2.4.2Reference Architecture with IUT  p. 48
7.2.4.3Impacts  p. 49
7.3Evaluation  p. 50
7.4Conclusion  p. 50
7.4.1Avoid SRVCC  p. 50
7.4.2WebRTC related IMS service control  p. 50
7.4.3WebRTC with Inter-UE Transfer (IUT)  p. 50
8Architectural aspects for minimizing the need for bearer level protocol conversion  p. 50
8.0General description  p. 50
8.1Architectural requirements  p. 50
8.2Solutions  p. 51
8.2.1Solution 1: Transmit of WebRTC specific SDP information to establish e2e media path  p. 51
8.2.1.1Reference Architecture  p. 51
8.2.1.2Solution Principles  p. 51
8.2.1.3Signalling Procedures  p. 52
8.2.1.4Media plane related procedures  p. 54
8.2.1.4.1Media plane related procedures without IMS core enhanced to support WebRTC accessing  p. 54
8.2.1.4.2Media plane related procedures with IMS core enhanced to support WebRTC accessing  p. 56
8.2.2Solution 2: OMR-based e2e media transport  p. 57
8.2.2.1Reference Architecture  p. 57
8.2.2.2Solution Principles  p. 57
8.2.2.3Procedures  p. 57
8.2.3Solution 3: OMR-based e2ae media transport  p. 59
8.2.3.1Reference Architecture  p. 59
8.2.3.2Solution Principles  p. 59
8.2.3.3Procedure  p. 59
8.3Evaluation  p. 61
8.4Conclusion  p. 61
9Architectural aspects to support for end to end WebRTC security  p. 61
9.0General description  p. 61
9.1Architectural requirements  p. 61
9.2Solutions  p. 61
9.3Evaluation  p. 61
9.4Conclusion  p. 61
10Conclusion  p. 61
$Change History  p. 63

Up   Top