Tech-invite  3GPPspecsRELsGlossariesSIP
21222324252627282931323334353637384‑5x

full Table of Contents for  TS 23.501  Word version:   16.3.0

Top   Up   Prev   Next
1…   3…   4…   4.2.4   4.2.5…   4.2.8…   4.2.8.2.2   4.2.8.2.3…   4.2.8.4…   4.2.9…   4.3…   4.3.3   4.3.4   4.3.5   4.4…   4.4.6…   4.4.8   5…   5.3…   5.3.3…   5.4…   5.5…   5.6…   5.6.7…   5.7…   5.8…   5.9…   5.10   5.11…   5.15…   5.16…   5.17…   5.18…   5.19…   5.21…   5.22…   5.27…   5.28…   5.29…   5.30…   5.31…   5.32…   5.33…   5.34…   5.35…   6…   6.3…   7…   7.2…   8…   8.2.4   8.2.5…   8.3…   A…   D…   E…   F   G…   G.3   G.4…   J

 

4.2.5  Data Storage architecturesWord-p. 36
As depicted in Figure 4.2.5-1, the 5G System architecture allows any NF to store and retrieve its unstructured data into/from a UDSF (e.g. UE contexts). The UDSF belongs to the same PLMN where the network function is located. CP NFs may share a UDSF for storing their respective unstructured data or may each have their own UDSF (e.g. a UDSF may be located close to the respective NF).
NOTE 1: Structured data in this specification refers to data for which the structure is defined in 3GPP specifications. Unstructured data refers to data for which the structure is not defined in 3GPP specifications.
Reproduction of 3GPP TS 23.501, Figure 4.2.5-1: Data storage architecture for unstructured data from any NF
Figure 4.2.5-1: Data storage architecture for unstructured data from any NF
As depicted in Figure 4.2.5-2, the 5G System architecture allows the UDM, PCF and NEF to store data in the UDR, including subscription data and policy data by UDM and PCF, structured data for exposure and application data (including Packet Flow Descriptions (PFDs) for application detection, AF request information for multiple UEs) by the NEF. UDR can be deployed in each PLMN and it can serve different functions as follows:
  • UDR accessed by the NEF belongs to the same PLMN where the NEF is located.
  • UDR accessed by the UDM belongs to the same PLMN where the UDM is located if UDM supports a split architecture.
  • UDR accessed by the PCF belongs to the same PLMN where the PCF is located.
NOTE 3: The UDR deployed in each PLMN can store application data for roaming subscribers.
Reproduction of 3GPP TS 23.501, Figure 4.2.5-2: Data storage architecture
Figure 4.2.5-2: Data storage architecture
NOTE 4: There can be multiple UDRs deployed in the network, each of which can accommodate different data sets or subsets, (e.g. subscription data, subscription policy data, data for exposure, application data) and/or serve different sets of NFs. Deployments where a UDR serves a single NF and stores its data, and, thus, can be integrated with this NF, can be possible.
NOTE 5: The internal structure of the UDR in figure 4.2.5-2 is shown for information only.
The Nudr interface is defined for the network functions (i.e. NF Service Consumers), such as UDM, PCF and NEF, to access a particular set of the data stored and to read, update (including add, modify), delete, and subscribe to notification of relevant data changes in the UDR.
Each NF Service Consumer accessing the UDR, via Nudr, shall be able to add, modify, update or delete only the data it is authorised to change. This authorisation shall be performed by the UDR on a per data set and NF service consumer basis and potentially on a per UE, subscription granularity. The following data in the UDR sets exposed via Nudr to the respective NF service consumer and stored shall be standardized:
  • Subscription Data,
  • Policy Data,
  • Structured Data for exposure,
  • Application data: Packet Flow Descriptions (PFDs) for application detection and AF request information for multiple UEs, as defined in clause 5.6.7.
