Actions
Bug #4892
closedgbproxy2: Route BSSGP-STATUS based on "Erroneous PDU IE"
Start date:
12/08/2020
Due date:
% Done:
100%
Spec Reference:
Description
NS-STATUS can only be routed as follows:
- PTP downlink: Simply route by NS-BVCI
- PTP uplink: route based on "Erroneous PDU IE"
- SIG downlink + uplink:
- don't route (but locally terminate) if optional BVCI IE, as that one only occurs for BVCI blocked / BVCI unknown whihc is a gbproxy problem, not one with a remote peer
- route messages without BVCI IE but with "PDU in error" IE based on the latter
- the contained BSSGP PDU might be truncated, and hence our TLV parser might not be playing well along
- we should look for TLLI + TMSI (and route based on NRI)
- if we cannot find any routing informatoin, we treat it like NULL NRI?
- fast path for single-SGSN case: simply route to "the" SGSN?
Related issues
Actions