Tech-invite3GPP-SpecsReleasesFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

Top   in Index   Prev   Next

TR 23.732SA2
Study on
User Data Interworking,
Coexistence and Migration

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V16.0.0 (Wzip)  2019/03  75 p.

Rapporteur:  Miss Sabater, Susana

The objective of this Technical Report is to investigate scenarios for co-existence of subscription data pertaining to legacy system (EPS) with data pertaining to the 5G system, when the HSS+UDM defined in Rel-15 is separated and both UDM and HSS are independent, and will propose solutions to support this deployment where necessary.
  • study diverse scenarios related to the storage of subscription data including, but not limited to, those of common repository for subscription data from EPS and 5GS, as well as separate repositories for EPS and 5GS subscription data,
  • investigate the relevant procedures in TS 23.502 (for e.g. authentication, mobility, handover and procedures for IMS and SMS handling in interworking between 5G system and EPS),
  • determine if there is a need for interaction between the consumers of EPS and 5GS data, in the different interworking cases and deployment scenarios.
NOTE: The subscription data referred to by this Technical Report comprises both static as well as dynamic data, including IMS, LCS, SMS data.

Existing procedures in TS 23.502 shall not be impacted.
Provisioning aspects are outside this study.
Direct interactions between the EPS UDR and the 5GS UDR are out of the scope of this TR (i.e. it is assumed that there is no direct interaction between these two repositories).

full Table of Contents for  TR 23.732  Word version:   16.0.0

Here   Top


1  ScopeWord-p. 7
2  References
3  Definitions and abbreviationsWord-p. 8
4  Architectural Assumptions and Principles
5  Key Issues
6  Solutions
6.1  Solution #1: Retrieving subscription data from separate UDR repositories for EPS and 5GS subscription data using a UDR Translation Function (UTF)
6.2  Solution #2: Direct SBA UDM-HSS Interworking
6.3  Solution #3: UDM/HSS FE interaction reusing legacy protocol
6.4  Solution #4: Use of a Data Access Layer for interaction between HSS FE and UDM with common repository
6.5  Solution #5: Use of a Data Access Layer for interaction between HSS FE and UDM with separate repositoriesWord-p. 55
6.6  Solution #6: Deployment and coexistence without interworking between UDM and existing HSSWord-p. 66
7  Evaluation
8  Conclusions
A  Change historyWord-p. 75

Up   Top