UGW rule filter group L7 rule service category group

User Profile Group L7 rule “L”

User Profile 1 CC “200”
APN “A” L7 info group
User Profile 2 CC “400” L7 info URL
L7 info cat_g
VRF

Rule bind 1 Priority 1 Category group “C”

User Profile Rule bind 2 Priority 2 Charge Property
Group
Rule bind 3 Priority 3
PPC (PCRF) Charge Property “CP”
Filter group “F” cbb up online up
Online/Offline offline
Filter 1 cbb up online down
Charging Filter 2 offline
UGW
Rule

Rules apply to both PCC and non-PCC subscribers. In PCC scenarios, the rules consist of
local predefined rules and PCRF-delivered predefined rules.
UGW
Category-group

A category group is a set of service properties, bandwidth control properties, charging

properties, and action properties.
UGW
Service-property

The service-property command is used to configure service properties. When you configure
the service-property command, a service can be bound to an APN. Among the services
configured by the UGW, the service IDs and priorities cannot be duplicate.
UGW
Category-property

Using the category-property command, you can configure a category property for matching
a bandwidth control policy. The bandwidth control function is performed according to the
bandwidth control policy corresponding to a specified category property, this is to associate
with filters in predefined rules for detecting and reporting application information.

The category-property command is used to configure a category property for matching a

bandwidth control policy, this is to associate with filters in predefined rules for detecting
and reporting application information.
UGW
Charge-property

Using the charge-property command, you can configure a charging property. A charging property specifies uplink
and downlink CBB IDs, which are used to charge uplink and downlink packets respectively.

This command is used to configure charging properties. Each charging property supports online charging, offline
charging, or hybrid charging.

Up to 10,001 charging properties can be configured on the entire UGW9811, including a global charging property.
Up to two uplink CBB IDs and up to two downlink CBB IDs for online or offline charging can be bound to a
charging property.
UGW
Action-property

Different actions can be taken for different services. The actions are configured with the action-list command. An action list
can be bound to an action property. If the packets that pass through the UGW match an action property, the uplink and
downlink packets are processed according to the configured action lists.
UGW
• User profile que tenga navegación a twitter RG 4 (capa 3) y whatsapp con RG 25 (capa
7)

rule r_facebook_he_free filter-group fg_header_facebook-test-free service-category-group

