Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 23.701
Word version: 12.0.0
1…
5…
5
Solutions
5.1
Solution 1
5.2
Solution 2
5.3
Solution 3
5.4
Solution 4
5.5
Solution 5
5.6
Solution 6
5.7
Solution 7
6
Evaluation
7
Conclusions
A
WebRTC access to IMS - network-based architecture
A.1
Overview
A.2
Procedures
$
Change History
5
Solutions
p. 10
5.1
Solution 1
p. 11
5.1.1
Overview
p. 11
5.1.2
Description of the solution - Procedures
p. 11
5.1.2.0
General Assumptions
p. 11
5.1.2.1
Registration
p. 12
5.1.2.1.1
WebRTC client-initiated registration
p. 12
5.1.2.1.2
IWF acting as an IP-PBX
p. 13
5.1.2.2
Session handing
p. 14
5.1.2.2.0
Assumptions
p. 14
5.1.2.2.1
Handling of outgoing sessions
p. 14
5.1.2.2.2
Handling of incoming sessions
p. 15
5.1.2.3
Extended role of the P-CSCF to handle interoperability between a WebRTC client and an existing 3GPP UE
p. 15
5.1.3
Impact on existing entities and interfaces
p. 16
5.1.4
Solution evaluation
p. 16
5.2
Solution 2
p. 16
5.2.1
Overview
p. 16
5.2.2
Description of the solution - Procedures
p. 16
5.2.2.1
Functions of the WebRTC Signalling Function
p. 16
5.2.2.2
Functions of the WebRTC Media Function
p. 18
5.2.2.3
Functions of the PCC framework
p. 18
5.2.2.4
IMS registration and authentication
p. 19
5.2.2.4.0
General
p. 19
5.2.2.4.1
Registration: WebRTC client uses SIP over WebSockets
p. 19
5.2.2.4.2
Registration: WebRTC client uses Web Authentication
p. 22
5.2.2.5
Origination and termination
p. 22
5.2.3
Impact on existing entities and interfaces
p. 23
5.2.4
Solution evaluation
p. 23
5.3
Solution 3
p. 23
5.3.1
Overview
p. 23
5.3.1.1
Assumptions
p. 23
5.3.1.2
Requirements
p. 23
5.3.1.2.0
Introduction
p. 23
5.3.1.2.1
Supported access networks
p. 23
5.3.1.2.2
Media processing
p. 24
5.3.1.2.3
QoS
p. 24
5.3.1.2.4
User identity and authentication
p. 24
5.3.1.2.5
Service architecture
p. 24
5.3.1.2.6
Subscriber data management
p. 24
5.3.1.3
Signalling architecture
p. 24
5.3.1.4
Functional entities
p. 25
5.3.1.4.1
WIC (WebRTC IMS Client)
p. 25
5.3.1.4.2
WWSF (WebRTC Web Server Function)
p. 25
5.3.1.4.3
WAAF (WebRTC Access Aggregator Function)
p. 26
5.3.1.4.4
P-CSCF
p. 26
5.3.1.4.5
AGW (Access GateWay)
p. 26
5.3.1.5
Reference points
p. 27
5.3.1.5.1
W1a (UE to WAAF)
p. 27
5.3.1.5.2
W1b (UE to WWSF)
p. 27
5.3.1.5.3
W2 (WWSF to WAAF)
p. 27
5.3.1.5.4
Gm (WAAF to P-CSCF)
p. 27
5.3.1.5.5
Iq+ (P-CSCF to AGW)
p. 27
5.3.1.5.6
W3 (UE to AGW)
p. 27
5.3.1.6
Media plane protocol architecture
p. 27
5.3.1.6.0
General
p. 27
5.3.1.6.1
Protocol architecture for MSRP
p. 28
5.3.1.6.2
Protocol architecture for BFCP
p. 28
5.3.1.6.3
Protocol architecture for T.140
p. 28
5.3.1.6.4
Protocol architecture for Voice and Video
p. 29
5.3.2
Description of the solution - Procedures
p. 29
5.3.2.1
Registration
p. 29
5.3.2.1.1
Introduction
p. 29
5.3.2.1.2
WIC registration of individual IMPU with IMS using IMS digest
p. 30
5.3.2.1.3
WIC registration of individual IMPU with IMS based on web authentication
p. 30
5.3.2.1.4
WAAF registration of wildcard IMPU with IMS on behalf of WWSF
p. 31
5.3.2.1.5
WIC registration of individual IMPU from wildcard IMPU range
p. 32
5.3.2.2
Origination and termination
p. 33
5.3.3
Impact on existing entities and interfaces
p. 33
5.3.4
Solution evaluation
p. 33
5.4
Solution 4
p. 34
5.4.1
Overview
p. 34
5.4.1.1
Reference architecture model
p. 34
5.4.1.2
Reference points
p. 34
5.4.1.3
Functional entities
p. 35
5.4.1.3.1
WebRTC Signalling Function
p. 35
5.4.1.3.2
WebRTC Media Function
p. 35
5.4.1.3.3
WebRTC portal/Unified Auth System
p. 35
5.4.2
Description of the solution - Procedures
p. 35
5.4.3
Impact on existing entities and interfaces
p. 36
5.4.4
Solution evaluation
p. 36
5.5
Solution 5
p. 36
5.5.1
Overview
p. 36
5.5.1.1
Reference architecture model
p. 36
5.5.1.2
Reference points
p. 36
5.5.1.3
Functional entities
p. 37
5.5.1.3.1
WebRTC Signalling Function
p. 37
5.5.1.3.2
WebRTC Media Function
p. 37
5.5.1.3.3
WebRTC Web Server Function
p. 37
5.5.2
Description of the solution - Procedures
p. 38
5.5.2.0
General
p. 38
5.5.2.1
Registration
p. 38
5.5.2.1.1
Introduction
p. 38
5.5.2.1.2
Registration procedures using operator provided credentials
p. 38
5.5.2.1.3
Registration of IMPU range by WWS
p. 41
5.5.3
Impact on existing entities and interfaces
p. 43
5.5.4
Solution evaluation
p. 43
5.6
Solution 6
p. 43
5.6.1
Overview
p. 43
5.6.2
Description of the solution - Procedures
p. 44
5.6.3
Impact on existing entities and interfaces
p. 44
5.6.4
Solution evaluation
p. 44
5.7
Solution 7
p. 44
5.7.1
Overview
p. 44
5.7.1.1
Assumptions
p. 44
5.7.1.2
High level architecture
p. 45
5.7.2
Description of the solution - Procedures
p. 46
5.7.2.0
General
p. 46
5.7.2.1
ICE procedure and candidate list buildup
p. 47
5.7.2.2
WebRTC call flow
p. 48
5.7.2.3
Media Interworking Function - Transcoding free operation
p. 50
5.7.3
Impact on existing entities and interfaces
p. 50
5.7.4
Solution evaluation
p. 50
6
Evaluation
p. 50
7
Conclusions
p. 50
A
WebRTC access to IMS - network-based architecture
p. 51
A.1
Overview
p. 51
A.1.1
Assumptions
p. 51
A.1.2
Signalling architecture
p. 51
A.1.3
Functional entities
p. 52
A.1.3.1
WIC (WebRTC IMS Client)
p. 52
A.1.3.2
WWSF (WebRTC Web Server Function)
p. 52
A.1.3.3
eP-CSCF (P-CSCF enhanced for WebRTC)
p. 53
A.1.3.4
eIMS-AGW (IMS Access GateWay enhanced for WebRTC)
p. 53
A.1.4
Reference points
p. 54
A.1.4.1
W1 (UE to WWSF)
p. 54
A.1.4.2
W2 (UE to eP-CSCF)
p. 54
A.1.4.3
Iq (eP-CSCF to eIMS-AGW)
p. 54
A.1.4.4
W3 (UE to eIMS-AGW)
p. 54
A.1.5
Media plane protocol architecture
p. 54
A.1.5.0
General
p. 54
A.1.5.1
Protocol architecture for MSRP
p. 54
A.1.5.2
Protocol architecture for BFCP
p. 55
A.1.5.3
Protocol architecture for T.140
p. 55
A.1.5.4
Protocol architecture for Voice and Video
p. 55
A.2
Procedures
p. 56
A.2.1
Registration
p. 56
A.2.1.1
Introduction
p. 56
A.2.1.2
WIC registration of individual IMPU with IMS using IMS digest
p. 57
A.2.1.3
WIC registration of individual IMPU with IMS based on web authentication
p. 57
A.2.2
Origination and termination
p. 58
$
Change History
p. 59