для Cisco Cisco Packet Data Gateway (PDG)
ECS Changes in Release 16
ECS Enhancements for 16.0 ▀
Release Change Reference, StarOS Release 16 ▄
117
Previous Behavior: In Release 14.0, the “
no policy-control update-default-bearer
” command was used to
suppress all Update Bearer Requests (UBRs) including those that contain changes to TFT, QCI, ARP, and APN-AMBR.
In Release 15.0, the “
In Release 15.0, the “
no tft-notify-ue-def-bearer
” command was used to enable the gateway to suppress the
UBR received when the TFT is changed on a bearer.
New Behavior: With this release, the Update Bearer Requests will not be sent to the UE for any changes in QCI, ARP,
or APN-AMBR irrespective of whether or not these commands are configured.
or APN-AMBR irrespective of whether or not these commands are configured.
CSCug71725, CSCuh65672 - ECS Normal Path Performance Improvements
Applicable Products: GGSN, P-GW
Feature Changes
ECS Performance Improvements
To improve data-path performance and reduce CPU utilization for control-path functions, lean paths are introduced in
this release. Lean path offers fast and light-weight processing for most common class of traffic. Lean path is introduced
at various stages of packet processing in ECS. For each stage of packet processing, a lean path is identified, which
captures most typical use case (processing path) in that stage. Logic and code of that stage is optimized for such a lean
path. Non-typical processing paths are treated as exceptions, and processed in non-lean path – referred to as normal-
path. Lean paths at each packet processing stage are identified and implemented independent of other stages. As a data
packet moves through packet processing path, it may take lean-path or normal-path at each stage as appropriate.
this release. Lean path offers fast and light-weight processing for most common class of traffic. Lean path is introduced
at various stages of packet processing in ECS. For each stage of packet processing, a lean path is identified, which
captures most typical use case (processing path) in that stage. Logic and code of that stage is optimized for such a lean
path. Non-typical processing paths are treated as exceptions, and processed in non-lean path – referred to as normal-
path. Lean paths at each packet processing stage are identified and implemented independent of other stages. As a data
packet moves through packet processing path, it may take lean-path or normal-path at each stage as appropriate.
Important:
The criteria for taking lean-path are totally driven by internal design and concerns about
traffic being processed in either path should be ignored. All the existing functionality in the data path
continues to be supported.
continues to be supported.
Lean-paths have been implemented in the following packet processing stages:
Shallow Packet Inspection – IP, TCP inspection
HTTP Protocol Analyzer
Packet Actions
CDR Generation
CSCug86838, CSCub86414, CSCui19930, CSCui19941, CSCug86780,
CSCug87258, CSCug87234 - [ICSR-Volte] Removing usage of pacing queue for
critical MC-ECS new frmk
Applicable Products: GGSN, P-GW
Feature Changes
ICSR Enhancements for VoLTE