для Cisco Cisco Packet Data Gateway (PDG)
S-GW Changes in Release 17
▀ S-GW Enhancements for 17.4
▄ Release Change Reference, StarOS Release 17
568
CSCuu37427, CSCut14324 - Assertion failure
egtpc_handle_create_sess_req_msg_at_sgw_ingress
Feature Changes
Parallel Create Session Requests Processed Correctly
The fix implemented for CSCuu37427 and CSCut14324 has resulted in a behavior change.
Previous Behavior: When two parallel Create Session Requests (CSReqs) with different EBI and 0 TEID were
received from the S4-SGSN, the second CSReq was rejected from the S-GW with the cause “No Resource Available.”
received from the S4-SGSN, the second CSReq was rejected from the S-GW with the cause “No Resource Available.”
New Behavior: When two parallel CSReqs with different EBI and 0 TEID are received from the S4-SGSN, both of the
CSReqs are processed and the PDNs are created successfully at the S-GW.
CSReqs are processed and the PDNs are created successfully at the S-GW.
1. Operators will see that both the PDNs are created successfully after the fix if the two CSReqs are received from
the S4-SGSN with 0 TEID and different EBI.
2. If two parallel CSReqs are received from the MME, then the old behavior of rejecting the second CSReq with
the cause “No Resource Available” is applicable.
3. If one CSReq is received from the MME and the other from the S4-SGSN, or vice-versa, with the same or
different EBI, then context replacement is triggered and the second CSReq results in the replacement of the
existing PDN with a new PDN.
existing PDN with a new PDN.