# US 2013/0212265 A1 · Method and apparatus for traffic classification

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0212265 A1
- Document ID: US20130212265A1
- Status: Published application
- Kind: A1
- Application number: 13/809,242
- Filed: 2010-07-09
- Published: 2013-08-15
- Earliest claimed: 2010-07-09
- Assignees: Telefonaktiebolaget L M Ericsson (publ)
- Inventors: Jose Rubio Vidales; Alfonso de Jesus Perez Martinez; Luis Campo Giralte; Rodrigo Alvarez Dominguez
- Web page: https://patentgrep.com/patent/US20130212265A1

## CPC

- H04L 12/14: Charging, metering or billing arrangements specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
- H04L 12/1403: {Architecture for metering, charging or billing}
- H04L 43/028: by filtering
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 43/18: Protocol analysers
- H04L 63/0227: {Filtering policies (mail message filtering H04L51/212)}
- H04L 65/1016: IP multimedia subsystem [IMS]
- H04M 15/66: {Policy and charging system}
- H04W 12/121: Wireless intrusion detection systems [WIDS]; Wireless intrusion prevention systems [WIPS]
- H04L 63/1408: {by monitoring network traffic (monitoring network traffic per se H04L43/00)}
- H04M 2215/204: UMTS; GPRS
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A Policy and Charging Rules Function server (PCRF) of a Policy and Charging Control (PCC) Architecture for deciding control rules applicable to user traffic flows to be inspected, in accordance with applicable telecommunication protocols for each traffic flow, by a Policy and Charging Enforcement Function server with Deep Packet inspection capabilities (PCEF-DPI) of the PCC Architecture. The PCRF includes a database having a list of protocols used in the user tialYtc flow s The PCRF includes an interface unit which receives a query from the PCEF-DPI about applicable control rules for an IP Connectivity Access Network (IP-CAN) session established for a user at the PCEF-DPI The PCRF includes a processing unit which sends the applicable control rules for the IP-CAN session and the list of protocols through the interface unit to the PCEF-DPI. A Policy and Charging Enforcement Function, server having Deep Packet Inspection capabilities (PCEF-DPI) of a Policy and Charging Control (PCC) Architecture. A method of a Policy and Charging Rules Function server (PCRF) of a Policy and Charging Control (PCC) Architecture. A method of a Policy and Charging Enforcement Function server having Deep Packet inspection capabilities (PCFF-DPI) of a Policy and Charging Control (PCC) Architecture.

## Claims

### Claim 1

A Policy and Charging Rules Function server (PCRF) of a Policy and Charging Control (PCC) Architecture for deciding control rules applicable to user traffic flows to be inspected, in accordance with applicable telecommunication protocols for each traffic flow, by a Policy and Charging Enforcement Function server with Deep Packet Inspection capabilities (PCEF-DPI) of the PCC Architecture, the PCRF comprising:
a database having a list of protocols used in the user traffic flows;
an interface unit which receives a query from the PCEF-DPI about applicable control rules for an IP Connectivity Access Network (IP-CAN) session established for a user at the PCEF-DPI; and
a processing unit which sends the applicable control rules for the IP-CAN session and the list of protocols through the interface unit to the PCEF-DPI.

### Claim 2 (depends on 1)

The PCRF of claim 1 wherein protocols in the list of protocols were used during previous IP-CAN sessions for the user at the PCEF-DPI.

### Claim 3 (depends on 2)

The PCRF of claim 2 wherein the processing unit determines that the list of protocols used in the user traffic flows during the previous IP-CAN sessions for the user is available.

### Claim 4 (depends on 3)

The PCRF of claim 3 wherein the interface unit receives from the PCEF-DPI the list of protocols used in the user traffic flows during the IP-CAN session for the user.

### Claim 5 (depends on 4)

The PCRF of claim 4 wherein the processing unit stores the list of used protocols for the user in the database either per user, or as a global aggregate of all protocols in the PCEF-DPI deployment, as an aggregate per user subscription type or user profile, or as an aggregate per node and group per day and time.

### Claim 6

A Policy and Charging Enforcement Function server having Deep Packet inspection capabilities (PCEF-DPI) of a Policy and Charging Control (PCC) Architecture for inspecting User traffic flows in accordance with applicable telecommunication protocols for each traffic flow, and for installing control rules applicable to the user traffic flows, control rules received from a Policy and Charging Rules Function server (PCRF) of the PCC Architecture, the PCEF-DPI comprising:
a processing unit which establishes an IP Connectivity Access Network (IP-CAN) session for a user, and which is arranged for classifying IP packets in each user traffic flow according to configured protocol rules and for assigning the IP packets to particular service sessions;
an interface unit from which a query is sent to the PCRF about applicable control rules for the IP-CAN session, and which receives from the PCRF the applicable control rules for the IP-CAN session along with a list of protocols; and
a DPI device for inspecting user traffic flows in accordance with applicable telecommunication protocols for each traffic flow by trying first with those protocols in the list of protocols received from the PCRF.

