How it Works
This section provides a brief of how the IP Pool Allocation per DNN feature works.
-
The DNN profile lookup is based on the subscriber policy or DNN policy. The DNN profiles are associated in the SMF profile configuration. The subscriber policy takes precedence over the DNN policy when both the configurations are present.
-
The subscriber policy contains a list of precedence values. The selection of the precedence is based on the SUPI, GPSI, serving PLMN, and NSSAI value of the subscriber.
-
Each precedence has an associated operator policy. The DNN policy is picked from the selected operator policy.
-
The DNN policy can have a DNN profile configuration for each of the UE-requested DNN.
-
The DNN profile contains the virtual or mapped DNN with its list of interfaces. This is an existing configuration and Redundancy Manager is also in the list of interfaces. For more information, see the “Configuring a Virtual DNN under a DNN Profile” section.
-
The new configuration under the DNN profile contains the mapping of the UE-requested DNN to IP Pool DNN.
-
The DNN profile selection occurs in the following order:
-
Based on subscriber policy, the order of selection is as follows: smf-profile > smf-service > subscriber-policy > precedence > operator-policy > dnn-policy > dnn-profile (based on UE-requested DNN) > Virtual DNN mapping.
-
Based on the DNN policy, the order of selection is as follows: smf-profile > dnn-policy > dnn-profile (based on UE requested Dnn) > Virtual DNN mapping.
-
Note |
|