Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TR 29.831
Study on NRF API enhancements to avoid Signalling and Storing of Redundant Data

3GPP‑Page  
V18.0.0 (Wzip)  2023/09  40 p.
Rapporteur:
Mr. Wiehe, Ulrich
Nokia Shanghai Bell

full Table of Contents for  TR 29.831  Word version:  18.0.0

Here   Top

 

1  Scopep. 6

The present document identifies deficiencies of the NRF APIs as specified in TS 29.510 and studies potential optimization solutions. The document will focus on the following aspects:
  • avoid data storage overhead in the NRF due to many NFs (especially NFs from the same NF set) registering with identical information,
  • avoid signalling overhead (both in terms of payload size and number of HTTP requests) due to discovery responses containing lots of duplicate information and due to the number of data change notification sent when duplicated data are changed one by one.
  • avoid processing overhead (both at NRF and its consumers) resulting e.g. from signalling overhead.
Up

2  Referencesp. 6

3  Definitions of terms, symbols and abbreviationsp. 6

3.1  Termsp. 6

3.2  Symbolsp. 7

3.3  Abbreviationsp. 7

4  Baselinep. 7

5  Key Issuesp. 8

6  Solutionsp. 9

6.1  Solution#1: Avoid Duplicate Configuration and Transmission of Shareable Datap. 9

6.2  Solution#2: Support of NF (Service) Set Profilesp. 11

6.3  Solution #3: Download Large Volume Data from NRFp. 20

6.4  Solution #4: Enhancement of inter NRF interaction to optimize shareable data transmissionp. 21

6.5  Solution #5: Optimization of shareable data transmission for NF set level shared datap. 23

6.6  Solution #6: NRF Policy Control on Information Exposure for different PLMNsp. 24

6.7  Solution#7: List of Shareable Profile Itemsp. 26

6.8  Solution #8: Single Subscription of NF Profile Change from an NF Setp. 27

6.9  Solution #9: Single NF Profile Change Notification to an NF Setp. 28

6.10  Solution #10: Simplifying the NF service discovery response of inter-PLMNp. 29

6.11  Solution 11: Avoid large configuration of UE Routing Indicatorp. 31

6.12  Solution #12: Support for NF Set level shared datap. 32

7  Evaluationsp. 34

8  Conclusionsp. 39

$  Change historyp. 40


Up   Top