Slicing capablities #642
-
|
Hi, |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 17 replies
-
|
srsRAN provides support for network slicing, see e.g. https://github.com/srsran/srsRAN_Project/blob/main/configs/slicing.yml One thing to pay attention to (at least with Open5GS, not sure with other cores) is that it interprets the SD has an hexadecimal number so, for instance, you have to set At the moment, we don't support RAN slicing. |
Beta Was this translation helpful? Give feedback.
-
|
Yes I did modify that config file and added the changes you mentioned. When it comes to rebuilding I run gNB config file 1 srsue config file, they are relatively identical. I should mention the system without slicing works as expected. |
Beta Was this translation helpful? Give feedback.
-
|
hmm, looks good. |
Beta Was this translation helpful? Give feedback.
-
|
Just to be sure. Did you apply this patch? https://github.com/srsran/srsRAN_4G/pull/1214/files |
Beta Was this translation helpful? Give feedback.
-
|
yes I did apply that patch, just commented out those lines of code. Oh wait, I just thought about it. I would have to then rebuild and make the srsRAN_4G project after modifying the code, correct. |
Beta Was this translation helpful? Give feedback.
-
Thanks so much, It ended up being that silly mistake lol. |
Beta Was this translation helpful? Give feedback.
-
|
Hi everyone! I follow the steps @pgawlowicz mentioned but I have this issue in the open5gs when the gbn tries to connect: Below I show you the configuration I have: I want to have 2 UEs, each of them in one slice. Maybe the problem is because open5gs-5gc.yml is using add_users.py and this script is only configured with one UE? I dont know... (without slicing the network works perfectly, srsrRAN Proyect lastest version). If you could help me!! Thanks!! |
Beta Was this translation helpful? Give feedback.
-
Hi, I am having trouble recalling the specific thread this was discussed within, but @pgawlowicz previously worked through this issue with another grad student in our lab. It occurs because this python script within srsRAN Project's dockerized version of Open5GS contains the slice service type (sst), but is missing the slice differentiator (sd). You need to add a "sd" key to this JSON at the same level as the existing "sst" key, and set it according the value your UE(s) are using. Here is a good bit of reading on the foundational 5G SA core network architecture which provides insight into the error. During 5G SA UE registration, the NSSF, UDM, and AMF network functions work together to validate and register the network slice reported by the UE. What you're looking at in this file is the list of all potential slices that each UE's request is validated against. Piotr can keep me honest, though I'm not sure there's an easy way to pass the slice data into this file from another source. Likely the easiest thing to do is to list all of your unique SD/SST value combinations as literals here, restart Open5GS in your environment (docker compose down/up), and then the registration requests should stop being rejected. slice_data = [
{
"sst": 1,
"default_indicator": True,
"session": [
{
"name": apn,
"type": 3, "pcc_rule": [], "ambr": {"uplink": {"value": 1, "unit": 3}, "downlink": {"value": 1, "unit": 3}},
"qos": {
"index": int(qci),
"arp": {"priority_level": 8, "pre_emption_capability": 1, "pre_emption_vulnerability": 1}
},
"ue": {
"ipv4": ip_alloc
}
},
{
"name": "ims",
"type": 3, "pcc_rule": [], "ambr": {"uplink": {"value": 1, "unit": 3}, "downlink": {"value": 1, "unit": 3}},
"qos": {
"index": 5,
"arp": {"priority_level": 8, "pre_emption_capability": 1, "pre_emption_vulnerability": 1}
}
}
]
}
] |
Beta Was this translation helpful? Give feedback.
-
|
Hi, @rcbarke was right!! The add_users.py needs to be configured to!! Also, @pgawlowicz, I wanted to ask you about being able to see that each user is in a slice. As you shown, you can see that each UE has connected to a different slice using the Wireshark captures in NGAP like: 
I've followed these instructions abou DTL_USER and NAS-5GS (https://docs.srsran.com/projects/project/en/latest/user_manuals/source/outputs.html#e2ap-pcap) to decode and view the messages in wireshark, but in the gnb_ngap.pcap I get is the following:
can you tell me how tomdo it @pgawlowicz? Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @pgawlowicz, thank you for the clear explanation on how to create a slice. I have a few questions: if I want to create a slice, is there a faster way to do it without having to restart Open5GS and srsRAN? If everything is already running, can I create a slice? |
Beta Was this translation helpful? Give feedback.
srsRAN provides support for network slicing, see e.g. https://github.com/srsran/srsRAN_Project/blob/main/configs/slicing.yml
You have to configure the UE to transmit on one slice, configure the core to support slices and also tell the core which slice is UE will be using.
One thing to pay attention to (at least with Open5GS, not sure with other cores) is that it interprets the SD has an hexadecimal number so, for instance, you have to set
SD: 42in the Open5GS configuration andSD: 0x42in the srsRAN configuration.At the moment, we don't support RAN slicing.