Tech-
invite
3GPP
space
IETF
RFCs
SIP
Quick
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 29.821
Word version: 17.0.0
1…
4…
4
Architectural Requirements and Assumptions
5
Key Issues
6
Solutions
7
Evaluations
8
Conclusions
$
Change history
4
Architectural Requirements and Assumptions
Word‑p. 9
4.1
Architectural Requirements
Word‑p. 9
4.2
Architectural Assumptions
Word‑p. 9
5
Key Issues
Word‑p. 10
5.1
Key Issue #1: Restoration of profile with AMF, SMF, SMSF and AUSF
Word‑p. 10
5.2
Key Issue #2: Restoration of profile with PCF
Word‑p. 10
5.3
Key Issue #3: Restoration of profile with NEF
Word‑p. 10
5.4
Key Issue #4: Granularity of Data
Word‑p. 11
5.5
Key Issue #5: Handling Nudm_UECM without Authentication Status
Word‑p. 11
5.6
Key Issue #6: Notification Path
Word‑p. 11
6
Solutions
Word‑p. 11
6.1
Solution#1: Restoration for AMF
Word‑p. 11
6.1.1
Description
Word‑p. 11
6.1.2
Procedures
Word‑p. 12
6.1.3
Impacts on services, entities and interfaces
Word‑p. 13
6.2
Solution #2: Restoration for AMF and SMF with event exposure
Word‑p. 13
6.2.1
Description
Word‑p. 13
6.2.2
Procedures
Word‑p. 13
6.2.3
Impacts on services, entities and interfaces
Word‑p. 14
6.3
Solution #3: Restoration for AMF and SMSF with event exposure
Word‑p. 14
6.3.1
Description
Word‑p. 14
6.3.2
Procedures
Word‑p. 14
6.3.3
Impacts on services, entities and interfaces
Word‑p. 15
6.4
Solution #4: Restoration for AMF and SMSF without event exposure
Word‑p. 15
6.4.1
Description
Word‑p. 15
6.4.2
Procedures
Word‑p. 15
6.4.3
Impacts on services, entities and interfaces
Word‑p. 16
6.5
Solution#5: <S#5> Propagate the change of the UDR NF status using direct signalling between UDM and NFs
Word‑p. 16
6.5.1
Introduction
Word‑p. 16
6.5.2
Functional Description
Word‑p. 16
6.5.3
Procedures
Word‑p. 17
6.5.4
Impacts on services, entities and interfaces
Word‑p. 18
6.6
Solution#6: <S#6> Propagate the change of the UDR NF status via NRF and UDM
Word‑p. 18
6.6.1
Introduction
Word‑p. 18
6.6.2
Functional Description
Word‑p. 19
6.6.3
Procedures
Word‑p. 20
6.6.4
Impacts on services, entities and interfaces
Word‑p. 21
6.7
Solution#7: Unified solution
Word‑p. 21
6.7.1
Introduction
Word‑p. 21
6.7.2
Functional Description
Word‑p. 22
6.7.3
Procedures
Word‑p. 24
6.7.4
Impacts on services, entities and interfaces
Word‑p. 25
6.8
Solution#8: Reset-IDs
Word‑p. 25
6.8.1
Description
Word‑p. 25
6.8.2
Procedures
Word‑p. 26
6.8.3
Impacts on services, entities and interfaces
Word‑p. 26
6.9
Solution#9: Unified solution with Reset-ID or SUPI ranges
Word‑p. 26
6.9.1
Introduction
Word‑p. 26
6.9.2
Functional Description
Word‑p. 26
6.9.3
Procedures
Word‑p. 27
6.9.4
Impacts on services, entities and interfaces
Word‑p. 28
6.10
Solution#10: Prevent overwriting of latest UECM Data
Word‑p. 28
6.10.1
Description
Word‑p. 28
6.10.2
Procedures
Word‑p. 28
6.10.3
Impacts on services, entities and interfaces
Word‑p. 29
6.11
Solution#11: Handling Nudm_UECM without Authentication Status
Word‑p. 29
6.11.1
Description
Word‑p. 29
6.11.2
Procedures
Word‑p. 29
6.11.3
Impacts on services, entities and interfaces
Word‑p. 29
6.12
Solution#12: Recovery of AUSF Instance holding latest KAUSF
Word‑p. 30
6.12.1
Description
Word‑p. 30
6.12.2
Procedures
Word‑p. 30
6.12.3
Impacts on services, entities and interfaces
Word‑p. 30
6.13
Solution#13: Unified solution with Implicit Subscription
Word‑p. 30
6.13.1
Introduction
Word‑p. 30
6.13.2
Functional Description
Word‑p. 31
6.13.3
Procedures
Word‑p. 31
6.13.4
Impacts on services, entities and interfaces
Word‑p. 32
6.14
Solution#14: Deferred Nudm_UECM due to lack of authentication status
Word‑p. 32
6.14.1
Description
Word‑p. 32
6.14.2
Procedures
Word‑p. 32
6.14.3
Impacts on services, entities and interfaces
Word‑p. 32
6.15
Solution#15: Notification via existing NRF services
Word‑p. 32
6.15.1
Introduction
Word‑p. 32
6.15.2
Functional Description
Word‑p. 32
6.15.3
Procedures
Word‑p. 33
6.16
Solution#16: Notification via UDR consumer and existing NRF services
Word‑p. 33
6.16.1
Introduction
Word‑p. 33
6.16.2
Functional Description
Word‑p. 33
6.16.3
Procedures
Word‑p. 34
6.17
Solution#17: Notification via a new NRF service
Word‑p. 34
6.17.1
Introduction
Word‑p. 34
6.17.2
Functional Description
Word‑p. 34
6.17.3
Procedures
Word‑p. 35
6.18
Solution#18: Notification via a new DataRestoration Network Function (DRNF)
Word‑p. 35
6.18.1
Introduction
Word‑p. 35
6.18.2
Functional Description
Word‑p. 35
6.18.3
Procedures
Word‑p. 36
6.19
Solution#19: Notification via UDM to Default Notification URIs
Word‑p. 36
6.19.1
Introduction
Word‑p. 36
6.19.2
Functional Description
Word‑p. 36
6.19.3
Procedures
Word‑p. 37
6.19.4
Impacts on services, entities and interfaces
Word‑p. 41
6.20
Solution#20: Notification via Reset Control Function (RCF)
Word‑p. 42
6.20.1
Introduction
Word‑p. 42
6.20.2
Functional Description
Word‑p. 42
6.20.3
Procedures
Word‑p. 43
6.20.4
Impacts on services, entities and interfaces
Word‑p. 44
6.21
Solution#21: Notification via Reset Control Function (RCF) without explicit subscription from end-consumer NF
Word‑p. 44
6.21.1
Introduction
Word‑p. 44
6.21.2
Functional Description
Word‑p. 44
6.21.3
Procedures
Word‑p. 45
6.21.4
Impacts on services, entities and interfaces
Word‑p. 46
6.22
Solution#22: DNN/S-NSSAI as new granularity
Word‑p. 46
6.22.1
Introduction
Word‑p. 46
6.22.2
Functional Description
Word‑p. 47
6.22.3
Impacts on services, entities and interfaces
Word‑p. 47
7
Evaluations
Word‑p. 47
7.1
Evaluation of Solutions for Key Issues#1, 2, 3, 4, 5, 6
Word‑p. 47
7.1.1
Overview of the evaluation
Word‑p. 47
7.1.2
Preparation of profile in NF
Word‑p. 50
7.1.3
Notification path from UDR to NF (Evaluation of Solutions for Key Issue#6)
Word‑p. 50
7.1.4
Notification content
Word‑p. 51
7.1.5
Synchronization trigger
Word‑p. 52
7.1.6
Synchronization procedure
Word‑p. 52
7.1.7
Other
Word‑p. 52
8
Conclusions
Word‑p. 53
8.1
Conclusion of Solutions for Key Issues#1, 2, 3, 4, 5
Word‑p. 53
$
Change history
Word‑p. 54