Skip to content
TechSpec
  • Foreword
  • Introduction
  • 1 Scope
  • 2 References
  • 3 Definitions, symbols and abbreviations
  • 4 User Data Convergence architecture
  • 5 User Data convergence information flows
  • A.0 Introduction
  • A.1 Information flows with Query data procedure over Ud
  • A.2 Information flows with Updating data procedure over Ud
  • A.3 Example Information flows for subscriptions to notifications
  • A.4 Information flows with notification procedure over Ud
  • B.1 Introduction
  • B.2 Basic Prerequisite
  • B.3 Step 1 – Separating User Data from Application Logic
  • B.4 Step 2 – Introducing Provisioning FEs
  • B.5 Step 3 - Storing outsourced user data in a logically single UDR
  • B.6 Step 4 –Full Load Sharing and Failover functionality
  • B.7 Step 5 – Converging user data in the UDR
  • B.8 Example analysis for HLR
  • B.9 Example analysis for S-CSCF
  • B.10 Example analysis for PCRF and SPR
  • B.11 Summary

B.3 Step 1 – Separating User Data from Application Logic

23.3353GPPRelease 17Stage 2Technical realization and information flowsTSUser Data Convergence (UDC)

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

In principle, any network node (in non-UDC networks) that stores user data while no session is ongoing and that performs application logic is a candidate for separation of user data and application logic:

Figure B.3.1/1: Separating User Data from Application Logic

However, separating user data from application logic without any additional steps does not provide much benefit (if any).