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 33.838
Word version: 11.0.0
1…
4…
4
Definition of PUCI scope
5
Design principles and security requirements
6
Preventive measures
7
Interworking with non-IMS systems
8
PUCI architectural considerations
9
Solution alternatives
10
PUCI information exchange
11
Conclusions and recommendations
$
Change history
4
Definition of PUCI scope
p. 7
4.1
Communication modes
p. 7
4.2
Bulk communications vs targeted communications
p. 7
5
Design principles and security requirements
p. 8
5.1
Design principles
p. 8
5.2
Security requirements
p. 8
6
Preventive measures
p. 9
6.1
Introduction
p. 9
6.2
Non-technical prevention measures
p. 9
6.2.1
General
p. 9
6.2.2
Legislation
p. 9
6.2.3
Contractual agreements between operators and their customers
p. 9
6.2.4
Contractual agreements between different operators (SLAs)
p. 10
6.3
Technical prevention measures
p. 10
7
Interworking with non-IMS systems
p. 11
7.1
Background
p. 11
7.1.1
IETF Work on SIP Peering
p. 11
7.1.2
Operator SPIT/UC interworking and source identification
p. 11
7.1.2.1
Introduction
p. 11
7.1.2.2
Interworking between mutually trusting VoIP operators
p. 12
8
PUCI architectural considerations
p. 14
8.1
Overview
p. 14
8.2
PUCI information storage
p. 14
8.3
PUCI function invocation
p. 14
8.4
Compatibility with IMS centralized services, SRVCC, and service continuity
p. 15
8.4.1
General
p. 15
8.4.2
Mechanisms based on supplementary services
p. 15
8.4.3
IMR
p. 15
9
Solution alternatives
p. 15
9.1
High level architecture
p. 15
10
PUCI information exchange
p. 16
10.1
PUCI information type and structure
p. 16
10.2
PUCI information signalling
p. 17
10.3
PUCI function communication
p. 19
10.4
PUCI user notification
p. 20
11
Conclusions and recommendations
p. 20
$
Change history
p. 21