### Claim 7 (depends on 6)

The PCEF-DPI of claim 6 wherein protocols in the list of protocols were used during previous IP-CAN sessions for the user.

### Claim 8 (depends on 7)

The PCEF-DPI of claim 7 wherein upon termination of each IP-CAN session for the user in the processing unit, an indication is sent to the PCRF from the interface unit indicating the termination of the IP-CAN session along with the list of protocols used in the user traffic flows during the IP-CAN session for the user.

### Claim 9 (depends on 8)

The PCEF-DPI of claim 8 wherein the DPI device classifies the traffic sequentially or in parallel.

### Claim 10 (depends on 9)

The PCEF-DPI of claim 9 wherein the DPI device uses a collection of rules for identifying a protocol to classify the traffic flow sequentially; and wherein they DPI device searches sequentially a plurality of rule sets, each of which has a collection of rules, for a match of one of its rules with the traffic flow to classify the traffic flow with the rule which matches the traffic flow.

### Claim 11 (depends on 9)

The PCEF-DPI of claim 9 wherein the DPI device includes a plurality of processing units, each of which executes in parallel on the traffic flow an algorithm different and independent from each other to identify a protocol to classify the traffic flow.

### Claim 12 (depends on 11)

The PCEF-DPI of claim 11 wherein each of the processing units produces a result on the traffic flow, and when results from the plurality of processing units of the DPI device are different, the list of protocols receive from the PCRF are used to reconcile the results and identify a correct protocol for the traffic flow.

### Claim 13

A method of a Policy and Charging Rules Function server (PCRF) of a Policy and Charging Control (PCC) Architecture for deciding control rules applicable to user traffic flows, to he inspected in accordance with applicable telecommunication protocols for each traffic flow, by a Policy and Charging Enforcement Function server with Deep Packet Inspection capabilities (PCEF-DPI) of the PCC Architecture, the method comprising the steps of:
receiving a query at an interface unit from the PCEF-DPI about applicable control rules for an IP Connectivity Access Network (IP-CAN) session established for a user at the PCEF-DPI; and
sending by a processing unit the applicable control rules for the IP-CAN session and a list of protocols used in the user traffic flows, which have been stored in a database, through the interface unit to the PCEF-DPI.

### Claim 14 (depends on 13)

The method of claim 13 including the step of adding in the list of protocols those protocols used during previous IP-CAN sessions for the user at the PCEF-DPI.

### Claim 15 (depends on 14)

The method of claim 14 including the step of the processing unit determining that the list of protocols used in the user traffic flows during the previous IP-CAN sessions for the user is available.

### Claim 16 (depends on 15)

The method of claim 15 including the step of the interface unit receiving from the PCEF-DPI the list of protocols used in the user traffic flows during the IP-CAN session for the user.

### Claim 17

A method of a Policy and Charging Enforcement Function server having Deep Packet Inspection capabilities (PCEF-DPI) of a Policy and Charging Control (PCC) Architecture for inspecting user traffic flows in accordance with applicable telecommunication protocols for each traffic flow, and for installing control rules applicable to the user traffic flows, control rules received from a Policy and Charging Rules Function server (PCRF) of the PCC Architecture, the method comprises the steps of:
establishing with a processing unit an :IP Connectivity Access Network (IP-CAN) session for a user;
sending from an interface unit a query to the PCRF about applicable control rules for the IP-CAN session;
receiving at the interface unit from the PCRF the applicable control rules for the IP-CAN session along with a list of protocols; and
inspecting with a DPI device user traffic flows in accordance with applicable telecommunication protocols for each traffic flow by trying first with those protocols in the list of protocols received from the PCRF.

### Claim 18 (depends on 17)

The method of claim 17 wherein upon termination of each IP-CAN session for the user in the processing unit, there is the step of sending an indication to the PCRF from the interface unit indicating the termination of the IP-CAN session along with the list of protocols used in the user traffic flows during the IP-CAN session fig the user.

### Claim 19 (depends on 18)

The method of claim 18 including the step of the DPI device classifying the traffic sequentially or in parallel.

### Claim 20 (depends on 19)

The method of claim 19 including the step of the DPI device using a collection of rules for identifying a protocol to classify the traffic sequentially.

### Claim 21 (depends on 20)

The method of claim 20 including the step of the DPI device searching sequentially a plurality of rule sets, each of which has a collection of rules, for a match of one of its rules with the traffic flow to classify the traffic flow with the rule which matches the traffic flow.

### Claim 22 (depends on 19)

The method of claim 19 wherein the DPI device includes a plurality of processing units, and including the step of each of the processing units executing in parallel on the traffic flow an algorithm different and independent from each other to identify a protocol to classify the traffic flow and the step of each of the processing units producing a result on the traffic flow, and where results from the plurality of processing units of the DPI device are different, using the list of protocols received from the PCR to reconcile the results and identify a correct protocol for the traffic flow.
