Introduction
License Requirements
Basic Features and Functionality
Shallow Packet Inspection
Deep Packet Inspection
Charging Subsystem
Traffic Analyzers
How ECS Works
Content Service Steering
IMPORTANT:
Protocol Analyzer
Protocol Analyzer Software Stack
Rule Definitions
IMPORTANT:
IMPORTANT:
Example
ruledef port-80
tcp
either-port = 80
rule-application routing
exit
ruledef bbc-news
http
url starts-with http://news.bbc.co.uk
rule-application charging
exit
ruledef catch-all
ip
any-match = TRUE
rule-application charging
exit
charging-action free-site
content-id 100
[ ... ]
exit
charging-action charge-by-duration
content-id 101
[ ... ]
exit
rulebase standard
[ ... ]
route
priority 1 ruledef
port-80 analyzer http
action
priority 101 ruledef
bbc-news charging-action free-site
action
priority 1000 ruledef
catch-all charging-action charge-by-duration
[ ... ]
exit
IMPORTANT:
Regular Expression Support for Rule Matching
| Regex Character | Description |
|---|---|
|
*
|
Zero or more characters
|
|
+
|
Zero or more repeated
instances of the token preceding the +
|
|
?
|
Match zero or one character
For example, if you want
to match the string “xyz<any one character>pqr”, you
must configure it as:
http host regex “xyz\077pqr”
In another example, if
you want to exactly match the string “url?resource=abc”,
you must configure it as:
http uri regex "url\\\077resource=abc"
Where, the first “\” (backslash)
is for the escaping of “?”, and then “\077” for specifying “?” to
the CLI.
|
|
\character
|
Escaped character
|
|
\?
|
Match the question mark
(\<ctrl-v>?) character
|
|
\+
|
Match the plus character
|
|
\*
|
Match the asterisk character
|
|
\a
|
Match the alert (ASCII
7) character
|
|
\b
|
Match the backspace (ASCII
8) character
|
|
\f
|
Match the form-feed (ASCII
12) character
|
|
\n
|
Match the new line (ASCII
10) character
|
|
\r
|
Match the carriage return
(ASCII 13) character
|
|
\t
|
Match the tab (ASCII 9)
character
|
|
\v
|
Match the vertical tab
(ASCII 11) character
|
|
\0
|
Match the null (ASCII
0) character
|
|
\\
|
Match the backslash character
|
|
Bracketed range [0-9]
|
Match any single character
from the range
|
|
A leading ^ in
a range
|
Do not match any in the
range. All other characters represent themselves.
|
|
.\x##
|
Any ASCII character as
specified in two-digit hex notation.
For example, \x5A
yields a “Z”.
|
|
|
|
Specify OR regular expression
operator
For example, if you want
to match the string pqr OR xyz, you must configure it as:
http host regex "pqr|xyz".
|
How it Works
Limitations and Dependencies
Group of Ruledefs
Rulebase
Rulebase List
ECS Deployment and Architecture
Enhanced Features and Functionality
IMPORTANT:
Session Control in ECS
Service Group QoS Feature
IMPORTANT:
IMPORTANT:
Configuration Overview
IMPORTANT:
IMPORTANT:
IMPORTANT:
IMPORTANT:
IMPORTANT:
IMPORTANT:
IMPORTANT:
Support for Service-based QoS
IMPORTANT:
Hierarchical Enforcement of QoS Parameters
Applying Flow-Rate
Monitoring Usage and Reporting Threshold Breaches
IMPORTANT:
FUP Enforcement for Dynamic Rules
Reporting Statistics and Usage to PCRF
Time and Flow-based Bearer Charging in ECS
Content Filtering Support
Content Filtering Server Group Support
In-line Content Filtering Support
DNS Snooping
IMPORTANT:
License Requirements
Bulk Statistics Support
How it Works
| Operator | Domain Name | IP Pool Pointer | Associated Ruledef | List of CNAMES |
|---|---|---|---|---|
| contains | gmail | ip-pool1 | domain_google | l.google.com |
| = | yahoo.com | ip-pool2 | domain_yahoo | . |
| starts-with | gmail | ip-pool3 | domain_start_gmail | . |
IMPORTANT:
Limitations and Dependencies
IP Readdressing
URL-based Re-addressing
Flow-based re-addressed connection
|
Step
|
Description
|
|---|---|
|
1—3
|
UE sets up a TCP connection
with the Origin Server (OS) by sending SYN. The TCP three-way handshake
takes place between UE and the Origin Server.
|
|
4
|
UE sends a HTTP request
to the OS which passes through the ASR5x00 L7 DPI rule-matching.
The URL of the request contains a known token, domain name, or a
token configured at ASR5x00 (in a ruledef).
|
|
5—8
|
ASR5x00 using L7 DPI
recognizes that the request is for New Server. ASR5x00 breaks/closes
the existing TCP connection with OS and establishes a new connection
with the New Server. TCP proxy is used to maintain TCP connection
between UE and ASR5x00.
|
|
9
|
ASR5x00 sends the HTTP
Request destined for Origin Server to New Server.
|
|
10
|
New Server sends back
the content in HTTP Response.
|
|
11
|
ASR5x00 proxies the
content back to the UE.
|
|
12
|
UE closes the TCP connection.
|
|
13
|
ASR5x00 closes the
connection with the New Server.
|
Post Processing
Tethering Detection
IMPORTANT:
IMPORTANT:
License Requirements
MUR/MURAL Support for Tethering Detection
/hd-raid/databases/ directory,
and loaded into configuration using CLI command.Tethering Detection Databases
Loading and Upgrading Tethering Detection Databases
/hd-raid/databases/
new-filename in
the designated directory path. ACS auto-detects the presence of
files available for upgrade daily. When a new version of a file
is found, the upgrade process is triggered. The upgrade can also
be forced by running the upgrade command in the CLI. On a successful
upgrade this file is renamed to filename.Session Recovery Support
Time-of-Day Activation/Deactivation of Rules
Transactional Rule Matching
Fastpath
IMPORTANT:
Feature Support
IMPORTANT:
|
Feature
|
Fastpath Optimized
|
Fastpath Eligible
|
Unsupported
|
|---|---|---|---|
|
Url Redirect
|
—
|
Yes
|
—
|
|
Charging Bucket Maintenance
|
—
|
Yes
|
—
|
|
ITC/BW control
|
—
|
Yes
|
—
|
|
Next Hop
|
—
|
Yes
|
—
|
|
TCP State based rules
|
—
|
Yes
|
—
|
|
Post-processing Rules
|
—
|
Yes
|
—
|
|
Flow limit - Discard/Redirect/Terminate-Flow/Terminate-Session
|
—
|
Yes
|
—
|
|
DSCP / IP TOS
|
—
|
Yes
|
—
|
|
ICSR
|
—
|
Yes
|
—
|
|
Session Recovery
|
—
|
Yes
|
—
|
|
Content Filtering(CF)
Static
|
—
|
—
|
Yes
|
|
CF Dynamic
|
—
|
—
|
Yes
|
|
Socket Migration
|
—
|
—
|
Yes
|
|
Blacklisting
|
—
|
Yes
|
—
|
|
ICAP
|
—
|
—
|
Yes
|
|
NAT
|
Yes
|
—
|
—
|
|
SFW
|
—
|
—
|
Yes
|
|
Video transrating
|
—
|
—
|
Yes
|
|
MVG CAE Readdressing
|
—
|
—
|
Yes
|
|
MVG Pacing
|
—
|
—
|
Yes
|
|
MVG Link Monitoring
|
—
|
—
|
Yes
|
|
MVG Header Insertion
|
—
|
—
|
Yes
|
|
P2P
|
—
|
—
|
Yes
|
|
SIP-ALG (App Layer Gateway)
|
—
|
—
|
Yes
|
|
H323 - ALG
|
—
|
—
|
Yes
|
|
DCCA
|
—
|
Yes
|
—
|
|
IPv6
|
Yes
|
—
|
—
|
|
Flow Readdress
|
—
|
—
|
Yes
|
|
Idle-timeout handling
|
Yes
|
—
|
—
|
|
Connection termination
(2MSL)
|
—
|
Yes
|
—
|
|
TCP Proxy
|
—
|
—
|
Yes
|
|
QOS
|
—
|
Yes
|
—
|
|
Lawful Intercept
|
—
|
Yes
|
—
|
|
HTTP/HTTPS
|
—
|
Yes
|
—
|
|
Non HTTP L7 protocols
|
—
|
—
|
Yes
|
|
NON UDP/TCP
flows
|
—
|
—
|
Yes
|
|
Tethering detection
|
—
|
—
|
Yes
|
|
Gx
|
—
|
Yes
|
—
|
|
Gy
|
—
|
Yes
|
—
|
|
HEE
|
—
|
Yes
|
—
|
|
Radius
|
—
|
Yes
|
—
|
|
Diameter
|
—
|
Yes
|
—
|
|
L4 checksum
|
—
|
—
|
Yes
|
|
TCP link monitoring
|
—
|
—
|
Yes
|
|
Header enrichment
|
—
|
—
|
Yes
|
|
Wimax Hotlining
|
—
|
—
|
Yes
|
|
Parsing Error Detection
Denial
|
—
|
—
|
Yes
|
|
IP only Byte Counting/Charging
|
Yes
|
—
|
—
|
|
DNS Snoop
|
—
|
Yes
|
—
|
|
ICMP
|
—
|
—
|
Yes
|
|
Data Record generation
|
—
|
Yes
|
—
|
|
Fair Usage
|
—
|
Yes
|
—
|
|
SPI
|
Yes
|
—
|
—
|
|
Packet Handling Feature
|
Fastpath Eligible
|
No Support
|
|---|---|---|
|
Valid UDP/TCP
in order pkts
|
Yes
|
—
|
|
OOO Packet handling
|
—
|
Yes
|
|
TCP Retransmissions
|
Yes
|
—
|
|
IP Fragmentation
|
—
|
Yes
|
|
TCP Handshaking
|
—
|
Yes
|
|
TCP Termination
|
—
|
Yes
|
|
First packet of Flow
|
—
|
Yes
|
|
Gx Rule Update
|
—
|
Yes
|
|
Invalid L3/L4
packet
|
Yes
|
—
|
|
Packet already queued
|
—
|
Yes
|
Limitations and Dependencies
Support for WebSocket Protocol Identification
How it Works
IMPORTANT:
URL Filtering
ruledef HTTP://AB-WAP.YZ
www
url starts-with HTTP://CDAB-SUBS.OPERA-MINI.NET/HTTP://AB-WAP.YZ
www
url starts-with HTTP://AB-WAP.YZ
multi-line-or
all-lines
exit
IMPORTANT:
Implementation of AES Encryption
TCP Proxy
Flow Admission Control
TCP Proxy Behavior and Limitations
Dynamic Disabling of TCP Proxy
Limitations for Dynamically Disabling TCP Proxy
X-Header Insertion and Encryption
IMPORTANT:
License Requirements
IMPORTANT:
TCP OOO Packets
Limitations to the Header Insertion and Encryption Features
Supported X-Headers
X-Header Enrichment Anti Spoofing
RAN Bandwidth Optimization
Selective TFT Suppression for Default Bearer
Accounting and Charging Interfaces
IMPORTANT:
GTPP Accounting
RADIUS Accounting and Credit Control
Diameter Accounting and Credit Control
Gx Interface Support
IMPORTANT:
Gy Interface Support
IMPORTANT:
Event Detail Records (EDRs)
EDR format
IMPORTANT:
Flow-overflow EDR
EDR Generation in Flow-end and Transaction Complete Scenarios with sn-volume Fields
edr-format edr1
rule-variable
http url priority 10
attribute
sn-volume-amt ip bytes uplink priority 500
attribute
sn-volume-amt ip bytes downlink priority 510
attribute
sn-volume-amt ip pkts uplink priority 520
attribute
sn-volume-amt ip pkts downlink priority 530
attribute
sn-app-protocol priority 1000
exit
edr-format edr2
rule-variable
http url priority 10
attribute
sn-app-protocol priority 1000
exit
edr-format edr3
rule-variable
http url priority 10
attribute
sn-volume-amt ip bytes uplink priority 500
attribute
sn-volume-amt ip bytes downlink priority 510
attribute
sn-app-protocol priority 1000
exit
Usage Detail Records (UDRs)
Charging Methods and Interfaces
Prepaid Credit Control
Postpaid
IMPORTANT:
Prepaid Billing in ECS
Credit Control Application (CCA) in ECS
How Credit Control Application (CCA) Works for Prepaid Billing
| Step No. | Description |
|---|---|
|
1
|
Subscriber session starts.
|
|
2
|
System sends request
to CCA for subscriber’s quota.
|
|
3
|
CCA sends request to
Data Warehouse (DW) credit quota for subscriber.
|
|
4
|
Credit Database in DW
sends pre-configured amount of usage limit from subscriber’s
quota to CCA. To reduce the need for multiple requests during subscriber’s
session configured amount of usage limit a major part of available
credit quota for subscriber is set.
|
|
5
|
CCA sends the amount
of quota required to fulfill the subscriber’s initial requirement
to the system.
|
|
6
|
When the initial amount
of quota runs out, system sends another request to the CCA and the CCA
sends another portion of available credit quota.
|
|
7
|
Subscriber session ends
after either quota exhausts for subscriber or subscriber terminates
the session.
|
|
8
|
CCA returns unused quota
to DW for update to subscribers Credit DB.
|
|
9
|
EDRs and UDRs are periodically
SFTPd from system memory to the ESS/external storage, if deployed
or to billing system directly as they are generated. Or, if configured,
pushed to the ESS/external storage at user-configurable
intervals.
|
|
10
|
The ESS/external
storage periodically sends records to the billing system or charging reporting
and analysis system.
|
IMPORTANT:
Postpaid Billing in ECS
How ECS Postpaid Billing Works
ECS Postpaid Billing in GPRS/UMTS Networks
| Step No. | Description |
|---|---|
|
1
|
The subscriber initiates
the session.
|
|
2
|
After subscriber authentication
and authorization, the system starts the session.
|
|
3
|
Data packet flow and
accounting starts.
|
|
4
|
System periodically
generates xDRs and stores them to the system memory.
|
|
5
|
System generates G-CDRs/eG-CDRs
and sends them to billing system as they are generated.
|
|
6
|
The billing system picks
up the CDR files periodically.
|
|
7
|
Subscriber session ends
after subscriber terminates the session.
|
|
8
|
The system stores the
last of the xDRs to the system memory and final xDRs are SFTPd from system
memory to ESS/external storage, if deployed or to billing
system directly.
|
|
9
|
System sends the last
of the G-CDRs/eG-CDRs to the billing system.
|
|
10
|
File Generation Utility,
FileGen in external storage periodically runs to generate G-CDRs/eG-CDRs
files for billing system and send them to the billing system.
|
|
11
|
The billing system picks
up the xDR files from the ESS/external storage periodically.
|
Postpaid Billing in CDMA-2000 Networks
| Step No. | Description |
|---|---|
|
1
|
The subscriber initiates
the session.
|
|
2
|
After subscriber authentication
and authorization, the system starts the session.
|
|
3
|
Data packet flow and
accounting starts.
|
|
4
|
System periodically
generates xDRs and stores them to the system memory.
|
|
5
|
EDRs/UDRs are
periodically SFTPd from system memory to ESS/external storage,
if deployed or to billing system directly as they are generated.
|
|
6
|
The billing system picks
up the xDR files from the ESS/external storage periodically.
|
|
7
|
Subscriber session ends
after subscriber terminates the session.
|
|
8
|
The system stores the
last of the xDRs to the system memory and final xDRs are SFTPd from system
memory to the ESS/external storage, if deployed or to billing
system directly.
|
|
9
|
The ESS/external
storage finally sends xDRs to the billing system.
|
External Storage System
IMPORTANT:
IMPORTANT:
Redundancy Support in ECS
Intra-chassis Session Recovery Interoperability
IMPORTANT:
Recovery from Task Failure
Inter-chassis Session Recovery Interoperability
Session Recovery Improvements
Impact on xDR File Naming
Impact on xDR File Content