cg_facebook l7-rule l7r-facebook-he-free priority 975
rule-enrichment rule r_facebook_he_free header-enrichment enable
filter-group fg_header_facebook-test-free filter f-facebook-ip209
filter f-facebook-ip209 l34-protocol any server-ip 37.228.107.241 32
category-group cg_facebook charge-property cp_facebook
charge-property cp_facebook up-initial offline facebook_offline online facebook_online
down-initial offline facebook_offline online facebook_online
cbb-id facebook_offline charge-method offline rg 25 sid 25 metering free
cbb-id facebook_online charge-method online rg 25 default-quota volume-defaultquota
10000 time-defaultquota 5 metering free
UGW
l7-rule l7r-facebook-he-free protocol http l7-info-group l7ig-facebook-he-free priority 65535
l7-info-group l7ig-facebook-he-free l7-info l7i-he-fbk1 sequence 1
l7-info l7i-he-fbk1 url h.facebook.com/* l7-category-group cg_header_facebook2
category-group cg_header_facebook2 charge-property cp_facebook action-property ap_facebook
charge-property cp_facebook up-initial offline facebook_offline online facebook_online down-initial offline
facebook_offline online facebook_online
cbb-id facebook_offline charge-method offline rg 25 sid 25 metering free
cbb-id facebook_online charge-method online rg 25 default-quota volume-defaultquota 10000 time-
defaultquota 5 metering free
action-property ap_facebook up-initial up-action-list al_facebook down-action-list al_facebook
action-list al_facebook charge-point header-enrichment he-fb
header-enrichment he-fb msisdn msisdn encryption-algorithm rc4 password
%$%$JTzL21tn\V&k8(7>tiM!;\VM>MIT*D<{/Y6iYkOp<[[5\VP;LaZX*o^0vK5L.Y'xoQ[AVY;\R[K7.&{QU*[k9;AaI
]@-p;\VSbdo'yKoA,P0QtH_pBN@;\V_j&"#4If8##y{%TQi!>q3\Vd;@fVfWT>'t:-
c,E$]d]/NVk;\=aBLHhN|xQZN82D^5cM>%;\V,l839e33c##S9d48:Q-
#;\V};kuU8*Ei9@+JLzN29>}N\V%;L&P]K+dyVAUD8]DE~mE6V&;\Vv1U4^7%p-
Qy"N"yX;dJ5;\V)!m;!N@ZGS}35$DVh%ZY;\V:F*eL7XrGVRBVpEXppu!Y\V5;1Y'gC=M}xCgfjh&%GY'FV:;\+C8f1
&g$U%'^;y3Et$)7G;\V%$%$
header-enrichment he-fb imsi imsi encryption-algorithm rc4 password %$%$De|s!g_8L8rO'=<zv4[=g01-
*gYW%M>++M}zlHP%t]w3010gXl;D>dXU;PlIlg>U"^&D19g0n=^MW8l7r21:c^OeZjD=Pg01Y.SZCW>GDAk$@KV
M4Ro;g01~m%rPQ(L~_VSv=06i'm,201DgrcSx'Ky<8OM=M)K@][`+1Kg0tE%hL4[k[=D4o^W5BmWUbg01_I'!BBp$~
@iEpc6kJSX3g01]Z=e;&j%#m~<sZ,#g*G4-01bg6hbgKjEca:#T;a=4]}s(1cg0#r>~0HehlV_^I=Icca2;rg01Z=V1D7)jU9y-
%FX;<m/1g01wFx7b=ECJT.01O&+&4%.*01rgh~_H,=}NlF!Z2s0Vt9XI1wg09/)q2!W~/;P,_E7`88N.'g01%$%$
PCC
PCC refers to policy and charging control. The PCRF NE is introduced. It
delivers PCC rules, including policies and charging information, to the
GGSN/PGW.
Operators impose higher requirements on service awareness, control, and
charging of the packet networks. The PCC functions can meet the
requirements of operators.
The PCC architecture on the GGSN/PGW can implement service-level QoS
control and charging, and dynamic adjustment of policies.
PCC
PCC
Gx interface

• It is located between the Policy and Charging Rules Function (PCRF) and the
Policy and Charging Enforcement Function (PCEF).

• It is used for provisioning and removal of PCC rules from the PCRF to the
PCEF and the transmission of traffic plane events from the PCEF to the PCRF.

• It can be used for charging control, policy control or both by applying AVPs
relevant to the application.

• It can also be used for application's traffic detection and control.

PCC
Networking model of the dynamic PCC policy
PCC
Networking model of the static PCC policy
PCC
Trigger
Condition
Rule 1 group 1

Policy Condition
Service Rule 2 group 2

Condition
Rule 3
group 3
PCC
PCC Rule

A PCC rule, which is called rule on the UPCC, is a set of parameters for
controlling service policies and charging policies. A PCC rule name must be
unique in an IP-CAN session. A PCC rule includes a rule name, quality of service
(QoS) parameters, charging parameters, charging identifier (RG/SID),
precedence, and service flow filter.
PCC
PCC Rule

Classification

• Dynamic PCC rules.

Dynamically provisioned by the PCRF to the PCEF via the Gx interface. These PCC rules
may be either predefined or dynamically generated in the PCRF. Dynamic PCC rules can
be installed, modified and removed at any time.

• Predefined PCC rules

Preconfigured in the PCEF. Predefined PCC rules can be activated or deactivated by the.
PCRF at any time. Predefined PCC rules within the PCEF may be grouped allowing the
PCRF to dynamically activate a set of PCC rules over the Gx reference point.
The operator can define a predefined PCC rule, to be activated by the PCEF. Such a
predefined rule is not explicitly known in the PCRF.
PCC
PCC Rule

Operations on PCC Rules

• For dynamic PCC rules, the following operations are available:

• Installation: to provision a PCC rules that has not been already provisioned.
• Modification: to modify a PCC rule already installed.
• Removal: to remove a PCC rule already installed.

• For predefined PCC rules, the following operations are available:

• Activation: to allow the PCC rule being active.
• Deactivation: to disallow the PCC rule.
PCC
Condition Group

A condition group consists of multiple conditions that have been configured with
object attributes. When you configure a rule, you need to
associate condition groups with the rule. When condition groups associated with
the rule are met, actions in the action group associated with the rule are
performed.
PCC
Condition Group

Purpose

• Detects packets that belong to a service flow.

-The service flow filters in the PCC rule are used for selecting downlink IP-CAN bearers.
-The service flow filters in the PCC rule are used for the enforcement so that uplink IP
flows are transported in the correct IP-CAN bearer.

• Identifies the service to which a service flow belongs.

• Provides applicable charging parameters for a service flow.

• Provides policy control for a service flow

PCC
Action Group

An action group consists of multiple actions. The actions are logically divided
into different groups to facilitate management.
When an event defined by the trigger occurs, all the rules triggered by the event
are enforced according to their priorities. In this case, the UPCC sends
the actions contained in an action group under the dynamic rules to the PCEF.
Therefore, you must specify an action group when configuring a dynamic rule.
PCC
Object

An object is an instance assigned with certain attributes. By default, the system

provides ten objects:

• Subscriber
• Subscription
• IP Session
• Application Session
• System
• Account
• Quota
• Accumulation
• Access Node
• Sub Segment.
PCC
Object

An object and its attributes are used to define a condition or to assign values to a
condition or an action element. Therefore, you need to select an object when you
configure a condition group or an action group. If default object attributes cannot
meet the configuration requirements, you must add object attributes as required.
Unless otherwise specified, retain the default object attribute.
PCC
Trigger

A trigger defines the decision point of the UPCC. The UPCC determines the
subsequent action or the policy to be delivered based on the trigger.

When configuring policies, you can use the triggers defined in the dictionary.
The UPCC provides multiple default triggers. If default triggers cannot meet the
actual requirements, you can add new triggers
PCC
Action

An action is an operation or a group of operations delivered by the Unified Policy and

Charging Controller (UPCC) to the policy and charging enforcement function (PCEF)
after a certain trigger is invoked. After an action is invoked, the PCEF executes the
operation based on the configuration of the action. Actions can be added to action groups.

A maximum of 3,072 actions can be configured in the system.

PCC
The Gx interface is used for
interworking between the
GGSN and PCRF and runs the
Diameter protocol. The GGSN
functioning as the PCEF
interworks with the PCRF
through the Gx interface to
implement the PCC functions.
PCC
PCC
Call Flow Procedures:

(1) User equipment (Mobile Station) wishes to establish a data application (data access/internet), so it
requests to BTS/Node B.
(2) Node B forward its request to BSC/RNC.
(3) After all queries and procedure related to authentication, IMEI check & subscriber static
information(HLR), BSC/RNC forward subscriber request to SGSN. Some of the queries are performed by
SGSN.
(4) SGSN requests to GGSN for PDP context/data access.
(5) GGSN signals/query to PCRF (Policy & Charging Rule Function) about UE/MS data session
establishment over Gx interface.
(6) PCRF queries the Subscriber Profile Repository(SPR) for dynamic information of subscriber over Sp
interface.
(7) SPR sends all information about the subscriber policy/quota/rules to PCRF over Sp interface.
PCC
(8) PCRF installs policies for subscriber on GGSN (by PCEF) (per access point name[APN] and per bearer
quota grants).
(9) PCRF installs policies for application control on DPI and DPI begins tracking usage.
(10) Now data session is established and the subscriber starts consuming the data.
(11) Over Gy interface GGSN/PCEF talks to OCS (Online Charging System) for charging/credit.
(12) GGSN receives the information from OCS about balance/quota.
(13) GGSN signals policy server(PCRF) that device has exceeded data/quota grant or credit is low.
(14) Over Sy interface OCS also sends the credit limit report to PCRF.