forked from acouzens/open5gs
0f5d968149
When UE would send a request to release PDU session, AMF would eventually send "PDU Session Resource Release Command" downlink to both UE (N1) and gNB (N2). Each UE and gNB would then reply with "PDU Session Resource Release Response" indicating they released their own resources. Usually the first one to respond would be gNB. SMF made an assumption that this would always be the case. And it would wait for signal that UE resources were freed, before releasing session resources. But occasionally the situation is that UE responds first, and SMF releases resources prematurely. This situation does not normally occur. But under high stress (100's of UE PDU releases at the same time) this happens occasionally. According to the standard, this situation is perfectly normal. 3GPP TS 23.502 Rel. 16 4.3.4.2 UE or network requested PDU Session Release for Non-Roaming and Roaming with Local Breakout ... Steps 8-10 may happen before steps 6-7. ... |
||
|---|---|---|
| .. | ||
| amf | ||
| ausf | ||
| bsf | ||
| hss | ||
| mme | ||
| nrf | ||
| nssf | ||
| pcf | ||
| pcrf | ||
| scp | ||
| sgwc | ||
| sgwu | ||
| smf | ||
| udm | ||
| udr | ||
| upf | ||
| main.c | ||
| meson.build | ||