Closed mariakagi closed 3 years ago
Hi @mariakagi
I think it's very useful.
For example, is it possible to select UPF by adding the Cell_ID of gNB to the PFCP parameter instead of locality
?
Best regards,
--Shigeru
Thank you @s5uishida.
At first, I considered the way to use "targetID" element in the CreateSMContext Request from AMF for SMF to know which gNB the UE connecting to.
For UPF selection in SMF using "targetID", change smfcfg.yaml:
userplane_information:
up_nodes:
gNB1:
type: AN
node_id: 000102
...
links:
- A: gNB1
B: UPF1
...
In the above figure if gNB3 is added to Area1, node_id and links should be updated in the idea of using "targetID". But using "locality" no need to update configuration.
The idea of using "the Cell_ID of gNB" looks like using "targetID", so I think using "locality" is better.
@mariakagi
Thanks for the PR!
Hi @mariakagi
I also thought that smfcfg.yaml
needed to be modified to support Cell_ID.
At this time, I made a suggestion with reference to the following Open5GS smf.yaml
.
https://github.com/open5gs/open5gs/blob/main/configs/open5gs/smf.yaml.in
# <SMF Selection - 5G Core only>
...
# o UPF selection by CellID(e_cell_id: 28bit, nr_cell_id: 36bit)
# (either single enb_id or multiple enb_ids, HEX representation)
...
I think locality
is also very useful.
Best regards,
--Shigeru
Issue Description
What's the version are you using
v3.0.5
Is your feature request related to a problem? Please describe.
SMF selects UPF by DNN and S-NSSAI, without considering the location of gNB.
IF UE connects to gNB in Area1, SMF should select UPF in Area1.
Describe the solution you'd like
Preparation
Execution
Pull Request
Pull Request for the feature.
Describe alternatives/workarounds you've considered
None
Additional context
None