TS 23.335
CT4
★
User Data Convergence (UDC)
use "3GPP‑Page" to get the Word version
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
V15.0.0 (PDF)
2018/06 42 p.
V14.0.0
2017/03 43 p.
V13.1.0
2016/03 43 p.
V12.0.0
2014/09 42 p.
V11.0.0
2012/09 42 p.
V10.0.0
2011/04 42 p.
V9.3.0
2010/12 41 p.
WI Acronym: UDC-CN
Rapporteur: Ms. Bartolome, Maria-Cruz Nanjing Ericsson Panda Com Ltd
Rapporteur: Ms. Bartolome, Maria-Cruz Nanjing Ericsson Panda Com Ltd
The UDC concept supports a layered architecture, separating the data from the application logic in the 3GPP system, so that user data is stored in a logically unique repository allowing access from core and service layer entities, named Application Front Ends.
full Table of Contents for TS 23.335 Word version: 15.0.0
1 Scope Word-p. 5
2 References
3 Definitions, symbols and abbreviations Word-p. 6
4 User Data Convergence architecture
4.1 UDC System architecture
4.2 Functional Entities Word-p. 9
5 User Data convergence information flows
4.2.1 Application Front Ends
4.2.2 Provisioning Front Ends 
4.2.3 User Data Repository Word-p. 10
4.2.4 Other Network Elements
4.3 Reference point Ud Word-p. 11
4.4 Front-End Session
4.5 UDR Session Word-p. 12
4.2.3 User Data Repository Word-p. 10
4.2.4 Other Network Elements
5.1 General
5.2 Requirements Word-p. 14
5.3 Querying data from the UDR Word-p. 15
5.4 Creating data within the UDR Word-p. 16
5.5 Deleting data from the UDR Word-p. 17
5.6 Updating data within the UDR Word-p. 18
5.7 Subscription to Notifications Word-p. 19
5.8 Notification of data modification Word-p. 20
A Information flows
A.0 Introduction
A.1 Information flows with Query data procedure over Ud
B Applicability of the UDC concept to network nodes Word-p. 34
A.1.1 General
A.1.2 CS terminating call information flow example
A.1.3 IMS re-registration information flow example Word-p. 23
A.2 Information flows with Updating data procedure over Ud Word-p. 24
A.1.2 CS terminating call information flow example
A.1.3 IMS re-registration information flow example Word-p. 23
A.2.1 General
A.2.2 CS location update information flow example Word-p. 25
A.2.3 IMS service data change information flow example Word-p. 26
A.3 Example Information flows for subscriptions to notifications Word-p. 27
A.4 Information flows with notification procedure over Ud Word-p. 28
A.4.1 General
A.4.2 IMS user capability change with notification information flow example Word-p. 29
A.4.3 Application Server Notification information flow example without Ud-Notify Word-p. 30
A.4.4 Application Server Notification information flow example with Ud-Notify Word-p. 31
A.4.5 Application Server Notification information flow example without Ud-Notify - Subscription expired Word-p. 32
A.4.6 Application Server Notification information flow example with Ud-Notify - Subscription expired Word-p. 33
B.1 Introduction
B.2 Basic Prerequisite
B.3 Step 1 - Separating User Data from Application Logic
B.4 Step 2 - Introducing Provisioning FEs Word-p. 35
B.5 Step 3 - Storing outsourced user data in a logically single UDR
B.6 Step 4 -Full Load Sharing and Failover functionality Word-p. 36
B.7 Step 5 - Converging user data in the UDR Word-p. 37
B.8 Example analysis for HLR
B.9 Example analysis for S-CSCF
B.10 Example analysis for PCRF and SPR Word-p. 38
B.11 Summary
C Change history Word-p. 39
B.4 Step 2 - Introducing Provisioning FEs Word-p. 35
B.5 Step 3 - Storing outsourced user data in a logically single UDR
B.6 Step 4 -Full Load Sharing and Failover functionality Word-p. 36
B.7 Step 5 - Converging user data in the UDR Word-p. 37
B.8 Example analysis for HLR
B.9 Example analysis for S-CSCF
B.10 Example analysis for PCRF and SPR Word-p. 38
B.11 Summary