The service based Nudr interface defines the content and format/encoding of the 3GPP defined information elements exposed by the data sets.
In addition, it shall be possible to access operator specific data sets by the NF Service Consumers from the UDR as well as operator specific data for each data set.
NOTE 6: The content and format/encoding of operator specific data and operator specific data sets are not subject to standardization.
NOTE 7: The organization of the different data stored in the UDR is not to be standardized.
4.2.5a  Radio Capabilities Signalling optimisation [R16]Word-p. 37
Figure 4.2.5a-1 depicts the AMF to UCMF reference point and interface. Figure 4.2.5a-2 depicts the related interfaces in AMF and UCMF for the Radio Capabilities Signalling optimisation in the roaming architecture.
Reproduction of 3GPP TS 23.501, Figure 4.2.5a-1: Radio Capability Signalling optimisation architecture
Figure 4.2.5a-1: Radio Capability Signalling optimisation architecture
Reproduction of 3GPP TS 23.501, Figure 4.2.5a-2: Roaming architecture for Radio Capability Signalling optimisation
Figure 4.2.5a-2: Roaming architecture for Radio Capability Signalling optimisation
NOTE: The AF in the VPLMN (i.e. the one having a relationship with the VPLMN NEF) is the one which provisions Manufacturer Assigned UE radio capability IDs in the VPLMN UCMF. RACS is a serving PLMN only feature (it requires no specific support in the roaming agreement with the UE HPLMN to operate).
4.2.6  Service-based interfacesWord-p. 38
The 5G System Architecture contains the following service-based interfaces:
Namf: Service-based interface exhibited by AMF.
Nsmf: Service-based interface exhibited by SMF.
Nnef: Service-based interface exhibited by NEF.
Npcf: Service-based interface exhibited by PCF.
Nudm: Service-based interface exhibited by UDM.
Naf: Service-based interface exhibited by AF.
Nnrf: Service-based interface exhibited by NRF.
Nnssf: Service-based interface exhibited by NSSF.
Nausf: Service-based interface exhibited by AUSF.
Nudr: Service-based interface exhibited by UDR.
Nudsf: Service-based interface exhibited by UDSF.
N5g-eir: Service-based interface exhibited by 5G-EIR.
Nnwdaf: Service-based interface exhibited by NWDAF.
Ni-nef: Service-based interface exhibited by I-NEF.
Nchf: Service-based interface exhibited by CHF.
Nucmf: Service-based interface exhibited by UCMF.
NOTE: The Service-based interface exhibited by CHF is defined in TS 32.240.
4.2.7  Reference pointsWord-p. 39
The 5G System Architecture contains the following reference points:
N1: Reference point between the UE and the AMF.
N2: Reference point between the (R)AN and the AMF.
N3: Reference point between the (R)AN and the UPF.
N4: Reference point between the SMF and the UPF.
N6: Reference point between the UPF and a Data Network.
NOTE 1: The traffic forwarding details of N6 between a UPF acting as an uplink classifier and a local data network are not specified in this Release of the specification.
N9: Reference point between two UPFs.
The following reference points show the interactions that exist between the NF services in the NFs. These reference points are realized by corresponding NF service-based interfaces and by specifying the identified consumer and producer NF service as well as their interaction in order to realize a particular system procedure.
N5: Reference point between the PCF and an AF.
N7: Reference point between the SMF and the PCF.
N8: Reference point between the UDM and the AMF.
N10: Reference point between the UDM and the SMF.
N11: Reference point between the AMF and the SMF.
N12: Reference point between AMF and AUSF.
N13: Reference point between the UDM and Authentication Server function the AUSF.
N14: Reference point between two AMFs.
N15: Reference point between the PCF and the AMF in the case of non-roaming scenario, PCF in the visited network and AMF in the case of roaming scenario.
N16: Reference point between two SMFs, (in roaming case between SMF in the visited network and the SMF in the home network).
N16a: Reference point between SMF and I-SMF.
N17: Reference point between AMF and 5G-EIR.
N18: Reference point between any NF and UDSF.
N19: Reference point between two PSA UPFs for 5G LAN-type service.
N22: Reference point between AMF and NSSF.
N23: Reference point between PCF and NWDAF.
N24: Reference point between the PCF in the visited network and the PCF in the home network.
N27: Reference point between NRF in the visited network and the NRF in the home network.
N28: Reference point between PCF and CHF.
N29: Reference point between NEF and SMF.
N29i: Reference point between I-NEF and SMF in the VPLMN.
N30: Reference point between PCF and NEF.
NOTE 2: The functionality of N28 and N29 and N30 reference points are defined in TS 23.503.
N31: Reference point between the NSSF in the visited network and the NSSF in the home network.
NOTE 3: in some cases, a couple of NFs may need to be associated with each other to serve a UE.
In addition to the reference points above, there are interfaces/reference point(s) between SMF and the CHF. The reference point(s) are not depicted in the architecture illustrations in this specification.
NOTE 4: The functionality of these interface/reference points are defined in TS 32.240. N32: Reference point between SEPP in the visited network and the SEPP in the home network.
NOTE 5: The functionality of N32 reference point is defined in TS 33.501.
N33: Reference point between NEF and AF.
N34: Reference point between NSSF and NWDAF.
N35: Reference point between UDM and UDR.
N36: Reference point between PCF and UDR.
N37: Reference point between NEF and UDR.
N38: Reference point between I-SMFs.
N40: Reference point between SMF and the CHF.
NOTE 6: The reference points from N40 up to and including N49 are reserved for allocation and definition in TS 23.503.
N50: Reference point between AMF and the CBCF.
N51: Reference point between AMF and NEF.
N51i: Reference point between I-NEF and the AMF in the VPLMN.
N52: Reference point between NEF and UDM.
N53: Reference point between the I-NEF and the NEF.
N55: Reference point between AMF and the UCMF.
N56: Reference point between NEF and the UCMF.
N57: Reference point between AF and the UCMF.
NOTE 7: The Public Warning System functionality of N50 reference point is defined in TS 23.041.
The reference points to support SMS over NAS are listed in clause 4.4.2.2.
The reference points to support Location Services are listed in TS 23.273.
The reference points to support SBA in IMS (N5, N70 and N71) are described in TS 23.228.

Up   Top   ToC