mirror of
https://github.com/open5gs/open5gs.git
synced 2026-04-28 03:19:31 +00:00
53a63e1b40
Consider the following situation. ``` 1. SMF->SGW-C->MME: First Update Bearer Request 2. MME->UE: First Modify EPS bearer context request 3. SMF->SGW-C->MME: Second Update Bearer Request 4. MME->UE: Second Modify EPS bearer context request 5. UE->MME: First Modify EPS bearer context accept 6. MME->SGW-C->SMF: First Update Bearer Response 7. UE->MME: Second Modify EPS bearer context accept 8. MME->SGW-C->SMF: Second Update Bearer Response ``` Until now, only one GTP transaction was managed for one bearer. Therefore, if the UE does not send an EPS Modify bearer accept to the MME, and the SMF/SGW-C sends an Update Bearer Request to the MME, The NEW update bearer request overwrites the OLD that was previously managed. So we modified it to manage them simultaneously. However, we don't know if this is the right way to implement it. So if the SMF/SGW-C sends 5 MMEs of Update Bearer Request and the UE sends only 3 MMEs of Modify EPS bearer context accept, we have no way to associate it. Therefore, it's implemented so that we just process them sequentially and 2 of them are just timeout. |
||
|---|---|---|
| .. | ||
| abts-main.c | ||
| bearer-test.c | ||
| cx-test.c | ||
| diameter-cx-path.c | ||
| diameter-rx-path.c | ||
| meson.build | ||
| rx-test.c | ||
| session-test.c | ||
| simple-test.c | ||
| test-fd-path.c | ||
| test-fd-path.h | ||
| video-test.c | ||