Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 29.821  Word version:  17.0.0

Top   Top   Up   Prev   None
1…   4…

 

4  Architectural Requirements and Assumptionsp. 9

5  Key Issuesp. 10

6  Solutionsp. 11

6.1  Solution#1: Restoration for AMFp. 11

6.2  Solution #2: Restoration for AMF and SMF with event exposurep. 13

6.3  Solution #3: Restoration for AMF and SMSF with event exposurep. 14

6.4  Solution #4: Restoration for AMF and SMSF without event exposurep. 15

6.5  Solution#5: <S#5> Propagate the change of the UDR NF status using direct signalling between UDM and NFsp. 16

6.6  Solution#6: <S#6> Propagate the change of the UDR NF status via NRF and UDMp. 18

6.7  Solution#7: Unified solutionp. 21

6.8  Solution#8: Reset-IDsp. 25

6.9  Solution#9: Unified solution with Reset-ID or SUPI rangesp. 26

6.10  Solution#10: Prevent overwriting of latest UECM Datap. 28

6.11  Solution#11: Handling Nudm_UECM without Authentication Statusp. 29

6.12  Solution#12: Recovery of AUSF Instance holding latest KAUSFp. 30

6.13  Solution#13: Unified solution with Implicit Subscriptionp. 30

6.14  Solution#14: Deferred Nudm_UECM due to lack of authentication statusp. 32

6.15  Solution#15: Notification via existing NRF servicesp. 32

6.16  Solution#16: Notification via UDR consumer and existing NRF servicesp. 33

6.17  Solution#17: Notification via a new NRF servicep. 34

6.18  Solution#18: Notification via a new DataRestoration Network Function (DRNF)p. 35

6.19  Solution#19: Notification via UDM to Default Notification URIsp. 36

6.20  Solution#20: Notification via Reset Control Function (RCF)p. 42

6.21  Solution#21: Notification via Reset Control Function (RCF) without explicit subscription from end-consumer NFp. 44

6.22  Solution#22: DNN/S-NSSAI as new granularityp. 46

7  Evaluationsp. 47

8  Conclusionsp. 53

$  Change historyp. 54


Up   Top