Cisco Cisco Packet Data Gateway (PDG)
ECS Changes in Release 16
▀ ECS Enhancements for 16.0
▄ Release Change Reference, StarOS Release 16
120
Feature Changes
ECS Cookie Match support for Websockets
Websocket protocol is an independent TCP based protocol. A connection is identified as websocket through the first
HTTP Get Request header after the three way handshake. This packet includes an upgrade header (Upgrade: websocket)
and other websocket headers (Sec-Websocket-*) to upgrade HTTP to websocket protocol. This helps operators to
categorize websocket traffic and apply different policies for such traffic. This could also help to zero-rate websocket
connection.
HTTP Get Request header after the three way handshake. This packet includes an upgrade header (Upgrade: websocket)
and other websocket headers (Sec-Websocket-*) to upgrade HTTP to websocket protocol. This helps operators to
categorize websocket traffic and apply different policies for such traffic. This could also help to zero-rate websocket
connection.
A new CLI “
websocket flow-detection
” has been implemented at rulebase level to detect the websocket protocol.
The websocket protocol identification can be enabled or disabled with the new CLI websocket protocol. If the
websocket detection is enabled in the rulebase, the ECS parser ensures that in the HTTP Get header fields Host,
Upgrade, Connection, Sec-Websocket-Key, Origin and Sec-Websocket-Version should be present to upgrade HTTP to
websocket protocol. A ruledef can be defined to identify the HTTP GET request for the websocket and rate it in a
certain way. The subsequent data that is transferred through the websocket is also billed the same way as the first
packet.
websocket detection is enabled in the rulebase, the ECS parser ensures that in the HTTP Get header fields Host,
Upgrade, Connection, Sec-Websocket-Key, Origin and Sec-Websocket-Version should be present to upgrade HTTP to
websocket protocol. A ruledef can be defined to identify the HTTP GET request for the websocket and rate it in a
certain way. The subsequent data that is transferred through the websocket is also billed the same way as the first
packet.
Previous Behavior: Websocket protocol was not detected.
New Behavior: A new CLI “
websocket flow-detection http
” is added at rulebase level. This CLI can detect
the websocket protocol, which helps in identifying the initial TCP connection for the websocket and rate it in certain
way.
way.
Customer Impact: Websocket protocol can be enabled or disabled with the new “
websocket flow-detection
http
” CLI.
Command Changes
websocket flow-detection
A new command
websocket flow-detection
has been added to enable/disable websocket flow detection.
To enable websocket flow detection feature, use the following configuration:
configure
active-charging service <ecs_service_name>
rulebase<rulebase name>
websocket flow-detection <protocol>
end
Notes:
Use the
no websocket flow-detection
command or
default websocket flow-detection
command to
disable retransmission counted feature.
Important:
Currently, only HTTP protocol is supported.